From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sources.redhat.com, nickrob@snap.net.nz
Subject: Re: MI solib notification
Date: Tue, 17 Feb 2009 21:37:00 -0000 [thread overview]
Message-ID: <20090217211159.GA25430@caradoc.them.org> (raw)
In-Reply-To: <200902172244.48437.vladimir@codesourcery.com>
On Tue, Feb 17, 2009 at 10:44:48PM +0300, Vladimir Prus wrote:
> commit c1091d19fe7c4b02bb5ea623761e4caa0d6fe537
> Author: Vladimir Prus <vladimir@codesourcery.com>
> Date: Fri Jan 30 20:50:50 2009 +0300
>
> Implement MI notification for library loading/unloading
>
> gdb/doc/
> * gdb.texinfo (GDB/MI Async Records): Document the
> =library-loaded and =library-unloaded notifications.
>
> gdb/
> * mi/mi-interp.c (mi_solib_loaded, mi_solib_unloaded): New.
> (mi_interpreter_init): Register the above.
> * solib.c (clear_solib): Notify solib unload.
> * breakpoint.c (disable_breakpoints_in_unloaded_shlib): Do not
> disable breakpoints on a.out targets.
>
> gdb/testsuite/
> * gdb.mi/mi-nonstop.exp (notifs): Adjust for library notifications.
> * gdb.mi/mi-nsintrall.exp (notifs): Likewise.
> * gdb.mi/mi-nsmoribund.exp (notifs): Likewise.
> * lib/mi-support.exp (library_loaded_re): New.
> (mi_run_cmd, mi_send_resuming_command_raw): Adjust.
The code portions of this are OK now, thanks.
> +static void mi_solib_loaded (struct so_list *solib)
> +static void mi_solib_unloaded (struct so_list *solib)
Newline after void please.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-02-17 21:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 23:44 Vladimir Prus
[not found] ` <utz7gzcmo.fsf@gnu.org>
2009-02-01 17:53 ` Daniel Jacobowitz
2009-02-01 18:22 ` Eli Zaretskii
2009-02-01 18:29 ` Daniel Jacobowitz
2009-02-17 19:09 ` Vladimir Prus
2009-02-17 19:45 ` Eli Zaretskii
2009-02-17 19:49 ` Vladimir Prus
2009-02-17 20:30 ` Eli Zaretskii
2009-02-17 21:45 ` Vladimir Prus
2009-02-17 21:59 ` Vladimir Prus
2009-02-18 7:31 ` Eli Zaretskii
2009-02-18 10:19 ` Vladimir Prus
2009-02-18 19:53 ` Eli Zaretskii
2009-02-18 20:04 ` Vladimir Prus
2009-02-18 22:28 ` Eli Zaretskii
2009-02-18 4:24 ` Eli Zaretskii
2009-02-17 21:37 ` Daniel Jacobowitz [this message]
2009-02-17 22:10 ` Pedro Alves
2009-02-18 2:01 ` Pedro Alves
2009-02-01 18:04 ` Daniel Jacobowitz
2009-02-12 9:12 ` Vladimir Prus
2009-02-12 13:22 ` Daniel Jacobowitz
2009-02-12 15:02 ` Vladimir Prus
2009-02-12 15:13 ` Daniel Jacobowitz
2009-02-12 17:35 ` Tom Tromey
2009-02-12 18:02 ` Daniel Jacobowitz
2009-02-12 20:11 ` Tom Tromey
2009-02-12 20:17 ` Vladimir Prus
2009-02-12 20:26 ` Daniel Jacobowitz
2009-02-17 19:08 ` Vladimir Prus
2009-02-12 18:06 ` Pedro Alves
2009-02-12 19:45 ` Pedro Alves
2009-02-12 19:56 ` Tom Tromey
2009-02-12 19:58 ` Daniel Jacobowitz
2009-02-13 2:22 ` Joel Brobecker
2009-02-01 18:47 ` Daniel Jacobowitz
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=20090217211159.GA25430@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
--cc=vladimir@codesourcery.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