On Tue, May 18, 2004 at 11:04:46AM +0200, Juraj Bednar wrote: > Running dpkg straight from gdb: > > (gdb) run -i /var/cache/apt/archives/libnewt0.51_0.51.6-3_i386.deb > Starting program: /usr/bin/dpkg -i /var/cache/apt/archives/libnewt0.51_0.51.6-3_i386.deb > (no debugging symbols found)...(no debugging symbols found)...(no > debugging symbols found)... > (Reading database ... 26414 files and directories currently installed.) > Preparing to replace libnewt0.51 0.51.4-23 (using > .../libnewt0.51_0.51.6-3_i386.deb) ... > Unpacking replacement libnewt0.51 ... > (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... > Program terminated with signal SIGSEGV, Segmentation fault. > The program no longer exists. > > > (of course I can not do stack trace at this point, gdb says "No stack"). This should not be an "of course". This should not happen at all. How did this happen? You *should* be looking at a process frozen in T state, and be able to examine its stack with gdb at this point. Something is very odd here, and it's probably with your system. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -><- |
Attachment:
signature.asc
Description: Digital signature