From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Remove CLEAR_SOLIB
Date: Wed, 14 Nov 2007 11:59:00 -0000 [thread overview]
Message-ID: <200711141457.52644.vladimir@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 160 bytes --]
It turns out that CLEAR_SOLIB macro is being tested
for in a couple of places, but it never set anywhere.
This patch removes all traces of it. OK?
- Volodya
[-- Attachment #2: CLEAR_SOLIB.diff --]
[-- Type: text/x-diff, Size: 1450 bytes --]
commit e1c46bff8634642eb8b98264ef020c30fefe1907
Author: Vladimir Prus <vladimir@codesourcery.com>
Date: Wed Nov 14 14:55:49 2007 +0300
Remove CLEAR_SOLIB use.
diff --git a/gdb/corelow.c b/gdb/corelow.c
index 07be3f4..faae451 100644
--- a/gdb/corelow.c
+++ b/gdb/corelow.c
@@ -199,11 +199,7 @@ core_close (int quitting)
/* Clear out solib state while the bfd is still open. See
comments in clear_solib in solib.c. */
-#ifdef CLEAR_SOLIB
- CLEAR_SOLIB ();
-#else
clear_solib ();
-#endif
name = bfd_get_filename (core_bfd);
if (!bfd_close (core_bfd))
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index e40dd4e..119eb7c 100644
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -4675,10 +4675,6 @@ the shell execs, and once when the program itself execs. If the actual
number of traps is something other than 2, then define this macro to
expand into the number expected.
-@item CLEAR_SOLIB
-@findex CLEAR_SOLIB
-See @file{objfiles.c}.
-
@end table
@node Support Libraries
diff --git a/gdb/infcmd.c b/gdb/infcmd.c
index 2fb0f23..079d586 100644
--- a/gdb/infcmd.c
+++ b/gdb/infcmd.c
@@ -1887,11 +1887,7 @@ attach_command (char *args, int from_tty)
(gdb) attach 4712
Cannot access memory at address 0xdeadbeef
*/
-#ifdef CLEAR_SOLIB
- CLEAR_SOLIB ();
-#else
- clear_solib ();
-#endif
+ clear_solib ();
target_attach (args, from_tty);
next reply other threads:[~2007-11-14 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 11:59 Vladimir Prus [this message]
2007-11-14 13:20 ` Daniel Jacobowitz
2007-11-15 6:21 ` Vladimir Prus
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=200711141457.52644.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.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