Re: segmentation on reply
David Yitzchak Cohen said:
> On Fri, May 14, 2004 at 04:11:52AM EDT, Eric Smith wrote:
> > David Champion said:
> > > * On 2004.05.11, in <20040511101752.GA15495@xxxxxxxxxxxx>,
> > > * "Eric Smith" <es@xxxxxxxxxxxx> wrote:
>
> > The fault was not there previosuly, it now occurs every single time on
> > reply or group-reply. So I have to use another binary if i want to
> > execute this function.
> >
> Great, it sounds like you have a reproducible problem! Why don't you run
> the thing under gdb and see what you can find out about where it's dying?
> If you can send a backtrace (gdb command "bt" after you get the SIGSEGV),
> it may hint at the underlying problem.
>
A bit of a delay, but ...
Program received signal SIGSEGV, Segmentation fault.
0x0809fa4e in ci_send_message (flags=0, msg=0x83f9bf8, tempfile=0x0,
ctx=0x83a2738, cur=0x83d27a8) at send.c:1246
1246 send.c: No such file or directory.
in send.c
(gdb) bt
#0 0x0809fa4e in ci_send_message (flags=0, msg=0x83f9bf8, tempfile=0x0,
ctx=0x83a2738, cur=0x83d27a8) at send.c:1246
#1 0x08089e6f in mutt_pager (banner=0x0, fname=0xbfffda10 "8':\b¨'=\b",
flags=66, extra=0xbfffda10) at pager.c:2407
#2 0x08055a06 in mutt_display_message (cur=0x83d27a8) at commands.c:208
#3 0x080618d7 in mutt_index_menu () at curs_main.c:1342
#4 0x0807bbaf in main (argc=1, argv=0xbffff834, env=0x0) at main.c:977
(gdb)
and strace spake:
rt_sigaction(SIGINT, {0x80a4dd0, [], SA_RESTART|0x4000000}, NULL, 8) = 0
write(1, "\33[34h\33[?25h", 11) = 11
getpid() = 20627
unlink("/tmp/mutt-pepper-20627-21") = -1 ENOENT (No such file or directory)
open("/tmp/mutt-pepper-20627-21", O_RDWR|O_CREAT|O_EXCL, 0600) = 4
lstat64("/tmp/mutt-pepper-20627-21", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
fstat64(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
fcntl64(4, F_GETFL) = 0x2 (flags O_RDWR)
fstat64(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x4001c000
_llseek(4, 0, [0], SEEK_CUR) = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
any ideas gratefully received :)