Eduardo Alvarez <[EMAIL PROTECTED]> writes: > > --AqsLC8rIMeq19msA > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > 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.
I've installed aterm 0.4.2. I started an aterm, then typed: aterm -name vim -e vim xxx That gave me a new window running vim. I typed a few characters, then saved the file and exited with ZZ. No problem. I notice that aterm can be compiled with "Afterstep support". When I configured aterm, it didn't use that option. I'm not sure if that would be shown with --help. Here's what I get: [EMAIL PROTECTED] tmp]$ aterm --help Usage v0.4.2 :(XPM,transparency,no fading,NeXT scrollbar,.Xdefaults) aterm [options] [-e command args] As far as the stack dump showing meaningless information, all I can suggest for that is to build fvwm yourself if you haven't done that already. -- 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]
