Bug#553213: Backtraces
Hi Karl: On 12/17/2009 09:09:43 PM Thu, Karl O. Pinc wrote: [ snip ] I was definitely responding to messages with content. Sorry, I was imprecise--I meant that the object that Balsa uses to represent a message had a NULL value for the pointer to the object that represents the message content--quite different from having no content! I suspect a race in the 'which message is selected' code when a new message arrives and a reply button is pressed, but that's a guess. If the new message is inserted into a thread in which some messages are selected, that can result in a message being deselected, so there can be interactions between new mail arrival and message selection. But it's not obvious from the code how that could result in the NULL pointer problem. For now, the only fix that I see is what we have currently: issue a warning and continue without retrieving the message content. FWIW: the code to detect and warn about the issue, avoiding the crash, was installed in August last year, so the possibility of a NULL pointer was known back then. However, I don't recall seeing the warning, so possibly some other change in more recent Balsa has fixed the underlying problem. Best, Peter pgpYzzOH9wc1C.pgp Description: PGP signature
Bug#553213: Backtraces
On 12/18/2009 07:58:38 AM, Peter Bloomfield wrote: Hi Karl: On 12/17/2009 09:09:43 PM Thu, Karl O. Pinc wrote: FWIW: the code to detect and warn about the issue, avoiding the crash, was installed in August last year, so the possibility of a NULL pointer was known back then. However, I don't recall seeing the warning, so possibly some other change in more recent Balsa has fixed the underlying problem. Ok. Thanks. I guess I'll live with the problem for another couple of years until squeeze goes stable -- unless you guys want to put something on backports.org or fix it in the next point release. (hint hint ;-) Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#553213: Backtraces
I finally figured out how to use gdb with the balsa-dbg package. Here are two backtraces. The first is a crash when pressing the reply-to-all button. The second is from the first core dump I captured: the bts says I said this happened when pressing the reply button. In both cases I think a new message was coming in when I pressed the button. $ gdb /usr/lib/debug/usr/bin/balsa core GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/ gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. Core was generated by `balsa'. Program terminated with signal 11, Segmentation fault. [New process 9338] #0 bsm_finish_setup (bsmsg=0x92ebbe8, part=0x0) at sendmsg- window.c:4737 4737sendmsg-window.c: No such file or directory. in sendmsg-window.c (gdb) bt #0 bsm_finish_setup (bsmsg=0x92ebbe8, part=0x0) at sendmsg- window.c:4737 #1 0x080bcbf4 in sendmsg_window_reply (mailbox=0x8cdb070, msgno=3694, reply_type=SEND_REPLY_ALL) at sendmsg-window.c:4883 #2 0x0806cf7b in bndx_compose_foreach (index=0x8d1e018, send_type=SEND_REPLY_ALL) at balsa-index.c:1518 #3 0xb7703064 in ?? () #4 0x08d1e018 in ?? () #5 0x08ba0060 in ?? () #6 0x00090002 in ?? () #7 0xb7726678 in ?? () #8 0x08bb2008 in ?? () #9 0x08bb0460 in ?? () #10 0xbfbc4e68 in ?? () #11 0xb76f590b in ?? () #12 0x08bb2008 in ?? () #13 0x in ?? () (gdb) exit Undefined command: exit. Try help. (gdb) quit k...@mofo:~/tmp/balsadebug$ gdb /usr/lib/debug/usr/bin/balsa core core core-2009-11-25 k...@mofo:~/tmp/balsadebug$ gdb /usr/lib/debug/usr/bin/balsa core-2009-11-25 GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/ gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. Core was generated by `balsa'. Program terminated with signal 11, Segmentation fault. [New process 10277] #0 bsm_finish_setup (bsmsg=0x9919f40, part=0x0) at sendmsg- window.c:4737 4737sendmsg-window.c: No such file or directory. in sendmsg-window.c (gdb) bt #0 bsm_finish_setup (bsmsg=0x9919f40, part=0x0) at sendmsg- window.c:4737 #1 0x080bcbf4 in sendmsg_window_reply (mailbox=0x9775070, msgno=3544, reply_type=SEND_REPLY) at sendmsg-window.c:4883 #2 0x0806cf7b in bndx_compose_foreach (index=0x97b8010, send_type=SEND_REPLY) at balsa-index.c:1518 #3 0xb7660064 in ?? () #4 0x097b8010 in ?? () #5 0x0963a060 in ?? () #6 0x00090002 in ?? () #7 0xb7683678 in ?? () #8 0x0964c060 in ?? () #9 0x0964a420 in ?? () #10 0xbf884178 in ?? () #11 0xb765290b in ?? () #12 0x0964c060 in ?? () #13 0x in ?? () (gdb) Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#553213: Backtraces
Hi Karl! On 12/17/2009 12:17:06 PM Thu, Karl O. Pinc wrote: I finally figured out how to use gdb with the balsa-dbg package. Here are two backtraces. The first is a crash when pressing the reply-to-all button. The second is from the first core dump I captured: the bts says I said this happened when pressing the reply button. In both cases I think a new message was coming in when I pressed the button. Since version 2.3.27, Balsa has had code to avoid that crash. The cause was trying to reply to a message that for some reason had no content, which in general doesn't happen. I'm not sure that we fixed that problem, but if not, at least it no longer causes a crash. Best, Peter pgpnWrVcf1sPu.pgp Description: PGP signature
Bug#553213: Backtraces
On 12/17/2009 06:13:56 PM, Peter Bloomfield wrote: Hi Karl! On 12/17/2009 12:17:06 PM Thu, Karl O. Pinc wrote: I finally figured out how to use gdb with the balsa-dbg package. Here are two backtraces. The first is a crash when pressing the reply-to-all button. The second is from the first core dump I captured: the bts says I said this happened when pressing the reply button. In both cases I think a new message was coming in when I pressed the button. Since version 2.3.27, Balsa has had code to avoid that crash. The cause was trying to reply to a message that for some reason had no content, which in general doesn't happen. I'm not sure that we fixed that problem, but if not, at least it no longer causes a crash. I was definitely responding to messages with content. I suspect a race in the 'which message is selected' code when a new message arrives and a reply button is pressed, but that's a guess. Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
