Hello, > If you run without the -D does it still segfault? of course, I added -D just after I found it segfaults so it has some debugging output. > How much memory does your system have? 256MB + 1GB swap, when doing it, at least 40MB of memory is free and 900MB of swap space is free too. > Run after "ulimit -c unlimited", then using gdb and the resulting core > file can you send trace information? it does not dump core even after this command, I really don't know why. 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"). Juraj.
Attachment:
pgpUAEOXbMUnU.pgp
Description: PGP signature