Re: HEADS UP! KSE needs more attention

On Mon, Jun 07, 2004 at 02:32:11AM +0200, Matthias Andree wrote:
> Marcel Moolenaar <marcel_at_xcllnt.net> writes:
> 
> > As for alpha, we don't even seem to be able to degrade it to tier 2
> > without losing face. kris_at_ 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.

This is fixed in gdb 6.x:

GNU gdb 6.1.0.90_20040413 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "alpha-intree-freebsd"...
Core was generated by `abortme'.
Program terminated with signal 6, Aborted.
Reading symbols from /lib/libc.so.5...done.
Loaded symbols for /lib/libc.so.5
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x00000001601b29bc in kill () from /lib/libc.so.5
(gdb) l
1       #include <stdlib.h>
2       int main()
3       {
4               abort();
5       }
(gdb) bt
#0  0x00000001601b29bc in kill () from /lib/libc.so.5
#1  0x00000001601a5298 in raise () from /lib/libc.so.5
#2  0x0000000160233f88 in abort () from /lib/libc.so.5
#3  0x00000001200008a0 in main () at abortme.c:4
(gdb) 

An import of gdb 6.1 or gdb 6.1.1 will resolve this.

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel_at_xcllnt.net