amd64 is missing aptitude-dbgsym (which is why I asked), but it appears to be created by gbp, so I've used that to build a debug package, which gives the following backtrace: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7b3feed in debVersioningSystem::CheckDep(char const*, int, char const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 #0 0x00007ffff7b3feed in debVersioningSystem::CheckDep(char const*, int, char const*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 #1 0x00005555557767c1 in infer_reason (pkg=..., reasons=std::set with 0 elements) at ../../../../src/generic/apt/infer_reason.cc:178 #2 0x0000555555650418 in reason_fragment (pkg=..., breakage=@0x7fffffffcf0e: false) at ../../src/reason_fragment.cc:447 #3 0x000055555564abcc in info_area_multiplex::set_package (this=0x555556b45fb0, pkg=..., ver=...) at ../../src/pkg_view.cc:454 #4 0x0000555555630a7a in sigc::internal::signal_emit0<void, sigc::nil>::emit (impl=0x555555b85090) at /usr/include/sigc++-2.0/sigc++/signal.h:790 #5 sigc::signal0<void, sigc::nil>::emit (this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/signal.h:2705 #6 sigc::signal0<void, sigc::nil>::operator() (this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/signal.h:2713 #7 pkg_tree_node::dispatch_key (this=this@entry=0x5555578f5990, k=..., owner=owner@entry=0x555555c99330) at ../../src/pkg_node.cc:86 #8 0x0000555555622066 in pkg_item::dispatch_key (this=0x5555578f5990, k=..., owner=0x555555c99330) at ../../src/pkg_item.cc:404 #9 0x00007ffff71d3fe5 in cwidget::widgets::tree::handle_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #10 0x000055555561641d in menu_tree::handle_key (this=this@entry=0x555555c99330, k=...) at ../../src/menu_tree.cc:430 #11 0x0000555555633973 in pkg_tree::handle_key (this=0x555555c99330, k=...) at ../../src/pkg_tree.cc:363 #12 0x00007ffff71d9ab3 in cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #13 0x00007ffff71c1da7 in cwidget::widgets::table::handle_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #14 0x00007ffff71d9ab3 in cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #15 0x00007ffff71ad4bb in cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #16 0x00007ffff71d9ab3 in cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #17 0x00007ffff71c1da7 in cwidget::widgets::table::handle_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #18 0x00007ffff71d9ab3 in cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #19 0x00007ffff71ad4bb in cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #20 0x00007ffff71d9ab3 in cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #21 0x00007ffff718e1f1 in cwidget::widgets::menubar::handle_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #22 0x00007ffff71d9ab3 in cwidget::widgets::widget::dispatch_key(cwidget::config::key const&) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #23 0x00007ffff715bdc9 in cwidget::toplevel::input_thread::get_input_event::dispatch() () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #24 0x00007ffff71536b5 in cwidget::toplevel::mainloop(int) () from /usr/lib/x86_64-linux-gnu/libcwidget.so.3 #25 0x000055555568c64a in ui_main () at ../../src/ui.cc:3075 #26 0x00005555555b50e0 in main (argc=<optimized out>, argv=<optimized out>) at ../../src/main.cc:1398
James On 17 May 2016 at 02:58, Axel Beckert <a...@debian.org> wrote: > Hi, > > Christoph Anton Mitterer wrote: > > On Mon, 2016-05-16 at 12:01 +1000, James Tocknell wrote: > > > Are there debug symbols for aptitude in unstable so I can provide a > > > backtrace, they only appear to be in testing? > > > > You probably need to use: > > https://wiki.debian.org/AutomaticDebugPackages > > Correct. > > Aptitude's debug package is now named aptitude-dbgsym. > > And yes, a backtrace would be nice as I can't reproduce the issue on > Sid amd64. > > Regards, Axel > -- > ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ > : :' : | Debian Developer, ftp.ch.debian.org Admin > `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 > `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE > -- Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It isn't good enough for Tim Berners-Lee <http://opendotdotdot.blogspot.com/2010/04/rms-and-tim-berners-lee-separated-at.html>, and it isn't good enough for me either. For more information visit http://www.gnu.org/philosophy/no-word-attachments.html. Truly great madness cannot be achieved without significant intelligence. - Henrik Tikkanen If you're not messing with your sanity, you're not having fun. - James Tocknell In theory, there is no difference between theory and practice; In practice, there is.
