On 12 Oct 2005 at 9:49, Dan Gregory wrote: > I have checked the pax.log because I figured that it would be that, but > there is nothing in there. There doesn't appear to be a core file that > I could analyze and there are no errors reported to stdout when I run it > from the command line. It just disappears. > > $ xchat-2 > Segmentation fault > > I recompiled with -g and ran it through gdb and when the segv is thrown > the stack dump looks like:
run xchat-2 from within gdb, that will break at the moment of the segfault, then "x/8i $pc", "x/16x $sp", "info reg", "bt", etc. in any case, since it's not a SIGKILL, PaX is not acting on it per se. > #0 0x148046f6 in ?? () > #1 0x8e7d66bf in ?? () > #2 0x149f8af8 in ?? () > > Which looks a little strange since there isn't 1 line that has any > non-optimized code in it. you're probably missing a lot of debugging symbols throughout your system, adding "nostrip" to FEATURES is highly recommended. -- [email protected] mailing list
