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.
Sorry, I guess I wasn't clear enough. We need a stack trace. Core files are usually only useful on the system they were generated on. To get a stack trace: cd to directory where core file is. get full path name to fvwm executable by typing which fvwm then run gdb supplying these 2 values: gdb full-path-fvwm name-of-core-file after gdb is done starting, type "where". That should print a stack trace (about 10 lines). Mail that. -- 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]
