I don't know. I once looked at gdb code to see how they did backtraces and left feeling violated. I wouldn't mind a newer gdb that doesn't crash all the time.
On Sun, Nov 14, 2010 at 05:35:00PM +0000, Edd Barrett wrote: > On Sun, Nov 14, 2010 at 05:12:13PM +0100, Landry Breuil wrote: > > So, update gdb in base or make a recent gdb port, and 'ill happily import > > nemiver. > > On the scale of one to "oh my god my eyes burn", how hard is updating gdb? > > I was able to build the most recent gdb (with no patches) in my home dir > and do some trivial tests, but I refuse to believe it is that easy! > > Where is that catch? > > ire% ./gdb ~/test > GNU gdb (GDB) 7.2 > Copyright (C) 2010 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i386-unknown-openbsd4.8". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /home/edd/test...done. > (gdb) break 6 > Breakpoint 1 at 0x1c00074a: file a.c, line 6. > (gdb) run > Starting program: /home/edd/test > this is a test > > Breakpoint 1, dostuff (a=8, b=5, j=3.1415) at a.c:6 > 6 printf("%d %d %f\n", a, b, j); > (gdb) print a > $1 = 8 > (gdb) frame 0 > #0 dostuff (a=8, b=5, j=3.1415) at a.c:6 > 6 printf("%d %d %f\n", a, b, j); > (gdb) bt > #0 dostuff (a=8, b=5, j=3.1415) at a.c:6 > #1 0x1c0007d5 in main () at a.c:21 > > > -- > Best Regards > Edd Barrett > > http://www.theunixzoo.co.uk
