From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: tromey@redhat.com, pmuldoon@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFC - Python] New ObjFile event
Date: Thu, 01 Sep 2011 11:01:00 -0000 [thread overview]
Message-ID: <E1Qz4Lp-0007E1-Kl@fencepost.gnu.org> (raw)
In-Reply-To: <CAPftXUKyge-BpB05PTn=5C=1HG6hgv8eS9rDYiZhooVMrrgZuQ@mail.gmail.com> (message from Kevin Pouget on Thu, 1 Sep 2011 11:17:51 +0200)
> From: Kevin Pouget <kevin.pouget@gmail.com>
> Date: Thu, 1 Sep 2011 11:17:51 +0200
> Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org
>
> This event indicates that the inferior or one of its threads has received as
> signal. @code{gdb.SignalEvent} has the following attributes:
>
> +@item events.newobjfile
> +Emits @code{gdb.NewObjFileEvent} which indicates that a new object-file has
> +been loaded by @value{GDBN}.
> +
> +During the callback, ``current objfile'' will be set to the new object file.
> +
> @table @code
> @defivar SignalEvent stop_signal
> A string representing the signal received by the inferior. A list of possible
> @@ -22949,10 +22955,10 @@ The following objfile-related functions are available in the
The addition doesn't look right: shouldn't it be _after_ the following
@table line? events.newobjfile is an attribute of the same object as
stop_signal, right?
> +When auto-loading a Python script (@pxref{Auto-loading}) and during new
> +object-file callbacks, @value{GDBN} sets the ``current objfile'' to the
Why did you use "new" here? New in relation to what?
Thanks.
next prev parent reply other threads:[~2011-09-01 10:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimybJtpUzy13FuLxQQMJfeWQuf3-cgqGmu23Bq5@mail.gmail.com>
2011-03-28 8:49 ` Kevin Pouget
2011-03-28 8:51 ` Kevin Pouget
2011-03-28 9:00 ` Phil Muldoon
2011-03-28 8:54 ` Phil Muldoon
2011-03-28 9:03 ` Phil Muldoon
2011-03-28 10:02 ` Kevin Pouget
2011-03-28 20:28 ` Tom Tromey
2011-03-29 11:11 ` Kevin Pouget
2011-03-30 11:32 ` Kevin Pouget
2011-03-30 12:14 ` Phil Muldoon
2011-03-30 12:15 ` Kevin Pouget
2011-05-19 20:21 ` Tom Tromey
2011-05-23 8:44 ` Kevin Pouget
2011-09-01 9:56 ` Kevin Pouget
2011-09-01 11:01 ` Eli Zaretskii [this message]
2011-09-01 11:09 ` Kevin Pouget
2011-10-03 16:32 ` Tom Tromey
[not found] ` <CAPftXULEe9R4m7tF=vtJe6NTXHSFAkXgsHCPb3r0mU4wKx0FFg@mail.gmail.com>
2011-10-04 8:25 ` Kevin Pouget
2011-10-04 17:02 ` Tom Tromey
2011-10-05 11:10 ` Kevin Pouget
2011-10-05 14:16 ` Tom Tromey
2011-10-05 17:40 ` Eli Zaretskii
2011-10-07 7:40 ` Kevin Pouget
2011-10-07 7:54 ` Kevin Pouget
2011-10-07 8:37 Andreas Tobler
2011-10-07 8:44 ` Kevin Pouget
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=E1Qz4Lp-0007E1-Kl@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevin.pouget@gmail.com \
--cc=pmuldoon@redhat.com \
--cc=tromey@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