The symbols are definitely present on my system. When I step through the execution, I can see where it is crashing inside the pthread library. The last thing it does is join with one thread that was previously spawned.
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f650debe720 (LWP 3784)] 0x00007f650c5f7d7c in pthread_join (threadid=190969600, thread_return=0x0) at pthread_join.c:46 On Sun, Oct 30, 2011 at 1:56 AM, Chow Loong Jin <hyper...@ubuntu.com> wrote: > On 30/10/2011 06:22, Dallas Clement wrote: >> That certainly makes sense. I'm still not seeing the symbols though. >> My kernel log show that the segfault came from the pthreads library, >> yet when I load the core file into gdb, I'm not seeing any symbols. >> >> (gdb) bt >> #0 0x00007f04e3102d7c in ?? () >> #1 0x00007f04e3e73a60 in ?? () >> #2 0x00007f04e47db695 in ?? () >> #3 0xffffffffe212a700 in ?? () >> #4 0x00007f04e3e73a60 in ?? () >> #5 0x0000000000000000 in ?? () >> >> Got any other ideas for me to try? > > You need to load the core file, *and* the program. Something like... > $ gdb -c $corefile $path_to_program > > -- > Kind regards, > Loong Jin > > -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cae9dzuq6wsjrsqrh5yrq0m_fadsjlkuzzqeemd_ydspok4o...@mail.gmail.com
