Date: Fri, 02 May 1997 12:53:01 +0000 From: Gary Jennejohn <garyj@munich.netsurf.de> To: KATO Takenori <kato@eclogite.eps.nagoya-u.ac.jp> Cc: freebsd-current@freebsd.org Subject: Re: gdb broken ? Message-ID: <199705021253.MAA17508@peedub.gj.org> In-Reply-To: Your message of "Fri, 02 May 1997 19:16:06 %2B0900." <199705021016.TAA00349@gneiss.eps.nagoya-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
KATO Takenori writes: >From: Gary Jennejohn <Gary.Jennejohn@munich.netsurf.de> >Subject: gdb broken ? >Date: Fri, 02 May 1997 11:12:13 +0000 > >> ``GDB can't read core files on this machine.'' >> >> I've tried doing a cleandir in /usr/src and even making gdb in >> a freshly checked-out directory. No dice. >> >> Is it just me, or has anyone else seen this ? > >I got same problem. I cannot analyze vmcore :-(. > I figured out what it is. init.c is calling _initialize_kcorelow() twice. That's because (mea culpa) the totally unneeded kcorelow.c is listed in the XSRCS. kcorelow.c is always empty because its compilation is controlled by KERNEL_DEBUGGING, which isn't defined anywhere. However, the generation of init.c isn't smart enough to know that it shouldn't pull the _initialize_kcorelow in from kcorelow.c. Only the reference from kvm-fbsd.c is needed. Just delete kcorelow.c from the list of sources, regenerate init.c and everything should work. That's what I did and gdb is now OK. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705021253.MAA17508>