On 24 Jan 2005 10:22:42 +0800, GuanFu Chen wrote:
>
> On 23 Jan 2005 18:14:35 +0000, Mikhael Goikhman <migo_at_homemail.com> wrote:
> >
> > What fvwm version do you run?
>
> fvwm 2.5.12 compiled on Nov 20 2004 at 21:26:15
>
> > Do you get "core" file?
>
> What core file?
Search for file like "core" or "core.13579" in your starting directory.
If it is compiled with -g flag (that I doubt if you use deb), then
type "gdb fvwm core" and then "where" and post relevant (or all) lines,
but only if you see source file lines together with C function names.
If your fvwm binary does not contain the debug info, then the only way to
find the source of this problem is to compile fvwm manually and try to
crash fvwm to get this core file. [There are cases when rebuilding may
"fix" a problem if it was system related, i.e. bugs in gcc or libraries.]
Regards,
Mikhael.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Jan 24 2005 - 15:23:23 GMT