From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cagney To: Stan Shebs Cc: Michael Snyder , gdb-patches@sourceware.cygnus.com Subject: Re: gdb.texinfo broken? Date: Tue, 21 Mar 2000 14:56:00 -0000 Message-id: <38D7FDD1.D54DE1D8@cygnus.com> References: <38D6CF69.6844@cygnus.com> <200003211819.NAA12435@indy.delorie.com> <38D7C977.FA3@cygnus.com> <5mitygglxs.fsf@jtc.redbacknetworks.com> X-SW-Source: 2000-03/msg00443.html "J.T. Conklin" wrote: > It looks like the changes to the directory entry require the latest > makeinfo. I tried to use makeinfo from texinfo-3.2 and it failed, > makeinfo from texinfo-4.0 works. >From memory, the possibility of requiring texinfo 4.0 as part of building GDB 5 was considered and rejected :-( oops, Andrew >From tromey@cygnus.com Tue Mar 21 15:03:00 2000 From: Tom Tromey To: "Peter.Schauer" Cc: gdb-patches@sourceware.cygnus.com, tromey@cygnus.com Subject: Re: RFA: minsyms.c: Fixes for serious demangled hash minsym lookup flaws. Date: Tue, 21 Mar 2000 15:03:00 -0000 Message-id: <200003212303.PAA22345@ferrule.cygnus.com> References: <200003212002.VAA19812@reisser.regent.e-technik.tu-muenchen.de> X-SW-Source: 2000-03/msg00444.html Content-length: 436 >>>>> "Peter" == Peter Schauer writes: Peter> There are two serious problems with the new demangled hash Peter> minsym lookup code, causing lookup of demangled names to fail. This would be my fault. Thanks. Note that when I wrote this patch, I did before-and-after testing against the gdb test suite with no regressions. It would be nice if there were test cases for this code. Tom >From kevinb@cygnus.com Tue Mar 21 15:07:00 2000 From: Kevin Buettner To: gdb-patches@sourceware.cygnus.com Subject: [PATCH] gdb.base/pointers.c commit Date: Tue, 21 Mar 2000 15:07:00 -0000 Message-id: <1000321230718.ZM26524@ocotillo.lan> X-SW-Source: 2000-03/msg00445.html Content-length: 1828 I've just committed the change below. (This change was for AIX 4.3.) * gdb.base/pointers.c (usevar): New function. (main): Make sure that global variables v_int_pointer2, rptr, and y are all referenced someplace in the program by calling usevar() on them. [Some linkers delete symbols which are never referenced. The space remains, but there's no way to get a (symbolic) handle on the variable from the debugger.] Index: gdb.base/pointers.c =================================================================== RCS file: /cvs/src/src/gdb/testsuite/gdb.base/pointers.c,v retrieving revision 1.1.1.3 diff -u -p -r1.1.1.3 pointers.c --- pointers.c 1999/08/02 23:46:51 1.1.1.3 +++ pointers.c 2000/03/21 22:59:17 @@ -71,35 +71,28 @@ float ** ptr_to_ptr_to_float; int y; +/* Do nothing function used for forcing some of the above variables to + be referenced by the program source. If the variables are not + referenced, some linkers will remove the symbol from the symbol + table making it impossible to refer to the variable in gdb. */ +void usevar (void *var) {} + int main () { - void dummy(); - int more_code(); - - /* Ensure that malloc is a pointer type; avoid use of "void" and any include files. */ - /* extern char *malloc();*/ - - /* void *malloc(size_t);*/ - - - + void dummy(); + int more_code(); + #ifdef usestubs set_debug_traps(); breakpoint(); #endif dummy(); -/* v_int_pointer2 = &v_int_pointer; - v_unsigned_int_pointer = &v_int; - - y = (v_unsigned_int_pointer == v_double_pointer); - - x = v_unsigned_int_pointer * v_double_pointer; - - v_unsigned_int_pointer = v_double_pointer; - - v_unsigned_int_pointer = v_unsigned_int;*/ more_code (); + + usevar (&v_int_pointer2); + usevar (&rptr); + usevar (&y); return 0;