[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sigprocmask.c appears to be incompatible w/ system headers

From: Bruno Haible
Subject: Re: sigprocmask.c appears to be incompatible w/ system headers
Date: Tue, 15 Mar 2011 11:05:13 +0100
User-agent: KMail/1.9.9

Godfrey, Keith wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x00002b630905ede8 in sigemptyset ()
>     from 
> /global/home/keith/software/octave-3.4.0/src/.libs/liboctinterp-3.4.0.so
> 2: x/10i $pc
> 0x2b630905ede8 <sigemptyset>:    callq  0x2b636c0ef3da
> 0x2b630905eded <sigemptyset+5>:    sub    (%rax),%eax
> 0x2b630905edef <sigemptyset+7>:    add    %dh,%al
> 0x2b630905edf1 <sigaction+1>:    in     (%dx),%eax

OK, so here you have an 8-byte area that defines a function 'sigemptyset'
and whose code starts with a 'call' instruction? That must be the PLT
(Procedure Linkage Table, [1]) in a state before the first 'sigemptyset'

Where does the 0x2b636c0ef3da point to? Look at the /proc/<pid>/maps file
of your process.

When you have a SIGSEGV in the PLT, there are two possible causes:
  - Either a problem with the shared libraries (maybe caused by some
    linker options, maybe by a linker bug),
  - Or you have general memory corruption that happens to hit the PLT.
    For detecting this case, please run your application under valgrind.

In either case, it's unrelated to gnulib. Please redirect followups to
Octave list again, and omit bug-gnulib.


[1] http://vxheavens.com/lib/vsc06.html
In memoriam Diego de Enzinas <http://en.wikipedia.org/wiki/Diego_de_Enzinas>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]