Date: Sun, 22 Sep 2002 13:47:26 -0400 From: Alexander Kabaev <kabaev@bellatlantic.net> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: ak03@gte.com, current@FreeBSD.ORG Subject: Re: buildworld fails in gnu/usr.bin/gperf/doc with an internal error Message-ID: <20020922134726.717fe34a.kabaev@bellatlantic.net> In-Reply-To: <20020922181052.4db1cf0f.Alexander@Leidinger.net> References: <20020922172014.26056daa.Alexander@Leidinger.net> <20020922112708.5f35315f.kabaev@bellatlantic.net> <20020922181052.4db1cf0f.Alexander@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> This is with a gcc 3.1 world, the internal error is in "stage 1:
> bootstrap tools" and gcc 3.2 isn't build at this point. Do you still
> want the backtrace?
Yes.
>
> If yes: I can't find a *.core in /usr/{src,obj}, there's no coredump
> limit, so how do I get the backtrace? I already tried to go into
> gnu/usr.bin/gperf and make a "make cleandir; make cleandir; make", but
> I don't get a coredump.
>
> I also tried to run it withhin gdb, but c++ exists with something like
> exit(1) and thats it, no way to make a backtrace.
What does kernel log say? When process dies with signal, kernel usually
logs the event. If anything, this should give you the name of the
process which has died. Running 'gcc' or 'c++' under debugger is not
very helpful, because these are just driver programs. The real processes
which do the work are cpp1, cc1, ccp1 etc.
--
Alexander Kabaev
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020922134726.717fe34a.kabaev>