Eduardo Alvarez <[EMAIL PROTECTED]> writes: > On Fri, Sep 19, 2003 at 09:28:16PM -0400, Dan Espen wrote: > > > > Eduardo Alvarez <[EMAIL PROTECTED]> writes: > > > As requested by Dan Espen, I am sending to you a core dump of fvwm 2.5.7 > > > which crashes when the following happens: > > > > > > I call 'aterm -name vim -e vim' either via a different aterm or by a > > > keyboard shortcut, as so: > > > > > > Key v A SCM Exec exec aterm -name vim -e vim > > > > > > The interesting thing is, if I call it, then immediately quit, nothing > > > happens. However, if I edit a buffer, whether I save it or not, fvwm > > > crahses with a signal 11, dumping core. It is noted that, if I open an > > > aterm an THEN call vim, there's no problem. Also, other applications > > > called similarly (eg: aterm -name mutt -e mutt), cause no problem on exit > . > > > > > > Thank you very much for any help you might provide. > > > > We need a stack trace. > > #0 0x80a660a in XMapRaised () > #1 0x8112c00 in ?? () > #2 0x80743ea in XMapRaised () > #3 0x80745e2 in XMapRaised () > #4 0x806fe83 in XMapRaised () > #5 0x80700e2 in XMapRaised () > #6 0x8070170 in XMapRaised () > #7 0x8084849 in XMapRaised () > #8 0x804d491 in XMapRaised ()
Well, that's not going to help. The stack should lead back to the main. I don't have aterm to try this myself. If no one else picks this up, I'll see about installing aterm. It didn't cause any problem for me when I tried xterm instead of aterm. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
