Re: [RFC - Python] New ObjFile event

Eli Zaretskii
2011-09-01T10:18:41Z

> 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.