From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA/doco] expand solib_unloaded documentation...
Date: Wed, 23 Sep 2009 22:43:00 -0000 [thread overview]
Message-ID: <20090923224315.GB5134@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
Hello,
It turns out from a discussion on when to reset watchpoint expressions
that it's important to know when solib_unloaded notifications are sent
(either before or after the solib's symbols are unloaded). Right now,
the notications are sent before, so this patch documents this fact.
2009-09-23 Joel Brobecker <brobecker@adacore.com>
* observer.texi (solib_unloaded): Document explicitly the fact that
this observer is called before the associated symbols are unloaded.
Tested by rebuilding gdb on x86_64-linux.
OK to apply?
Thanks,
--
Joel
[-- Attachment #2: solib_unloaded.diff --]
[-- Type: text/x-diff, Size: 819 bytes --]
commit 3bfb23d8921e95be5745080b913c0a81be6907fe
Author: Joel Brobecker <brobecker@adacore.com>
Date: Wed Sep 23 15:39:24 2009 -0700
* observer.texi (solib_unloaded): Document explicitly the fact that
this observer is called before the associated symbols are unloaded.
diff --git a/gdb/doc/observer.texi b/gdb/doc/observer.texi
index 4984f31..77d6b47 100644
--- a/gdb/doc/observer.texi
+++ b/gdb/doc/observer.texi
@@ -122,6 +122,8 @@ haven't been loaded yet.
@deftypefun void solib_unloaded (struct so_list *@var{solib})
The shared library specified by @var{solib} has been unloaded.
+Note that when @value{GDBN} calls this observer, the library's
+symbols have not been unloaded yet, and thus are still available.
@end deftypefun
@deftypefun void new_objfile (struct objfile *@var{objfile})
next reply other threads:[~2009-09-23 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 22:43 Joel Brobecker [this message]
2009-09-24 3:05 ` Eli Zaretskii
2009-09-24 17:50 ` Joel Brobecker
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=20090923224315.GB5134@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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