Date: Mon, 07 Jun 2004 02:32:11 +0200 From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: current@freebsd.org Subject: Re: HEADS UP! KSE needs more attention Message-ID: <m34qpoqkc4.fsf@merlin.emma.line.org> In-Reply-To: <20040606211249.GC96607@dhcp50.pn.xcllnt.net> (Marcel Moolenaar's message of "Sun, 6 Jun 2004 14:12:49 -0700") References: <40C36D31.4010003@freebsd.org> <20040606193510.GA95886@dhcp50.pn.xcllnt.net> <40C37F3C.1050602@freebsd.org> <20040606211249.GC96607@dhcp50.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar <marcel@xcllnt.net> writes:
> As for alpha, we don't even seem to be able to degrade it to tier 2
> without losing face. kris@ has already stopped package builds for it
> for his own sake.
Alpha is special, with what seems to me like a GDB bug. Try this:
echo '#include <stdlib.h>
int main() {abort();}' >abortme.c
gcc -O2 -o abortme abortme.c
./abortme
gdb ./abortme ./core.abortme
(inside gdb:) backtrace
(inside gdb:) backtrace full
(inside gdb:) quit
This stuff is run as part of the ports/mail/bogofilter test suite (which
is part of the build) determine if core dumps from the build logs are
usable.
A couple of days ago, the backtrace of the trivial program ended up in
an unterminated loop on the build cluster, GDB kept repeating stack
frame #0. Whoops. The other architectures appeared fine though.
I haven't bothered to file a PR as I don't have an Alpha machine and
I'm not comfortable with filing second-hand bugs.
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m34qpoqkc4.fsf>