|
From: Tom H. <to...@co...> - 2005-11-12 18:44:16
|
In message <2a2...@ma...>
Paul Pluzhnikov <ppl...@gm...> wrote:
> On 11/12/05, Tom Hughes <to...@co...> wrote:
>
> > Actually that address does look about right for the stack we
> > allocate - it's slightly higher on my machine but not much.
> >
> > Can you run with --trace-signals=yes and see what it says?
>
> $ /usr/local/valgrind-3.0.svn/bin/valgrind -q --trace-signals=yes ./a.out
> --30170-- Max kernel-supported signal is 64
> --30170-- signal 11 arrived ... si_code=196609, EIP=0x4EACC1EC,
> eip=0x477DC95
> --30170-- SIGSEGV: si_code=196609 faultaddr=0xFEF88EC0 tid=1 ESP=0xFEF88EC0
> seg=0xFE78A000-0xFEF88FFF
The si_code value is bogus (0x30001) so it doesn't realise it
needs to extend the stack. This is the bug we discussed on the
developer list last night but we thought it was a ppc specific
bug. Obviously it affects all 2.4 kernels of a certain vintage.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|