From: Andrew Cagney <ac131313@cygnus.com>
To: Stan Shebs <shebs@apple.com>
Cc: Michael Snyder <msnyder@cygnus.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: gdb.texinfo broken?
Date: Tue, 21 Mar 2000 14:56:00 -0000 [thread overview]
Message-ID: <38D7FDD1.D54DE1D8@cygnus.com> (raw)
In-Reply-To: <5mitygglxs.fsf@jtc.redbacknetworks.com>
"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 <tromey@cygnus.com>
To: "Peter.Schauer" <Peter.Schauer@Regent.E-Technik.TU-Muenchen.DE>
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 <Peter.Schauer@Regent.E-Technik.TU-Muenchen.DE> 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 <kevinb@cygnus.com>
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;
next prev parent reply other threads:[~2000-03-21 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38D6CF69.6844@cygnus.com>
[not found] ` <200003211819.NAA12435@indy.delorie.com>
[not found] ` <38D7C977.FA3@cygnus.com>
2000-03-21 11:31 ` J.T. Conklin
2000-03-21 14:56 ` Andrew Cagney [this message]
2000-04-01 0:00 ` Dmitry Sivachenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38D7FDD1.D54DE1D8@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=msnyder@cygnus.com \
--cc=shebs@apple.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox