Control: tags -1 + moreinfo
Hi Bjarni and Paul,
2015-12-28 02:25 Paul Wise:
On Mon, 28 Dec 2015 01:57:25 +0000 Bjarni Ingi Gislason wrote:
aptitude changelog apt ...
Does this always produce the same outcome?
Output was "Illegal instruction" with a return value of 132.
...
Architecture: i386 (i586)
There are some things that would help the aptitude maintainers figure
out what the problem is:
Send the output of this command:
cat /proc/cpuinfo
Enable the debug repo, install debug symbols, gdb and make a backtrace:
Create this file:
/etc/apt/sources.list.d/04-debian-debug.sources
Put this line in it:
deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main
Update the apt cache:
sudo apt-get update
Install the gdb debugger and debug symbols:
sudo apt-get install gdb aptitude-dbg libapt-pkg5.0-dbgsym libboost1.58-dbg
libc6-dbg libncursesw5-dbg libgcc1-dbg libsqlite3-0-dbg libstdc++6-5-dbg
libtinfo5-dbg libxapian22v5-dbg
Run the debugger and get a crash trace:
gdb -batch -n -ex 'set height 0' -ex run -ex bt -ex 'thread apply all bt full'
--args aptitude changelog apt
As Paul says it would be interesting to know about this, to know exactly
what's causing the program to abort. I don't have access to machines
with i386+unstable right now.
This looks like a case of miscompilation of some package (e.g. the
compiler using wrong machine code).
If the package being miscompiled was aptitude itself, it would probably
abort in many other places, not only with the "changelog" operation --
which is a minuscule part of aptitude. But one never knows, so it would
be good to pin-point which library or code-path is causing this.
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
