Subject: Re: WM core
To: Jeremy C. Reed <reed@reedmedia.net>
From: Juergen Tritthardt <juergent@mpimf-heidelberg.mpg.de>
List: netbsd-users
Date: 03/31/2002 00:01:48
On Thu, 28 Mar 2002, Jeremy C. Reed wrote:
> On Thu, 28 Mar 2002, Juergen Tritthardt wrote:
>=20
> > The gzip core dump is still 150k big so I didn't attach it. I will
> > send it to anyone who's interested to help me.
>=20
> Is your WindowMaker built with debugging symbols? I guess if using a
> package it is stripped unless you have DEBUG_FLAGS defined.
>=20
> Anyways, to look at a core dump, use gdb like:
>=20
> gdb program core
>=20
> gdb `which wmaker` /path/to/wmaker.core
>=20
> Then type "bt" to show a few details.
I didn't manage to rebuild it unstripped with some mk.conf settings but I
just did a make in /usr/pkgsrc/wm/windowmaker an copied the unstripped
binary to the right position.
Now I get the following in gdb:
(gdb) bt
#0 0x482d4f97 in kill ()
#1 0x482d4171 in abort ()
#2 0x48297d9e in __assert ()
#3 0x8094773 in WMGetFromPLDictionary ()
#4 0x807c01d in wScreenRestoreState ()
#5 0x807ed4e in StartUp ()
#6 0x806c830 in main ()
#7 0x804d2d5 in ___start ()
Is it possible to say what caused the problem? Should I contact the
WindowMaker guys?
=09Regards
J=FCrgen
--=20
J=FCrgen Tritthardt Max-Planck-Institut f=FCr med. Forschung
Tel. 06221/486279 Abt. Biomedizinische Optik
Fax. 06221/486225 Jahnstr. 29, 69120 Heidelberg