I know it's not the right place to ask this question,
but according to my experiences I get 75% of my non-fvwm
related questions answered on this list and 0% on other
lists or newsgroups.
My problem is: since I upgraded from SuSE 6.2 to SuSE 6.4
(Linux 2.2.14, i386), all generated core files seem to be
corrupt. Whenever I call gdb to get a stack trace all I
get is something like this:
$ gdb <program> core
warning: wrong size gregset struct in core file
warning: wrong size fpregset struct in core file
#0 0x0 in ?? ()
(gdb) where
#0 0x0 in ?? ()
I've already tried to recompile gdb, but to no avail. With
my old SuSE 6.2 (kernel 2.2.10), fvwm's core dumps were
about 1.5 meg, but not they are only 300k. I guess there
is a connection. I can vaguely remember that there is some
way to reduce the information in a core file, but perhaps
this was on AIX. BTW, of course I do not limit core dump
size with ulimit.
Bye
Dominik ^_^
--
Dominik Vogt, dominik.vogt_at_gmx.de
Reply-To: dominik.vogt_at_gmx.de
--
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 Sat May 06 2000 - 15:52:18 BST