"aptitude changelog heroes" crashes

Bug #57326 reported by Vassilis Pandis
2
Affects Status Importance Assigned to Milestone
aptitude (Ubuntu)
Fix Released
Medium
Michael Vogt

Bug Description

On current edgy with aptitude 0.4.1-1.1ubuntu3, |"aptitude changelog
heroes" crashes. This is on x86.

pandis@pandis-laptop:~$ gdb aptitude
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run changelog heroes
Starting program: /usr/bin/aptitude changelog heroes
[Thread debugging using libthread_db enabled]
[New Thread -1212385616 (LWP 14548)]
[New Thread -1254208608 (LWP 14552)]
No candidate version found for heroes

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1212385616 (LWP 14548)]
cmdline_do_download (m=0x0) at cmdline_util.cc:168
168 if(!m->prepare(progress, *log.get(), log.get()))
(gdb) bt
#0 cmdline_do_download (m=0x0) at cmdline_util.cc:168
#1 0x081293da in do_cmdline_changelog (packages=@0xbfeea478) at cmdline_changelog.cc:257
#2 0x08129f30 in cmdline_changelog (argc=2, argv=0xbfeea768) at cmdline_changelog.cc:342
#3 0x08053e52 in main (argc=2, argv=0xbfeea764) at main.cc:489
(gdb) bt thread apply all
No symbol "thread" in current context.
(gdb) thread apply all bt

Thread 2 (Thread -1254208608 (LWP 14552)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7e1dfde in __lll_mutex_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7e1945a in _L_mutex_lock_1239 () from /lib/tls/i686/cmov/libpthread.so.0
#3 0xb53e44b0 in ?? ()
#4 0x00000000 in ?? ()

Thread 1 (Thread -1212385616 (LWP 14548)):
#0 cmdline_do_download (m=0x0) at cmdline_util.cc:168
#1 0x081293da in do_cmdline_changelog (packages=@0xbfeea478) at cmdline_changelog.cc:257
#2 0x08129f30 in cmdline_changelog (argc=2, argv=0xbfeea768) at cmdline_changelog.cc:342
#3 0x08053e52 in main (argc=2, argv=0xbfeea764) at main.cc:489
(gdb)

Related branches

Changed in aptitude:
importance: Untriaged → Medium
Revision history for this message
Simon Law (sfllaw) wrote :

That null pointer is obviously a bug.

Changed in aptitude:
status: Unconfirmed → Confirmed
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

I commited a patch to the ubuntu patckage and will fix it with next upload (and send the patch upstream).

Cheers,
 Michael

Changed in aptitude:
assignee: nobody → mvo
status: Confirmed → Fix Committed
Michael Vogt (mvo)
Changed in aptitude:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.