Re: segfault causes system freeze
Hi There, Just an update on this issue. My machine just froze while NOT using mutt. I was in the terminal, typed the few first letters of a command, then hit and the machine froze. So to my big despair, it is not a mutt issue; I bet it's more a hardware issue, and that is bad. Have a nice day, Steve
Re: segfault causes system freeze
Le 23-11-2018, à 09:52:59 -0800, Kevin J. McCarthy a écrit : On Fri, Nov 23, 2018 at 07:30:00AM +0100, steve wrote: I think it's when I just go back from editing with vim to the pager. Also, are you using IMAP? Yes I do via offlineimap. It sounds like this may be triggered by offlineimap updating while you are in the middle of composing the message. NeoMutt checks for new mail in the pager too, but it looks like in 1.7.2 they botched the redraw-data updates, setting "max" before the index data structures were updated. It looks like this is fixed in the latest version link posted by Jörg. However, I think it would be tricky to get Debian/Ubuntu to patch this for a non-security issue. Your best bet would be to update. You mean compiling myself the last git version? I'd like to stick to Debian's version if possible. Another workaround might be turning off $pager_index_lines. Currently it's set to pager_index_lines=9 which I find useful. Since the problem hasn't occurred for the 4 last days, I'll wait a bit before your suggested workaround. Thanks a lot for your help. Have a nice weekend. Steve
Re: segfault causes system freeze
Le 23-11-2018, à 21:31:25 +0100, Jörg Sommer a écrit : steve hat am Do 22. Nov, 16:19 (+0100) geschrieben: Le 22-11-2018, à 16:09:50 +0100, Jörg Sommer a écrit : > > #0 0x5592c9a59c68 in index_make_entry (s=0x7fff20afb090 "", l=1024, menu=, num=) at ../../curs_main.c:300 > > h = 0x5592cbef1670 > > flag = (MUTT_FORMAT_TREE | MUTT_FORMAT_MAKEPRINT | MUTT_FORMAT_ARROWCURSOR | MUTT_FORMAT_INDEX) > > edgemsgno = 40 > > reverse = > > tmp = > > This is here > https://sources.debian.org/src/mutt/1.7.2-1+deb9u1/curs_main.c/#L300 and > in the current version (of neomutt) here > https://salsa.debian.org/mutt-team/neomutt/blob/master/curs_main.c#L550 > > The best would be to create a bug report and if you don't care too much, I > can send the developer the coredump in a *private* mail. He might dig out > something more. That would be really nice of you. But does it mean I also have to open a bug report? I think that's the best to do. Do you have reportbug installed? This eases the creation of bug reports. Yes I have. Problem, it asks me if I really want to report a bug since my version is said to be outdated. Moreover, looking at the already reported bug, some might be the same, or very close, as mine. And other problem, I can not reproduce it at will. So not enough information yet. And as Kevin said, it might be related to offlineimap. With therefore wait a bit and try to collect more info before opening a bug.
Re: segfault causes system freeze
steve hat am Do 22. Nov, 16:19 (+0100) geschrieben: > Le 22-11-2018, à 16:09:50 +0100, Jörg Sommer a écrit : > > > > #0 0x5592c9a59c68 in index_make_entry (s=0x7fff20afb090 "", l=1024, > > > menu=, num=) at ../../curs_main.c:300 > > > h = 0x5592cbef1670 > > > flag = (MUTT_FORMAT_TREE | MUTT_FORMAT_MAKEPRINT | > > > MUTT_FORMAT_ARROWCURSOR | MUTT_FORMAT_INDEX) > > > edgemsgno = 40 > > > reverse = > > > tmp = > > > > This is here > > https://sources.debian.org/src/mutt/1.7.2-1+deb9u1/curs_main.c/#L300 and > > in the current version (of neomutt) here > > https://salsa.debian.org/mutt-team/neomutt/blob/master/curs_main.c#L550 > > > > The best would be to create a bug report and if you don't care too much, I > > can send the developer the coredump in a *private* mail. He might dig out > > something more. > > That would be really nice of you. But does it mean I also have to open a > bug report? I think that's the best to do. Do you have reportbug installed? This eases the creation of bug reports. Kind regards Jörg -- „Dass man etwas durchdringen kann, wenn man es durchschaut hat, ist der Irrtum der Fliege an der Fensterscheibe.“ (Nietzsche) signature.asc Description: PGP signature
Re: segfault causes system freeze
On Fri, Nov 23, 2018 at 07:30:00AM +0100, steve wrote: I think it's when I just go back from editing with vim to the pager. Also, are you using IMAP? Yes I do via offlineimap. It sounds like this may be triggered by offlineimap updating while you are in the middle of composing the message. NeoMutt checks for new mail in the pager too, but it looks like in 1.7.2 they botched the redraw-data updates, setting "max" before the index data structures were updated. It looks like this is fixed in the latest version link posted by Jörg. However, I think it would be tricky to get Debian/Ubuntu to patch this for a non-security issue. Your best bet would be to update. Another workaround might be turning off $pager_index_lines. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: segfault causes system freeze
Hi Kevin, Le 22-11-2018, à 17:48:14 -0800, Kevin J. McCarthy a écrit : On Thu, Nov 22, 2018 at 04:19:43PM +0100, steve wrote: I would guess that one of the thread chains is broken. Does the crash happen everytime in the same mailbox? That's a question I also asked myself. I don't know for now. I'll have to investigate a bit more. The problem is that it doesn't happen so often. I'm not familiar with the changes NeoMutt may have made to their version, but if you can duplicate with a recent Mutt, I may be able investigate further. I'm trying to duplicate but no occurrence for the last three days. However, I do have a couple questions that may (or may not) be relevant. Do you always see the crashes in the pager, or is it random? I think it's when I just go back from editing with vim to the pager. Also, are you using IMAP? Yes I do via offlineimap. Thank you. Best, Steve
Re: segfault causes system freeze
On Thu, Nov 22, 2018 at 04:19:43PM +0100, steve wrote: I would guess that one of the thread chains is broken. Does the crash happen everytime in the same mailbox? That's a question I also asked myself. I don't know for now. I'll have to investigate a bit more. The problem is that it doesn't happen so often. I'm not familiar with the changes NeoMutt may have made to their version, but if you can duplicate with a recent Mutt, I may be able investigate further. However, I do have a couple questions that may (or may not) be relevant. Do you always see the crashes in the pager, or is it random? Also, are you using IMAP? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: segfault causes system freeze
Le 22-11-2018, à 07:35:08 -0800, Felix Finch a écrit : On 20181122, Nathan Stratton Treadway wrote: On Thu, Nov 22, 2018 at 07:51:48 +0100, steve wrote: > No. If switch to another console, and launch a 'ls' for example, the > cursor goes to the line and then nothing happens. Ctlr-x doesn't do > anything. Opening a new one and launching htop for example freeze the > terminal. But was it funny, is that I can firefox still works as > expected. At this stage I normally shutdown the computer physically. Hmmm, interesting... the system is not truely locked up, but perhaps it's now unable to launch new processes, or something like that. (It would be interesting to know if an instance of "htop" running on another console continues keep running even after the segfault, for example.) I have seen screen (the command!) leave the tty in a very confused state, where it thinks the usable area is less than full size, such that scrolls for instance only operate on a subsection. Try "stty sane^J". If using screen or tmux, try ^D to exit and ^A^C or ^B^C to open a new session. Sometimes I have cat'd a binary file by mistake and left the tty so confused that I have to log out and back in. Do you have ssh set up, and do you have a second computer you can ssh in from? Try ssh on that other compputer just to have an independent tty available, and see if it behaves normally after mutt locks things up. I of course tried sshing the machine, but after password prompt, nothing happened (I waited 3 minutes or so). One problem with power cycling is the file system recovery after a power loss; you can avoid that by starting a root sleep+reboot in the background, which you abort if you don't need it, otherwise let it reboot for you if possible. sudo su - (sleep 300; reboot) & ^D su was blocked too. In fact opening any new terminal left me with no possibility to enter commands. and on to your mutt crashing. If mutt locks up, wait 5 minutes and see it it reboots on its own. If not, power cycle. You can use "shutdown -h now" instead of reboot if you want. Doesn't work either. If nutt locks up but the other suggestions leave you with a working tty, or if mutt doesn't lock up, you have 5 minutes to "sudo su -" again and kill the sleep+reboot job. Adjust the 300 second sleep to your patience; how quickly can you make mutt lockup? How often do you wnat to kill and restart that sleeper, and how long do you want to wait for it to reboot after a lockup? You can start similar background jobs to report interesting data and wait a few minutes, then on reboot, check its logged output. while :; do date >>~/loggy; sleep 10; done & You may need a nohup in there; try logging out with that running and make sure it remans running. If mutt locks up, not the exact time, wiat 5 minutes, power cycle, and check ~/loggy to see how long it kept logging. Thanks Felix for this lengthy help, but it looks a bit too much for me of an action. I'm getting too old for this kind of fun ;) That's why I love Debian, it's so rock solid and stable that I don't need to go in that kind of things (any more). Best, Steve
Re: segfault causes system freeze
On 20181122, Felix Finch wrote: > Try "stty sane^J". I should have clarified; someimes the tty gets in such a state that it doesn't echo any characters nor recognize ; you have to type this on blind faith it's getting through to the shell, and the ^J works when doesn't. You may need a ^C or ^Z beforehand to abort any existing command. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & wood chipper / fe...@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
Re: segfault causes system freeze
On 20181122, Nathan Stratton Treadway wrote: > On Thu, Nov 22, 2018 at 07:51:48 +0100, steve wrote: > > No. If switch to another console, and launch a 'ls' for example, the > > cursor goes to the line and then nothing happens. Ctlr-x doesn't do > > anything. Opening a new one and launching htop for example freeze the > > terminal. But was it funny, is that I can firefox still works as > > expected. At this stage I normally shutdown the computer physically. > > Hmmm, interesting... the system is not truely locked up, but perhaps > it's now unable to launch new processes, or something like that. (It > would be interesting to know if an instance of "htop" running on another > console continues keep running even after the segfault, for example.) I have seen screen (the command!) leave the tty in a very confused state, where it thinks the usable area is less than full size, such that scrolls for instance only operate on a subsection. Try "stty sane^J". If using screen or tmux, try ^D to exit and ^A^C or ^B^C to open a new session. Sometimes I have cat'd a binary file by mistake and left the tty so confused that I have to log out and back in. Do you have ssh set up, and do you have a second computer you can ssh in from? Try ssh on that other compputer just to have an independent tty available, and see if it behaves normally after mutt locks things up. One problem with power cycling is the file system recovery after a power loss; you can avoid that by starting a root sleep+reboot in the background, which you abort if you don't need it, otherwise let it reboot for you if possible. sudo su - (sleep 300; reboot) & ^D and on to your mutt crashing. If mutt locks up, wait 5 minutes and see it it reboots on its own. If not, power cycle. You can use "shutdown -h now" instead of reboot if you want. If nutt locks up but the other suggestions leave you with a working tty, or if mutt doesn't lock up, you have 5 minutes to "sudo su -" again and kill the sleep+reboot job. Adjust the 300 second sleep to your patience; how quickly can you make mutt lockup? How often do you wnat to kill and restart that sleeper, and how long do you want to wait for it to reboot after a lockup? You can start similar background jobs to report interesting data and wait a few minutes, then on reboot, check its logged output. while :; do date >>~/loggy; sleep 10; done & You may need a nohup in there; try logging out with that running and make sure it remans running. If mutt locks up, not the exact time, wiat 5 minutes, power cycle, and check ~/loggy to see how long it kept logging. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & wood chipper / fe...@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
Re: segfault causes system freeze
Le 22-11-2018, à 16:09:50 +0100, Jörg Sommer a écrit : #0 0x5592c9a59c68 in index_make_entry (s=0x7fff20afb090 "", l=1024, menu=, num=) at ../../curs_main.c:300 h = 0x5592cbef1670 flag = (MUTT_FORMAT_TREE | MUTT_FORMAT_MAKEPRINT | MUTT_FORMAT_ARROWCURSOR | MUTT_FORMAT_INDEX) edgemsgno = 40 reverse = tmp = This is here https://sources.debian.org/src/mutt/1.7.2-1+deb9u1/curs_main.c/#L300 and in the current version (of neomutt) here https://salsa.debian.org/mutt-team/neomutt/blob/master/curs_main.c#L550 The best would be to create a bug report and if you don't care too much, I can send the developer the coredump in a *private* mail. He might dig out something more. That would be really nice of you. But does it mean I also have to open a bug report? I would guess that one of the thread chains is broken. Does the crash happen everytime in the same mailbox? That's a question I also asked myself. I don't know for now. I'll have to investigate a bit more. The problem is that it doesn't happen so often. Thank you very much for your help Best, Steve
Re: segfault causes system freeze
steve hat am Do 22. Nov, 15:45 (+0100) geschrieben: > Le 21-11-2018, à 23:10:51 +0100, Jörg Sommer a écrit : > > > > This does not tell me anything (I'm not a developer). Do you think I > > > should > > > open a bug report on the Debian BTS? > > > > Yes, this would be helpful. Do you have gdb installed? Can you run > > `coredumpctl debug` and run `bt full` on the gdb prompt? This output would > > be very helpful for the developer to see, what was the state before the > > crash. > > Ok, I attached the output of 'bt full' in gdb. Doesn't speak to me :) > > Thanks. > > Steve > > #0 0x5592c9a59c68 in index_make_entry (s=0x7fff20afb090 "", l=1024, > menu=, num=) at ../../curs_main.c:300 > h = 0x5592cbef1670 > flag = (MUTT_FORMAT_TREE | MUTT_FORMAT_MAKEPRINT | > MUTT_FORMAT_ARROWCURSOR | MUTT_FORMAT_INDEX) > edgemsgno = 40 > reverse = > tmp = This is here https://sources.debian.org/src/mutt/1.7.2-1+deb9u1/curs_main.c/#L300 and in the current version (of neomutt) here https://salsa.debian.org/mutt-team/neomutt/blob/master/curs_main.c#L550 The best would be to create a bug report and if you don't care too much, I can send the developer the coredump in a *private* mail. He might dig out something more. I would guess that one of the thread chains is broken. Does the crash happen everytime in the same mailbox? Jörg -- Damit das Mögliche entsteht, muß immer wieder das Unmögliche versucht werden. (Hermann Hesse) signature.asc Description: PGP signature
Re: segfault causes system freeze
Le 22-11-2018, à 02:09:46 -0500, Nathan Stratton Treadway a écrit : On Thu, Nov 22, 2018 at 07:51:48 +0100, steve wrote: No. If switch to another console, and launch a 'ls' for example, the cursor goes to the line and then nothing happens. Ctlr-x doesn't do anything. Opening a new one and launching htop for example freeze the terminal. But was it funny, is that I can firefox still works as expected. At this stage I normally shutdown the computer physically. Hmmm, interesting... the system is not truely locked up, but perhaps it's now unable to launch new processes, or something like that. (It would be interesting to know if an instance of "htop" running on another console continues keep running even after the segfault, for example.) I'll leave an htop running just in case. [...] No, nothing in syslog I think. (It might be worth double-checking to make sure -- if for example [Byour follow-on attempts to run "ls" and "htop" also show up as segfaults in the log, that would certainly tell you something.) Double checked and I'm pretty sure there is nothing else. Yes, I think it might be a hardware problem triggered by a mutt segfault. Still looking around. (The distinction may not matter in the end, but off hand I'd suspect the hardware fault [or whatever it is] is causing both the mutt segfault and the other symptoms you are seeing.) It's really only mutt (or neomutt…) that triggers the problem, no other program. Anyway, good luck tracking it down... Thank you, I hope I can succeed (with your and Jörg nice help). Best, Steve
Re: segfault causes system freeze
Le 21-11-2018, à 23:10:51 +0100, Jörg Sommer a écrit :
This does not tell me anything (I'm not a developer). Do you think I should
open a bug report on the Debian BTS?
Yes, this would be helpful. Do you have gdb installed? Can you run
`coredumpctl debug` and run `bt full` on the gdb prompt? This output would
be very helpful for the developer to see, what was the state before the
crash.
Ok, I attached the output of 'bt full' in gdb. Doesn't speak to me :)
Thanks.
Steve
#0 0x5592c9a59c68 in index_make_entry (s=0x7fff20afb090 "", l=1024,
menu=, num=) at ../../curs_main.c:300
h = 0x5592cbef1670
flag = (MUTT_FORMAT_TREE | MUTT_FORMAT_MAKEPRINT |
MUTT_FORMAT_ARROWCURSOR | MUTT_FORMAT_INDEX)
edgemsgno = 40
reverse =
tmp =
#1 0x5592c9a822bc in menu_redraw_index (menu=0x5592cbed50b0) at
../../menu.c:323
buf =
"\000\000\000\000\000\000\000\000p\231\353\060\000\177\000\000\377\377\377\377\000\000\000\000\065\000\000\000\000\000\000\000\000\261\257
\377\177\000\000@\341\370.\000\177\000\000\000\000\000\000\000\000\000\000\311\320\354\060\000\177\000\000\000\000\000\000\001\000\000\000\066\000\000\000\036\000\000\000
\261\257 \377\177\000\000
_\312\060\000\177\000\000\000\000\000\000\000\177\000\000\213?\355\060\000\177\000\000/home/st\036\001\254ɒU\000\000/INBOX/n\220\263\257
\377\177\000\000\b\262\257 \377\177", '\000' ,
"\002\327\300˒U\000\000\000\262\257
\377\177\000\000H\261\305˒U\000\000@\262\257 \377\177\000\000\210\261\257"...
i = 40
do_color =
attr = 2098432
#2 0x5592c9a90d3b in mutt_pager (banner=banner@entry=0x0,
fname=fname@entry=0x7fff20afc180
"/home/steve/.mutt/tmp/mutt-paros-1000-1678-17662420033214884750",
flags=, flags@entry=66,
extra=extra@entry=0x7fff20afc150) at ../../pager.c:1864
do_new_mail =
searchbuf = '\000'
buffer = "-*-NeoMutt: =prof/trex [Msgs:51 Inc:8 43M]---(threads/date)",
'-' , "(end)---", '\000'
helpstr = "e:Quitter -:PgPréc :PgSuiv v:Voir attach.
d:Effacer r:Répondre j:Suivant ?:Aide\000\000\000\003", '\000'
tmphelp = "e:Quitter -:PgPréc :PgSuiv v:Voir attach.
d:Effacer r:Répondre j:Suivant", '\000' ,
"\260g\355˒U\000\000@\344\370.\000\177\000\000\n\000\000\000\000\000\000\000|\203\355˒U\000\000\377\002\000\000\000\000\000\000\062\313\306."...
maxLine = 55
lastLine = 37
lineInfo = 0x5592cbed45f0
QuoteList = 0x0
i =
j =
ch =
rc = 103
hideQuoted =
q_level = 0
force_redraw = 0
lines =
curline =
topline = 0
oldtopline =
err =
first =
r =
wrapped =
searchctx =
redraw = 32
fp = 0x5592cbee43a0
last_pos = 3186
last_offset =
old_smart_wrap =
old_markers =
sb = {st_dev = 2305, st_ino = 3672769, st_nlink = 1, st_mode = 33152,
st_uid = 1000, st_gid = 1000, __pad0 = 0, st_rdev = 0, st_size = 3186,
st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1542825837,
tv_nsec = 471228302}, st_mtim = {tv_sec = 1542825837, tv_nsec = 519226284},
st_ctim = {tv_sec = 1542825837, tv_nsec = 519226284},
__glibc_reserved = {0, 0, 0}}
SearchRE = {buffer = 0x0, allocated = 0, used = 0, syntax = 0,
fastmap = 0xff00 ,
translate = 0xff ,
re_nsub = 2971003703785480807, can_be_null = 0, regs_allocated = 0,
fastmap_accurate = 0, no_sub = 0, not_bol = 1, not_eol = 0,
newline_anchor = 0}
SearchCompiled = 0
SearchFlag =
SearchBack =
has_types =
index_status_window = 0x5592cbee4b70
index_window = 0x5592cbed5050
pager_status_window = 0x5592cbed5070
pager_window = 0x5592cbed5090
index = 0x5592cbed50b0
indexlen =
indicator = 4
old_PagerIndexLines =
index_hint = 0
oldcount =
check =
followup_to =
#3 0x5592c9a4ea85 in mutt_display_message (cur=0x5592cbead5a0) at
../../commands.c:225
info = {ctx = 0x5592cbd45ea0, hdr = 0x5592cbead5a0, bdy = 0x0, fp =
0x0, idx = 0x0, idxlen = 0}
tempfile =
"/home/steve/.mutt/tmp/mutt-paros-1000-1678-17662420033214884750\000\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\000\000"...
buf =
"multipart/alternative\000\000\000\063\000\000\000\000\000\000\000\360¯
\377\177\000\000\250\227\353\060\000\177\000\000\020\000\000\000\000\000\000\000\311\320\354\060\000\177\000\000\000\000\000\000\001\000\000\000\066\000\000\000\036\000\000\000\020ï
\377\177\000\000
_\312\060\000\177\000\000\000\000\000\000\000\177\000\000\213?\355\060\000\1
Re: segfault causes system freeze
On Thu, Nov 22, 2018 at 07:51:48 +0100, steve wrote: > No. If switch to another console, and launch a 'ls' for example, the > cursor goes to the line and then nothing happens. Ctlr-x doesn't do > anything. Opening a new one and launching htop for example freeze the > terminal. But was it funny, is that I can firefox still works as > expected. At this stage I normally shutdown the computer physically. Hmmm, interesting... the system is not truely locked up, but perhaps it's now unable to launch new processes, or something like that. (It would be interesting to know if an instance of "htop" running on another console continues keep running even after the segfault, for example.) [...] > No, nothing in syslog I think. > (It might be worth double-checking to make sure -- if for example [Byour follow-on attempts to run "ls" and "htop" also show up as segfaults in the log, that would certainly tell you something.) > Yes, I think it might be a hardware problem triggered by a mutt > segfault. Still looking around. (The distinction may not matter in the end, but off hand I'd suspect the hardware fault [or whatever it is] is causing both the mutt segfault and the other symptoms you are seeing.) Anyway, good luck tracking it down... Nathan
Re: segfault causes system freeze
Le 21-11-2018, à 23:10:51 +0100, Jörg Sommer a écrit : steve hat am Mi 21. Nov, 19:50 (+0100) geschrieben: # coredumpctl info PID: 1678 (mutt) UID: 1000 (steve) GID: 1000 (steve) Signal: 11 (SEGV) Timestamp: Wed 2018-11-21 19:45:57 CET (17s ago) Command Line: mutt -y -n Executable: /usr/bin/mutt Control Group: /user.slice/user-1000.slice/session-3.scope Unit: session-3.scope Slice: user-1000.slice Session: 3 Owner UID: 1000 (steve) Boot ID: 75e02422e0584081937ef6fe13f1e8ba Machine ID: 63a22f7a1c2437b0703353c75343f80e Hostname: box.maison.mrs Storage: /var/lib/systemd/coredump/core.mutt.1000.75e02422e0584081937ef6fe13f1e8ba.1678.154282595700.lz4 Message: Process 1678 (mutt) of user 1000 dumped core. Stack trace of thread 1678: #0 0x5592c9a59c68 index_make_entry (mutt) #1 0x5592c9a822bc menu_redraw_index (mutt) #2 0x5592c9a90d3b mutt_pager (mutt) #3 0x5592c9a4ea85 mutt_display_message (mutt) #4 0x5592c9a5df9c mutt_index_menu (mutt) #5 0x5592c9a3ef16 main (mutt) #6 0x7f002ec182e1 __libc_start_main (libc.so.6) #7 0x5592c9a3ef8a _start (mutt) This does not tell me anything (I'm not a developer). Do you think I should open a bug report on the Debian BTS? Yes, this would be helpful. Do you have gdb installed? Can you run `coredumpctl debug` and run `bt full` on the gdb prompt? This output would be very helpful for the developer to see, what was the state before the crash. I will do this this afternoon. Thank you. Steve
Re: segfault causes system freeze
Hi, Le 21-11-2018, à 17:51:39 -0500, Nathan Stratton Treadway a écrit : On Tue, Nov 20, 2018 at 12:42:02 +0100, steve wrote: I have a new box for about two months and it appears that each time mutt segfaults, the console freezes and I have to hard stop the machine. Here is what I have in /var/log/kernel.log: When you say "the console freezes": are you able to log in normally using another virtual terminal or ssh session or anything? No. If switch to another console, and launch a 'ls' for example, the cursor goes to the line and then nothing happens. Ctlr-x doesn't do anything. Opening a new one and launching htop for example freeze the terminal. But was it funny, is that I can firefox still works as expected. At this stage I normally shutdown the computer physically. Or is the system fully locked up, no longer responding to pings, etc.? Does the syslog file show any activity at all between the mutt segfault and the restart-after-reboot messages? No, nothing in syslog I think. If a Mutt segfault is really able to lock up the system entirely, that is a sign of a bigger problem with your kernel and/or hardware (i.e. a user process such as Mutt should not be able to lock up the entire system, no matter how it crashes). Tracking down the Mutt coredump may help you narrow down what part of the broader system is failing, but really it seems like you are trying to figure out what system-wide problem Mutt happens to be tickling Yes, I think it might be a hardware problem triggered by a mutt segfault. Still looking around. Thank you, Steve
Re: segfault causes system freeze
On Tue, Nov 20, 2018 at 12:42:02 +0100, steve wrote: > I have a new box for about two months and it appears that each time mutt > segfaults, the console freezes and I have to hard stop the machine. Here > is what I have in /var/log/kernel.log: When you say "the console freezes": are you able to log in normally using another virtual terminal or ssh session or anything? Or is the system fully locked up, no longer responding to pings, etc.? Does the syslog file show any activity at all between the mutt segfault and the restart-after-reboot messages? If a Mutt segfault is really able to lock up the system entirely, that is a sign of a bigger problem with your kernel and/or hardware (i.e. a user process such as Mutt should not be able to lock up the entire system, no matter how it crashes). Tracking down the Mutt coredump may help you narrow down what part of the broader system is failing, but really it seems like you are trying to figure out what system-wide problem Mutt happens to be tickling Nathan
Re: segfault causes system freeze
steve hat am Mi 21. Nov, 19:50 (+0100) geschrieben: > # coredumpctl info > PID: 1678 (mutt) > UID: 1000 (steve) > GID: 1000 (steve) >Signal: 11 (SEGV) > Timestamp: Wed 2018-11-21 19:45:57 CET (17s ago) > Command Line: mutt -y -n >Executable: /usr/bin/mutt > Control Group: /user.slice/user-1000.slice/session-3.scope > Unit: session-3.scope > Slice: user-1000.slice > Session: 3 > Owner UID: 1000 (steve) > Boot ID: 75e02422e0584081937ef6fe13f1e8ba >Machine ID: 63a22f7a1c2437b0703353c75343f80e > Hostname: box.maison.mrs > Storage: > /var/lib/systemd/coredump/core.mutt.1000.75e02422e0584081937ef6fe13f1e8ba.1678.154282595700.lz4 > Message: Process 1678 (mutt) of user 1000 dumped core. >Stack trace of thread 1678: >#0 0x5592c9a59c68 index_make_entry (mutt) >#1 0x5592c9a822bc menu_redraw_index (mutt) >#2 0x5592c9a90d3b mutt_pager (mutt) >#3 0x5592c9a4ea85 mutt_display_message (mutt) >#4 0x5592c9a5df9c mutt_index_menu (mutt) >#5 0x5592c9a3ef16 main (mutt) >#6 0x7f002ec182e1 __libc_start_main (libc.so.6) >#7 0x5592c9a3ef8a _start (mutt) > > > This does not tell me anything (I'm not a developer). Do you think I should > open a bug report on the Debian BTS? Yes, this would be helpful. Do you have gdb installed? Can you run `coredumpctl debug` and run `bt full` on the gdb prompt? This output would be very helpful for the developer to see, what was the state before the crash. Regards Jörg -- http://www.gnu.org/fun/jokes/ed.msg.html »Note the consistent user interface and error reportage. Ed is generous enough to flag errors, yet prudent enough not to overwhelm the novice with verbosity.« signature.asc Description: PGP signature
Re: segfault causes system freeze
Hi, Mutt crashed just after hitting 'r'. Here is the output of # coredumpctl info PID: 1678 (mutt) UID: 1000 (steve) GID: 1000 (steve) Signal: 11 (SEGV) Timestamp: Wed 2018-11-21 19:45:57 CET (17s ago) Command Line: mutt -y -n Executable: /usr/bin/mutt Control Group: /user.slice/user-1000.slice/session-3.scope Unit: session-3.scope Slice: user-1000.slice Session: 3 Owner UID: 1000 (steve) Boot ID: 75e02422e0584081937ef6fe13f1e8ba Machine ID: 63a22f7a1c2437b0703353c75343f80e Hostname: box.maison.mrs Storage: /var/lib/systemd/coredump/core.mutt.1000.75e02422e0584081937ef6fe13f1e8ba.1678.154282595700.lz4 Message: Process 1678 (mutt) of user 1000 dumped core. Stack trace of thread 1678: #0 0x5592c9a59c68 index_make_entry (mutt) #1 0x5592c9a822bc menu_redraw_index (mutt) #2 0x5592c9a90d3b mutt_pager (mutt) #3 0x5592c9a4ea85 mutt_display_message (mutt) #4 0x5592c9a5df9c mutt_index_menu (mutt) #5 0x5592c9a3ef16 main (mutt) #6 0x7f002ec182e1 __libc_start_main (libc.so.6) #7 0x5592c9a3ef8a _start (mutt) This does not tell me anything (I'm not a developer). Do you think I should open a bug report on the Debian BTS? Thanks. Best, Steve
Re: segfault causes system freeze
Le 21-11-2018, à 08:53:53 +0100, Jörg Sommer a écrit : steve hat am Mi 21. Nov, 06:42 (+0100) geschrieben: Le 20-11-2018, à 21:19:05 +0100, Jörg Sommer a écrit : > > > Do you use systemd? Can you install the packages systemd-coredump and > > > mutt-dbgsym? After a crash you can run `coredumpctl info -1` and post the > > > > There is no mutt-dbgsym in stretch, only jessie and sid. I installed > > systemd-coredump. Will launch the command after next freeze. > > You have to add the following line to /etc/apt/sources.list > > deb http://ftp.de.debian.org/debian-debug/ stable-debug main non-free contrib Thanks, I didn't know about that repo. Installed now, waiting for the next freeze. Can I run the command after a reboot? Yes. Coredumpctl should capture the crash dump and you can inspect it later, if it was successful. But maybe the crash causes the kernel can not even write the core dump out to disk. Thank you for the explanations. Best, Steve
Re: segfault causes system freeze
steve hat am Mi 21. Nov, 06:42 (+0100) geschrieben: > Le 20-11-2018, à 21:19:05 +0100, Jörg Sommer a écrit : > > > > > Do you use systemd? Can you install the packages systemd-coredump and > > > > mutt-dbgsym? After a crash you can run `coredumpctl info -1` and post > > > > the > > > > > > There is no mutt-dbgsym in stretch, only jessie and sid. I installed > > > systemd-coredump. Will launch the command after next freeze. > > > > You have to add the following line to /etc/apt/sources.list > > > > deb http://ftp.de.debian.org/debian-debug/ stable-debug main non-free > > contrib > > Thanks, I didn't know about that repo. Installed now, waiting for the > next freeze. Can I run the command after a reboot? Yes. Coredumpctl should capture the crash dump and you can inspect it later, if it was successful. But maybe the crash causes the kernel can not even write the core dump out to disk. -- “Computer games don't affect kids. If Pacman would have affected us as children, we would now run around in darkened rooms, munching yellow pills and listening to repetetive music.” signature.asc Description: PGP signature
Re: segfault causes system freeze
Le 20-11-2018, à 21:19:05 +0100, Jörg Sommer a écrit : > Do you use systemd? Can you install the packages systemd-coredump and > mutt-dbgsym? After a crash you can run `coredumpctl info -1` and post the There is no mutt-dbgsym in stretch, only jessie and sid. I installed systemd-coredump. Will launch the command after next freeze. You have to add the following line to /etc/apt/sources.list deb http://ftp.de.debian.org/debian-debug/ stable-debug main non-free contrib Thanks, I didn't know about that repo. Installed now, waiting for the next freeze. Can I run the command after a reboot?
Re: segfault causes system freeze
steve hat am Di 20. Nov, 15:18 (+0100) geschrieben: > Le 20-11-2018, à 14:29:30 +0100, Jörg Sommer a écrit : > > steve hat am Di 20. Nov, 12:42 (+0100) geschrieben: > > > Hi There, > > > > > > I have a new box for about two months and it appears that each time mutt > > > segfaults, the console freezes and I have to hard stop the machine. Here > > > is what I have in /var/log/kernel.log: > > > > > > Nov 19 15:54:17 box kernel: [ 7970.303276] mutt[13832]: segfault at 8 ip > > > 55a9d9996c68 sp 7fff5e7f47c0 error 4 in mutt[55a9d9963000+115000] > > > Nov 19 15:54:17 box kernel: [ 7970.303284] Code: e1 00 01 41 89 cb 0f 84 > > > c6 00 00 00 8b 4a 2c 03 8a 90 00 00 00 48 63 52 1c 39 d1 0f 8e cc 00 00 > > > 00 45 8b > > > 54 92 fc 49 8b 58 68 <48> 8b 53 08 48 85 d2 75 26 eb 3d 0f 1f 44 00 00 44 > > > 3b 51 38 41 0f > > > > Do you use systemd? Can you install the packages systemd-coredump and > > mutt-dbgsym? After a crash you can run `coredumpctl info -1` and post the > > There is no mutt-dbgsym in stretch, only jessie and sid. I installed > systemd-coredump. Will launch the command after next freeze. You have to add the following line to /etc/apt/sources.list deb http://ftp.de.debian.org/debian-debug/ stable-debug main non-free contrib Regards Jörg -- “Politics is for the moment, equations are forever” (Albert Einstein) signature.asc Description: PGP signature
Re: segfault causes system freeze
Le 20-11-2018, à 14:29:30 +0100, Jörg Sommer a écrit : steve hat am Di 20. Nov, 12:42 (+0100) geschrieben: Hi There, I have a new box for about two months and it appears that each time mutt segfaults, the console freezes and I have to hard stop the machine. Here is what I have in /var/log/kernel.log: Nov 19 15:54:17 box kernel: [ 7970.303276] mutt[13832]: segfault at 8 ip 55a9d9996c68 sp 7fff5e7f47c0 error 4 in mutt[55a9d9963000+115000] Nov 19 15:54:17 box kernel: [ 7970.303284] Code: e1 00 01 41 89 cb 0f 84 c6 00 00 00 8b 4a 2c 03 8a 90 00 00 00 48 63 52 1c 39 d1 0f 8e cc 00 00 00 45 8b 54 92 fc 49 8b 58 68 <48> 8b 53 08 48 85 d2 75 26 eb 3d 0f 1f 44 00 00 44 3b 51 38 41 0f Do you use systemd? Can you install the packages systemd-coredump and mutt-dbgsym? After a crash you can run `coredumpctl info -1` and post the There is no mutt-dbgsym in stretch, only jessie and sid. I installed systemd-coredump. Will launch the command after next freeze. Thank you Steve
Re: segfault causes system freeze
steve hat am Di 20. Nov, 12:42 (+0100) geschrieben: > Hi There, > > I have a new box for about two months and it appears that each time mutt > segfaults, the console freezes and I have to hard stop the machine. Here > is what I have in /var/log/kernel.log: > > Nov 19 15:54:17 box kernel: [ 7970.303276] mutt[13832]: segfault at 8 ip > 55a9d9996c68 sp 7fff5e7f47c0 error 4 in mutt[55a9d9963000+115000] > Nov 19 15:54:17 box kernel: [ 7970.303284] Code: e1 00 01 41 89 cb 0f 84 c6 > 00 00 00 8b 4a 2c 03 8a 90 00 00 00 48 63 52 1c 39 d1 0f 8e cc 00 00 00 45 8b > 54 92 fc 49 8b 58 68 <48> 8b 53 08 48 85 d2 75 26 eb 3d 0f 1f 44 00 00 44 3b > 51 38 41 0f Do you use systemd? Can you install the packages systemd-coredump and mutt-dbgsym? After a crash you can run `coredumpctl info -1` and post the output here. The backtrace might help to see what's wrong. Regards Jörg -- “Politics is for the moment, equations are forever” (Albert Einstein) signature.asc Description: PGP signature
Re: segfault causes system freeze
* steve [11-20-18 06:42]: > Hi There, > > I have a new box for about two months and it appears that each time mutt > segfaults, the console freezes and I have to hard stop the machine. Here > is what I have in /var/log/kernel.log: > > Nov 19 15:54:17 box kernel: [ 7970.303276] mutt[13832]: segfault at 8 ip > 55a9d9996c68 sp 7fff5e7f47c0 error 4 in mutt[55a9d9963000+115000] > Nov 19 15:54:17 box kernel: [ 7970.303284] Code: e1 00 01 41 89 cb 0f 84 c6 > 00 00 00 8b 4a 2c 03 8a 90 00 00 00 48 63 52 1c 39 d1 0f 8e cc 00 00 00 45 8b > 54 92 fc 49 8b 58 68 <48> 8b 53 08 48 85 d2 75 26 eb 3d 0f 1f 44 00 00 44 3b > 51 38 41 0f > > I don't understand the above message. > > > I'm using NeoMutt 20170113 (1.7.2) from Debian stretch. > > What should I do/try? contact the providers of neomutt as it is a different project than mutt. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
segfault causes system freeze
Hi There, I have a new box for about two months and it appears that each time mutt segfaults, the console freezes and I have to hard stop the machine. Here is what I have in /var/log/kernel.log: Nov 19 15:54:17 box kernel: [ 7970.303276] mutt[13832]: segfault at 8 ip 55a9d9996c68 sp 7fff5e7f47c0 error 4 in mutt[55a9d9963000+115000] Nov 19 15:54:17 box kernel: [ 7970.303284] Code: e1 00 01 41 89 cb 0f 84 c6 00 00 00 8b 4a 2c 03 8a 90 00 00 00 48 63 52 1c 39 d1 0f 8e cc 00 00 00 45 8b 54 92 fc 49 8b 58 68 <48> 8b 53 08 48 85 d2 75 26 eb 3d 0f 1f 44 00 00 44 3b 51 38 41 0f I don't understand the above message. I'm using NeoMutt 20170113 (1.7.2) from Debian stretch. What should I do/try? Thanks. Best, Steve
mutt with sidebar patch: problems with display followed by segfault
Hello,
I have mutt with sidebar patch configured for two account in such a
way so it will change sidebar when changing the account. Unfortunately
I'm experiencing strange problems with display which are followed by
segfault. Its difficult to explain so I did a screen cast to
illustrate the issue [1]. Please notice how after mutt's segfault even
output of simple 'ls -l' command is distorted.
I tried 'mutt-sidebar' [2] and 'uber-mutt' [3] from AUR (both using
different sidebar patches) but the issue persists. Mutt's behaviour is
the same regardless of using it under terminal without X-windows,
urxvt or tmux.
Content of my muttrc:
set alias_file = ${MUTTDIR}/aliases
set mailcap_path = ${MUTTDIR}/mailcap
set tmpdir = ${MUTTDIR}/temp
source ${MUTTDIR}/aliases
source ${MUTTDIR}/macros
set mbox_type = Maildir
set folder = ~/mail
set spoolfile = +gmail/INBOX
set auto_tag
unset beep
set beep_new
unset confirmappend
set delete
unset markers
unset mark_old
set menu_scroll
set pager_context = 5
set pager_index_lines = 10
set pager_stop
set reverse_alias
set sendmail_wait = -1
set sort = threads
set sort_aux = reverse-last-date-received
unset sort_re
set thorough_search
set thread_received
set tilde
set timeout= 3
unset use_domain
unset wait_key
unset wrap_search
set sidebar_width = 25
set sidebar_visible= yes
set sidebar_delim = '|'
bind index \Cp sidebar-prev
bind index \Cn sidebar-next
bind index \Co sidebar-open
bind pager \Cp sidebar-prev
bind pager \Cn sidebar-next
bind pager \Co sidebar-open
auto_viewtext/html
alternative_ordertext/plain text/enriched text/html
set alias_format = "%4n %t %-20a %r"
set compose_format = "──| %v : Compose |/ Approx. msg
size: %l Atts. %a /%>─"
set date_format= "%m/%d/%y@%H:%M"
set forward_format = "Fwd: %s"
set index_format = "%3C %Z %D %-17.17F %s"
set quote_regexp = "^( {0,4}[>|:#%]| {0,4}[a-z0-9]+[>|]+)+"
set reply_regexp = "^(([Rr][Ee]?(\[[0-9]+\])?: *)?(\[[^]]+\] *)?)*"
set status_format = "-%r- %v ───/ %f %m%?n? [+%n]?%?d?
[-%d]?%?t? [*%t]? /%?p?───/ %p waiting to send /?─%>─(%P)───"
set abort_nosubject
set autoedit
set edit_headers
set forward_quote
set include
set realname= "Me"
set reply_to
set reverse_name
unset user_agent
ignore *
unignore from: to: cc: date: subject:
hdr_order from: to: cc: date: subject:
folder-hook gmail/* source ${MUTTDIR}/accounts/gmail
folder-hook two/* source ${MUTTDIR}/accounts/two
subscribe offlineimap-project mutt-users
folder-hook two/lists/(offlineimap|mutt-users|) "exec collapse-all"
Content of settings form specific accounts (both are almost the same
so here is just one):
color status green default
set from= 'Me '
set sendmail= "/usr/bin/msmtpq -a gmail"
unmailboxes *
mailboxes = +gmail/INBOX +gmail/spam +gmail/drafts
+gmail/bin +gmail/sent +gmail/archive
set postponed = +gmail/drafts
set record = +gmail/sent
set trash = +gmail/bin
set signature = ${MUTTDIR}/sigs/gmail.sig
macro index ,c "+two/INBOX" "change accounts"
macro index S "+gmail/spam" "mark message as spam"
I tried stripping muttrc to bare minimum, like so:
set mbox_type = Maildir
set folder = ~/mail
set spoolfile = +gmail/INBOX
set sidebar_width = 25
set sidebar_visible= yes
set sidebar_delim = '|'
bind index \Cp sidebar-prev
bind index \Cn sidebar-next
bind index \Co sidebar-open
bind pager \Cp sidebar-prev
bind pager \Cn sidebar-next
bind pager \Co sidebar-open
folder-hook gmail/* source ${MUTTDIR}/accounts/gmail
folder-hook two/* source ${MUTTDIR}/accounts/two
But that didn't help... Did anyone came across similar behaviour and -
what's more important - solution to it?
1. http://dl.dropbox.com/u/11250432/index.html
2. http://aur.archlinux.org/packages.php?ID=7168
3. http://aur.archlinux.org/packages.php?ID=37609
Regards,
weertex
Re: mutt is crashing with segfault when running a macro
On Mon, Sep 6, 2010 at 3:42 PM, Asif Iqbal wrote: > On Mon, Sep 6, 2010 at 3:01 PM, Asif Iqbal wrote: >> When I run the following macro mutt exits with segfault >> >> macro index S >> '/home/axisys/.mutt/script/reportspam.sh' >> >> Here is the script >> >> #!/bin/bash >> # take the email and send it as attachment to abuse >> # save to tmp file >> spam=$(tempfile -s .eml) >> abuse=ab...@example.net >> >> cat > "$spam" >> >> # use formail to extract subject (could use grep in a pinch) >> subj=$(formail -x subject < $spam) >> >> if [ ! -z "$spam" ]; then >> mutt -e 'set from=u...@example.com' -s "[spam]$subj" -a $spam >> -- "$ABUSE" >> fi >> rm "$spam" >> >> >> Here is the segfault in `dmesg' >> >> http://pastebin.com/29JuFUCv >> >> I am running mutt 1.5.20 on ubuntu lucid >> >> If I add `set -x' in that macro script this is how it reports about the >> segfault >> >> ++ tempfile -s .eml >> + spam=/tmp/fileMWDTFO.eml >> + abuse=ab...@example.net >> + cat - >> Segmentation fault >> ++ formail -x subject >> + subj= >> + '[' '!' -z /tmp/fileMWDTFO.eml ']' >> + mutt -e 'set from=u...@example.com' -s '[spam]' -a >> /tmp/fileMWDTFO.eml -- ab...@example.net >> + rm /tmp/fileMWDTFO.eml >> >> Am I hitting a bug? Is there a way to run mutt in debug mode to get more >> details > > Thanks to rudy_s in #mutt.. I needed to install the mutt-dbg pkg for > ubuntu. now I have core > files. Here is the backtrace > > Core was generated by `mutt -d5 -F work.muttrc'. > Program terminated with signal 11, Segmentation fault. > #0 0x7f53f7d6835e in vfprintf () from /lib/libc.so.6 > (gdb) bt > #0 0x7f53f7d6835e in vfprintf () from /lib/libc.so.6 > #1 0x7f53f7e1c750 in __vsnprintf_chk () from /lib/libc.so.6 > #2 0x0041f9ce in vsnprintf (fmt=0x0) at /usr/include/bits/stdio2.h:78 > #3 mutt_curses_message (fmt=0x0) at ../curs_lib.c:330 > #4 0x0041e0c2 in mutt_progress_update > (progress=0x7fff9846cbd0, pos=0, percent=0) > at ../curs_lib.c:439 > #5 0x004a4258 in imap_read_literal (fp=0x1e69550, > idata=0xde21b0, bytes=2439, pbar=0x7fff9846cbd0) > at ../../imap/imap.c:237 > #6 0x004a73bb in imap_fetch_message (msg=0x1e66690, > ctx=0xded730, msgno=) > at ../../imap/message.c:495 > #7 0x00447935 in mx_open_message (ctx=0xded730, msgno=1) at > ../mx.c:1503 > #8 0x0041da8a in mutt_copy_message (fpout=0x1e66450, > src=0x7f530003, hdr=0x10, flags=-1, > chflags=0) at ../copy.c:685 > #9 0x0041607c in _mutt_pipe_message (h=0x1e6cd10, cmd= optimized out>, decode=0, > print=, split=, > sep=0xdd5ec0 "\n") at ../commands.c:416 > #10 0x004165ce in mutt_pipe_message (h=0x1e6cd10) at ../commands.c:497 > #11 0x00421aa7 in mutt_index_menu () at ../curs_main.c:2030 > #12 0x0043df57 in main (argc=-1740186176, argv= optimized out>) at ../main.c:1026 problem went away after installing the mutt from hg repo hg clone http://dev.mutt.org/hg/mutt#HEAD cd mutt ./prepare (thanks to rudy_s from #mutt for suggesting that) ./configure --enable-imap --enable-debug --with-ssl --enable-hcache > > >> >> -- >> Asif Iqbal >> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu >> A: Because it messes up the order in which people normally read text. >> Q: Why is top-posting such a bad thing? >> > > > > -- > Asif Iqbal > PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
Re: mutt is crashing with segfault when running a macro
On Mon, Sep 6, 2010 at 3:01 PM, Asif Iqbal wrote: > When I run the following macro mutt exits with segfault > > macro index S > '/home/axisys/.mutt/script/reportspam.sh' > > Here is the script > > #!/bin/bash > # take the email and send it as attachment to abuse > # save to tmp file > spam=$(tempfile -s .eml) > abuse=ab...@example.net > > cat > "$spam" > > # use formail to extract subject (could use grep in a pinch) > subj=$(formail -x subject < $spam) > > if [ ! -z "$spam" ]; then > mutt -e 'set from=u...@example.com' -s "[spam]$subj" -a $spam > -- "$ABUSE" > fi > rm "$spam" > > > Here is the segfault in `dmesg' > > http://pastebin.com/29JuFUCv > > I am running mutt 1.5.20 on ubuntu lucid > > If I add `set -x' in that macro script this is how it reports about the > segfault > > ++ tempfile -s .eml > + spam=/tmp/fileMWDTFO.eml > + abuse=ab...@example.net > + cat - > Segmentation fault > ++ formail -x subject > + subj= > + '[' '!' -z /tmp/fileMWDTFO.eml ']' > + mutt -e 'set from=u...@example.com' -s '[spam]' -a > /tmp/fileMWDTFO.eml -- ab...@example.net > + rm /tmp/fileMWDTFO.eml > > Am I hitting a bug? Is there a way to run mutt in debug mode to get more > details Thanks to rudy_s in #mutt.. I needed to install the mutt-dbg pkg for ubuntu. now I have core files. Here is the backtrace Core was generated by `mutt -d5 -F work.muttrc'. Program terminated with signal 11, Segmentation fault. #0 0x7f53f7d6835e in vfprintf () from /lib/libc.so.6 (gdb) bt #0 0x7f53f7d6835e in vfprintf () from /lib/libc.so.6 #1 0x7f53f7e1c750 in __vsnprintf_chk () from /lib/libc.so.6 #2 0x0041f9ce in vsnprintf (fmt=0x0) at /usr/include/bits/stdio2.h:78 #3 mutt_curses_message (fmt=0x0) at ../curs_lib.c:330 #4 0x0041e0c2 in mutt_progress_update (progress=0x7fff9846cbd0, pos=0, percent=0) at ../curs_lib.c:439 #5 0x004a4258 in imap_read_literal (fp=0x1e69550, idata=0xde21b0, bytes=2439, pbar=0x7fff9846cbd0) at ../../imap/imap.c:237 #6 0x004a73bb in imap_fetch_message (msg=0x1e66690, ctx=0xded730, msgno=) at ../../imap/message.c:495 #7 0x00447935 in mx_open_message (ctx=0xded730, msgno=1) at ../mx.c:1503 #8 0x0041da8a in mutt_copy_message (fpout=0x1e66450, src=0x7f530003, hdr=0x10, flags=-1, chflags=0) at ../copy.c:685 #9 0x0041607c in _mutt_pipe_message (h=0x1e6cd10, cmd=, decode=0, print=, split=, sep=0xdd5ec0 "\n") at ../commands.c:416 #10 0x004165ce in mutt_pipe_message (h=0x1e6cd10) at ../commands.c:497 #11 0x00421aa7 in mutt_index_menu () at ../curs_main.c:2030 #12 0x0043df57 in main (argc=-1740186176, argv=) at ../main.c:1026 > > -- > Asif Iqbal > PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
mutt is crashing with segfault when running a macro
When I run the following macro mutt exits with segfault macro index S '/home/axisys/.mutt/script/reportspam.sh' Here is the script #!/bin/bash # take the email and send it as attachment to abuse # save to tmp file spam=$(tempfile -s .eml) abuse=ab...@example.net cat > "$spam" # use formail to extract subject (could use grep in a pinch) subj=$(formail -x subject < $spam) if [ ! -z "$spam" ]; then mutt -e 'set from=u...@example.com' -s "[spam]$subj" -a $spam -- "$ABUSE" fi rm "$spam" Here is the segfault in `dmesg' http://pastebin.com/29JuFUCv I am running mutt 1.5.20 on ubuntu lucid If I add `set -x' in that macro script this is how it reports about the segfault ++ tempfile -s .eml + spam=/tmp/fileMWDTFO.eml + abuse=ab...@example.net + cat - Segmentation fault ++ formail -x subject + subj= + '[' '!' -z /tmp/fileMWDTFO.eml ']' + mutt -e 'set from=u...@example.com' -s '[spam]' -a /tmp/fileMWDTFO.eml -- ab...@example.net + rm /tmp/fileMWDTFO.eml Am I hitting a bug? Is there a way to run mutt in debug mode to get more details -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
Re: Mutt 1.5.19 segfault on FreeBSD (mutt-devel port)
On Fri, Mar 27, 2009 at 11:27:13PM +0100, Lagrange Marc wrote: > Hi all, > > I've just compiled mutt 1.5.19 on my freebsd (7.1) laptop and mutt > 1.5.19 is unable to start. > > I've a working config from another freebsd.. This sounds similar to the experience I have been having with the same FreeBSD 7.1 (I have 7.1-R) and mutt-devel. The problem might have something to do with the sidebar patch. Try rebuilding without the sidebar and see if you get the same crash. I'll have to check, but I believe someone from this list submitted a patch for this issue. - jt > All infos i can provides : > > mutt -v > Mutt 1.5.19 (2009-01-05) > Copyright (C) 1996-2009 Michael R. Elkins and others. > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > Mutt is free software, and you are welcome to redistribute it > under certain conditions; type `mutt -vv' for details. > > System: FreeBSD 7.1-STABLE (i386) > ncurses: ncurses 5.7.20081102 (compiled with 5.6) > libiconv: 1.11 > libidn: 1.13 (compiled with 1.13) > hcache backend: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) > Compile options: > -DOMAIN > +DEBUG > -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK > +USE_POP +USE_IMAP +USE_SMTP > +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO > +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED > +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET > +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM > +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME > -EXACT_ADDRESS -SUN_ATTACHMENT > -ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET > +HAVE_LANGINFO_YESEXPR > +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE > -ISPELL > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/mail" > PKGDATADIR="/usr/local/share/mutt" > SYSCONFDIR="/usr/local/etc" > EXECSHELL="/bin/sh" > -MIXMASTER > To contact the developers, please mail to . > To report a bug, please visit http://bugs.mutt.org/. > > patch-1.5.17.sidebar.20080412 > vvv.quote > patch-1.5.0.ats.date_conditional.1 > dgc.deepif.1 > vvv.initials > rr.compressed > > > > gdb mutt > Program received signal SIGSEGV, Segmentation fault. > 0x28693c12 in memcpy () from /lib/libc.so.7 > (gdb) bt > #0 0x28693c12 in memcpy () from /lib/libc.so.7 > #1 0x282db449 in c2i_ASN1_BIT_STRING () from /lib/libcrypto.so.5 > #2 0x282d8eb9 in asn1_ex_c2i () from /lib/libcrypto.so.5 > #3 0x282d97a1 in asn1_ex_c2i () from /lib/libcrypto.so.5 > #4 0x282da12c in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 > #5 0x282d9bde in asn1_ex_c2i () from /lib/libcrypto.so.5 > #6 0x282d9ee7 in asn1_ex_c2i () from /lib/libcrypto.so.5 > #7 0x282da688 in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 > #8 0x282d9bde in asn1_ex_c2i () from /lib/libcrypto.so.5 > #9 0x282d9ee7 in asn1_ex_c2i () from /lib/libcrypto.so.5 > #10 0x282da688 in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 > #11 0x282d9bde in asn1_ex_c2i () from /lib/libcrypto.so.5 > #12 0x282d9ee7 in asn1_ex_c2i () from /lib/libcrypto.so.5 > #13 0x282da688 in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 > #14 0x282daab1 in ASN1_item_d2i () from /lib/libcrypto.so.5 > #15 0x282ae405 in d2i_X509 () from /lib/libcrypto.so.5 > #16 0x2838127a in ssl3_get_server_certificate () from /usr/lib/libssl.so.5 > #17 0x28382812 in ssl3_connect () from /usr/lib/libssl.so.5 > #18 0x2838a7ea in SSL_connect () from /usr/lib/libssl.so.5 > #19 0x2837333b in ssl23_connect () from /usr/lib/libssl.so.5 > #20 0x2838a7ea in SSL_connect () from /usr/lib/libssl.so.5 > #21 0x080e509f in ?? () > #22 0x288b3040 in ?? () > #23 0x0021 in ?? () > #24 0x0004 in ?? () > #25 0x in ?? () > #26 0x288b3040 in ?? () > #27 0x28886bc0 in ?? () > #28 0x28886bc0 in ?? () > #29 0x0009 in ?? () > #30 0x0088 in ?? () > #31 0x288aebc0 in ?? () > #32 0x0009 in ?? () > #33 0x2838c5fa in SSL_set_fd () from /usr/lib/libssl.so.5 > #34 0x080e5015 in ?? () > #35 0x288a2000 in ?? () > #36 0x288aeaf0 in ?? () > #37 0xbfbfd388 in ?? () > #38 0x080c6fc8 in ?? () > #39 0x0001 in ?? () > #40 0x in ?? () > #41 0xbfbfd478 in ?? () > #42 0xbfbfd38c in ?? () > #43 0x28709400 in ?? () > #44 0x288aeaf0 in ?? () > #45 0xbfbfd3b8 in ?? () > #46 0x080e3626 in ?? () > #47 0x288a2000 in ?? () > #48 0x288a2000 in ?? () > #49 0xbfbfd3a8 in ?? () > ---Type to continue, or q to quit--- > #50 0x080e4033 in ?? () > #51 0x0001 in ?? () > #52 0x0574 in ?? () > #53 0xbfbfd3a8 in ?? () > #54 0x080e4e00 in ?? () > #55 0x in ?? () > #56 0x in ?? () > #57 0xbfbfd7e8 in ?? () > #58 0x080e3da7 in ?? () > #59 0x288a2000 in ?? () > #60 0x28709400 in ?? () > #61 0xbfbfd7e8 in ?? () > #62 0x080efd42 in ?? () > #63 0x288a2000 in ?? () > #64 0x288a2000 in ?? () > #65 0x in ?? () > #66 0x70616d69 in ?? () > #67 0x2f2f3a73 in ?? () > #68 0x70616d69 in ?? () > #69 0x6c69702e in ?? () > #70 0x7973
Mutt 1.5.19 segfault on FreeBSD (mutt-devel port)
Hi all, I've just compiled mutt 1.5.19 on my freebsd (7.1) laptop and mutt 1.5.19 is unable to start. I've a working config from another freebsd.. All infos i can provides : mutt -v Mutt 1.5.19 (2009-01-05) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 7.1-STABLE (i386) ncurses: ncurses 5.7.20081102 (compiled with 5.6) libiconv: 1.11 libidn: 1.13 (compiled with 1.13) hcache backend: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT -ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" EXECSHELL="/bin/sh" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. patch-1.5.17.sidebar.20080412 vvv.quote patch-1.5.0.ats.date_conditional.1 dgc.deepif.1 vvv.initials rr.compressed gdb mutt Program received signal SIGSEGV, Segmentation fault. 0x28693c12 in memcpy () from /lib/libc.so.7 (gdb) bt #0 0x28693c12 in memcpy () from /lib/libc.so.7 #1 0x282db449 in c2i_ASN1_BIT_STRING () from /lib/libcrypto.so.5 #2 0x282d8eb9 in asn1_ex_c2i () from /lib/libcrypto.so.5 #3 0x282d97a1 in asn1_ex_c2i () from /lib/libcrypto.so.5 #4 0x282da12c in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 #5 0x282d9bde in asn1_ex_c2i () from /lib/libcrypto.so.5 #6 0x282d9ee7 in asn1_ex_c2i () from /lib/libcrypto.so.5 #7 0x282da688 in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 #8 0x282d9bde in asn1_ex_c2i () from /lib/libcrypto.so.5 #9 0x282d9ee7 in asn1_ex_c2i () from /lib/libcrypto.so.5 #10 0x282da688 in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 #11 0x282d9bde in asn1_ex_c2i () from /lib/libcrypto.so.5 #12 0x282d9ee7 in asn1_ex_c2i () from /lib/libcrypto.so.5 #13 0x282da688 in ASN1_item_ex_d2i () from /lib/libcrypto.so.5 #14 0x282daab1 in ASN1_item_d2i () from /lib/libcrypto.so.5 #15 0x282ae405 in d2i_X509 () from /lib/libcrypto.so.5 #16 0x2838127a in ssl3_get_server_certificate () from /usr/lib/libssl.so.5 #17 0x28382812 in ssl3_connect () from /usr/lib/libssl.so.5 #18 0x2838a7ea in SSL_connect () from /usr/lib/libssl.so.5 #19 0x2837333b in ssl23_connect () from /usr/lib/libssl.so.5 #20 0x2838a7ea in SSL_connect () from /usr/lib/libssl.so.5 #21 0x080e509f in ?? () #22 0x288b3040 in ?? () #23 0x0021 in ?? () #24 0x0004 in ?? () #25 0x in ?? () #26 0x288b3040 in ?? () #27 0x28886bc0 in ?? () #28 0x28886bc0 in ?? () #29 0x0009 in ?? () #30 0x0088 in ?? () #31 0x288aebc0 in ?? () #32 0x0009 in ?? () #33 0x2838c5fa in SSL_set_fd () from /usr/lib/libssl.so.5 #34 0x080e5015 in ?? () #35 0x288a2000 in ?? () #36 0x288aeaf0 in ?? () #37 0xbfbfd388 in ?? () #38 0x080c6fc8 in ?? () #39 0x0001 in ?? () #40 0x in ?? () #41 0xbfbfd478 in ?? () #42 0xbfbfd38c in ?? () #43 0x28709400 in ?? () #44 0x288aeaf0 in ?? () #45 0xbfbfd3b8 in ?? () #46 0x080e3626 in ?? () #47 0x288a2000 in ?? () #48 0x288a2000 in ?? () #49 0xbfbfd3a8 in ?? () ---Type to continue, or q to quit--- #50 0x080e4033 in ?? () #51 0x0001 in ?? () #52 0x0574 in ?? () #53 0xbfbfd3a8 in ?? () #54 0x080e4e00 in ?? () #55 0x in ?? () #56 0x in ?? () #57 0xbfbfd7e8 in ?? () #58 0x080e3da7 in ?? () #59 0x288a2000 in ?? () #60 0x28709400 in ?? () #61 0xbfbfd7e8 in ?? () #62 0x080efd42 in ?? () #63 0x288a2000 in ?? () #64 0x288a2000 in ?? () #65 0x in ?? () #66 0x70616d69 in ?? () #67 0x2f2f3a73 in ?? () #68 0x70616d69 in ?? () #69 0x6c69702e in ?? () #70 0x7973746f in ?? () #71 0x6d657473 in ?? () #72 0x656e2e73 in ?? () #73 0x39393a74 in ?? () #74 0x2f33 in ?? () #75 0x in ?? () #76 0x in ?? () #77 0x in ?? () #78 0x in ?? () #79 0x in ?? () #80 0x in ?? () #81 0x in ?? () #82 0x in ?? () #83 0x in ?? () #84 0x in ?? () #85 0x287140b4 in ?? () #86 0x28140e00 in ?? () #87 0x7ffd in ?? () #88 0x0208 in ?? () #89 0x287140b2 in ?? () #90 0x7fff in ?? () #91 0x281db800 in ?? () #92 0x281dba00 in ?? () #93 0x281dbc00 in ?? () #94 0x281dbe00 in ?? () #95 0x281dc000 in ?? () #96 0x in ?? () #97 0x0070 in ?? () #98 0
Segfault in Mutt 1.2.5i, while executing $ update
I produced a segfault in Mutt 1.2.5i as follows. I have a folder hook set for mbox to show only new messages. I started Mutt, went to mbox. Deleted the one message which was marked as new. I then pressed $ to update mbox, thinking this would show the remaining contents (which is over 300 messages). Instead, I got a segfault. Also, it turned the text on my gnome-terminal blue (sadness, I suppose) John -- John P. Verel Norwalk, CT
Re: Segfault
begin Bob Bell quotation: > I'm unable to reproduce this with mutt 1.3.11i. Have you tried to > reproduce it? Do you have a few short lines I can add to my muttrc to > reproduce it? No, I was not able to reproduce it, sorry I forgot to mention that. I took it for granted that he was giving me exact information. I will check to see if he has a copy of the .muttrc that was giving him the problem. If he does, I'll examine it and optionally send it to you/anybody if requested. -- Blue skies... Todd | Get a bigger hammer! | Sometimes you get what you want. | | http://www.mrball.net | Sometimes you get experience. | | http://faq.mrball.net | --unknown origin | PGP signature
Re: Segfault
I'm unable to reproduce this with mutt 1.3.11i. Have you tried to reproduce it? Do you have a few short lines I can add to my muttrc to reproduce it? On Thu, Apr 26, 2001 at 02:54:44PM -0700, CB <[EMAIL PROTECTED]> wrote: > This is from a Mandrake mailing list. I wanted to point this out to the > developers and let them know that an audit might be in order to > verify/disprove that this exists in other config options as well (the > segfault on a blank option). > > >Forwarded message > I just wanted to update the group on this issue. > > For those of you that use Mutt, you know how customizable it is via > your .muttrc file. Well that's where the problem was. > > In the .muttrc you can specify who you are, your email address and the > organization that you belong to. The lines would look something like > this. > > my_hdr From: Tim Holmes <[EMAIL PROTECTED]> > my_hdr Organization: UNIXTECHS ORG > my_hdr Reply-To: Tim Holmes <[EMAIL PROTECTED]> > > Well there's often another line in the .muttrc that tell tells it to > remove > all "extra" headers as well. That looks like this. > > unmy_hdr * > > Well, from what I've been told by others, if you have the line for > unmy_hdr > in your .muttrc, it will ignore error messages that you may have from > reading > the .muttrc. > > That's what allowed the problem to slip through, but the problem was > caused > by the line for Organization. If you leave my_hdr Organization: blank, > it > causes an error. It will allow you to open your mailbox and move around > in > them and read messages, and even right them, but as soon as you try and > send > them, you recieve a lovely segment fault, and sometimes a core is > dumped. > > Instead of just ignoring the blank field is dies on you. Personally > this being > the case is completely retarded, but that's just me. I spent almost an > entire > day trying to figure out why I had two users, that would continue to get > segment > faults each time they sent mail. But 5 other users were just fine! > That's what > pointed me towards the .muttrc. > > After rebuilding my .muttrc file line by line, (Which was a pain in the > @%$ if you > ask me!) and finally found that it was the Organization line that was > causing my > problem. I removed that line, and the problem is gone. I think the > people with > mutt were retarded for doing that! But again... that's just me. > > -- Bob Bell <[EMAIL PROTECTED]> - "For example, OS/360 devotes 26 bytes of the permanently resident date-turnover routine to the proper handling of December 31 on leap years (when it is Day 366). That might have been left to the operator." -- Fred Brooks, _The Mythical Man-Month_, on wasting resources
Segfault
This is from a Mandrake mailing list. I wanted to point this out to the developers and let them know that an audit might be in order to verify/disprove that this exists in other config options as well (the segfault on a blank option). >Forwarded message I just wanted to update the group on this issue. For those of you that use Mutt, you know how customizable it is via your .muttrc file. Well that's where the problem was. In the .muttrc you can specify who you are, your email address and the organization that you belong to. The lines would look something like this. my_hdr From: Tim Holmes <[EMAIL PROTECTED]> my_hdr Organization: UNIXTECHS ORG my_hdr Reply-To: Tim Holmes <[EMAIL PROTECTED]> Well there's often another line in the .muttrc that tell tells it to remove all "extra" headers as well. That looks like this. unmy_hdr * Well, from what I've been told by others, if you have the line for unmy_hdr in your .muttrc, it will ignore error messages that you may have from reading the .muttrc. That's what allowed the problem to slip through, but the problem was caused by the line for Organization. If you leave my_hdr Organization: blank, it causes an error. It will allow you to open your mailbox and move around in them and read messages, and even right them, but as soon as you try and send them, you recieve a lovely segment fault, and sometimes a core is dumped. Instead of just ignoring the blank field is dies on you. Personally this being the case is completely retarded, but that's just me. I spent almost an entire day trying to figure out why I had two users, that would continue to get segment faults each time they sent mail. But 5 other users were just fine! That's what pointed me towards the .muttrc. After rebuilding my .muttrc file line by line, (Which was a pain in the @%$ if you ask me!) and finally found that it was the Organization line that was causing my problem. I removed that line, and the problem is gone. I think the people with mutt were retarded for doing that! But again... that's just me. -- Blue skies... Todd | Get a bigger hammer! | Sometimes you get what you want. | | http://www.mrball.net | Sometimes you get experience. | | http://faq.mrball.net | --unknown origin | PGP signature
Re: segfault at sending message
Look at your "set editor" function. On Sat, Mar 03, 2001 at 12:14:29AM +0100, Marco Ahrendt muttered: | hi all, | | anyone knows why mutt crashes with segmentation fault if i press "y" to | send the message ?? i'm running kernel 2.4.1 and mutt 1.3.12i. | | Marco | | -- | Marco Ahrendt phone : +49-341-98-474-0 | adconsys AGfax : +49-341-98-474-59 | Karl-Liebknecht-Str. 19email : [EMAIL PROTECTED] | 04107 Leipzig/Germany gnupg key at www.aktex.net/marco_work.asc -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
segfault at sending message
hi all, anyone knows why mutt crashes with segmentation fault if i press "y" to send the message ?? i'm running kernel 2.4.1 and mutt 1.3.12i. Marco -- Marco Ahrendt phone : +49-341-98-474-0 adconsys AGfax : +49-341-98-474-59 Karl-Liebknecht-Str. 19email : [EMAIL PROTECTED] 04107 Leipzig/Germany gnupg key at www.aktex.net/marco_work.asc
Segfault in 1.2.5i -- Update
Hi, Thomas.
Just an update on occurrences of segfault. I've changed my .muttrc setting around a
bit to change
the way a folder is displayed when first opened. I have the following:
folder-hook =mbox 'push odl~N'
folder-hook =outbox 'push od
folder-hook =CGO_Chorus 'push od'
folder-hook . 'push otV'
If I:
Open a folder
Execute order|date|END
Scroll with an arrow key to a new article in the index
Execute order|thread
Press the up arrow
I always get a segfault.
This occurs regardless of folder.
--
John P. Verel
Norwalk, CT
Re: SEGFAULT
On Fri, Dec 01, 2000 at 04:05:14PM +0530, Suresh Ramasubramanian wrote:
> Johannes Zellner proclaimed on mutt-users that:
>
> > I discovered a reproducable SEGFAULT:
> > using c to change folder
> > c
> > using a directory, e.g.
> > ~/
> > hitting (twice) to get the directory listing
> > and then using `m' to compose a mail will SEGFAULT
> > mutt.
>
> No it doesnt - mutt-1.2.5i here (standard rpm from mutt.linuxatwork.at)
>
> File Mask: !^\.[^.] <= this is what I am asked when I repeat your keystrokes
I've the default bindings here. I can even:
c~/
where is bound to show help here. This shows
menter-mask
then returning from help with `q' and hitting `m'
will again segfault mutt.
Well, I guess I'll just install the latest devel version
and hope that it's ok there...
Futhermore, if I KNOW that this causes a segfault
I haven't to use it :-)
--
Johannes
Re: SEGFAULT
Johannes Zellner proclaimed on mutt-users that: > I discovered a reproducable SEGFAULT: > using c to change folder > c > using a directory, e.g. > ~/ > hitting (twice) to get the directory listing > and then using `m' to compose a mail will SEGFAULT > mutt. No it doesnt - mutt-1.2.5i here (standard rpm from mutt.linuxatwork.at) File Mask: !^\.[^.] <= this is what I am asked when I repeat your keystrokes -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI Just about every computer on the market today runs Unix, except the Mac (and nobody cares about it). -- Bill Joy 6/21/85
Re: SEGFAULT
Hello Johannes, * Johannes Zellner wrote: > I discovered a reproducable SEGFAULT: > > using c to change folder > > c > > using a directory, e.g. > > ~/ > > hitting (twice) to get the directory listing > and then using `m' to compose a mail will SEGFAULT > mutt. [...] > mutt 1.2.5i. Can't reproduce this with mutt 1.2.5 here. 'm' in directory view mode is used for setting the file mask. Did you change the default key bindings? christian -- No courtesy copy (CC:), please. I'm reading here!
SEGFAULT
Hi, I discovered a reproducable SEGFAULT: using c to change folder c using a directory, e.g. ~/ hitting (twice) to get the directory listing and then using `m' to compose a mail will SEGFAULT mutt. So the key stokes again: c~/m I'm not subscribed to the list, so if you've more questions you've reply to me directly. mutt 1.2.5i. btw.: Is there any CVS access to the devel source ? -- Johannes
Re: Segfault in 1.2.5i
On 2000-11-01 21:53:46 -0500, John P. Verel wrote: > I've just determined that this is confined to one particular folder. Could you please try to confine this further, possible to one particular thread in that folder? -- Thomas Roessler <[EMAIL PROTECTED]>
Re: Segfault in 1.2.5i
I've just determined that this is confined to one particular folder. On 11/01/00, 09:15:47PM -0500, John P. Verel wrote: > I can always produce a segfault with the following sequence, while in > in a folder: > > order|date|End|Order|Thread|Up Arrow > > I have the following in my .muttrc, which may be germane: > > folder-hook . 'push V' > > I'm running Red Hat 7, 2.2.16-22. > > I do not recall this happening in 1.2i (which I was running under > 2.2.14). I upgraded to 1.2.5i as part of the Red Hat 7 upgrade > > John
Segfault in 1.2.5i
I can always produce a segfault with the following sequence, while in in a folder: order|date|End|Order|Thread|Up Arrow I have the following in my .muttrc, which may be germane: folder-hook . 'push V' I'm running Red Hat 7, 2.2.16-22. I do not recall this happening in 1.2i (which I was running under 2.2.14). I upgraded to 1.2.5i as part of the Red Hat 7 upgrade John
Re: Mutt 1.2.5i SegFault and core dumps
On Sat, Sep 16, 2000 at 19:02:32 +0200, Zak Le Roux wrote: > Forgot to add the CORE DUMP file (gzipped) ... sorry ! We cannot use the core file without having exactly the same environment and the executable file as where it was made. You can however help by analyzing the core with the gdb debugger and sending the results. A good start would be the following gdb commands: $ gdb mutt core (gdb) bt (gdb) info locals (gdb) quit $ Please also send the output of "mutt -v" > Permissions on Mutt files are as follows:- > > /usr/local/bin/mutt rootroot-rwxr-xr-x > /usr/local/bin/mut_dotlock rootmail-rwxr-xr-x > > Are these OK ? No. If you have and use mutt_dotlock (with double t) it should be setgid mail (i.e. permissions -rwxr-sr-x). -- Byrial http://home.worldonline.dk/~byrial/
Mutt 1.2.5i SegFault and core dumps
Forgot to add the CORE DUMP file (gzipped) ... sorry ! Hi, I have recently installed the new version of Mutt (1.2.5i). I am new to this application and find it tough going. but I am learning a lot. I am however having some trouble with it ... causes a segmentation fault and core dumps when I exit from sometimes. Here are some details that may be helpful ... As long as I don't read any emails (I can reply, forward or flag to delete OK) then I can exit and nothing happens. However, once I have selected an email to read a message and then exit, it core dumps. I thought this may have something to do with permissions (and it may very well still do), but the other mail boxes I have set up (for Pine and the like) work just fine. I am running RedHat 5.2 with GLIBC2 (2.1.3) on a 2.0.36-3 kernel. Permissions on Mutt files are as follows:- /usr/local/bin/mutt rootroot-rwxr-xr-x /usr/local/bin/mut_dotlock rootmail-rwxr-xr-x Are these OK ? Mail Spool file permissions (zaklr is my mailbox) are:- /var/spool/mail/zaklr zaklr mail-rw-rw I guess the answer is something really trivial but I have no idea anymore .. and you may well say "These Linux newbies". I would appreciate your help however ... :-) TIA Zak Le Roux core.gz
Mutt 1.2.5i SegFault and core dumps
Hi, I have recently installed the new version of Mutt (1.2.5i). I am new to this application and find it tough going. but I am learning a lot. I am however having some trouble with it ... causes a segmentation fault and core dumps when I exit from sometimes. Here are some details that may be helpful ... As long as I don't read any emails (I can reply, forward or flag to delete OK) then I can exit and nothing happens. However, once I have selected an email to read a message and then exit, it core dumps. I thought this may have something to do with permissions (and it may very well still do), but the other mail boxes I have set up (for Pine and the like) work just fine. I am running RedHat 5.2 with GLIBC2 (2.1.3) on a 2.0.36-3 kernel. Permissions on Mutt files are as follows:- /usr/local/bin/mutt rootroot-rwxr-xr-x /usr/local/bin/mut_dotlock rootmail-rwxr-xr-x Are these OK ? Mail Spool file permissions (zaklr is my mailbox) are:- /var/spool/mail/zaklr zaklr mail-rw-rw I guess the answer is something really trivial but I have no idea anymore .. and you may well say "These Linux newbies". I would appreciate your help however ... :-) TIA Zak Le Roux
[1.1.7] IMAP segfault
The attached patch fixes a segmentation fault which would occur when
the operates without a Context (this happens, for instance, when you
can't connect to an IMAP folder).
--
http://www.guug.de/~roessler/
Index: imap/util.c
===
RCS file: /home/roessler/cvsroot/mutt/imap/util.c,v
retrieving revision 1.18
diff -u -p -u -r1.18 util.c
--- imap/util.c 2000/02/28 17:54:41 1.18
+++ imap/util.c 2000/03/01 11:56:53
@@ -375,12 +375,12 @@ int imap_wait_keepalive (pid_t pid)
void imap_allow_reopen (CONTEXT *ctx)
{
- if (ctx->magic == M_IMAP && CTX_DATA->selected_ctx == ctx)
+ if (ctx && ctx->magic == M_IMAP && CTX_DATA->selected_ctx == ctx)
CTX_DATA->reopen |= IMAP_REOPEN_ALLOW;
}
void imap_disallow_reopen (CONTEXT *ctx)
{
- if (ctx->magic == M_IMAP && CTX_DATA->selected_ctx == ctx)
+ if (ctx && ctx->magic == M_IMAP && CTX_DATA->selected_ctx == ctx)
CTX_DATA->reopen &= ~IMAP_REOPEN_ALLOW;
}
PGP signature
still segfault...
i recently downloaded /mutt-0.96.2/ and still get the annoying segfault when syncing the mailbox... (gdb) bt #0 0x400b4ef1 in _IO_old_file_close_it (fp=0x80c90f0) at oldfileops.c:140 #1 0x400b1257 in freopen (filename=0x80c9050 "/var/spool/mail/martin", mode=0x80a4821 "r+", fp=0x80c90f0) at freopen.c:53 #2 0x806e9f3 in mbox_sync_mailbox (ctx=0x80c8ff0) at mbox.c:682 #3 0x8073c0f in sync_mailbox (ctx=0x80c8ff0) at mx.c:690 #4 0x80746f4 in mx_sync_mailbox (ctx=0x80c8ff0) at mx.c:996 #5 0x805a8d1 in mutt_index_menu () at curs_main.c:795 #6 0x806d7a3 in main (argc=1, argv=0xb6c4) at main.c:682 greets -- Martin "Lolly" Lorenz ** a simple way to overcome melissa** ** DON'T USE MICROSOFT ** http://hasiti.mir.at/~martin the more daring thing mostly is to question the known than to explore the unknown
