1999-04-16 09:35:26 +08:00
|
|
|
What has changed in GDB?
|
|
|
|
|
(Organized release by release)
|
|
|
|
|
|
2024-05-27 00:02:38 +08:00
|
|
|
*** Changes since GDB 15
|
|
|
|
|
|
2024-03-06 19:22:49 +08:00
|
|
|
* Debugging support for Intel MPX has been removed. This includes the
|
|
|
|
|
removal of
|
|
|
|
|
** MPX register support
|
|
|
|
|
** the commands "show/set mpx bound" (deprecated since GDB 15)
|
|
|
|
|
** i386 and amd64 implementation of the hooks report_signal_info and
|
|
|
|
|
get_siginfo_type.
|
|
|
|
|
|
2023-06-28 16:15:04 +08:00
|
|
|
* GDB now supports printing of asynchronous events from the Intel Processor
|
|
|
|
|
Trace during 'record instruction-history', 'record function-call-history'
|
|
|
|
|
and all stepping commands. This can be controlled with the new
|
|
|
|
|
"set record btrace pt event-tracing" command.
|
|
|
|
|
|
2019-02-18 22:50:49 +08:00
|
|
|
* GDB now supports printing of ptwrite payloads from the Intel Processor
|
|
|
|
|
Trace during 'record instruction-history', 'record function-call-history'
|
|
|
|
|
and all stepping commands. The payload is also accessible in Python as a
|
|
|
|
|
RecordAuxiliary object. Printing is customizable via a ptwrite filter
|
|
|
|
|
function in Python. By default, the raw ptwrite payload is printed for
|
|
|
|
|
each ptwrite that is encountered.
|
|
|
|
|
|
gdb: parse pending breakpoint thread/task immediately
The initial motivation for this commit was to allow thread or inferior
specific breakpoints to only be inserted within the appropriate
inferior's program-space. The benefit of this is that inferiors for
which the breakpoint does not apply will no longer need to stop, and
then resume, for such breakpoints. This commit does not make this
change, but is a refactor to allow this to happen in a later commit.
The problem we currently have is that when a thread-specific (or
inferior-specific) breakpoint is created, the thread (or inferior)
number is only parsed by calling find_condition_and_thread_for_sals.
This function is only called for non-pending breakpoints, and requires
that we know the locations at which the breakpoint will be placed (for
expression checking in case the breakpoint is also conditional).
A consequence of this is that by the time we figure out the breakpoint
is thread-specific we have already looked up locations in all program
spaces. This feels wasteful -- if we knew the thread-id earlier then
we could reduce the work GDB does by only looking up locations within
the program space for which the breakpoint applies.
Another consequence of how find_condition_and_thread_for_sals is
called is that pending breakpoints don't currently know they are
thread-specific, nor even that they are conditional! Additionally, by
delaying parsing the thread-id, pending breakpoints can be created for
non-existent threads, this is different to how non-pending
breakpoints are handled, so I can do this:
$ gdb -q ./gdb/testsuite/outputs/gdb.multi/pending-bp/pending-bp
Reading symbols from ./gdb/testsuite/outputs/gdb.multi/pending-bp/pending-bp...
(gdb) break foo thread 99
Function "foo" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (foo thread 99) pending.
(gdb) r
Starting program: /tmp/gdb/testsuite/outputs/gdb.multi/pending-bp/pending-bp
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Error in re-setting breakpoint 1: Unknown thread 99.
[Inferior 1 (process 3329749) exited normally]
(gdb)
GDB only checked the validity of 'thread 99' at the point the 'foo'
location became non-pending. In contrast, if I try this:
$ gdb -q ./gdb/testsuite/outputs/gdb.multi/pending-bp/pending-bp
Reading symbols from ./gdb/testsuite/outputs/gdb.multi/pending-bp/pending-bp...
(gdb) break main thread 99
Unknown thread 99.
(gdb)
GDB immediately checks if 'thread 99' exists. I think inconsistencies
like this are confusing, and should be fixed if possible.
In this commit the create_breakpoint function is updated so that the
extra_string, which contains the thread, inferior, task, and/or
condition information, is parsed immediately, even for pending
breakpoints.
Obviously, the condition still can't be validated until the breakpoint
becomes non-pending, but the thread, inferior, and task information
can be pulled from the extra-string, and can be validated early on,
even for pending breakpoints. The -force-condition flag is also
parsed as part of this early parsing change.
There are a couple of benefits to doing this:
1. Printing of breakpoints is more consistent now. Consider creating
a conditional breakpoint before this commit:
(gdb) set breakpoint pending on
(gdb) break pendingfunc if (0)
Function "pendingfunc" not defined.
Breakpoint 1 (pendingfunc if (0)) pending.
(gdb) break main if (0)
Breakpoint 2 at 0x401198: file /tmp/hello.c, line 18.
(gdb) info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep y <PENDING> pendingfunc if (0)
2 breakpoint keep y 0x0000000000401198 in main at /tmp/hello.c:18
stop only if (0)
(gdb)
And after this commit:
(gdb) set breakpoint pending on
(gdb) break pendingfunc if (0)
Function "pendingfunc" not defined.
Breakpoint 1 (pendingfunc) pending.
(gdb) break main if (0)
Breakpoint 2 at 0x401198: file /home/andrew/tmp/hello.c, line 18.
(gdb) info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep y <PENDING> pendingfunc
stop only if (0)
2 breakpoint keep y 0x0000000000401198 in main at /home/andrew/tmp/hello.c:18
stop only if (0)
(gdb)
Notice that the display of the condition is now the same for the
pending and non-pending breakpoints.
The same is true for the thread, inferior, or task information in
thread, inferior, or task specific breakpoints; this information is
displayed on its own line rather than being part of the 'What'
field.
2. We can check that the thread exists as soon as the pending
breakpoint is created. Currently there is a weird difference
between pending and non-pending breakpoints when creating a
thread-specific breakpoint.
A pending thread-specific breakpoint only checks its thread when it
becomes non-pending, at which point the thread the breakpoint was
intended for might have exited. Here's the behaviour before this
commit:
(gdb) set breakpoint pending on
(gdb) break foo thread 2
Function "foo" not defined.
Breakpoint 2 (foo thread 2) pending.
(gdb) c
Continuing.
[Thread 0x7ffff7c56700 (LWP 2948835) exited]
Error in re-setting breakpoint 2: Unknown thread 2.
[Inferior 1 (process 2948832) exited normally]
(gdb)
Notice the 'Error in re-setting breakpoint 2: Unknown thread 2.'
line, this was triggered when GDB tried to make the breakpoint
non-pending, and GDB discovers that the thread no longer exists.
Compare that to the behaviour after this commit:
(gdb) set breakpoint pending on
(gdb) break foo thread 2
Function "foo" not defined.
Breakpoint 2 (foo) pending.
(gdb) c
Continuing.
[Thread 0x7ffff7c56700 (LWP 2949243) exited]
Thread-specific breakpoint 2 deleted - thread 2 no longer in the thread list.
[Inferior 1 (process 2949240) exited normally]
(gdb)
Now the behaviour for pending breakpoints is identical to
non-pending breakpoints, the thread specific breakpoint is removed
as soon as the thread the breakpoint is associated with exits.
There is an additional change; when the pending breakpoint is
created prior to this patch we see this line:
Breakpoint 2 (foo thread 2) pending.
While after this patch we get this line:
Breakpoint 2 (foo) pending.
Notice that 'thread 2' has disappeared. This might look like a
regression, but I don't think it is. That we said 'thread 2'
before was just a consequence of the lazy parsing of the breakpoint
specification, while with this patch GDB understands, and has
parsed away the 'thread 2' bit of the spec. If folk think the old
information was useful then this would be trivial to add back in
code_breakpoint::say_where.
As a result of this commit the breakpoints 'extra_string' field is now
only used by bp_dprintf type breakpoints to hold the printf format and
arguments. This string should always be empty for other breakpoint
types. This allows some cleanup in print_breakpoint_location.
In code_breakpoint::code_breakpoint I've changed an error case into an
assert. This is because the error is now handled earlier in
create_breakpoint. As a result we know that by this point, the
extra_string will always be nullptr for anything other than a
bp_dprintf style breakpoint.
The find_condition_and_thread_for_sals function is now no longer
needed, this was previously doing the delayed splitting of the extra
string into thread, task, and condition, but this is now all done in
create_breakpoint, so find_condition_and_thread_for_sals can be
deleted, and the code that calls this in
code_breakpoint::location_spec_to_sals can be removed. With this
update this code would only ever be reached for bp_dprintf style
breakpoints, and in these cases the extra_string should not contain
anything other than format and args.
The most interesting changes are all in create_breakpoint and in the
new file break-cond-parse.c. We have a new block of code early on in
create_breakpoint that is responsible for splitting the extra_string
into its component parts by calling create_breakpoint_parse_arg_string
a function in the new break-cond-parse.c file. This means that some
of the later code can be simplified a little.
The new break-cond-parse.c file implements the splitting up the
extra_string and finding all the parts, as well as some self-tests for
the new function.
Finally, now we know all the breakpoint details, these can be stored
within the breakpoint object if we end up creating a deferred
breakpoint. Additionally, if we are creating a deferred bp_dprintf we
can parse the extra_string to build the printf command.
The implementation here aims to maintain backwards compatibility as
much as possible, this means that:
1. We support abbreviations of 'thread', 'task', and 'inferior' in
some places on the breakpoint line. The handling of abbreviations
has (before this patch) been a little weird, so this works:
(gdb) break *main th 1
And creates a breakpoint at '*main' for thread 1 only, while this
does not work:
(gdb) break main th 1
In this case GDB will try to find the symbol 'main th 1'. This
weirdness exists before and after this patch.
2. The handling of '-force-condition' is odd, if this flag appears
immediately after a condition then it will be treated as part of the
condition, e.g.:
(gdb) break main if 0 -force-condition
No symbol "force" in current context.
But we are fine with these alternatives:
(gdb) break main if 0 thread 1 -force-condition
(gdb) break main -force-condition if 0
Again, this is just a quirk of how the breakpoint line used to be
parsed, but I've maintained this for backward compatibility. During
review it was suggested that -force-condition should become an
actual breakpoint flag (i.e. only valid after the 'break' command
but before the function name), and I don't think that would be a
terrible idea, however, that's not currently a trivial change, and I
think should be done as a separate piece of work. For now, this
patch just maintains the current behaviour.
The implementation works by first splitting the breakpoint condition
string (everything after the location specification) into a list of
tokens, each token has a type and a value. (e.g. we have a THREAD
token where the value is the thread-id string). The list of tokens is
validated, and in some cases, tokens are merged. Then the values are
extracted from the remaining token list.
Consider this breakpoint command:
(gdb) break main thread 1 if argc == 2
The condition string passed to create_breakpoint_parse_arg_string is
going to be 'thread 1 if argc == 2', which is then split into the
tokens:
{ THREAD: "1" } { CONDITION: "argc == 2" }
The thread-id (1) and the condition string 'argc == 2' are extracted
from these tokens and returns back to create_breakpoint.
Now consider this breakpoint command:
(gdb) break some_function if ( some_var == thread )
Here the user wants a breakpoint if 'some_var' is equal to the
variable 'thread'. However, when this is initially parsed we will
find these tokens:
{ CONDITION: "( some_var == " } { THREAD: ")" }
This is a consequence of how we have to try and figure out the
contents of the 'if' condition without actually parsing the
expression; parsing the expression requires that we know the location
in order to lookup the variables by name, and this can't be done for
pending breakpoints (their location isn't known yet), and one of the
points of this work is that we extract things like thread-id for
pending breakpoints.
And so, it is in this case that token merging takes place. We check
if the value of a token appearing immediately after the CONDITION
token looks valid. In this case, does ')' look like a valid
thread-id. Clearly, in this case ')' does not, and so me merge the
THREAD token into the condition token, giving:
{ CONDITION: "( some_var == thread )" }
Which is what we want.
I'm sure that we might still be able to come up with some edge cases
where the parser makes the wrong choice. I think long term the best
way to work around these would be to move the thread, inferior, task,
and -force-condition flags to be "real" command options for the break
command. I am looking into doing this, but can't guarantee if/when
that work would be completed, so this patch should be reviewed assume
that the work will never arrive (though I hope it will).
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
2023-03-31 02:21:22 +08:00
|
|
|
* For breakpoints that are created in the 'pending' state, any
|
|
|
|
|
'thread' or 'task' keywords are parsed at the time the breakpoint is
|
|
|
|
|
created, rather than at the time the breakpoint becomes non-pending.
|
|
|
|
|
|
gdb: only insert thread-specific breakpoints in the relevant inferior
This commit updates GDB so that thread or inferior specific
breakpoints are only inserted into the program space in which the
specific thread or inferior is running.
In terms of implementation, getting this basically working is easy
enough, now that a breakpoint's thread or inferior field is setup
prior to GDB looking for locations, we can easily use this information
to find a suitable program_space and pass this to as a filter when
creating the sals.
Or we could if breakpoint_ops::create_sals_from_location_spec allowed
us to pass in a filter program_space.
So, this commit extends breakpoint_ops::create_sals_from_location_spec
to take a program_space argument, and uses this to filter the set of
returned sals. This accounts for about half the change in this patch.
The second set of changes starts from breakpoint_set_thread and
breakpoint_set_inferior, this is called when the thread or inferior
for a breakpoint changes, e.g. from the Python API.
Previously this call would never result in the locations of a
breakpoint changing, after all, locations were inserted in every
program space, and we just use the thread or inferior variable to
decide when we should stop. Now though, changing a breakpoint's
thread or inferior can mean we need to figure out a new set of
breakpoint locations.
To support this I've added a new breakpoint_re_set_one function, which
is like breakpoint_re_set, but takes a single breakpoint, and just
updates the locations for that one breakpoint. We only need to call
this function if the program_space in which a breakpoint's thread (or
inferior) is running actually changes. If the program_space does
change then we call the new breakpoint_re_set_one function passing in
the program_space which should be used to filter the new locations (or
nullptr to indicate we should set locations in all program spaces).
This filter program_space needs to propagate down to all the re_set
methods, this accounts for the remaining half of the changes in this
patch.
There were a couple of existing tests that created thread or inferior
specific breakpoints and then checked the 'info breakpoints' output,
these needed updating. These were:
gdb.mi/user-selected-context-sync.exp
gdb.multi/bp-thread-specific.exp
gdb.multi/multi-target-continue.exp
gdb.multi/multi-target-ping-pong-next.exp
gdb.multi/tids.exp
gdb.mi/new-ui-bp-deleted.exp
gdb.multi/inferior-specific-bp.exp
gdb.multi/pending-bp-del-inferior.exp
I've also added some additional tests to:
gdb.multi/pending-bp.exp
I've updated the documentation and added a NEWS entry.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
2023-03-04 03:03:15 +08:00
|
|
|
* Thread-specific breakpoints are only inserted into the program space
|
|
|
|
|
in which the thread of interest is running. In most cases program
|
|
|
|
|
spaces are unique for each inferior, so this means that
|
|
|
|
|
thread-specific breakpoints will usually only be inserted for the
|
|
|
|
|
inferior containing the thread of interest. The breakpoint will
|
|
|
|
|
be hit no less than before.
|
|
|
|
|
|
2024-06-19 15:52:01 +08:00
|
|
|
* For ARM targets, the offset of the pc in the jmp_buf has been fixed to match
|
|
|
|
|
glibc 2.20 and later. This should only matter when not using libc probes.
|
|
|
|
|
This may cause breakage when using an incompatible libc, like uclibc or
|
|
|
|
|
newlib, or an older glibc.
|
|
|
|
|
|
2024-07-30 22:39:36 +08:00
|
|
|
* MTE (Memory Tagging Extension) debugging is now supported on AArch64 baremetal
|
|
|
|
|
targets.
|
|
|
|
|
|
2024-08-12 22:29:36 +08:00
|
|
|
* Remove support (native and remote) for QNX Neutrino (triplet
|
|
|
|
|
`i[3456]86-*-nto*`).
|
|
|
|
|
|
Change message when reaching end of reverse history.
In a record session, when we move backward, GDB switches from normal
execution to simulation. Moving forward again, the emulation continues
until the end of the reverse history. When the end is reached, the
execution stops, and a warning message is shown. This message has been
modified to indicate that the forward emulation has reached the end, but
the execution can continue as normal, and the recording will also continue.
Before this patch, the warning message shown in that case was the same as
in the reverse case. This meant that when the end of history was reached in
either backward or forward emulation, the same message was displayed:
"No more reverse-execution history."
This message has changed for these two cases. Backward emulation:
"Reached end of recorded history; stopping.
Backward execution from here not possible."
Forward emulation:
"Reached end of recorded history; stopping.
Following forward execution will be added to history."
The reason for this change is that the initial message was deceiving, for
the forward case, making the user believe that forward debugging could not
continue.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31224
Reviewed-By: Markus T. Metzger <markus.t.metzger@intel.com> (btrace)
Approved-By: Guinevere Larsen <blarsen@redhat.com>
2024-08-26 21:33:17 +08:00
|
|
|
* In a record session, when a forward emulation reaches the end of the reverse
|
|
|
|
|
history, the warning message has been changed to indicate that the end of the
|
|
|
|
|
history has been reached. It also specifies that the forward execution can
|
|
|
|
|
continue, and the recording will also continue.
|
|
|
|
|
|
2024-09-19 02:44:42 +08:00
|
|
|
* The Ada 'Object_Size attribute is now supported.
|
|
|
|
|
|
2024-09-09 18:27:30 +08:00
|
|
|
* Python API
|
|
|
|
|
|
|
|
|
|
** Added gdb.record.clear. Clears the trace data of the current recording.
|
|
|
|
|
This forces re-decoding of the trace for successive commands.
|
|
|
|
|
|
2024-09-25 22:27:51 +08:00
|
|
|
** Added the new event source gdb.tui_enabled.
|
|
|
|
|
|
gdb/python: implement Python find_exec_by_build_id hook
Implement extension_language_ops::find_objfile_from_buildid within
GDB's Python API. Doing this allows users to write Python extensions
that can help locate missing objfiles when GDB opens a core file. A
handler might perform some project- or site-specific actions to find a
missing objfile. Or might provide some project- or site-specific
advice to the user on how they can obtain the missing objfile.
The implementation is very similar to the approach taken in:
commit 8f6c452b5a4e50fbb55ff1d13328b392ad1fd416
Date: Sun Oct 15 22:48:42 2023 +0100
gdb: implement missing debug handler hook for Python
The following new commands are added as commands implemented in
Python, this is similar to how the Python missing debug and unwinder
commands are implemented:
info missing-objfile-handlers
enable missing-objfile-handler LOCUS HANDLER
disable missing-objfile-handler LOCUS HANDLER
To make use of this extension hook a user will create missing objfile
handler objects, and registers these handlers with GDB. When GDB
opens a core file and encounters a missing objfile each handler is
called in turn until one is able to help. Here is a minimal handler
that does nothing useful:
import gdb
import gdb.missing_objfile
class MyFirstHandler(gdb.missing_objfile.MissingObjfileHandler):
def __init__(self):
super().__init__("my_first_handler")
def __call__(self, pspace, build_id, filename):
# This handler does nothing useful.
return None
gdb.missing_objfile.register_handler(None, MyFirstHandler())
Returning None from the __call__ method tells GDB that this handler
was unable to find the missing objfile, and GDB should ask any other
registered handlers.
Possible return values from a handler:
- None: This means the handler couldn't help. GDB will call other
registered handlers to see if they can help instead.
- False: The handler has done all it can, but the objfile couldn't
be found. GDB will not call any other handlers, and will
continue without the objfile.
- True: The handler has installed the objfile into a location where
GDB would normally expect to find it. GDB should repeat its
normal lookup process and the objfile should now be found.
- A string: The handler can return a filename, which is the missing
objfile. GDB will load this file.
Handlers can be registered globally, or per program space. GDB checks
the handlers for the current program space first, and then all of the
global handles. The first handler that returns a value that is not
None, has "handled" the missing objfile, at which point GDB continues.
The implementation of this feature is mostly straight forward. I have
reworked some of the missing debug file related code so that it can be
shared with this feature. E.g. gdb/python/lib/gdb/missing_files.py is
mostly content moved from gdb/python/lib/gdb/missing_debug.py, but
updated to be more generic. Now gdb/python/lib/gdb/missing_debug.py
and the new file gdb/python/lib/gdb/missing_objfile.py both call into
the missing_files.py file.
For gdb/python/lib/gdb/command/missing_files.py this is even more
extreme, gdb/python/lib/gdb/command/missing_debug.py is completely
gone now and gdb/python/lib/gdb/command/missing_files.py provides all
of the new commands in a generic way.
I have made one change to the existing Python API, I renamed the
attribute Progspace.missing_debug_handlers to
Progspace.missing_file_handlers. I don't see this as too
problematic. This attribute was only used to implement the missing
debug feature and was never documented beyond the fact that it
existed. There was no reason for users to be touching this attribute.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
2024-07-31 22:55:57 +08:00
|
|
|
** New module gdb.missing_objfile that facilitates dealing with
|
|
|
|
|
missing objfiles when opening a core-file.
|
|
|
|
|
|
|
|
|
|
** New function gdb.missing_objfile.register_handler that can
|
|
|
|
|
register an instance of a sub-class of
|
|
|
|
|
gdb.missing_debug.MissingObjfileHandler as a handler for missing
|
|
|
|
|
objfiles.
|
|
|
|
|
|
|
|
|
|
** New class gdb.missing_objfile.MissingObjfileHandler which can be
|
|
|
|
|
sub-classed to create handlers for missing objfiles.
|
|
|
|
|
|
2024-09-09 18:27:30 +08:00
|
|
|
* Debugger Adapter Protocol changes
|
|
|
|
|
|
|
|
|
|
** The "scopes" request will now return a scope holding global
|
|
|
|
|
variables from the stack frame's compilation unit.
|
|
|
|
|
|
|
|
|
|
** The "scopes" request will return a "returnValue" scope holding
|
|
|
|
|
the return value from the latest "stepOut" command, when
|
|
|
|
|
appropriate.
|
|
|
|
|
|
2024-07-31 14:42:56 +08:00
|
|
|
* New commands
|
|
|
|
|
|
2024-09-15 05:07:17 +08:00
|
|
|
set style line-number foreground COLOR
|
|
|
|
|
set style line-number background COLOR
|
|
|
|
|
set style line-number intensity VALUE
|
|
|
|
|
Control the styling of line numbers printed by GDB.
|
|
|
|
|
|
2024-11-02 00:08:34 +08:00
|
|
|
set warn-language-frame-mismatch [on|off]
|
|
|
|
|
show warn-language-frame-mismatch
|
|
|
|
|
Control the warning that is emitted when specifying a language that
|
|
|
|
|
does not match the current frame's language.
|
|
|
|
|
|
2024-07-31 14:42:56 +08:00
|
|
|
maintenance info inline-frames [ADDRESS]
|
|
|
|
|
New command which displays GDB's inline-frame information for the
|
|
|
|
|
current address, or for ADDRESS if specified. The output identifies
|
|
|
|
|
inlined frames which start at the specified address.
|
|
|
|
|
|
2024-07-18 18:16:13 +08:00
|
|
|
maintenance info blocks [ADDRESS]
|
|
|
|
|
New command which displays information about all of the blocks at
|
|
|
|
|
ADDRESS, or at the current address if ADDRESS is not given. Blocks
|
|
|
|
|
are listed starting at the inner global block out to the most inner
|
|
|
|
|
block.
|
|
|
|
|
|
gdb/python: implement Python find_exec_by_build_id hook
Implement extension_language_ops::find_objfile_from_buildid within
GDB's Python API. Doing this allows users to write Python extensions
that can help locate missing objfiles when GDB opens a core file. A
handler might perform some project- or site-specific actions to find a
missing objfile. Or might provide some project- or site-specific
advice to the user on how they can obtain the missing objfile.
The implementation is very similar to the approach taken in:
commit 8f6c452b5a4e50fbb55ff1d13328b392ad1fd416
Date: Sun Oct 15 22:48:42 2023 +0100
gdb: implement missing debug handler hook for Python
The following new commands are added as commands implemented in
Python, this is similar to how the Python missing debug and unwinder
commands are implemented:
info missing-objfile-handlers
enable missing-objfile-handler LOCUS HANDLER
disable missing-objfile-handler LOCUS HANDLER
To make use of this extension hook a user will create missing objfile
handler objects, and registers these handlers with GDB. When GDB
opens a core file and encounters a missing objfile each handler is
called in turn until one is able to help. Here is a minimal handler
that does nothing useful:
import gdb
import gdb.missing_objfile
class MyFirstHandler(gdb.missing_objfile.MissingObjfileHandler):
def __init__(self):
super().__init__("my_first_handler")
def __call__(self, pspace, build_id, filename):
# This handler does nothing useful.
return None
gdb.missing_objfile.register_handler(None, MyFirstHandler())
Returning None from the __call__ method tells GDB that this handler
was unable to find the missing objfile, and GDB should ask any other
registered handlers.
Possible return values from a handler:
- None: This means the handler couldn't help. GDB will call other
registered handlers to see if they can help instead.
- False: The handler has done all it can, but the objfile couldn't
be found. GDB will not call any other handlers, and will
continue without the objfile.
- True: The handler has installed the objfile into a location where
GDB would normally expect to find it. GDB should repeat its
normal lookup process and the objfile should now be found.
- A string: The handler can return a filename, which is the missing
objfile. GDB will load this file.
Handlers can be registered globally, or per program space. GDB checks
the handlers for the current program space first, and then all of the
global handles. The first handler that returns a value that is not
None, has "handled" the missing objfile, at which point GDB continues.
The implementation of this feature is mostly straight forward. I have
reworked some of the missing debug file related code so that it can be
shared with this feature. E.g. gdb/python/lib/gdb/missing_files.py is
mostly content moved from gdb/python/lib/gdb/missing_debug.py, but
updated to be more generic. Now gdb/python/lib/gdb/missing_debug.py
and the new file gdb/python/lib/gdb/missing_objfile.py both call into
the missing_files.py file.
For gdb/python/lib/gdb/command/missing_files.py this is even more
extreme, gdb/python/lib/gdb/command/missing_debug.py is completely
gone now and gdb/python/lib/gdb/command/missing_files.py provides all
of the new commands in a generic way.
I have made one change to the existing Python API, I renamed the
attribute Progspace.missing_debug_handlers to
Progspace.missing_file_handlers. I don't see this as too
problematic. This attribute was only used to implement the missing
debug feature and was never documented beyond the fact that it
existed. There was no reason for users to be touching this attribute.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
2024-07-31 22:55:57 +08:00
|
|
|
info missing-objfile-handlers
|
|
|
|
|
List all the registered missing-objfile handlers.
|
|
|
|
|
|
|
|
|
|
enable missing-objfile-handler LOCUS HANDLER
|
|
|
|
|
disable missing-objfile-handler LOCUS HANDLER
|
|
|
|
|
Enable or disable a missing-objfile handler with a name matching the
|
|
|
|
|
regular expression HANDLER, in LOCUS.
|
|
|
|
|
|
|
|
|
|
LOCUS can be 'global' to operate on global missing-objfile handler,
|
|
|
|
|
'progspace' to operate on handlers within the current program space,
|
|
|
|
|
or can be a regular expression which is matched against the filename
|
|
|
|
|
of the primary executable in each program space.
|
|
|
|
|
|
gdb: add remove-symbol-file command completion
The 'remove-symbol-file' command doesn't currently offer command
completion. This commit addresses this.
The 'remove-symbol-file' uses gdb_argv to split its command arguments,
this means that the filename the command expects can be quoted.
However, the 'remove-symbol-file' command is a little weird in that it
also has a '-a' option, if this option is passed then the command
expects not a filename, but an address.
Currently the remove_symbol_file_command function splits the command
args using gdb_argv, checks for a '-a' flag by looking at the first
argument value, and then expects the filename or address to occupy a
single entry in the gdb_argv array.
The first thing I do is handle the '-a' flag using GDB's option
system. I model this option as a flag_option_def (a boolean option).
I've dropped the use of gdb_argv and instead use the new(ish) function
extract_single_filename_arg, which was added a couple of commits back,
to parse the filename argument (when '-a' is not given).
If '-a' is given the the remove-symbol-file command expects an address
rather than a filename. As we previously split the arguments using
gdb_argv this meant the address needed to appear as a single
argument. So a user could write:
(gdb) remove-symbol-file 0x1234
Or they could write:
(gdb) remove-symbol-file some_function
Both of these would work fine. But a user could not write:
(gdb) remove-symbol-file some_function + 0x1000
As only the 'some_function' part would be processed. Now the user
could do this:
(gdb) remove-symbol-file "some_function + 0x1000"
By enclosing the address expression in quotes this would be handled as
a single argument. However, this is a little weird, that's not how
commands like 'print' or 'x' work. Also this functionality was
neither documented, or tested.
And so, in this commit, by removing the use of gdb_argv I bring the
'remove-symbol-file' command inline with GDB's other commands that
take an expression, the quotes are no longer needed.
Usually in a completer we call 'complete_options', but don't actually
capture the option values. But for remove-symbol-file I do. This
allows me to spot when the '-a' option has been given, I can then
complete the rest of the command line as either a filename or an
expression.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
2024-06-22 18:39:38 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
|
|
|
|
remove-symbol-file
|
|
|
|
|
This command now supports file-name completion.
|
|
|
|
|
|
|
|
|
|
remove-symbol-file -a ADDRESS
|
|
|
|
|
The ADDRESS expression can now be a full expression consisting of
|
|
|
|
|
multiple terms, e.g. 'function + 0x1000' (without quotes),
|
|
|
|
|
previously only a single term could be given.
|
|
|
|
|
|
2024-06-19 18:14:08 +08:00
|
|
|
target core
|
|
|
|
|
target exec
|
|
|
|
|
target tfile
|
|
|
|
|
target ctf
|
2024-06-20 20:44:28 +08:00
|
|
|
compile file
|
|
|
|
|
maint print c-tdesc
|
|
|
|
|
save gdb-index
|
|
|
|
|
These commands now require their filename argument to be quoted if
|
|
|
|
|
it contains white space or quote characters. If the argument
|
|
|
|
|
contains no such special characters then quoting is not required.
|
|
|
|
|
|
2024-09-05 12:42:02 +08:00
|
|
|
maintenance print remote-registers
|
|
|
|
|
Add an "Expedited" column to the output of the command. It indicates
|
|
|
|
|
which registers were included in the last stop reply packet received by
|
|
|
|
|
GDB.
|
|
|
|
|
|
2024-10-30 19:44:23 +08:00
|
|
|
show configuration
|
|
|
|
|
Now includes the version of GNU Readline library that GDB is using.
|
|
|
|
|
|
2024-08-30 00:29:08 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
vFile:stat
|
|
|
|
|
Return information about files on the remote system. Like
|
|
|
|
|
vFile:fstat but takes a filename rather than an open file
|
|
|
|
|
descriptor.
|
|
|
|
|
|
2024-05-27 00:02:38 +08:00
|
|
|
*** Changes in GDB 15
|
2023-10-08 16:04:34 +08:00
|
|
|
|
2024-03-05 23:14:53 +08:00
|
|
|
* The MPX commands "show/set mpx bound" have been deprecated, as Intel
|
|
|
|
|
listed MPX as removed in 2019.
|
|
|
|
|
|
2023-09-12 20:34:51 +08:00
|
|
|
* Building GDB and GDBserver now requires a C++17 compiler.
|
|
|
|
|
For example, GCC 9 or later.
|
|
|
|
|
|
2023-10-20 17:56:49 +08:00
|
|
|
* GDB index now contains information about the main function. This speeds up
|
[gdb/symtab] Add name_of_main and language_of_main to the DWARF index
This patch adds a new section to the DWARF index containing the name
and the language of the main function symbol, gathered from
`cooked_index::get_main`, if available. Currently, for lack of a better name,
this section is called the "shortcut table". The way this name is both saved and
applied upon an index being loaded in mirrors how it is done in
`cooked_index_functions`, more specifically, the full name of the main function
symbol is saved and `set_objfile_main_name` is used to apply it after it is
loaded.
The main use case for this patch is in improving startup times when dealing with
large binaries. Currently, when an index is used, GDB has to expand symtabs
until it finds out what the language of the main function symbol is. For some
large executables, this may take a considerable amount of time to complete,
slowing down startup. This patch bypasses that operation by having both the name
and language of the main function symbol be provided ahead of time by the index.
In my testing (a binary with about 1.8GB worth of DWARF data) this change brings
startup time down from about 34 seconds to about 1.5 seconds.
When testing the patch with target board cc-with-gdb-index, test-case
gdb.fortran/nested-funcs-2.exp starts failing, but this is due to a
pre-existing issue, filed as PR symtab/30946.
Tested on x86_64-linux, with target board unix and cc-with-gdb-index.
PR symtab/24549
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=24549
Approved-By: Tom de Vries <tdevries@suse.de>
2023-10-10 16:26:40 +08:00
|
|
|
startup when it is being used for some large binaries.
|
|
|
|
|
|
2023-10-22 05:22:09 +08:00
|
|
|
* On hosts where threading is available, DWARF reading is now done in
|
|
|
|
|
the background, resulting in faster startup. This can be controlled
|
|
|
|
|
using "maint set dwarf synchronous".
|
|
|
|
|
|
2023-10-20 18:15:51 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
|
|
|
|
disassemble
|
|
|
|
|
Attempting to use both the 'r' and 'b' flags with the disassemble
|
|
|
|
|
command will now give an error. Previously the 'b' flag would
|
|
|
|
|
always override the 'r' flag.
|
|
|
|
|
|
Teach GDB to generate sparse core files (PR corefiles/31494)
This commit teaches GDB's gcore command to generate sparse core files
(if supported by the filesystem).
To create a sparse file, all you have to do is skip writing zeros to
the file, instead lseek'ing-ahead over them.
The sparse logic is applied when writing the memory sections, as
that's where the bulk of the data and the zeros are.
The commit also tweaks gdb.base/bigcore.exp to make it exercise
gdb-generated cores in addition to kernel-generated cores. We
couldn't do that before, because GDB's gcore on that test's program
would generate a multi-GB non-sparse core (16GB on my system).
After this commit, gdb.base/bigcore.exp generates, when testing with
GDB's gcore, a much smaller core file, roughly in line with what the
kernel produces:
real sizes:
$ du --hu testsuite/outputs/gdb.base/bigcore/bigcore.corefile.*
2.2M testsuite/outputs/gdb.base/bigcore/bigcore.corefile.gdb
2.0M testsuite/outputs/gdb.base/bigcore/bigcore.corefile.kernel
apparent sizes:
$ du --hu --apparent-size testsuite/outputs/gdb.base/bigcore/bigcore.corefile.*
16G testsuite/outputs/gdb.base/bigcore/bigcore.corefile.gdb
16G testsuite/outputs/gdb.base/bigcore/bigcore.corefile.kernel
Time to generate the core also goes down significantly. On my machine, I get:
when writing to an SSD, from 21.0s, down to 8.0s
when writing to an HDD, from 31.0s, down to 8.5s
The changes to gdb.base/bigcore.exp are smaller than they look at
first sight. It's basically mostly refactoring -- moving most of the
code to a new procedure which takes as argument who should dump the
core, and then calling the procedure twice. I purposely did not
modernize any of the refactored code in this patch.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31494
Reviewed-By: Lancelot Six <lancelot.six@amd.com>
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Reviewed-By: John Baldwin <jhb@FreeBSD.org>
Change-Id: I2554a6a4a72d8c199ce31f176e0ead0c0c76cff1
2024-03-22 20:31:29 +08:00
|
|
|
gcore
|
|
|
|
|
generate-core-file
|
|
|
|
|
GDB now generates sparse core files, on systems that support it.
|
|
|
|
|
|
2023-11-02 00:25:32 +08:00
|
|
|
maintenance info line-table
|
|
|
|
|
Add an EPILOGUE-BEGIN column to the output of the command. It indicates
|
|
|
|
|
if the line is considered the start of the epilgoue, and thus a point at
|
|
|
|
|
which the frame can be considered destroyed.
|
|
|
|
|
|
2023-01-18 20:09:05 +08:00
|
|
|
set unwindonsignal on|off
|
|
|
|
|
show unwindonsignal
|
|
|
|
|
These commands are now aliases for the new set/show unwind-on-signal.
|
|
|
|
|
|
2024-04-15 21:02:15 +08:00
|
|
|
target record-full
|
|
|
|
|
This command now gives an error if any unexpected arguments are
|
|
|
|
|
found after the command.
|
|
|
|
|
|
2024-02-13 22:36:23 +08:00
|
|
|
list .
|
|
|
|
|
When using the command "list ." in a location that has no debug information
|
|
|
|
|
or no file loaded, GDB now says that there is no debug information to print
|
|
|
|
|
lines. This makes it more obvious that there is no information, as opposed
|
|
|
|
|
to implying there is no inferior loaded.
|
|
|
|
|
|
2023-11-16 19:11:30 +08:00
|
|
|
* New commands
|
gdb: implement missing debug handler hook for Python
This commit builds on the previous commit, and implements the
extension_language_ops::handle_missing_debuginfo function for Python.
This hook will give user supplied Python code a chance to help find
missing debug information.
The implementation of the new hook is pretty minimal within GDB's C++
code; most of the work is out-sourced to a Python implementation which
is modelled heavily on how GDB's Python frame unwinders are
implemented.
The following new commands are added as commands implemented in
Python, this is similar to how the Python unwinder commands are
implemented:
info missing-debug-handlers
enable missing-debug-handler LOCUS HANDLER
disable missing-debug-handler LOCUS HANDLER
To make use of this extension hook a user will create missing debug
information handler objects, and registers these handlers with GDB.
When GDB encounters an objfile that is missing debug information, each
handler is called in turn until one is able to help. Here is a
minimal handler that does nothing useful:
import gdb
import gdb.missing_debug
class MyFirstHandler(gdb.missing_debug.MissingDebugHandler):
def __init__(self):
super().__init__("my_first_handler")
def __call__(self, objfile):
# This handler does nothing useful.
return None
gdb.missing_debug.register_handler(None, MyFirstHandler())
Returning None from the __call__ method tells GDB that this handler
was unable to find the missing debug information, and GDB should ask
any other registered handlers.
By extending the __call__ method it is possible for the Python
extension to locate the debug information for objfile and return a
value that tells GDB how to use the information that has been located.
Possible return values from a handler:
- None: This means the handler couldn't help. GDB will call other
registered handlers to see if they can help instead.
- False: The handler has done all it can, but the debug information
for the objfile still couldn't be found. GDB will not call
any other handlers, and will continue without the debug
information for objfile.
- True: The handler has installed the debug information into a
location where GDB would normally expect to find it. GDB
should look again for the debug information.
- A string: The handler can return a filename, which is the file
containing the missing debug information. GDB will load
this file.
When a handler returns True, GDB will look again for the debug
information, but only using the standard built-in build-id and
.gnu_debuglink based lookup strategies. It is not possible for an
extension to trigger another debuginfod lookup; the assumption is that
the debuginfod server is remote, and out of the control of extensions
running within GDB.
Handlers can be registered globally, or per program space. GDB checks
the handlers for the current program space first, and then all of the
global handles. The first handler that returns a value that is not
None, has "handled" the objfile, at which point GDB continues.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-By: Tom Tromey <tom@tromey.com>
2023-10-16 05:48:42 +08:00
|
|
|
|
|
|
|
|
info missing-debug-handler
|
|
|
|
|
List all the registered missing debug handlers.
|
|
|
|
|
|
|
|
|
|
enable missing-debug-handler LOCUS HANDLER
|
|
|
|
|
disable missing-debug-handler LOCUS HANDLER
|
|
|
|
|
Enable or disable a missing debug handler with a name matching the
|
|
|
|
|
regular expression HANDLER, in LOCUS.
|
|
|
|
|
|
|
|
|
|
LOCUS can be 'global' to operate on global missing debug handler,
|
|
|
|
|
'progspace' to operate on handlers within the current program space,
|
|
|
|
|
or can be a regular expression which is matched against the filename
|
|
|
|
|
of the primary executable in each program space.
|
|
|
|
|
|
2023-11-16 19:11:30 +08:00
|
|
|
maintenance info linux-lwps
|
|
|
|
|
List all LWPs under control of the linux-nat target.
|
|
|
|
|
|
|
|
|
|
set remote thread-options-packet
|
|
|
|
|
show remote thread-options-packet
|
|
|
|
|
Set/show the use of the thread options packet.
|
|
|
|
|
|
gdb: add timeouts for inferior function calls
In the previous commits I have been working on improving inferior
function call support. One thing that worries me about using inferior
function calls from a conditional breakpoint is: what happens if the
inferior function call fails?
If the failure is obvious, e.g. the thread performing the call
crashes, or hits a breakpoint, then this case is already well handled,
and the error is reported to the user.
But what if the thread performing the inferior call just deadlocks?
If the user made the call from a 'print' or 'call' command, then the
user might have some expectation of when the function call should
complete, and, when this time limit is exceeded, the user
will (hopefully) interrupt GDB and regain control of the debug
session.
But, when the inferior function call is from a breakpoint condition it
is much harder to understand that GDB is deadlocked within an inferior
call. Maybe the breakpoint hasn't been hit yet? Or maybe the
condition was always false? Or maybe GDB is deadlocked in an inferior
call? The only way to know for sure is for the user to periodically
interrupt the inferior, check on the state of all the threads, and
then continue.
Additionally, the focus of the previous commit was inferior function
calls, from a conditional breakpoint, in a multi-threaded inferior.
This opens up a whole new set of potential failure conditions. For
example, what if the function called relies on interaction with some
other thread, and the other thread crashes? Or hits a breakpoint?
Given how inferior function calls work (in a synchronous manner), a
stop event in some other thread is going to be ignored while the
inferior function call is being executed as part of a breakpoint
condition, and this means that GDB could get stuck waiting for the
original condition thread, which will now never complete.
In this commit I propose a solution to this problem. A timeout. For
targets that support async-mode we can install an event-loop timer
before starting the inferior function call. When the timer expires we
will stop the thread performing the inferior function call. With this
mechanism in place a user can be sure that any inferior call they make
will either complete, or timeout eventually.
Adding a timer like this is obviously a change in behaviour for the
more common 'call' and 'print' uses of inferior function calls, so, in
this patch, I propose having two different timers. One I call the
'direct-call-timeout', which is used for 'call' and 'print' commands.
This timeout is by default set to unlimited, which, not surprisingly,
means there is no timeout in place.
A second timer, which I've called 'indirect-call-timeout', is used for
inferior function calls from breakpoint conditions. This timeout has
a default value of 30 seconds. This is a reasonably long time to
wait, and hopefully should be enough in most cases to allow the
inferior call to complete. An inferior call that takes more than 30
seconds, which is installed on a breakpoint condition is really going
to slow down the debug session, so hopefully this is not a common use
case.
The user is, of course, free to reduce, or increase the timeout value,
and can always use Ctrl-c to interrupt an inferior function call, but
this timeout will ensure that GDB will stop at some point.
The new commands added by this commit are:
set direct-call-timeout SECONDS
show direct-call-timeout
set indirect-call-timeout SECONDS
show indirect-call-timeout
These new timeouts do depend on async-mode, so, if async-mode is
disabled (maint set target-async off), or not supported (e.g. target
sim), then the timeout is treated as unlimited (that is, no timeout is
set).
For targets that "fake" non-async mode, e.g. Linux native, where
non-async mode is really just async mode, but then we park the target
in a sissuspend, we could easily fix things so that the timeouts still
work, however, for targets that really are not async aware, like the
simulator, fixing things so that timeouts work correctly would be a
much bigger task - that effort would be better spent just making the
target async-aware. And so, I'm happy for now that this feature will
only work on async targets.
The two new show commands will display slightly different text if the
current target is a non-async target, which should allow users to
understand what's going on.
There's a somewhat random test adjustment needed in gdb.base/help.exp,
the test uses a regexp with the apropos command, and expects to find a
single result. Turns out the new settings I added also matched the
regexp, which broke the test. I've updated the regexp a little to
exclude my new settings.
Reviewed-By: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Tested-By: Luis Machado <luis.machado@arm.com>
Tested-By: Keith Seitz <keiths@redhat.com>
2022-10-07 19:39:07 +08:00
|
|
|
set direct-call-timeout SECONDS
|
|
|
|
|
show direct-call-timeout
|
|
|
|
|
set indirect-call-timeout SECONDS
|
|
|
|
|
show indirect-call-timeout
|
|
|
|
|
These new settings can be used to limit how long GDB will wait for
|
|
|
|
|
an inferior function call to complete. The direct timeout is used
|
|
|
|
|
for inferior function calls from e.g. 'call' and 'print' commands,
|
|
|
|
|
while the indirect timeout is used for inferior function calls from
|
|
|
|
|
within a conditional breakpoint expression.
|
|
|
|
|
|
|
|
|
|
The default for the direct timeout is unlimited, while the default
|
|
|
|
|
for the indirect timeout is 30 seconds.
|
|
|
|
|
|
|
|
|
|
These timeouts will only have an effect for targets that are
|
|
|
|
|
operating in async mode. For non-async targets the timeouts are
|
|
|
|
|
ignored, GDB will wait indefinitely for an inferior function to
|
|
|
|
|
complete, unless interrupted by the user using Ctrl-C.
|
|
|
|
|
|
2023-01-18 18:17:57 +08:00
|
|
|
set unwind-on-timeout on|off
|
|
|
|
|
show unwind-on-timeout
|
|
|
|
|
These commands control whether GDB should unwind the stack when a
|
|
|
|
|
timeout occurs during an inferior function call. The default is
|
|
|
|
|
off, in which case the inferior will remain in the frame where the
|
|
|
|
|
timeout occurred. When on, GDB will unwind the stack removing the
|
|
|
|
|
dummy frame that was added for the inferior call, and restoring the
|
|
|
|
|
inferior state to how it was before the inferior call started.
|
|
|
|
|
|
2023-01-18 20:09:05 +08:00
|
|
|
set unwind-on-signal on|off
|
|
|
|
|
show unwind-on-signal
|
|
|
|
|
These new commands replaces the existing set/show unwindonsignal. The
|
|
|
|
|
old command is maintained as an alias.
|
|
|
|
|
|
gdbserver: allow the --debug command line option to take a value
Currently, gdbserver has the following command line options related to
debugging output:
--debug
--remote-debug
--event-loop-debug
This doesn't scale well. If I want an extra debug component I need to
add another command line flag.
This commit changes --debug to take a list of components.
The currently supported components are: all, threads, remote, and
event-loop. The 'threads' component represents the debug we currently
get from the --debug option. And if --debug is used without a
component list then the threads component is assumed as the default.
Currently the threads component actually includes a lot of output that
is not really threads related. In the future I'd like to split this
up into some new, separate components. But that is not part of this
commit, or even this series.
The special component 'all' does what you'd expect: enables debug
output from all supported components.
The component list is parsed left to write, and you can prefix a
component with '-' to disable that component, so I can write:
target> gdbserver --debug=all,-event-loop
to get debug for all components except the event-loop component.
I've removed the existing --remote-debug and --event-loop-debug
command line options, these are equivalent to --debug=remote and
--debug=event-loop respectively, or --debug=remote,event-loop to
enable both components.
In this commit I've only update the command line options, in the next
commit I'll update the monitor commands to support a similar
interface.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-By: Tom Tromey <tom@tromey.com>
2023-11-06 05:02:03 +08:00
|
|
|
* New features in the GDB remote stub, GDBserver
|
|
|
|
|
|
|
|
|
|
** The --remote-debug and --event-loop-debug command line options
|
|
|
|
|
have been removed.
|
|
|
|
|
|
|
|
|
|
** The --debug command line option now takes an optional comma
|
|
|
|
|
separated list of components to emit debug for. The currently
|
|
|
|
|
supported components are: all, threads, event-loop, and remote.
|
|
|
|
|
If no components are given then threads is assumed.
|
|
|
|
|
|
gdbserver: allow for general 'monitor set debug COMPONENT VALUE' use
Building on the last commit, which added a general --debug=COMPONENT
option to the gdbserver command line, this commit updates the monitor
command to allow for general:
(gdb) monitor set debug COMPONENT off|on
style commands. Just like with the previous commit, the COMPONENT can
be any one of all, threads, remote, event-loop, and correspond to the
same set of global debug flags.
While on the command line it is possible to do:
--debug=remote,event-loop,threads
the components have to be entered one at a time with the monitor
command. I guess there's no reason why we couldn't allow component
grouping within the monitor command, but (to me) what I have here
seemed more in the spirit of GDB's existing 'set debug ...' commands.
If people want it then we can always add component grouping later.
Notice in the above that I use 'off' and 'on' instead of '0' and '1',
which is what the 'monitor set debug' command used to use. The 0/1
can still be used, but I now advertise off/on in all the docs and help
text, again, this feels more inline with GDB's existing boolean
settings.
I have removed the two existing monitor commands:
monitor set remote-debug 0|1
monitor set event-loop-debug 0|1
These are replaced by:
monitor set debug remote off|on
monitor set debug event-loop off|on
respectively.
Approved-By: Tom Tromey <tom@tromey.com>
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
2023-11-08 00:46:34 +08:00
|
|
|
** The 'monitor set remote-debug' and 'monitor set event-loop-debug'
|
|
|
|
|
command have been removed.
|
|
|
|
|
|
|
|
|
|
** The 'monitor set debug 0|1' command has been extended to take a
|
|
|
|
|
component name, e.g.: 'monitor set debug COMPONENT off|on'.
|
|
|
|
|
Possible component names are: all, threads, event-loop, and
|
|
|
|
|
remote.
|
|
|
|
|
|
2023-10-10 18:22:56 +08:00
|
|
|
* Python API
|
|
|
|
|
|
|
|
|
|
** New function gdb.notify_mi(NAME, DATA), that emits custom
|
|
|
|
|
GDB/MI async notification.
|
|
|
|
|
|
2023-10-18 22:46:23 +08:00
|
|
|
** New read/write attribute gdb.Value.bytes that contains a bytes
|
|
|
|
|
object holding the contents of this value.
|
|
|
|
|
|
gdb: implement missing debug handler hook for Python
This commit builds on the previous commit, and implements the
extension_language_ops::handle_missing_debuginfo function for Python.
This hook will give user supplied Python code a chance to help find
missing debug information.
The implementation of the new hook is pretty minimal within GDB's C++
code; most of the work is out-sourced to a Python implementation which
is modelled heavily on how GDB's Python frame unwinders are
implemented.
The following new commands are added as commands implemented in
Python, this is similar to how the Python unwinder commands are
implemented:
info missing-debug-handlers
enable missing-debug-handler LOCUS HANDLER
disable missing-debug-handler LOCUS HANDLER
To make use of this extension hook a user will create missing debug
information handler objects, and registers these handlers with GDB.
When GDB encounters an objfile that is missing debug information, each
handler is called in turn until one is able to help. Here is a
minimal handler that does nothing useful:
import gdb
import gdb.missing_debug
class MyFirstHandler(gdb.missing_debug.MissingDebugHandler):
def __init__(self):
super().__init__("my_first_handler")
def __call__(self, objfile):
# This handler does nothing useful.
return None
gdb.missing_debug.register_handler(None, MyFirstHandler())
Returning None from the __call__ method tells GDB that this handler
was unable to find the missing debug information, and GDB should ask
any other registered handlers.
By extending the __call__ method it is possible for the Python
extension to locate the debug information for objfile and return a
value that tells GDB how to use the information that has been located.
Possible return values from a handler:
- None: This means the handler couldn't help. GDB will call other
registered handlers to see if they can help instead.
- False: The handler has done all it can, but the debug information
for the objfile still couldn't be found. GDB will not call
any other handlers, and will continue without the debug
information for objfile.
- True: The handler has installed the debug information into a
location where GDB would normally expect to find it. GDB
should look again for the debug information.
- A string: The handler can return a filename, which is the file
containing the missing debug information. GDB will load
this file.
When a handler returns True, GDB will look again for the debug
information, but only using the standard built-in build-id and
.gnu_debuglink based lookup strategies. It is not possible for an
extension to trigger another debuginfod lookup; the assumption is that
the debuginfod server is remote, and out of the control of extensions
running within GDB.
Handlers can be registered globally, or per program space. GDB checks
the handlers for the current program space first, and then all of the
global handles. The first handler that returns a value that is not
None, has "handled" the objfile, at which point GDB continues.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-By: Tom Tromey <tom@tromey.com>
2023-10-16 05:48:42 +08:00
|
|
|
** New module gdb.missing_debug that facilitates dealing with
|
|
|
|
|
objfiles that are missing any debug information.
|
|
|
|
|
|
|
|
|
|
** New function gdb.missing_debug.register_handler that can register
|
|
|
|
|
an instance of a sub-class of gdb.missing_debug.MissingDebugInfo
|
|
|
|
|
as a handler for objfiles that are missing debug information.
|
|
|
|
|
|
|
|
|
|
** New class gdb.missing_debug.MissingDebugInfo which can be
|
|
|
|
|
sub-classed to create handlers for objfiles with missing debug
|
|
|
|
|
information.
|
|
|
|
|
|
2023-11-04 03:23:41 +08:00
|
|
|
** Stop events now have a "details" attribute that holds a
|
|
|
|
|
dictionary that carries the same information as an MI "*stopped"
|
|
|
|
|
event.
|
|
|
|
|
|
2023-11-17 01:44:42 +08:00
|
|
|
** New function gdb.interrupt(), that interrupts GDB as if the user
|
|
|
|
|
typed control-c.
|
|
|
|
|
|
2024-01-10 01:29:24 +08:00
|
|
|
** New gdb.InferiorThread.ptid_string attribute. This read-only
|
|
|
|
|
attribute contains the string that appears in the 'Target Id'
|
|
|
|
|
column of the 'info threads' command output.
|
|
|
|
|
|
gdb/python: remove users ability to create gdb.Progspace objects
I noticed that it is possible for the user to create a new
gdb.Progspace object, like this:
(gdb) pi
>>> p = gdb.Progspace()
>>> p
<gdb.Progspace object at 0x7ffad4219c10>
>>> p.is_valid()
False
As the new gdb.Progspace object is not associated with an actual C++
program_space object within GDB core, then the new gdb.Progspace is
created invalid, and there is no way in which the new object can ever
become valid.
Nor do I believe there's anywhere in the Python API where it makes
sense to consume an invalid gdb.Progspace created in this way, for
example, the gdb.Progspace could be passed as the locus to
register_type_printer, but all that would happen is that the
registered printer would never be used.
In this commit I propose to remove the ability to create new
gdb.Progspace objects. Attempting to do so now gives an error, like
this:
(gdb) pi
>>> gdb.Progspace()
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: cannot create 'gdb.Progspace' instances
Of course, there is a small risk here that some existing user code
might break ... but if that happens I don't believe the user code can
have been doing anything useful, so I see this as a small risk.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-By: Tom Tromey <tom@tromey.com>
2024-01-04 22:24:12 +08:00
|
|
|
** It is no longer possible to create new gdb.Progspace object using
|
|
|
|
|
'gdb.Progspace()', this will result in a TypeError. Progspace
|
|
|
|
|
objects can still be obtained through calling other API
|
|
|
|
|
functions, for example 'gdb.current_progspace()'.
|
|
|
|
|
|
2024-01-05 00:46:40 +08:00
|
|
|
** User defined attributes can be added to a gdb.Inferior object,
|
|
|
|
|
these will be stored in the object's new Inferior.__dict__
|
|
|
|
|
attribute.
|
|
|
|
|
|
2024-01-05 19:05:51 +08:00
|
|
|
** User defined attributes can be added to a gdb.InferiorThread
|
|
|
|
|
object, these will be stored in the object's new
|
|
|
|
|
InferiorThread.__dict__ attribute.
|
|
|
|
|
|
2023-11-19 01:00:12 +08:00
|
|
|
** New constants gdb.SYMBOL_TYPE_DOMAIN, gdb.SYMBOL_FUNCTION_DOMAIN,
|
|
|
|
|
and gdb.SEARCH_*_DOMAIN corresponding to all the existing symbol
|
|
|
|
|
domains. Symbol lookup can now search in multiple domains at
|
|
|
|
|
once, and can also narrowly search for just a type or function.
|
|
|
|
|
|
2023-12-11 22:50:46 +08:00
|
|
|
* Debugger Adapter Protocol changes
|
|
|
|
|
|
|
|
|
|
** GDB now emits the "process" event.
|
|
|
|
|
|
2023-11-08 01:56:07 +08:00
|
|
|
** GDB now supports the "cancel" request.
|
|
|
|
|
|
2023-12-08 00:51:52 +08:00
|
|
|
** The "attach" request now supports specifying the program.
|
|
|
|
|
|
2023-12-13 00:30:41 +08:00
|
|
|
** New command "set debug dap-log-level" controls DAP logging.
|
|
|
|
|
|
|
|
|
|
** The "set debug dap-log-file" command is now documented. This
|
|
|
|
|
command was available in GDB 14 but not documented.
|
|
|
|
|
|
2023-11-19 01:00:12 +08:00
|
|
|
* Guile API
|
|
|
|
|
|
|
|
|
|
** New constants SYMBOL_TYPE_DOMAIN, SYMBOL_FUNCTION_DOMAIN, and
|
|
|
|
|
SEARCH_*_DOMAIN corresponding to all the existing symbol domains.
|
|
|
|
|
Symbol lookup can now search in multiple domains at once, and can
|
|
|
|
|
also narrowly search for just a type or function.
|
|
|
|
|
|
2022-06-14 02:26:59 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
New stop reason: clone
|
|
|
|
|
Indicates that a clone system call was executed.
|
|
|
|
|
|
|
|
|
|
QThreadOptions
|
|
|
|
|
Enable/disable optional event reporting, on a per-thread basis.
|
|
|
|
|
Currently supported options are GDB_THREAD_OPTION_CLONE, to enable
|
|
|
|
|
clone event reporting, and GDB_THREAD_OPTION_EXIT to enable thread
|
|
|
|
|
exit event reporting.
|
|
|
|
|
|
|
|
|
|
QThreadOptions in qSupported
|
|
|
|
|
The qSupported packet allows GDB to inform the stub it supports the
|
|
|
|
|
QThreadOptions packet, and the qSupported response can contain the
|
|
|
|
|
set of thread options the remote stub supports.
|
|
|
|
|
|
2024-04-19 04:10:39 +08:00
|
|
|
qIsAddressTagged
|
|
|
|
|
This new packet allows GDB to query the stub about a given address to check
|
|
|
|
|
if it is tagged or not. Many memory tagging-related GDB commands need to
|
|
|
|
|
perform this check before they read/write the allocation tag related to an
|
|
|
|
|
address. Currently, however, this is done through a 'vFile' request to read
|
|
|
|
|
the file /proc/<PID>/smaps and check if the address is in a region reported
|
|
|
|
|
as memory tagged. Since not all targets have a notion of what the smaps
|
|
|
|
|
file is about, this new packet provides a more generic way to perform such
|
|
|
|
|
a check.
|
|
|
|
|
|
2023-10-08 16:04:34 +08:00
|
|
|
*** Changes in GDB 14
|
2022-12-18 12:38:25 +08:00
|
|
|
|
2023-06-23 06:52:36 +08:00
|
|
|
* GDB now supports the AArch64 Scalable Matrix Extension 2 (SME2), which
|
|
|
|
|
includes a new 512 bit lookup table register named ZT0.
|
|
|
|
|
|
2023-02-01 07:54:39 +08:00
|
|
|
* GDB now supports the AArch64 Scalable Matrix Extension (SME), which includes
|
|
|
|
|
a new matrix register named ZA, a new thread register TPIDR2 and a new vector
|
|
|
|
|
length register SVG (streaming vector granule). GDB also supports tracking
|
|
|
|
|
ZA state across signal frames.
|
|
|
|
|
|
|
|
|
|
Some features are still under development or are dependent on ABI specs that
|
|
|
|
|
are still in alpha stage. For example, manual function calls with ZA state
|
|
|
|
|
don't have any special handling, and tracking of SVG changes based on
|
|
|
|
|
DWARF information is still not implemented, but there are plans to do so in
|
|
|
|
|
the future.
|
|
|
|
|
|
2023-09-16 07:24:26 +08:00
|
|
|
* GDB now recognizes the NO_COLOR environment variable and disables
|
|
|
|
|
styling according to the spec. See https://no-color.org/.
|
|
|
|
|
Styling can be re-enabled with "set style enabled on".
|
|
|
|
|
|
2023-04-03 17:43:34 +08:00
|
|
|
* The AArch64 'org.gnu.gdb.aarch64.pauth' Pointer Authentication feature string
|
|
|
|
|
has been deprecated in favor of the 'org.gnu.gdb.aarch64.pauth_v2' feature
|
|
|
|
|
string.
|
|
|
|
|
|
2023-03-02 06:13:21 +08:00
|
|
|
* GDB now has some support for integer types larger than 64 bits.
|
|
|
|
|
|
2023-03-07 21:22:19 +08:00
|
|
|
* Removed targets and native configurations
|
|
|
|
|
|
|
|
|
|
GDB no longer supports AIX 4.x, AIX 5.x and AIX 6.x. The minimum supported
|
|
|
|
|
AIX version is now AIX 7.1.
|
|
|
|
|
|
gdb: Make global feature array a per-remote target array
This patch applies the appropriate FIXME notes described in commit 5b6d1e4
"Multi-target support".
"You'll notice that remote.c includes some FIXME notes. These refer to
the fact that the global arrays that hold data for the remote packets
supported are still globals. For example, if we connect to two
different servers/stubs, then each might support different remote
protocol features. They might even be different architectures, like
e.g., one ARM baremetal stub, and a x86 gdbserver, to debug a
host/controller scenario as a single program. That isn't going to
work correctly today, because of said globals. I'm leaving fixing
that for another pass, since it does not appear to be trivial, and I'd
rather land the base work first. It's already useful to be able to
debug multiple instances of the same server (e.g., a distributed
cluster, where you have full control over the servers installed), so I
think as is it's already reasonable incremental progress."
Using this patch it is possible to configure per-remote targets'
feature packets.
Given the following setup for two gdbservers:
~~~~
gdbserver --multi :1234
gdbserver --disable-packet=vCont --multi :2345
~~~~
Before this patch configuring of range-stepping was not possible for one
of two connected remote targets with different support for the vCont
packet. As one of the targets supports vCont, it should be possible to
configure "set range-stepping". However, the output of GDB looks like:
(gdb) target extended-remote :1234
Remote debugging using :1234
(gdb) add-inferior -no-connection
[New inferior 2]
Added inferior 2
(gdb) inferior 2
[Switching to inferior 2 [<null>] (<noexec>)]
(gdb) target extended-remote :2345
Remote debugging using :2345
(gdb) set range-stepping on
warning: Range stepping is not supported by the current target
(gdb) inferior 1
[Switching to inferior 1 [<null>] (<noexec>)]
(gdb) set range-stepping on
warning: Range stepping is not supported by the current target
~~~~
Two warnings are shown. The warning for inferior 1 should not appear
as it is connected to a target supporting the vCont package.
~~~~
(gdb) target extended-remote :1234
Remote debugging using :1234
(gdb) add-inferior -no-connection
[New inferior 2]
Added inferior 2
(gdb) inferior 2
[Switching to inferior 2 [<null>] (<noexec>)]
(gdb) target extended-remote :2345
Remote debugging using :2345
(gdb) set range-stepping on
warning: Range stepping is not supported by the current target
(gdb) inferior 1
[Switching to inferior 1 [<null>] (<noexec>)]
(gdb) set range-stepping on
(gdb)
~~~~
Now only one warning is shown for inferior 2, which is connected to
a target not supporting vCont.
The per-remote target feature array is realized by a new class
remote_features, which stores the per-remote target array and
provides functions to determine supported features of the target.
A remote_target object now has a new member of that class.
Each time a new remote_target object is initialized, a new per-remote
target array is constructed based on the global remote_protocol_packets
array. The global array is initialized in the function _initialize_remote
and can be configured using the command line. Before this patch the
command line configuration affected current targets and future remote
targets (due to the global feature array used by all remote
targets). This behavior is different and the configuration applies as
follows:
- If a target is connected, the command line configuration affects the
current connection. All other existing remote targets are not
affected.
- If not connected, the command line configuration affects future
connections.
The show command displays the current remote target's configuration. If no
remote target is selected the default configuration for future
connections is shown.
If we have for instance the following setup with inferior 2 being
selected:
~~~~
(gdb) info inferiors
Num Description Connection Executable
1 <null> 1 (extended-remote :1234)
* 2 <null> 2 (extended-remote :2345)
~~~~
Before this patch, if we run 'set remote multiprocess-feature-packet', the
following configuration was set:
The feature array of all remote targets (in this setup the two connected
targets) and all future remote connections are affected.
After this patch, it will be configured as follows:
The feature array of target with port :2345 which is currently selected
will be configured. All other existing remote targets are not affected.
The show command 'show remote multiprocess-feature-packet' will display
the configuration of target with port :2345.
Due to this configuration change, it is required to adapt the test
"gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp" to configure the
multiprocess-feature-packet before the connections are created.
To inform the gdb user about the new behaviour of the 'show remote
PACKET-NAME' commands and the new configuration impact for remote
targets using the 'set remote PACKET-NAME' commands the commands'
outputs are adapted. Due to this change it is required to adapt each
test using the set/show remote 'PACKET-NAME' commands.
2021-11-19 00:13:16 +08:00
|
|
|
* Multi-target feature configuration
|
|
|
|
|
|
|
|
|
|
GDB now supports the individual configuration of remote targets' feature
|
|
|
|
|
sets. Based on the current selection of a target, the commands 'set remote
|
|
|
|
|
<name>-packet (on|off|auto)' and 'show remote <name>-packet' can be used to
|
|
|
|
|
configure a target's feature packet and to display its configuration,
|
|
|
|
|
respectively.
|
|
|
|
|
|
2021-11-27 02:23:48 +08:00
|
|
|
The individual packet sizes can be configured and shown using the commands
|
|
|
|
|
** 'set remote memory-read-packet-size (number of bytes|fixed|limit)'
|
|
|
|
|
** 'set remote memory-write-packet-size (number of bytes|fixed|limit)'
|
|
|
|
|
** 'show remote memory-read-packet-size'
|
|
|
|
|
** 'show remote memory-write-packet-size'.
|
|
|
|
|
|
|
|
|
|
The configuration of the packet itself, as well as the size of a memory-read
|
|
|
|
|
or memory-write packet applies to the currently selected target (if
|
|
|
|
|
available). If no target is selected, it applies to future remote
|
gdb: Make global feature array a per-remote target array
This patch applies the appropriate FIXME notes described in commit 5b6d1e4
"Multi-target support".
"You'll notice that remote.c includes some FIXME notes. These refer to
the fact that the global arrays that hold data for the remote packets
supported are still globals. For example, if we connect to two
different servers/stubs, then each might support different remote
protocol features. They might even be different architectures, like
e.g., one ARM baremetal stub, and a x86 gdbserver, to debug a
host/controller scenario as a single program. That isn't going to
work correctly today, because of said globals. I'm leaving fixing
that for another pass, since it does not appear to be trivial, and I'd
rather land the base work first. It's already useful to be able to
debug multiple instances of the same server (e.g., a distributed
cluster, where you have full control over the servers installed), so I
think as is it's already reasonable incremental progress."
Using this patch it is possible to configure per-remote targets'
feature packets.
Given the following setup for two gdbservers:
~~~~
gdbserver --multi :1234
gdbserver --disable-packet=vCont --multi :2345
~~~~
Before this patch configuring of range-stepping was not possible for one
of two connected remote targets with different support for the vCont
packet. As one of the targets supports vCont, it should be possible to
configure "set range-stepping". However, the output of GDB looks like:
(gdb) target extended-remote :1234
Remote debugging using :1234
(gdb) add-inferior -no-connection
[New inferior 2]
Added inferior 2
(gdb) inferior 2
[Switching to inferior 2 [<null>] (<noexec>)]
(gdb) target extended-remote :2345
Remote debugging using :2345
(gdb) set range-stepping on
warning: Range stepping is not supported by the current target
(gdb) inferior 1
[Switching to inferior 1 [<null>] (<noexec>)]
(gdb) set range-stepping on
warning: Range stepping is not supported by the current target
~~~~
Two warnings are shown. The warning for inferior 1 should not appear
as it is connected to a target supporting the vCont package.
~~~~
(gdb) target extended-remote :1234
Remote debugging using :1234
(gdb) add-inferior -no-connection
[New inferior 2]
Added inferior 2
(gdb) inferior 2
[Switching to inferior 2 [<null>] (<noexec>)]
(gdb) target extended-remote :2345
Remote debugging using :2345
(gdb) set range-stepping on
warning: Range stepping is not supported by the current target
(gdb) inferior 1
[Switching to inferior 1 [<null>] (<noexec>)]
(gdb) set range-stepping on
(gdb)
~~~~
Now only one warning is shown for inferior 2, which is connected to
a target not supporting vCont.
The per-remote target feature array is realized by a new class
remote_features, which stores the per-remote target array and
provides functions to determine supported features of the target.
A remote_target object now has a new member of that class.
Each time a new remote_target object is initialized, a new per-remote
target array is constructed based on the global remote_protocol_packets
array. The global array is initialized in the function _initialize_remote
and can be configured using the command line. Before this patch the
command line configuration affected current targets and future remote
targets (due to the global feature array used by all remote
targets). This behavior is different and the configuration applies as
follows:
- If a target is connected, the command line configuration affects the
current connection. All other existing remote targets are not
affected.
- If not connected, the command line configuration affects future
connections.
The show command displays the current remote target's configuration. If no
remote target is selected the default configuration for future
connections is shown.
If we have for instance the following setup with inferior 2 being
selected:
~~~~
(gdb) info inferiors
Num Description Connection Executable
1 <null> 1 (extended-remote :1234)
* 2 <null> 2 (extended-remote :2345)
~~~~
Before this patch, if we run 'set remote multiprocess-feature-packet', the
following configuration was set:
The feature array of all remote targets (in this setup the two connected
targets) and all future remote connections are affected.
After this patch, it will be configured as follows:
The feature array of target with port :2345 which is currently selected
will be configured. All other existing remote targets are not affected.
The show command 'show remote multiprocess-feature-packet' will display
the configuration of target with port :2345.
Due to this configuration change, it is required to adapt the test
"gdb/testsuite/gdb.multi/multi-target-info-inferiors.exp" to configure the
multiprocess-feature-packet before the connections are created.
To inform the gdb user about the new behaviour of the 'show remote
PACKET-NAME' commands and the new configuration impact for remote
targets using the 'set remote PACKET-NAME' commands the commands'
outputs are adapted. Due to this change it is required to adapt each
test using the set/show remote 'PACKET-NAME' commands.
2021-11-19 00:13:16 +08:00
|
|
|
connections. Similarly, the show commands print the configuration of the
|
|
|
|
|
currently selected target. If no remote target is selected, the default
|
|
|
|
|
configuration for future connections is shown.
|
|
|
|
|
|
Initial implementation of Debugger Adapter Protocol
The Debugger Adapter Protocol is a JSON-RPC protocol that IDEs can use
to communicate with debuggers. You can find more information here:
https://microsoft.github.io/debug-adapter-protocol/
Frequently this is implemented as a shim, but it seemed to me that GDB
could implement it directly, via the Python API. This patch is the
initial implementation.
DAP is implemented as a new "interp". This is slightly weird, because
it doesn't act like an ordinary interpreter -- for example it doesn't
implement a command syntax, and doesn't use GDB's ordinary event loop.
However, this seemed like the best approach overall.
To run GDB in this mode, use:
gdb -i=dap
The DAP code will accept JSON-RPC messages on stdin and print
responses to stdout. GDB redirects the inferior's stdout to a new
pipe so that output can be encapsulated by the protocol.
The Python code uses multiple threads to do its work. Separate
threads are used for reading JSON from the client and for writing JSON
to the client. All GDB work is done in the main thread. (The first
implementation used asyncio, but this had some limitations, and so I
rewrote it to use threads instead.)
This is not a complete implementation of the protocol, but it does
implement enough to demonstrate that the overall approach works.
There is a rudimentary test suite. It uses a JSON parser written in
pure Tcl. This parser is under the same license as Tcl itself, so I
felt it was acceptable to simply import it into the tree.
There is also a bit of documentation -- just documenting the new
interpreter name.
2022-06-24 01:11:36 +08:00
|
|
|
* GDB has initial built-in support for the Debugger Adapter Protocol.
|
|
|
|
|
This support requires that GDB be built with Python scripting
|
|
|
|
|
enabled.
|
|
|
|
|
|
gdb: error if 'thread' or 'task' keywords are overused
When creating a breakpoint or watchpoint, the 'thread' and 'task'
keywords can be used to create a thread or task specific breakpoint or
watchpoint.
Currently, a thread or task specific breakpoint can only apply for a
single thread or task, if multiple threads or tasks are specified when
creating the breakpoint (or watchpoint), then the last specified id
will be used.
The exception to the above is that when the 'thread' keyword is used
during the creation of a watchpoint, GDB will give an error if
'thread' is given more than once.
In this commit I propose making this behaviour consistent, if the
'thread' or 'task' keywords are used more than once when creating
either a breakpoint or watchpoint, then GDB will give an error.
I haven't updated the manual, we don't explicitly say that these
keywords can be repeated, and (to me), given the keyword takes a
single id, I don't think it makes much sense to repeat the keyword.
As such, I see this more as adding a missing error to GDB, rather than
making some big change. However, I have added an entry to the NEWS
file as I guess it is possible that some people might hit this new
error with an existing (I claim, badly written) GDB script.
I've added some new tests to check for the new error.
Just one test needed updating, gdb.linespec/keywords.exp, this test
did use the 'thread' keyword twice, and expected the breakpoint to be
created. Looking at what this test was for though, it was checking
the use of '-force-condition', and I don't think that being able to
repeat 'thread' was actually a critical part of this test.
As such, I've updated this test to expect the error when 'thread' is
repeated.
2022-11-09 20:54:55 +08:00
|
|
|
* For the break command, multiple uses of the 'thread' or 'task'
|
|
|
|
|
keywords will now give an error instead of just using the thread or
|
|
|
|
|
task id from the last instance of the keyword. E.g.:
|
|
|
|
|
break foo thread 1 thread 2
|
|
|
|
|
will now give an error rather than using 'thread 2'.
|
|
|
|
|
|
|
|
|
|
* For the watch command, multiple uses of the 'task' keyword will now
|
|
|
|
|
give an error instead of just using the task id from the last
|
|
|
|
|
instance of the keyword. E.g.:
|
|
|
|
|
watch my_var task 1 task 2
|
|
|
|
|
will now give an error rather than using 'task 2'. The 'thread'
|
|
|
|
|
keyword already gave an error when used multiple times with the
|
|
|
|
|
watch command, this remains unchanged.
|
|
|
|
|
|
GDB: Introduce limited array lengths while printing values
This commit introduces the idea of loading only part of an array in
order to print it, what I call "limited length" arrays.
The motivation behind this work is to make it possible to print slices
of very large arrays, where very large means bigger than
`max-value-size'.
Consider this GDB session with the current GDB:
(gdb) set max-value-size 100
(gdb) p large_1d_array
value requires 400 bytes, which is more than max-value-size
(gdb) p -elements 10 -- large_1d_array
value requires 400 bytes, which is more than max-value-size
notice that the request to print 10 elements still fails, even though 10
elements should be less than the max-value-size. With a patched version
of GDB:
(gdb) p -elements 10 -- large_1d_array
$1 = {0, 1, 2, 3, 4, 5, 6, 7, 8, 9...}
So now the print has succeeded. It also has loaded `max-value-size'
worth of data into value history, so the recorded value can be accessed
consistently:
(gdb) p -elements 10 -- $1
$2 = {0, 1, 2, 3, 4, 5, 6, 7, 8, 9...}
(gdb) p $1
$3 = {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, <unavailable> <repeats 75 times>}
(gdb)
Accesses with other languages work similarly, although for Ada only
C-style [] array element/dimension accesses use history. For both Ada
and Fortran () array element/dimension accesses go straight to the
inferior, bypassing the value history just as with C pointers.
Co-Authored-By: Maciej W. Rozycki <macro@embecosm.com>
2023-02-11 07:49:19 +08:00
|
|
|
* The 'set print elements' setting now helps when printing large arrays.
|
|
|
|
|
If an array would otherwise exceed max-value-size, but 'print elements'
|
|
|
|
|
is set such that the size of elements to print is less than or equal
|
|
|
|
|
to 'max-value-size', GDB will now still print the array, however only
|
|
|
|
|
'max-value-size' worth of data will be added into the value history.
|
|
|
|
|
|
gdb: only allow one of thread or task on breakpoints or watchpoints
After this mailing list posting:
https://sourceware.org/pipermail/gdb-patches/2023-February/196607.html
it seems to me that in practice an Ada task maps 1:1 with a GDB
thread, and so it doesn't really make sense to allow uses to give both
a thread and a task within a single breakpoint or watchpoint
condition.
This commit updates GDB so that the user will get an error if both
are specified.
I've added new tests to cover the CLI as well as the Python and Guile
APIs. For the Python and Guile testing, as far as I can tell, this
was the first testing for this corner of the APIs, so I ended up
adding more than just a single test.
For documentation I've added a NEWS entry, but I've not added anything
to the docs themselves. Currently we document the commands with a
thread-id or task-id as distinct command, e.g.:
'break LOCSPEC task TASKNO'
'break LOCSPEC task TASKNO if ...'
'break LOCSPEC thread THREAD-ID'
'break LOCSPEC thread THREAD-ID if ...'
As such, I don't believe there is any indication that combining 'task'
and 'thread' would be expected to work; it seems clear to me in the
above that those four options are all distinct commands.
I think the NEWS entry is enough that if someone is combining these
keywords (it's not clear what the expected behaviour would be in this
case) then they can figure out that this was a deliberate change in
GDB, but for a new user, the manual doesn't suggest combining them is
OK, and any future attempt to combine them will give an error.
Approved-By: Pedro Alves <pedro@palves.net>
2023-02-06 21:04:16 +08:00
|
|
|
* For both the break and watch commands, it is now invalid to use both
|
|
|
|
|
the 'thread' and 'task' keywords within the same command. For
|
|
|
|
|
example the following commnds will now give an error:
|
|
|
|
|
break foo thread 1 task 1
|
|
|
|
|
watch var thread 2 task 3
|
|
|
|
|
|
gdb: add support for %V to printf command
This commit adds a new format for the printf and dprintf commands:
'%V'. This new format takes any GDB expression and formats it as a
string, just as GDB would for a 'print' command, e.g.:
(gdb) print a1
$a = {2, 4, 6, 8, 10, 12, 14, 16, 18, 20}
(gdb) printf "%V\n", a1
{2, 4, 6, 8, 10, 12, 14, 16, 18, 20}
(gdb)
It is also possible to pass the same options to %V as you might pass
to the print command, e.g.:
(gdb) print -elements 3 -- a1
$4 = {2, 4, 6...}
(gdb) printf "%V[-elements 3]\n", a1
{2, 4, 6...}
(gdb)
This new feature would effectively replace an existing feature of GDB,
the $_as_string builtin convenience function. However, the
$_as_string function has a few problems which this new feature solves:
1. $_as_string doesn't currently work when the inferior is not
running, e.g:
(gdb) printf "%s", $_as_string(a1)
You can't do that without a process to debug.
(gdb)
The reason for this is that $_as_string returns a value object with
string type. When we try to print this we call value_as_address,
which ends up trying to push the string into the inferior's address
space.
Clearly we could solve this problem, the string data exists in GDB, so
there's no reason why we have to push it into the inferior, but this
is an existing problem that would need solving.
2. $_as_string suffers from the fact that C degrades arrays to
pointers, e.g.:
(gdb) printf "%s\n", $_as_string(a1)
0x404260 <a1>
(gdb)
The implementation of $_as_string is passed a gdb.Value object that is
a pointer, it doesn't understand that it's actually an array. Solving
this would be harder than issue #1 I think. The whole array to
pointer transformation is part of our expression evaluation. And in
most cases this is exactly what we want. It's not clear to me how
we'd (easily) tell GDB that we didn't want this reduction in _some_
cases. But I'm sure this is solvable if we really wanted to.
3. $_as_string is a gdb.Function sub-class, and as such is passed
gdb.Value objects. There's no super convenient way to pass formatting
options to $_as_string. By this I mean that the new %V feature
supports print formatting options. Ideally, we might want to add this
feature to $_as_string, we might imagine it working something like:
(gdb) printf "%s\n", $_as_string(a1,
elements = 3,
array_indexes = True)
where the first item is the value to print, while the remaining
options are the print formatting options. However, this relies on
Python calling syntax, which isn't something that convenience
functions handle. We could possibly rely on strictly positional
arguments, like:
(gdb) printf "%s\n", $_as_string(a1, 3, 1)
But that's clearly terrible as there's far more print formatting
options, and if you needed to set the 9th option you'd need to fill in
all the previous options.
And right now, the only way to pass these options to a gdb.Function is
to have GDB first convert them all into gdb.Value objects, which is
really overkill for what we want.
The new %V format solves all these problems: the string is computed
and printed entirely on the GDB side, we are able to print arrays as
actual arrays rather than pointers, and we can pass named format
arguments.
Finally, the $_as_string is sold in the manual as allowing users to
print the string representation of flag enums, so given:
enum flags
{
FLAG_A = (1 << 0),
FLAG_B = (1 << 1),
FLAG_C = (1 << 1)
};
enum flags ff = FLAG_B;
We can:
(gdb) printf "%s\n", $_as_string(ff)
FLAG_B
This works just fine with %V too:
(gdb) printf "%V\n", ff
FLAG_B
So all functionality of $_as_string is replaced by %V. I'm not
proposing to remove $_as_string, there might be users currently
depending on it, but I am proposing that we don't push $_as_string in
the documentation.
As %V is a feature of printf, GDB's dprintf breakpoints naturally gain
access to this feature too. dprintf breakpoints can be operated in
three different styles 'gdb' (use GDB's printf), 'call' (call a
function in the inferior), or 'agent' (perform the dprintf on the
remote).
The use of '%V' will work just fine when dprintf-style is 'gdb'.
When dprintf-style is 'call' the format string and arguments are
passed to an inferior function (printf by default). In this case GDB
doesn't prevent use of '%V', but the documentation makes it clear that
support for '%V' will depend on the inferior function being called.
I chose this approach because the current implementation doesn't place
any restrictions on the format string when operating in 'call' style.
That is, the user might already be calling a function that supports
custom print format specifiers (maybe including '%V') so, I claim, it
would be wrong to block use of '%V' in this case. The documentation
does make it clear that users shouldn't expect this to "just work"
though.
When dprintf-style is 'agent' then GDB does no support the use of
'%V' (right now). This is handled at the point when GDB tries to
process the format string and send the dprintf command to the remote,
here's an example:
Reading symbols from /tmp/hello.x...
(gdb) dprintf call_me, "%V", a1
Dprintf 1 at 0x401152: file /tmp/hello.c, line 8.
(gdb) set sysroot /
(gdb) target remote | gdbserver --once - /tmp/hello.x
Remote debugging using | gdbserver --once - /tmp/hello.x
stdin/stdout redirected
Process /tmp/hello.x created; pid = 3088822
Remote debugging using stdio
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in /lib64/ld-linux-x86-64.so.2)
0x00007ffff7fd3110 in _start () from /lib64/ld-linux-x86-64.so.2
(gdb) set dprintf-style agent
(gdb) c
Continuing.
Unrecognized format specifier 'V' in printf
Command aborted.
(gdb)
This is exactly how GDB would handle any other invalid format
specifier, for example:
Reading symbols from /tmp/hello.x...
(gdb) dprintf call_me, "%Q", a1
Dprintf 1 at 0x401152: file /tmp/hello.c, line 8.
(gdb) set sysroot /
(gdb) target remote | gdbserver --once - /tmp/hello.x
Remote debugging using | gdbserver --once - /tmp/hello.x
stdin/stdout redirected
Process /tmp/hello.x created; pid = 3089193
Remote debugging using stdio
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in /lib64/ld-linux-x86-64.so.2)
0x00007ffff7fd3110 in _start () from /lib64/ld-linux-x86-64.so.2
(gdb) set dprintf-style agent
(gdb) c
Continuing.
Unrecognized format specifier 'Q' in printf
Command aborted.
(gdb)
The error message isn't the greatest, but improving that can be put
off for another day I hope.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Acked-By: Simon Marchi <simon.marchi@efficios.com>
2023-03-23 20:12:38 +08:00
|
|
|
* The printf command now accepts a '%V' output format which will
|
|
|
|
|
format an expression just as the 'print' command would. Print
|
2024-10-06 13:59:48 +08:00
|
|
|
options can be placed within '[...]' after the '%V' to modify how
|
gdb: add support for %V to printf command
This commit adds a new format for the printf and dprintf commands:
'%V'. This new format takes any GDB expression and formats it as a
string, just as GDB would for a 'print' command, e.g.:
(gdb) print a1
$a = {2, 4, 6, 8, 10, 12, 14, 16, 18, 20}
(gdb) printf "%V\n", a1
{2, 4, 6, 8, 10, 12, 14, 16, 18, 20}
(gdb)
It is also possible to pass the same options to %V as you might pass
to the print command, e.g.:
(gdb) print -elements 3 -- a1
$4 = {2, 4, 6...}
(gdb) printf "%V[-elements 3]\n", a1
{2, 4, 6...}
(gdb)
This new feature would effectively replace an existing feature of GDB,
the $_as_string builtin convenience function. However, the
$_as_string function has a few problems which this new feature solves:
1. $_as_string doesn't currently work when the inferior is not
running, e.g:
(gdb) printf "%s", $_as_string(a1)
You can't do that without a process to debug.
(gdb)
The reason for this is that $_as_string returns a value object with
string type. When we try to print this we call value_as_address,
which ends up trying to push the string into the inferior's address
space.
Clearly we could solve this problem, the string data exists in GDB, so
there's no reason why we have to push it into the inferior, but this
is an existing problem that would need solving.
2. $_as_string suffers from the fact that C degrades arrays to
pointers, e.g.:
(gdb) printf "%s\n", $_as_string(a1)
0x404260 <a1>
(gdb)
The implementation of $_as_string is passed a gdb.Value object that is
a pointer, it doesn't understand that it's actually an array. Solving
this would be harder than issue #1 I think. The whole array to
pointer transformation is part of our expression evaluation. And in
most cases this is exactly what we want. It's not clear to me how
we'd (easily) tell GDB that we didn't want this reduction in _some_
cases. But I'm sure this is solvable if we really wanted to.
3. $_as_string is a gdb.Function sub-class, and as such is passed
gdb.Value objects. There's no super convenient way to pass formatting
options to $_as_string. By this I mean that the new %V feature
supports print formatting options. Ideally, we might want to add this
feature to $_as_string, we might imagine it working something like:
(gdb) printf "%s\n", $_as_string(a1,
elements = 3,
array_indexes = True)
where the first item is the value to print, while the remaining
options are the print formatting options. However, this relies on
Python calling syntax, which isn't something that convenience
functions handle. We could possibly rely on strictly positional
arguments, like:
(gdb) printf "%s\n", $_as_string(a1, 3, 1)
But that's clearly terrible as there's far more print formatting
options, and if you needed to set the 9th option you'd need to fill in
all the previous options.
And right now, the only way to pass these options to a gdb.Function is
to have GDB first convert them all into gdb.Value objects, which is
really overkill for what we want.
The new %V format solves all these problems: the string is computed
and printed entirely on the GDB side, we are able to print arrays as
actual arrays rather than pointers, and we can pass named format
arguments.
Finally, the $_as_string is sold in the manual as allowing users to
print the string representation of flag enums, so given:
enum flags
{
FLAG_A = (1 << 0),
FLAG_B = (1 << 1),
FLAG_C = (1 << 1)
};
enum flags ff = FLAG_B;
We can:
(gdb) printf "%s\n", $_as_string(ff)
FLAG_B
This works just fine with %V too:
(gdb) printf "%V\n", ff
FLAG_B
So all functionality of $_as_string is replaced by %V. I'm not
proposing to remove $_as_string, there might be users currently
depending on it, but I am proposing that we don't push $_as_string in
the documentation.
As %V is a feature of printf, GDB's dprintf breakpoints naturally gain
access to this feature too. dprintf breakpoints can be operated in
three different styles 'gdb' (use GDB's printf), 'call' (call a
function in the inferior), or 'agent' (perform the dprintf on the
remote).
The use of '%V' will work just fine when dprintf-style is 'gdb'.
When dprintf-style is 'call' the format string and arguments are
passed to an inferior function (printf by default). In this case GDB
doesn't prevent use of '%V', but the documentation makes it clear that
support for '%V' will depend on the inferior function being called.
I chose this approach because the current implementation doesn't place
any restrictions on the format string when operating in 'call' style.
That is, the user might already be calling a function that supports
custom print format specifiers (maybe including '%V') so, I claim, it
would be wrong to block use of '%V' in this case. The documentation
does make it clear that users shouldn't expect this to "just work"
though.
When dprintf-style is 'agent' then GDB does no support the use of
'%V' (right now). This is handled at the point when GDB tries to
process the format string and send the dprintf command to the remote,
here's an example:
Reading symbols from /tmp/hello.x...
(gdb) dprintf call_me, "%V", a1
Dprintf 1 at 0x401152: file /tmp/hello.c, line 8.
(gdb) set sysroot /
(gdb) target remote | gdbserver --once - /tmp/hello.x
Remote debugging using | gdbserver --once - /tmp/hello.x
stdin/stdout redirected
Process /tmp/hello.x created; pid = 3088822
Remote debugging using stdio
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in /lib64/ld-linux-x86-64.so.2)
0x00007ffff7fd3110 in _start () from /lib64/ld-linux-x86-64.so.2
(gdb) set dprintf-style agent
(gdb) c
Continuing.
Unrecognized format specifier 'V' in printf
Command aborted.
(gdb)
This is exactly how GDB would handle any other invalid format
specifier, for example:
Reading symbols from /tmp/hello.x...
(gdb) dprintf call_me, "%Q", a1
Dprintf 1 at 0x401152: file /tmp/hello.c, line 8.
(gdb) set sysroot /
(gdb) target remote | gdbserver --once - /tmp/hello.x
Remote debugging using | gdbserver --once - /tmp/hello.x
stdin/stdout redirected
Process /tmp/hello.x created; pid = 3089193
Remote debugging using stdio
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in /lib64/ld-linux-x86-64.so.2)
0x00007ffff7fd3110 in _start () from /lib64/ld-linux-x86-64.so.2
(gdb) set dprintf-style agent
(gdb) c
Continuing.
Unrecognized format specifier 'Q' in printf
Command aborted.
(gdb)
The error message isn't the greatest, but improving that can be put
off for another day I hope.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Acked-By: Simon Marchi <simon.marchi@efficios.com>
2023-03-23 20:12:38 +08:00
|
|
|
the value is printed. E.g:
|
|
|
|
|
printf "%V", some_array
|
|
|
|
|
printf "%V[-array-indexes on]", some_array
|
|
|
|
|
will print the array without, or with array indexes included, just
|
|
|
|
|
as the array would be printed by the 'print' command. This
|
|
|
|
|
functionality is also available for dprintf when dprintf-style is
|
|
|
|
|
'gdb'.
|
|
|
|
|
|
gdb: check max-value-size when reading strings for printf
I noticed that the printf code for strings, printf_c_string and
printf_wide_c_string, don't take max-value-size into account, but do
load a complete string from the inferior into a GDB buffer.
As such it would be possible for an badly behaved inferior to cause
GDB to try and allocate an excessively large buffer, potentially
crashing GDB, or at least causing GDB to swap lots, which isn't
great.
We already have a setting to protect against this sort of thing, the
'max-value-size'. So this commit updates the two function mentioned
above to check the max-value-size and give an error if the
max-value-size is exceeded.
If the max-value-size is exceeded, I chose to continue reading
inferior memory to figure out how long the string actually is, we just
don't store the results. The benefit of this is that when we give the
user an error we can tell the user how big the string actually is,
which would allow them to correctly adjust max-value-size, if that's
what they choose to do.
The default for max-value-size is 64k so there should be no user
visible changes after this commit, unless the user was previously
printing very large strings. If that is the case then the user will
now need to increase max-value-size.
2023-06-01 04:41:48 +08:00
|
|
|
* When the printf command requires a string to be fetched from the
|
|
|
|
|
inferior, GDB now uses the existing 'max-value-size' setting to the
|
|
|
|
|
limit the memory allocated within GDB. The default 'max-value-size'
|
|
|
|
|
is 64k. To print longer strings you should increase
|
|
|
|
|
'max-value-size'.
|
|
|
|
|
|
2023-06-23 23:59:38 +08:00
|
|
|
* The Ada 2022 Enum_Rep and Enum_Val attributes are now supported.
|
|
|
|
|
|
2023-06-23 20:38:55 +08:00
|
|
|
* The Ada 2022 target name symbol ('@') is now supported by the Ada
|
|
|
|
|
expression parser.
|
|
|
|
|
|
2023-06-15 18:14:22 +08:00
|
|
|
* The 'list' command now accepts '.' as an argument, which tells GDB to
|
2023-09-19 20:06:49 +08:00
|
|
|
print the location around the point of execution within the current frame.
|
|
|
|
|
If the inferior hasn't started yet, the command will print around the
|
|
|
|
|
beginning of the 'main' function.
|
2023-06-15 18:14:22 +08:00
|
|
|
|
2023-06-15 17:17:07 +08:00
|
|
|
* Using the 'list' command with no arguments in a situation where the
|
|
|
|
|
command would attempt to list past the end of the file now warns the
|
|
|
|
|
user that the end of file has been reached, refers the user to the
|
|
|
|
|
newly added '.' argument
|
|
|
|
|
|
gdb: add inferior-specific breakpoints
This commit extends the breakpoint mechanism to allow for inferior
specific breakpoints (but not watchpoints in this commit).
As GDB gains better support for multiple connections, and so for
running multiple (possibly unrelated) inferiors, then it is not hard
to imagine that a user might wish to create breakpoints that apply to
any thread in a single inferior. To achieve this currently, the user
would need to create a condition possibly making use of the $_inferior
convenience variable, which, though functional, isn't the most user
friendly.
This commit adds a new 'inferior' keyword that allows for the creation
of inferior specific breakpoints.
Inferior specific breakpoints are automatically deleted when the
associated inferior is removed from GDB, this is similar to how
thread-specific breakpoints are deleted when the associated thread is
deleted.
Watchpoints are already per-program-space, which in most cases mean
watchpoints are already inferior specific. There is a small window
where inferior-specific watchpoints might make sense, which is after a
vfork, when two processes are sharing the same address space.
However, I'm leaving that as an exercise for another day. For now,
attempting to use the inferior keyword with a watchpoint will give an
error, like this:
(gdb) watch a8 inferior 1
Cannot use 'inferior' keyword with watchpoints
A final note on the implementation: currently, inferior specific
breakpoints, like thread-specific breakpoints, are inserted into every
inferior, GDB then checks once the inferior stops if we are in the
correct thread or inferior, and resumes automatically if we stopped in
the wrong thread/inferior.
An obvious optimisation here is to only insert breakpoint locations
into the specific program space (which mostly means inferior) that
contains either the inferior or thread we are interested in. This
would reduce the number times GDB has to stop and then resume again in
a multi-inferior setup.
I have a series on the mailing list[1] that implements this
optimisation for thread-specific breakpoints. Once this series has
landed I'll update that series to also handle inferior specific
breakpoints in the same way. For now, inferior specific breakpoints
are just slightly less optimal, but this is no different to
thread-specific breakpoints in a multi-inferior debug session, so I
don't see this as a huge problem.
[1] https://inbox.sourceware.org/gdb-patches/cover.1685479504.git.aburgess@redhat.com/
2022-11-08 20:32:51 +08:00
|
|
|
* Breakpoints can now be inferior-specific. This is similar to the
|
|
|
|
|
existing thread-specific breakpoint support. Breakpoint conditions
|
|
|
|
|
can include the 'inferior' keyword followed by an inferior id (as
|
|
|
|
|
displayed in the 'info inferiors' output). It is invalid to use the
|
|
|
|
|
'inferior' keyword with either the 'thread' or 'task' keywords when
|
|
|
|
|
creating a breakpoint.
|
|
|
|
|
|
2023-09-29 21:26:01 +08:00
|
|
|
* New convenience function "$_shell", to execute a shell command and
|
|
|
|
|
return the result. This lets you run shell commands in expressions.
|
|
|
|
|
Some examples:
|
|
|
|
|
|
|
|
|
|
(gdb) p $_shell("true")
|
|
|
|
|
$1 = 0
|
|
|
|
|
(gdb) p $_shell("false")
|
|
|
|
|
$2 = 1
|
|
|
|
|
(gdb) break func if $_shell("some command") == 0
|
|
|
|
|
|
2023-06-03 04:39:54 +08:00
|
|
|
* Configure changes
|
|
|
|
|
|
|
|
|
|
--additional-debug-dirs=PATHs
|
|
|
|
|
|
|
|
|
|
Provide a colon-separated list of additional directories to search for
|
|
|
|
|
separate debug info. These directories are added to the default value of
|
|
|
|
|
the 'debug-file-directory' GDB parameter.
|
|
|
|
|
|
2022-11-03 17:17:36 +08:00
|
|
|
* New commands
|
|
|
|
|
|
2019-12-03 20:13:25 +08:00
|
|
|
set debug breakpoint on|off
|
|
|
|
|
show debug breakpoint
|
|
|
|
|
Print additional debug messages about breakpoint insertion and removal.
|
|
|
|
|
|
2022-11-03 17:17:36 +08:00
|
|
|
maintenance print record-instruction [ N ]
|
|
|
|
|
Print the recorded information for a given instruction. If N is not given
|
|
|
|
|
prints how GDB would undo the last instruction executed. If N is negative,
|
|
|
|
|
prints how GDB would undo the N-th previous instruction, and if N is
|
|
|
|
|
positive, it prints how GDB will redo the N-th following instruction.
|
|
|
|
|
|
2023-02-10 20:07:14 +08:00
|
|
|
maintenance info frame-unwinders
|
|
|
|
|
List the frame unwinders currently in effect, starting with the highest
|
|
|
|
|
priority.
|
|
|
|
|
|
2023-03-04 00:41:35 +08:00
|
|
|
maintenance wait-for-index-cache
|
|
|
|
|
Wait until all pending writes to the index cache have completed.
|
|
|
|
|
|
[gdb/symtab] Add set/show always-read-ctf on/off
[ This is a simplified rewrite of an earlier submission "[RFC][gdb/symtab] Add
maint set symbol-read-order", submitted here (
https://sourceware.org/pipermail/gdb-patches/2022-September/192044.html
). ]
With the test-case included in this patch, we run into:
...
(gdb) file dwarf2-and-ctf
(gdb) print var_ctf^M
'var_ctf' has unknown type; cast it to its declared type^M
...
The problem is that the executable contains both ctf and dwarf2, so the ctf
info (which contains the type information about var_ctf) is ignored.
GDB has support for handling multiple debug formats, but the common use case
for ctf is to be used when dwarf2 is not present, and gdb reflects that,
assuming that by reading ctf in addition there won't be any extra information,
so it's not worth the additional cycles and memory.
Add a new command "set/show always-read-ctf on/off", that when on forces
unconditional reading of ctf, allowing us to do:
...
(gdb) set always-read-ctf on
(gdb) file dwarf2-and-ctf
(gdb) print var_ctf^M
$2 = 2^M
...
The setting is off by default, preserving current behaviour.
A bit of background on the relevance of reading order: the formats have a
priority relationship between them, where reading earlier means lower
priority. By reading the format with the most detail last, we ensure it has
the highest priority, which makes sure that in case there is overlapping info,
the most detailed info is found. This explains the current reading order of
mdebug, stabs and dwarf2.
Add the unconditional reading of ctf before dwarf2, because it's less detailed
than dwarf2. The conditional reading of ctf is still done after the attempt to
read dwarf2, necessarily so because we only know whether there's dwarf2 after
we've tried to read it.
The new command allow us to replace uses of -Wl,--strip-debug added in commit
908a926ec4e ("[gdb/testsuite] Fix ctf test-cases on openSUSE Tumbleweed") by
uses of "set always-read-ctf on", but I've left that for another commit.
Tested on x86_64-linux.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Reviewed-By: Tom Tromey <tom@tromey.com>
2023-03-02 17:56:40 +08:00
|
|
|
set always-read-ctf on|off
|
|
|
|
|
show always-read-ctf
|
|
|
|
|
When off, CTF is only read if DWARF is not present. When on, CTF is
|
|
|
|
|
read regardless of whether DWARF is present. Off by default.
|
|
|
|
|
|
2023-03-31 22:31:40 +08:00
|
|
|
info main
|
|
|
|
|
Get main symbol to identify entry point into program.
|
|
|
|
|
|
gdb/tui: add 'set tui mouse-events off' to restore mouse selection
Rationale:
I use the mouse with my terminal to select and copy text. In gdb, I use
the mouse to select a function name to set a breakpoint, or a variable
name to print, for example.
When gdb is compiled with ncurses mouse support, gdb's TUI mode
intercepts mouse events. Left-clicking and dragging, which would
normally select text, seems to do nothing. This means I cannot select
text using my mouse anymore. This makes it harder to set breakpoints,
print variables, etc.
Solution:
I tried to fix this issue by editing the 'mousemask' call to only enable
buttons 4 and 5. However, this still caused my terminal (gnome-terminal)
to not allow text to be selected. The only way I could make it work is
by calling 'mousemask (0, NULL);'. But doing so disables the mouse code
entirely, which other people might want.
I therefore decided to make a setting in gdb called 'tui mouse-events'.
If enabled (the default), the behavior is as it is now: terminal mouse
events are given to gdb, disabling the terminal's default behavior.
If disabled (opt-in), the behavior is as it was before the year 2020:
terminal mouse events are not given to gdb, therefore the mouse can be
used to select and copy text.
Notes:
I am not attached to the setting name or its description. Feel free to
suggest better wording.
Testing:
I tested this change in gnome-terminal by performing the following steps
manually:
1. Run: gdb --args ./myprogram
2. Enable TUI: press ctrl-x ctrl-a
3. Click and drag text with the mouse. Observe no selection.
4. Input: set tui mouse-events off
5. Click and drag text with the mouse. Observe that selection works now.
6. Input: set tui mouse-events on.
7. Click and drag text with the mouse. Observe no selection.
2023-01-28 08:19:45 +08:00
|
|
|
set tui mouse-events [on|off]
|
|
|
|
|
show tui mouse-events
|
|
|
|
|
When on (default), mouse clicks control the TUI and can be accessed by
|
|
|
|
|
Python extensions. When off, mouse clicks are handled by the terminal,
|
|
|
|
|
enabling terminal-native text selection.
|
|
|
|
|
|
gdb/mi: add no-history stop reason
When executing in reverse and runs out of recorded history, GDB prints
a warning to the user, but does not add a reason in the stopped record,
for example:
*stopped,frame={addr="0x000000000040113e",func="main",args=[],file="/home/blarsen/Documents/fsf_build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.reverse/solib-reverse.c",fullname="/home/blarsen/Documents/binutils-gdb/gdb/testsuite/gdb.reverse/solib-reverse.c",line="27",arch="i386:x86-64"},thread-id="1",stopped-threads="all",core="1"
This problem was reported as record/29260.
This commit adds the reason no-history to the record, making it easier
for interfaces using the mi interpreter to report the result. It also
changes the test gdb.mi/mi-reverse.exp to test that the reason shows up
correctly.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29260
2023-01-02 21:35:50 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
2023-09-29 21:26:01 +08:00
|
|
|
** MI version 1 has been removed.
|
|
|
|
|
|
gdb/mi: add no-history stop reason
When executing in reverse and runs out of recorded history, GDB prints
a warning to the user, but does not add a reason in the stopped record,
for example:
*stopped,frame={addr="0x000000000040113e",func="main",args=[],file="/home/blarsen/Documents/fsf_build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.reverse/solib-reverse.c",fullname="/home/blarsen/Documents/binutils-gdb/gdb/testsuite/gdb.reverse/solib-reverse.c",line="27",arch="i386:x86-64"},thread-id="1",stopped-threads="all",core="1"
This problem was reported as record/29260.
This commit adds the reason no-history to the record, making it easier
for interfaces using the mi interpreter to report the result. It also
changes the test gdb.mi/mi-reverse.exp to test that the reason shows up
correctly.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29260
2023-01-02 21:35:50 +08:00
|
|
|
** mi now reports 'no-history' as a stop reason when hitting the end of the
|
|
|
|
|
reverse execution history.
|
|
|
|
|
|
gdb: don't duplicate 'thread' field in MI breakpoint output
When creating a thread-specific breakpoint with a single location, the
'thread' field would be repeated in the MI output. This can be seen
in two existing tests gdb.mi/mi-nsmoribund.exp and
gdb.mi/mi-pending.exp, e.g.:
(gdb)
-break-insert -p 1 bar
^done,bkpt={number="1",type="breakpoint",disp="keep",
enabled="y",
addr="0x000000000040110a",func="bar",
file="/tmp/mi-thread-specific-bp.c",
fullname="/tmp/mi-thread-specific-bp.c",
line="32",thread-groups=["i1"],
thread="1",thread="1", <================ DUPLICATION!
times="0",original-location="bar"}
I know we need to be careful when adjusting MI output, but I'm hopeful
in this case, as the field is duplicated, and the field contents are
always identical, that we might get away with removing one of the
duplicates.
The change in GDB is a fairly trivial condition change.
We did have a couple of tests that contained the duplicate fields in
their expected output, but given there was no comment pointing out
this oddity either in the GDB code, or in the test, I suspect this was
more a case of copying whatever output GDB produced and using that as
the expected results. I've updated these tests to remove the
duplication.
I've update lib/mi-support.exp to provide support for building
breakpoint patterns that contain the thread field, and I've made use
of this in a new test I've added that is just about creating
thread-specific breakpoints and checking the results. The two tests I
mentioned above as being updated could also use the new
lib/mi-support.exp functionality, but I'm going to do that in a later
patch, this way it is clear what changes I'm actually proposing to
make to the expected output.
As I said, I hope that frontends will be able to handle this change,
but I still think its worth adding a NEWS entry, that way, if someone
runs into problems, there's a chance they can figure out what's going
on.
This should not impact CLI output at all.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-By: Pedro Alves <pedro@palves.net>
2023-02-17 18:48:06 +08:00
|
|
|
** When creating a thread-specific breakpoint using the '-p' option,
|
|
|
|
|
the -break-insert command would report the 'thread' field twice in
|
|
|
|
|
the reply. The content of both fields was always identical. This
|
|
|
|
|
has now been fixed; the 'thread' field will be reported just once
|
|
|
|
|
for thread-specific breakpoints, or not at all for breakpoints
|
|
|
|
|
without a thread restriction. The same is also true for the 'task'
|
|
|
|
|
field of an Ada task-specific breakpoint.
|
|
|
|
|
|
gdb/mi: check thread exists when creating thread-specific b/p
I noticed the following behaviour:
$ gdb -q -i=mi /tmp/hello.x
=thread-group-added,id="i1"
=cmd-param-changed,param="print pretty",value="on"
~"Reading symbols from /tmp/hello.x...\n"
(gdb)
-break-insert -p 99 main
^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000000000401198",func="main",file="/tmp/hello.c",fullname="/tmp/hello.c",line="18",thread-groups=["i1"],thread="99",times="0",original-location="main"}
(gdb)
info breakpoints
&"info breakpoints\n"
~"Num Type Disp Enb Address What\n"
~"1 breakpoint keep y 0x0000000000401198 in main at /tmp/hello.c:18\n"
&"../../src/gdb/thread.c:1434: internal-error: print_thread_id: Assertion `thr != nullptr' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable."
&"\n"
&"----- Backtrace -----\n"
&"Backtrace unavailable\n"
&"---------------------\n"
&"\nThis is a bug, please report it."
&" For instructions, see:\n"
&"<https://www.gnu.org/software/gdb/bugs/>.\n\n"
Aborted (core dumped)
What we see here is that when using the MI a user can create
thread-specific breakpoints for non-existent threads. Then if we try
to use the CLI 'info breakpoints' command GDB throws an assertion.
The assert is a result of the print_thread_id call when trying to
build the 'stop only in thread xx.yy' line; print_thread_id requires a
valid thread_info pointer, which we can't have for a non-existent
thread.
In contrast, when using the CLI we see this behaviour:
$ gdb -q /tmp/hello.x
Reading symbols from /tmp/hello.x...
(gdb) break main thread 99
Unknown thread 99.
(gdb)
The CLI doesn't allow a breakpoint to be created for a non-existent
thread. So the 'info breakpoints' command is always fine.
Interestingly, the MI -break-info command doesn't crash, this is
because the MI uses global thread-ids, and so never calls
print_thread_id. However, GDB does support using CLI and MI in
parallel, so we need to solve this problem.
One option would be to change the CLI behaviour to allow printing
breakpoints for non-existent threads. This would preserve the current
MI behaviour.
The other option is to pull the MI into line with the CLI and prevent
breakpoints being created for non-existent threads. This is good for
consistency, but is a breaking change for the MI.
In the end I figured that it was probably better to retain the
consistent CLI behaviour, and just made the MI reject requests to
place a breakpoint on a non-existent thread. The only test we had
that depended on the old behaviour was
gdb.mi/mi-thread-specific-bp.exp, which was added by me in commit:
commit 2fd9a436c8d24eb0af85ccb3a2fbdf9a9c679a6c
Date: Fri Feb 17 10:48:06 2023 +0000
gdb: don't duplicate 'thread' field in MI breakpoint output
I certainly didn't intend for this test to rely on this feature of the
MI, so I propose to update this test to only create breakpoints for
threads that exist.
Actually, I've added a new test that checks the MI rejects creating a
breakpoint for a non-existent thread, and I've also extended the test
to run with the separate MI/CLI UIs, and then tested 'info
breakpoints' to ensure this command doesn't crash.
I've extended the documentation of the `-p` flag to explain the
constraints better.
I have also added a NEWS entry just in case someone runs into this
issue, at least then they'll know this change in behaviour was
intentional.
One thing that I did wonder about while writing this patch, is whether
we should treat requests like this, on both the MI and CLI, as another
form of pending breakpoint, something like:
(gdb) break foo thread 9
Thread 9 does not exist.
Make breakpoint pending on future thread creation? (y or [n]) y
Breakpoint 1 (foo thread 9) pending.
(gdb) info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep y <PENDING> foo thread 9
Don't know if folk think that would be a useful idea or not? Either
way, I think that would be a separate patch from this one.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
2023-03-04 07:17:39 +08:00
|
|
|
** It is no longer possible to create a thread-specific breakpoint for
|
|
|
|
|
a thread that doesn't exist using '-break-insert -p ID'. Creating
|
|
|
|
|
breakpoints for non-existent threads is not allowed when using the
|
|
|
|
|
CLI, that the MI allowed it was a long standing bug, which has now
|
|
|
|
|
been fixed.
|
|
|
|
|
|
Don't treat references to compound values as "simple".
SUMMARY
The '--simple-values' argument to '-stack-list-arguments' and similar
GDB/MI commands does not take reference types into account, so that
references to arbitrarily large structures are considered "simple" and
printed. This means that the '--simple-values' argument cannot be used
by IDEs when tracing the stack due to the time taken to print large
structures passed by reference.
DETAILS
Various GDB/MI commands ('-stack-list-arguments', '-stack-list-locals',
'-stack-list-variables' and so on) take a PRINT-VALUES argument which
may be '--no-values' (0), '--all-values' (1) or '--simple-values' (2).
In the '--simple-values' case, the command is supposed to print the
name, type, and value of variables with simple types, and print only the
name and type of variables with compound types.
The '--simple-values' argument ought to be suitable for IDEs that need
to update their user interface with the program's call stack every time
the program stops. However, it does not take C++ reference types into
account, and this makes the argument unsuitable for this purpose.
For example, consider the following C++ program:
struct s {
int v[10];
};
int
sum(const struct s &s)
{
int total = 0;
for (int i = 0; i < 10; ++i) total += s.v[i];
return total;
}
int
main(void)
{
struct s s = { { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 } };
return sum(s);
}
If we start GDB in MI mode and continue to 'sum', the behaviour of
'-stack-list-arguments' is as follows:
(gdb)
-stack-list-arguments --simple-values
^done,stack-args=[frame={level="0",args=[{name="s",type="const s &",value="@0x7fffffffe310: {v = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10}}"}]},frame={level="1",args=[]}]
Note that the value of the argument 's' was printed, even though 's' is
a reference to a structure, which is not a simple value.
See https://github.com/microsoft/MIEngine/pull/673 for a case where this
behaviour caused Microsoft to avoid the use of '--simple-values' in
their MIEngine debug adapter, because it caused Visual Studio Code to
take too long to refresh the call stack in the user interface.
SOLUTIONS
There are two ways we could fix this problem, depending on whether we
consider the current behaviour to be a bug.
1. If the current behaviour is a bug, then we can update the behaviour
of '--simple-values' so that it takes reference types into account:
that is, a value is simple if it is neither an array, struct, or
union, nor a reference to an array, struct or union.
In this case we must add a feature to the '-list-features' command so
that IDEs can detect that it is safe to use the '--simple-values'
argument when refreshing the call stack.
2. If the current behaviour is not a bug, then we can add a new option
for the PRINT-VALUES argument, for example, '--scalar-values' (3),
that would be suitable for use by IDEs.
In this case we must add a feature to the '-list-features' command
so that IDEs can detect that the '--scalar-values' argument is
available for use when refreshing the call stack.
PATCH
This patch implements solution (1) as I think the current behaviour of
not printing structures, but printing references to structures, is
contrary to reasonable expectation.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29554
2023-03-11 19:49:34 +08:00
|
|
|
** The '--simple-values' argument to the '-stack-list-arguments',
|
|
|
|
|
'-stack-list-locals', '-stack-list-variables', and '-var-list-children'
|
|
|
|
|
commands now takes reference types into account: that is, a value is now
|
|
|
|
|
considered simple if it is neither an array, structure, or union, nor a
|
|
|
|
|
reference to an array, structure, or union. (Previously all references were
|
|
|
|
|
considered simple.) Support for this feature can be verified by using the
|
|
|
|
|
'-list-features' command, which should contain "simple-values-ref-types".
|
|
|
|
|
|
gdb: add inferior-specific breakpoints
This commit extends the breakpoint mechanism to allow for inferior
specific breakpoints (but not watchpoints in this commit).
As GDB gains better support for multiple connections, and so for
running multiple (possibly unrelated) inferiors, then it is not hard
to imagine that a user might wish to create breakpoints that apply to
any thread in a single inferior. To achieve this currently, the user
would need to create a condition possibly making use of the $_inferior
convenience variable, which, though functional, isn't the most user
friendly.
This commit adds a new 'inferior' keyword that allows for the creation
of inferior specific breakpoints.
Inferior specific breakpoints are automatically deleted when the
associated inferior is removed from GDB, this is similar to how
thread-specific breakpoints are deleted when the associated thread is
deleted.
Watchpoints are already per-program-space, which in most cases mean
watchpoints are already inferior specific. There is a small window
where inferior-specific watchpoints might make sense, which is after a
vfork, when two processes are sharing the same address space.
However, I'm leaving that as an exercise for another day. For now,
attempting to use the inferior keyword with a watchpoint will give an
error, like this:
(gdb) watch a8 inferior 1
Cannot use 'inferior' keyword with watchpoints
A final note on the implementation: currently, inferior specific
breakpoints, like thread-specific breakpoints, are inserted into every
inferior, GDB then checks once the inferior stops if we are in the
correct thread or inferior, and resumes automatically if we stopped in
the wrong thread/inferior.
An obvious optimisation here is to only insert breakpoint locations
into the specific program space (which mostly means inferior) that
contains either the inferior or thread we are interested in. This
would reduce the number times GDB has to stop and then resume again in
a multi-inferior setup.
I have a series on the mailing list[1] that implements this
optimisation for thread-specific breakpoints. Once this series has
landed I'll update that series to also handle inferior specific
breakpoints in the same way. For now, inferior specific breakpoints
are just slightly less optimal, but this is no different to
thread-specific breakpoints in a multi-inferior debug session, so I
don't see this as a huge problem.
[1] https://inbox.sourceware.org/gdb-patches/cover.1685479504.git.aburgess@redhat.com/
2022-11-08 20:32:51 +08:00
|
|
|
** The -break-insert command now accepts a '-g thread-group-id' option
|
|
|
|
|
to allow for the creation of inferior-specific breakpoints.
|
|
|
|
|
|
|
|
|
|
** The bkpt tuple, which appears in breakpoint-created notifications,
|
|
|
|
|
and in the result of the -break-insert command can now include an
|
|
|
|
|
optional 'inferior' field for both the main breakpoint, and each
|
|
|
|
|
location, when the breakpoint is inferior-specific.
|
|
|
|
|
|
2023-03-09 00:11:30 +08:00
|
|
|
* Python API
|
|
|
|
|
|
gdb/Python: Added ThreadExitedEvent
v6:
Fix comments.
Fix copyright
Remove unnecessary test suite stuff. save_var had to stay, as it mutates
some test suite state that otherwise fails.
v5:
Did what Tom Tromey requested in v4; which can be found here: https://pi.simark.ca/gdb-patches/87pmjm0xar.fsf@tromey.com/
v4:
Doc formatting fixed.
v3:
Eli:
Updated docs & NEWS to reflect new changes. Added
a reference from the .ptid attribute of the ThreadExitedEvent
to the ptid attribute of InferiorThread. To do this,
I've added an anchor to that attribute.
Tom:
Tom requested that I should probably just emit the thread object;
I ran into two issues for this, which I could not resolve in this patch;
1 - The Thread Object (the python type) checks it's own validity
by doing a comparison of it's `thread_info* thread` to nullptr. This
means that any access of it's attributes may (probably, since we are
in "async" land) throw Python exceptions because the thread has been
removed from the thread object. Therefore I've decided in v3 of this
patch to just emit most of the same fields that gdb.InferiorThread has, namely
global_num, name, num and ptid (the 3-attribute tuple provided by
gdb.InferiorThread.ptid).
2 - A python user can hold a global reference to an exiting thread. Thus
in order to have a ThreadExit event that can provide attribute access
reliably (both as a global reference, but also inside the thread exit
handler, as we can never guarantee that it's executed _before_ the
thread_info pointer is removed from the gdbpy thread object),
the `thread_info *` thread pointer must not be null. However, this
comes at the cost of gdb.InferiorThread believing it is "valid" - which means,
that if a user holds takes a global reference to that
exiting event thread object, they can some time later do `t.switch()` at which
point GDB will 'explode' so to speak.
v2:
Fixed white space issues and NULL/nullptr stuff,
as requested by Tom Tromey.
v1:
Currently no event is emitted for a thread exit.
This adds this functionality by emitting a new gdb.ThreadExitedEvent.
It currently provides four attributes:
- global_num: The GDB assigned global thread number
- num: the per-inferior thread number
- name: name of the thread or none if not set
- ptid: the PTID of the thread, a 3-attribute tuple, identical to
InferiorThread.ptid attribute
Added info to docs & the NEWS file as well.
Added test to test suite.
Fixed formatting.
Feedback wanted and appreciated.
2022-04-20 16:25:47 +08:00
|
|
|
** gdb.ThreadExitedEvent added. Emits a ThreadEvent.
|
|
|
|
|
|
2023-03-09 00:11:30 +08:00
|
|
|
** The gdb.unwinder.Unwinder.name attribute is now read-only.
|
|
|
|
|
|
|
|
|
|
** The name argument passed to gdb.unwinder.Unwinder.__init__ must
|
|
|
|
|
now be of type 'str' otherwise a TypeError will be raised.
|
|
|
|
|
|
|
|
|
|
** The gdb.unwinder.Unwinder.enabled attribute can now only accept
|
|
|
|
|
values of type 'bool'. Changing this attribute will now
|
|
|
|
|
invalidate GDB's frame-cache, which means GDB will need to
|
|
|
|
|
rebuild its frame-cache when next required - either with, or
|
|
|
|
|
without the particular unwinder, depending on how 'enabled' was
|
|
|
|
|
changed.
|
|
|
|
|
|
gdb/python: add some additional methods to gdb.PendingFrame
The gdb.Frame class has far more methods than gdb.PendingFrame. Given
that a PendingFrame hasn't yet been claimed by an unwinder, there is a
limit to which methods we can add to it, but many of the methods that
the Frame class has, the PendingFrame class could also support.
In this commit I've added those methods to PendingFrame that I believe
are safe.
In terms of implementation: if I was starting from scratch then I
would implement many of these (or most of these) as attributes rather
than methods. However, given both Frame and PendingFrame are just
different representation of a frame, I think there is value in keeping
the interface for the two classes the same. For this reason
everything here is a method -- that's what the Frame class does.
The new methods I've added are:
- gdb.PendingFrame.is_valid: Return True if the pending frame
object is valid.
- gdb.PendingFrame.name: Return the name for the frame's function,
or None.
- gdb.PendingFrame.pc: Return the $pc register value for this
frame.
- gdb.PendingFrame.language: Return a string containing the
language for this frame, or None.
- gdb.PendingFrame.find_sal: Return a gdb.Symtab_and_line object
for the current location within the pending frame, or None.
- gdb.PendingFrame.block: Return a gdb.Block for the current
pending frame, or None.
- gdb.PendingFrame.function: Return a gdb.Symbol for the current
pending frame, or None.
In every case I've just copied the implementation over from gdb.Frame
and cleaned the code slightly e.g. NULL to nullptr. Additionally each
function required a small update to reflect the PendingFrame type, but
that's pretty minor.
There are tests for all the new methods.
For more extensive testing, I added the following code to the file
gdb/python/lib/command/unwinders.py:
from gdb.unwinder import Unwinder
class TestUnwinder(Unwinder):
def __init__(self):
super().__init__("XXX_TestUnwinder_XXX")
def __call__(self,pending_frame):
lang = pending_frame.language()
try:
block = pending_frame.block()
assert isinstance(block, gdb.Block)
except RuntimeError as rte:
assert str(rte) == "Cannot locate block for frame."
function = pending_frame.function()
arch = pending_frame.architecture()
assert arch is None or isinstance(arch, gdb.Architecture)
name = pending_frame.name()
assert name is None or isinstance(name, str)
valid = pending_frame.is_valid()
pc = pending_frame.pc()
sal = pending_frame.find_sal()
assert sal is None or isinstance(sal, gdb.Symtab_and_line)
return None
gdb.unwinder.register_unwinder(None, TestUnwinder())
This registers a global unwinder that calls each of the new
PendingFrame methods and checks the result is of an acceptable type.
The unwinder never claims any frames though, so shouldn't change how
GDB actually behaves.
I then ran the testsuite. There was only a single regression, a test
that uses 'disable unwinder' and expects a single unwinder to be
disabled -- the extra unwinder is now disabled too, which changes the
test output. So I'm reasonably confident that the new methods are not
going to crash GDB.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Reviewed-By: Tom Tromey <tom@tromey.com>
2023-03-09 00:11:45 +08:00
|
|
|
** New methods added to the gdb.PendingFrame class. These methods
|
|
|
|
|
have the same behaviour as the corresponding methods on
|
|
|
|
|
gdb.Frame. The new methods are:
|
|
|
|
|
|
|
|
|
|
- gdb.PendingFrame.name: Return the name for the frame's
|
|
|
|
|
function, or None.
|
|
|
|
|
- gdb.PendingFrame.is_valid: Return True if the pending frame
|
|
|
|
|
object is valid.
|
|
|
|
|
- gdb.PendingFrame.pc: Return the $pc register value for this
|
|
|
|
|
frame.
|
|
|
|
|
- gdb.PendingFrame.language: Return a string containing the
|
|
|
|
|
language for this frame, or None.
|
|
|
|
|
- gdb.PendingFrame.find_sal: Return a gdb.Symtab_and_line
|
|
|
|
|
object for the current location within the pending frame, or
|
|
|
|
|
None.
|
|
|
|
|
- gdb.PendingFrame.block: Return a gdb.Block for the current
|
|
|
|
|
pending frame, or None.
|
|
|
|
|
- gdb.PendingFrame.function: Return a gdb.Symbol for the
|
|
|
|
|
current pending frame, or None.
|
|
|
|
|
|
gdb/python: Allow gdb.UnwindInfo to be created with non gdb.Value args
Currently when creating a gdb.UnwindInfo object a user must call
gdb.PendingFrame.create_unwind_info and pass a frame-id object.
The frame-id object should have at least a 'sp' attribute, and
probably a 'pc' attribute too (it can also, in some cases have a
'special' attribute).
Currently all of these frame-id attributes need to be gdb.Value
objects, but the only reason for that requirement is that we have some
code in py-unwind.c that only handles gdb.Value objects.
If instead we switch to using get_addr_from_python in py-utils.c then
we will support both gdb.Value objects and also raw numbers, which
might make things simpler in some cases.
So, I started rewriting pyuw_object_attribute_to_pointer (in
py-unwind.c) to use get_addr_from_python. However, while looking at
the code I noticed a problem.
The pyuw_object_attribute_to_pointer function returns a boolean flag,
if everything goes OK we return true, but we return false in two
cases, (1) when the attribute is not present, which might be
acceptable, or might be an error, and (2) when we get an error trying
to extract the attribute value, in which case a Python error will have
been set.
Now in pending_framepy_create_unwind_info we have this code:
if (!pyuw_object_attribute_to_pointer (pyo_frame_id, "sp", &sp))
{
PyErr_SetString (PyExc_ValueError,
_("frame_id should have 'sp' attribute."));
return NULL;
}
Notice how we always set an error. This will override any error that
is already set.
So, if you create a frame-id object that has an 'sp' attribute, but
the attribute is not a gdb.Value, then currently we fail to extract
the attribute value (it's not a gdb.Value) and set this error in
pyuw_object_attribute_to_pointer:
rc = pyuw_value_obj_to_pointer (pyo_value.get (), addr);
if (!rc)
PyErr_Format (
PyExc_ValueError,
_("The value of the '%s' attribute is not a pointer."),
attr_name);
Then we return to pending_framepy_create_unwind_info and immediately
override this error with the error about 'sp' being missing.
This all feels very confused.
Here's my proposed solution: pyuw_object_attribute_to_pointer will now
return a tri-state enum, with states OK, MISSING, or ERROR. The
meanings of these states are:
OK - Attribute exists and was extracted fine,
MISSING - Attribute doesn't exist, no Python error was set.
ERROR - Attribute does exist, but there was an error while
extracting it, a Python error was set.
We need to update pending_framepy_create_unwind_info, the only user of
pyuw_object_attribute_to_pointer, but now I think things are much
clearer. Errors from lower levels are not blindly overridden with the
generic meaningless error message, but we still get the "missing 'sp'
attribute" error when appropriate.
This change also includes the switch to get_addr_from_python which was
what started this whole journey.
For well behaving user code there should be no visible changes after
this commit.
For user code that hits an error, hopefully the new errors should be
more helpful in figuring out what's gone wrong.
Additionally, users can now use integers for the 'sp' and 'pc'
attributes in their frame-id objects if that is useful.
Reviewed-By: Tom Tromey <tom@tromey.com>
2023-03-10 19:29:39 +08:00
|
|
|
** The frame-id passed to gdb.PendingFrame.create_unwind_info can
|
|
|
|
|
now use either an integer or a gdb.Value object for each of its
|
|
|
|
|
'sp', 'pc', and 'special' attributes.
|
|
|
|
|
|
2023-03-10 20:29:58 +08:00
|
|
|
** A new class gdb.unwinder.FrameId has been added. Instances of
|
|
|
|
|
this class are constructed with 'sp' (stack-pointer) and 'pc'
|
|
|
|
|
(program-counter) values, and can be used as the frame-id when
|
|
|
|
|
calling gdb.PendingFrame.create_unwind_info.
|
|
|
|
|
|
gdb/python: rework how the disassembler API reads the result object
This commit is a refactor ahead of the next change which will make
disassembler styling available through the Python API.
Unfortunately, in order to make the styling support available, I think
the easiest solution is to make a very small change to the existing
API.
The current API relies on returning a DisassemblerResult object to
represent each disassembled instruction. Currently GDB allows the
DisassemblerResult class to be sub-classed, which could mean that a
user tries to override the various attributes that exist on the
DisassemblerResult object.
This commit removes this ability, effectively making the
DisassemblerResult class final.
Though this is a change to the existing API, I'm hoping this isn't
going to cause too many issues:
- The Python disassembler API was only added in the previous release
of GDB, so I don't expect it to be widely used yet, and
- It's not clear to me why a user would need to sub-class the
DisassemblerResult type, I allowed it in the original patch
because at the time I couldn't see any reason to NOT allow it.
Having prevented sub-classing I can now rework the tail end of the
gdbpy_print_insn function; instead of pulling the results out of the
DisassemblerResult object by calling back into Python, I now cast the
Python object back to its C++ type (disasm_result_object), and access
the fields directly from there. In later commits I will be reworking
the disasm_result_object type in order to hold information about the
styled disassembler output.
The tests that dealt with sub-classing DisassemblerResult have been
removed, and a new test that confirms that DisassemblerResult can't be
sub-classed has been added.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Reviewed-By: Tom Tromey <tom@tromey.com>
2023-01-23 23:31:28 +08:00
|
|
|
** It is now no longer possible to sub-class the
|
|
|
|
|
gdb.disassembler.DisassemblerResult type.
|
|
|
|
|
|
gdb/python: extend the Python Disassembler API to allow for styling
This commit extends the Python Disassembler API to allow for styling
of the instructions.
Before this commit the Python Disassembler API allowed the user to do
two things:
- They could intercept instruction disassembly requests and return a
string of their choosing, this string then became the disassembled
instruction, or
- They could call builtin_disassemble, which would call back into
libopcode to perform the disassembly. As libopcode printed the
instruction GDB would collect these print requests and build a
string. This string was then returned from the builtin_disassemble
call, and the user could modify or extend this string as needed.
Neither of these approaches allowed for, or preserved, disassembler
styling, which is now available within libopcodes for many of the more
popular architectures GDB supports.
This commit aims to fill this gap. After this commit a user will be
able to do the following things:
- Implement a custom instruction disassembler entirely in Python
without calling back into libopcodes, the custom disassembler will
be able to return styling information such that GDB will display
the instruction fully styled. All of GDB's existing style
settings will affect how instructions coming from the Python
disassembler are displayed in the expected manner.
- Call builtin_disassemble and receive a result that represents how
libopcode would like the instruction styled. The user can then
adjust or extend the disassembled instruction before returning the
result to GDB. Again, the instruction will be styled as expected.
To achieve this I will add two new classes to GDB,
DisassemblerTextPart and DisassemblerAddressPart.
Within builtin_disassemble, instead of capturing the print calls from
libopcodes and building a single string, we will now create either a
text part or address part and store these parts in a vector.
The DisassemblerTextPart will capture a small piece of text along with
the associated style that should be used to display the text. This
corresponds to the disassembler calling
disassemble_info::fprintf_styled_func, or for disassemblers that don't
support styling disassemble_info::fprintf_func.
The DisassemblerAddressPart is used when libopcodes requests that an
address be printed, and takes care of printing the address and
associated symbol, this corresponds to the disassembler calling
disassemble_info::print_address_func.
These parts are then placed within the DisassemblerResult when
builtin_disassemble returns.
Alternatively, the user can directly create parts by calling two new
methods on the DisassembleInfo class: DisassembleInfo.text_part and
DisassembleInfo.address_part.
Having created these parts the user can then pass these parts when
initializing a new DisassemblerResult object.
Finally, when we return from Python to gdbpy_print_insn, one way or
another, the result being returned will have a list of parts. Back in
GDB's C++ code we walk the list of parts and call back into GDB's core
to display the disassembled instruction with the correct styling.
The new API lives in parallel with the old API. Any existing code
that creates a DisassemblerResult using a single string immediately
creates a single DisassemblerTextPart containing the entire
instruction and gives this part the default text style. This is also
what happens if the user calls builtin_disassemble for an architecture
that doesn't (yet) support libopcode styling.
This matches up with what happens when the Python API is not involved,
an architecture without disassembler styling support uses the old
libopcodes printing API (the API that doesn't pass style info), and
GDB just prints everything using the default text style.
The reason that parts are created by calling methods on
DisassembleInfo, rather than calling the class constructor directly,
is DisassemblerAddressPart. Ideally this part would only hold the
address which the part represents, but in order to support backwards
compatibility we need to be able to convert the
DisassemblerAddressPart into a string. To do that we need to call
GDB's internal print_address function, and to do that we need an
gdbarch.
What this means is that the DisassemblerAddressPart needs to take a
gdb.Architecture object at creation time. The only valid place a user
can pull this from is from the DisassembleInfo object, so having the
DisassembleInfo act as a factory ensures that the correct gdbarch is
passed over each time. I implemented both solutions (the one
presented here, and an alternative where parts could be constructed
directly), and this felt like the cleanest solution.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Reviewed-By: Tom Tromey <tom@tromey.com>
2023-01-24 23:35:45 +08:00
|
|
|
** The Disassembler API from the gdb.disassembler module has been
|
|
|
|
|
extended to include styling support:
|
|
|
|
|
|
|
|
|
|
- The DisassemblerResult class can now be initialized with a list
|
|
|
|
|
of parts. Each part represents part of the disassembled
|
|
|
|
|
instruction along with the associated style information. This
|
|
|
|
|
list of parts can be accessed with the new
|
|
|
|
|
DisassemblerResult.parts property.
|
|
|
|
|
|
|
|
|
|
- New constants gdb.disassembler.STYLE_* representing all the
|
|
|
|
|
different styles part of an instruction might have.
|
|
|
|
|
|
|
|
|
|
- New methods DisassembleInfo.text_part and
|
|
|
|
|
DisassembleInfo.address_part which are used to create the new
|
|
|
|
|
styled parts of a disassembled instruction.
|
|
|
|
|
|
|
|
|
|
- Changes are backwards compatible, the older API can still be
|
|
|
|
|
used to disassemble instructions without styling.
|
|
|
|
|
|
2023-03-17 00:57:32 +08:00
|
|
|
** New function gdb.execute_mi(COMMAND, [ARG]...), that invokes a
|
|
|
|
|
GDB/MI command and returns the output as a Python dictionary.
|
|
|
|
|
|
2023-07-04 23:15:54 +08:00
|
|
|
** New function gdb.block_signals(). This returns a context manager
|
|
|
|
|
that blocks any signals that GDB needs to handle itself.
|
|
|
|
|
|
|
|
|
|
** New class gdb.Thread. This is a subclass of threading.Thread
|
|
|
|
|
that calls gdb.block_signals in its "start" method.
|
|
|
|
|
|
2023-04-28 23:11:23 +08:00
|
|
|
** gdb.parse_and_eval now has a new "global_context" parameter.
|
|
|
|
|
This can be used to request that the parse only examine global
|
|
|
|
|
symbols.
|
|
|
|
|
|
2023-05-02 03:53:59 +08:00
|
|
|
** gdb.Inferior now has a new "arguments" attribute. This holds the
|
|
|
|
|
command-line arguments to the inferior, if known.
|
|
|
|
|
|
|
|
|
|
** gdb.Inferior now has a new "main_name" attribute. This holds the
|
|
|
|
|
name of the inferior's "main", if known.
|
|
|
|
|
|
|
|
|
|
** gdb.Inferior now has new methods "clear_env", "set_env", and
|
|
|
|
|
"unset_env". These can be used to modify the inferior's
|
|
|
|
|
environment before it is started.
|
|
|
|
|
|
2023-05-13 04:10:56 +08:00
|
|
|
** gdb.Value now has the 'assign' method.
|
|
|
|
|
|
2023-07-24 21:29:46 +08:00
|
|
|
** gdb.Value now has the 'to_array' method. This converts an
|
|
|
|
|
array-like Value to an array.
|
|
|
|
|
|
2023-05-23 01:40:10 +08:00
|
|
|
** gdb.Progspace now has the new method "objfile_for_address". This
|
|
|
|
|
returns the gdb.Objfile, if any, that covers a given address.
|
|
|
|
|
|
gdb: add inferior-specific breakpoints
This commit extends the breakpoint mechanism to allow for inferior
specific breakpoints (but not watchpoints in this commit).
As GDB gains better support for multiple connections, and so for
running multiple (possibly unrelated) inferiors, then it is not hard
to imagine that a user might wish to create breakpoints that apply to
any thread in a single inferior. To achieve this currently, the user
would need to create a condition possibly making use of the $_inferior
convenience variable, which, though functional, isn't the most user
friendly.
This commit adds a new 'inferior' keyword that allows for the creation
of inferior specific breakpoints.
Inferior specific breakpoints are automatically deleted when the
associated inferior is removed from GDB, this is similar to how
thread-specific breakpoints are deleted when the associated thread is
deleted.
Watchpoints are already per-program-space, which in most cases mean
watchpoints are already inferior specific. There is a small window
where inferior-specific watchpoints might make sense, which is after a
vfork, when two processes are sharing the same address space.
However, I'm leaving that as an exercise for another day. For now,
attempting to use the inferior keyword with a watchpoint will give an
error, like this:
(gdb) watch a8 inferior 1
Cannot use 'inferior' keyword with watchpoints
A final note on the implementation: currently, inferior specific
breakpoints, like thread-specific breakpoints, are inserted into every
inferior, GDB then checks once the inferior stops if we are in the
correct thread or inferior, and resumes automatically if we stopped in
the wrong thread/inferior.
An obvious optimisation here is to only insert breakpoint locations
into the specific program space (which mostly means inferior) that
contains either the inferior or thread we are interested in. This
would reduce the number times GDB has to stop and then resume again in
a multi-inferior setup.
I have a series on the mailing list[1] that implements this
optimisation for thread-specific breakpoints. Once this series has
landed I'll update that series to also handle inferior specific
breakpoints in the same way. For now, inferior specific breakpoints
are just slightly less optimal, but this is no different to
thread-specific breakpoints in a multi-inferior debug session, so I
don't see this as a huge problem.
[1] https://inbox.sourceware.org/gdb-patches/cover.1685479504.git.aburgess@redhat.com/
2022-11-08 20:32:51 +08:00
|
|
|
** gdb.Breakpoint now has an "inferior" attribute. If the
|
|
|
|
|
Breakpoint object is inferior specific then this attribute holds
|
|
|
|
|
the inferior-id (an integer). If the Breakpoint object is not
|
|
|
|
|
inferior specific, then this field contains None. This field can
|
|
|
|
|
be written too.
|
|
|
|
|
|
2023-07-24 21:29:46 +08:00
|
|
|
** gdb.Type now has the "is_array_like" and "is_string_like"
|
|
|
|
|
methods. These reflect GDB's internal idea of whether a type
|
|
|
|
|
might be array- or string-like, even if they do not have the
|
|
|
|
|
corresponding type code.
|
|
|
|
|
|
2023-09-08 03:40:29 +08:00
|
|
|
** gdb.ValuePrinter is a new class that can be used as the base
|
|
|
|
|
class for the result of applying a pretty-printer. As a base
|
|
|
|
|
class, it signals to gdb that the printer may implement new
|
|
|
|
|
pretty-printer methods.
|
|
|
|
|
|
2023-09-07 18:18:16 +08:00
|
|
|
** New attribute Progspace.symbol_file. This attribute holds the
|
|
|
|
|
gdb.Objfile that corresponds to Progspace.filename (when
|
|
|
|
|
Progspace.filename is not None), otherwise, this attribute is
|
|
|
|
|
itself None.
|
|
|
|
|
|
2023-09-07 22:47:07 +08:00
|
|
|
** New attribute Progspace.executable_filename. This attribute
|
|
|
|
|
holds a string containing a file name set by the "exec-file" or
|
|
|
|
|
"file" commands, or None if no executable file is set. This
|
|
|
|
|
isn't the exact string passed by the user to these commands; the
|
|
|
|
|
file name will have been partially resolved to an absolute file
|
|
|
|
|
name.
|
|
|
|
|
|
gdb/python: make the executable_changed event available from Python
This commit makes the executable_changed observable available through
the Python API as an event. There's nothing particularly interesting
going on here, it just follows the same pattern as many of the other
Python events we support.
The new event registry is called events.executable_changed, and this
emits an ExecutableChangedEvent object which has two attributes, a
gdb.Progspace called 'progspace', this is the program space in which
the executable changed, and a Boolean called 'reload', which is True
if the same executable changed on disk and has been reloaded, or is
False when a new executable has been loaded.
One interesting thing did come up during testing though, you'll notice
the test contains a setup_kfail call. During testing I observed that
the executable_changed event would trigger twice when GDB restarted an
inferior. However, the ExecutableChangedEvent object is identical for
both calls, so the wrong information is never sent out, we just see
one too many events.
I tracked this down to how the reload_symbols function (symfile.c)
takes care to also reload the executable, however, I've split fixing
this into a separate commit, so see the next commit for details.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-By: Tom Tromey <tom@tromey.com>
2023-08-28 23:22:36 +08:00
|
|
|
** A new executable_changed event registry is available. This event
|
|
|
|
|
emits ExecutableChangedEvent objects, which have 'progspace' (a
|
|
|
|
|
gdb.Progspace) and 'reload' (a Boolean) attributes. This event
|
|
|
|
|
is emitted when gdb.Progspace.executable_filename changes.
|
|
|
|
|
|
gdb: add Python events for program space addition and removal
Initially I just wanted a Python event for when GDB removes a program
space, I'm writing a Python extension that caches information for each
program space, and need to know when I should discard entries for a
particular program space.
But, it seemed easy enough to also add an event for when GDB adds a
new program space, so I went ahead and added both new events.
Of course, we don't currently have an observable for program space
addition or removal, so I first needed to add these. After that it's
pretty simple to add two new Python events and have these trigger.
The two new event registries are:
events.new_progspace
events.free_progspace
These emit NewProgspaceEvent and FreeProgspaceEvent objects
respectively, each of these new event types has a 'progspace'
attribute that contains the relevant gdb.Progspace object.
There's a couple of things to be mindful of.
First, it is not possible to catch the NewProgspaceEvent for the very
first program space, the one that is created when GDB first starts, as
this program space is created before any Python scripts are sourced.
In order to allow this event to be caught we would need to defer
creating the first program space, and as a consequence the first
inferior, until some later time. But, existing scripts could easily
depend on there being an initial inferior, so I really don't think we
should change that -- and so, we end up with the consequence that we
can't catch the event for the first program space.
The second, I think minor, issue, is that GDB doesn't clean up its
program spaces upon exit -- or at least, they are not cleaned up
before Python is shut down. As a result, any program spaces in use at
the time GDB exits don't generate a FreeProgspaceEvent. I'm not
particularly worried about this for my use case, I'm using the event
to ensure that a cache doesn't hold stale entries within a single GDB
session. It's also easy enough to add a Python at-exit callback which
can do any final cleanup if needed.
Finally, when testing, I did hit a slightly weird issue with some of
the remote boards (e.g. remote-stdio-gdbserver). As a consequence of
this issue I see some output like this in the gdb.log:
(gdb) PASS: gdb.python/py-progspace-events.exp: inferior 1
step
FreeProgspaceEvent: <gdb.Progspace object at 0x7fb7e1d19c10>
warning: cannot close "target:/lib64/libm.so.6": Cannot execute this command while the target is running.
Use the "interrupt" command to stop the target
and then try again.
warning: cannot close "target:/lib64/libc.so.6": Cannot execute this command while the target is running.
Use the "interrupt" command to stop the target
and then try again.
warning: cannot close "target:/lib64/ld-linux-x86-64.so.2": Cannot execute this command while the target is running.
Use the "interrupt" command to stop the target
and then try again.
do_parent_stuff () at py-progspace-events.c:41
41 ++global_var;
(gdb) PASS: gdb.python/py-progspace-events.exp: step
The 'FreeProgspaceEvent ...' line is expected, that's my test Python
extension logging the event. What isn't expected are all the blocks
like:
warning: cannot close "target:/lib64/libm.so.6": Cannot execute this command while the target is running.
Use the "interrupt" command to stop the target
and then try again.
It turns out that this has nothing to do with my changes, this is just
a consequence of reading files over the remote protocol. The test
forks a child process which GDB stays attached too. When the child
exits, GDB cleans up by calling prune_inferiors, which in turn can
result in GDB trying to close some files that are open because of the
inferior being deleted.
If the prune_inferiors call occurs when the remote target is
running (and in non-async mode) then GDB will try to send a fileio
packet while the remote target is waiting for a stop reply, and the
remote target will throw an error, see remote_target::putpkt_binary in
remote.c for details.
I'm going to look at fixing this, but, as I said, this is nothing to
do with this change, I just mention it because I ended up needing to
account for these warning messages in one of my tests, and it all
looks a bit weird.
Approved-By: Tom Tromey <tom@tromey.com>
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
2023-09-19 18:45:36 +08:00
|
|
|
** New event registries gdb.events.new_progspace and
|
|
|
|
|
gdb.events.free_progspace, these emit NewProgspaceEvent and
|
|
|
|
|
FreeProgspaceEvent event types respectively. Both of these event
|
|
|
|
|
types have a single 'progspace' attribute, which is the
|
|
|
|
|
gdb.Progspace that is either being added to GDB, or removed from
|
|
|
|
|
GDB.
|
|
|
|
|
|
2023-10-05 01:22:05 +08:00
|
|
|
** gdb.LazyString now implements the __str__ method.
|
|
|
|
|
|
2023-10-24 22:05:06 +08:00
|
|
|
** New method gdb.Frame.static_link that returns the outer frame
|
|
|
|
|
of a nested function frame.
|
|
|
|
|
|
2022-12-18 12:38:25 +08:00
|
|
|
*** Changes in GDB 13
|
2022-03-20 13:17:42 +08:00
|
|
|
|
2022-09-22 00:46:51 +08:00
|
|
|
* MI version 1 is deprecated, and will be removed in GDB 14.
|
|
|
|
|
|
2022-03-31 18:42:35 +08:00
|
|
|
* GDB now supports dumping memory tag data for AArch64 MTE. It also supports
|
|
|
|
|
reading memory tag data for AArch64 MTE from core files generated by
|
|
|
|
|
the gcore command or the Linux kernel.
|
|
|
|
|
|
|
|
|
|
When a process uses memory-mapped pages protected by memory tags (for
|
|
|
|
|
example, AArch64 MTE), this additional information will be recorded in
|
|
|
|
|
the core file in the event of a crash or if GDB generates a core file
|
|
|
|
|
from the current process state. GDB will show this additional information
|
|
|
|
|
automatically, or through one of the memory-tag subcommands.
|
|
|
|
|
|
Don't resume new threads if scheduler-locking is in effect
If scheduler-locking is in effect, e.g., with "set scheduler-locking
on", and you step over a function that spawns a new thread, the new
thread is allowed to run free, at least until some event is hit, at
which point, whether the new thread is re-resumed depends on a number
of seemingly random factors. E.g., if the target is all-stop, and the
parent thread hits a breakpoint, and GDB decides the breakpoint isn't
interesting to report to the user, then the parent thread is resumed,
but the new thread is left stopped.
I think that letting the new threads run with scheduler-locking
enabled is a defect. This commit fixes that, making use of the new
clone events on Linux, and of target_thread_events() on targets where
new threads have no connection to the thread that spawned them.
Testcase and documentation changes included.
Approved-By: Eli Zaretskii <eliz@gnu.org>
Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Change-Id: Ie12140138b37534b7fc1d904da34f0f174aa11ce
2021-12-01 03:52:11 +08:00
|
|
|
* Scheduler-locking and new threads
|
|
|
|
|
|
|
|
|
|
When scheduler-locking is in effect, only the current thread may run
|
|
|
|
|
when the inferior is resumed. However, previously, new threads
|
|
|
|
|
created by the resumed thread would still be able to run free. Now,
|
|
|
|
|
they are held stopped.
|
|
|
|
|
|
2022-05-25 02:30:10 +08:00
|
|
|
* "info breakpoints" now displays enabled breakpoint locations of
|
|
|
|
|
disabled breakpoints as in the "y-" state. For example:
|
|
|
|
|
|
|
|
|
|
(gdb) info breakpoints
|
|
|
|
|
Num Type Disp Enb Address What
|
|
|
|
|
1 breakpoint keep n <MULTIPLE>
|
|
|
|
|
1.1 y- 0x00000000000011b6 in ...
|
|
|
|
|
1.2 y- 0x00000000000011c2 in ...
|
|
|
|
|
1.3 n 0x00000000000011ce in ...
|
|
|
|
|
|
2022-05-04 07:05:11 +08:00
|
|
|
* Support for Thread Local Storage (TLS) variables on FreeBSD arm and
|
|
|
|
|
aarch64 architectures.
|
|
|
|
|
|
2022-03-23 03:05:43 +08:00
|
|
|
* GDB now supports hardware watchpoints on FreeBSD/Aarch64.
|
|
|
|
|
|
2021-12-24 09:20:46 +08:00
|
|
|
* Remove support for building against Python 2, it is now only possible to
|
|
|
|
|
build GDB against Python 3.
|
|
|
|
|
|
2022-03-05 02:29:27 +08:00
|
|
|
* DBX mode has been removed.
|
|
|
|
|
|
gdb: Add support for DW_LNS_set_prologue_end in line-table
Add support for DW_LNS_set_prologue_end when building line-tables. This
attribute can be set by the compiler to indicate that an instruction is
an adequate place to set a breakpoint just after the prologue of a
function.
The compiler might set multiple prologue_end, but considering how
current skip_prologue_using_sal works, this commit modifies it to accept
the first instruction with this marker (if any) to be the place where a
breakpoint should be placed to be at the end of the prologue.
The need for this support came from a problematic usecase generated by
hipcc (i.e. clang). The problem is as follows: There's a function
(lets call it foo) which covers PC from 0xa800 to 0xa950. The body of
foo begins with a call to an inlined function, covering from 0xa800 to
0xa94c. The issue is that when placing a breakpoint at 'foo', GDB
inserts the breakpoint at 0xa818. The 0x18 offset is what GDB thinks is
foo's first address past the prologue.
Later, when hitting the breakpoint, GDB reports the stop within the
inlined function because the PC falls in its range while the user
expects to stop in FOO.
Looking at the line-table for this location, we have:
INDEX LINE ADDRESS IS-STMT
[...]
14 293 0x000000000000a66c Y
15 END 0x000000000000a6e0 Y
16 287 0x000000000000a800 Y
17 END 0x000000000000a818 Y
18 287 0x000000000000a824 Y
[...]
For comparison, let's look at llvm-dwarfdump's output for this CU:
Address Line Column File ISA Discriminator Flags
------------------ ------ ------ ------ --- ------------- -------------
[...]
0x000000000000a66c 293 12 2 0 0 is_stmt
0x000000000000a6e0 96 43 82 0 0 is_stmt
0x000000000000a6f8 102 18 82 0 0 is_stmt
0x000000000000a70c 102 24 82 0 0
0x000000000000a710 102 18 82 0 0
0x000000000000a72c 101 16 82 0 0 is_stmt
0x000000000000a73c 2915 50 83 0 0 is_stmt
0x000000000000a74c 110 1 1 0 0 is_stmt
0x000000000000a750 110 1 1 0 0 is_stmt end_sequence
0x000000000000a800 107 0 1 0 0 is_stmt
0x000000000000a800 287 12 2 0 0 is_stmt prologue_end
0x000000000000a818 114 59 81 0 0 is_stmt
0x000000000000a824 287 12 2 0 0 is_stmt
0x000000000000a828 100 58 82 0 0 is_stmt
[...]
The main difference we are interested in here is that llvm-dwarfdump's
output tells us that 0xa800 is an adequate place to place a breakpoint
past a function prologue. Since we know that foo covers from 0xa800 to
0xa94c, 0xa800 is the address at which the breakpoint should be placed
if the user wants to break in foo.
This commit proposes to add support for the prologue_end flag in the
line-program processing.
The processing of this prologue_end flag is made in skip_prologue_sal,
before it calls gdbarch_skip_prologue_noexcept. The intent is that if
the compiler gave information on where the prologue ends, we should use
this information and not try to rely on architecture dependent logic to
guess it.
The testsuite have been executed using this patch on GNU/Linux x86_64.
Testcases have been compiled with both gcc/g++ (verison 9.4.0) and
clang/clang++ (version 10.0.0) since at the time of writing GCC does not
set the prologue_end marker. Tests done with GCC 11.2.0 (not over the
entire testsuite) show that it does not emit this flag either.
No regression have been observed with GCC or Clang. Note that when
using Clang, this patch fixes a failure in
gdb.opt/inline-small-func.exp.
Change-Id: I720449a8a9b2e1fb45b54c6095d3b1e9da9152f8
2022-02-26 07:41:47 +08:00
|
|
|
* GDB now honours the DWARF prologue_end line-table entry flag the compiler can
|
|
|
|
|
emit to indicate where a breakpoint should be placed to break in a function
|
|
|
|
|
past its prologue.
|
|
|
|
|
|
2022-07-01 02:57:34 +08:00
|
|
|
* Completion now also offers "NUMBER" for "set" commands that accept
|
|
|
|
|
a numeric argument and the "unlimited" keyword. For example:
|
|
|
|
|
|
|
|
|
|
(gdb) set width <TAB>
|
|
|
|
|
NUMBER unlimited
|
|
|
|
|
|
|
|
|
|
and consequently:
|
|
|
|
|
|
|
|
|
|
(gdb) complete set width
|
|
|
|
|
set width NUMBER
|
|
|
|
|
set width unlimited
|
|
|
|
|
|
gdb: add support for disassembler styling using libopcodes
This commit extends GDB to make use of libopcodes styling support
where available, currently this is just i386 based architectures, and
RISC-V.
For architectures that don't support styling using libopcodes GDB will
fall back to using the Python Pygments package, when the package is
available.
The new libopcodes based styling has the disassembler identify parts
of the disassembled instruction, e.g. registers, immediates,
mnemonics, etc, and can style these components differently.
Additionally, as the styling is now done in GDB we can add settings to
allow the user to configure which colours are used right from the GDB
CLI.
There's some new maintenance commands:
maintenance set libopcodes-styling enabled on|off
maintenance show libopcodes-styling
These can be used to manually disable use of libopcodes styling. This
is a maintenance command as it's not anticipated that a user should
need to do this. But, this could be useful for testing, or, in some
rare cases, a user might want to override the Python hook used for
disassembler styling, and then disable libopcode styling so that GDB
falls back to using Python. Right now I would consider this second
use case a rare situation, which is why I think a maintenance command
is appropriate.
When libopcodes is being used for styling then the user can make use
of the following new styles:
set/show style disassembler comment
set/show style disassembler immediate
set/show style disassembler mnemonic
set/show style disassembler register
The disassembler also makes use of the 'address' and 'function'
styles to style some parts of the disassembler output. I have also
added the following aliases though:
set/show style disassembler address
set/show style disassembler symbol
these are aliases for:
set/show style address
set/show style function
respectively, and exist to make it easier for users to discover
disassembler related style settings. The 'address' style is used to
style numeric addresses in the disassembler output, while the 'symbol'
or 'function' style is used to style the names of symbols in
disassembler output.
As not every architecture supports libopcodes styling, the maintenance
setting 'libopcodes-styling enabled' has an "auto-off" type behaviour.
Consider this GDB session:
(gdb) show architecture
The target architecture is set to "auto" (currently "i386:x86-64").
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "on".
the setting defaults to "on" for architectures that support libopcodes
based styling.
(gdb) set architecture sparc
The target architecture is set to "sparc".
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "off" (not supported on architecture "sparc")
the setting will show as "off" if the user switches to an architecture
that doesn't support libopcodes styling. The underlying setting is
still "on" at this point though, if the user switches back to
i386:x86-64 then the setting would go back to being "on".
(gdb) maintenance set libopcodes-styling enabled off
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "off".
now the setting is "off" for everyone, even if the user switches back
to i386:x86-64 the setting will still show as "off".
(gdb) maintenance set libopcodes-styling enabled on
Use of libopcodes styling not supported on architecture "sparc".
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "off".
attempting to switch the setting "on" for an unsupported architecture
will give an error, and the setting will remain "off".
(gdb) set architecture auto
The target architecture is set to "auto" (currently "i386:x86-64").
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "off".
(gdb) maintenance set libopcodes-styling enabled on
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "on".
the user will need to switch back to a supported architecture before
they can one again turn this setting "on".
2022-02-14 22:40:52 +08:00
|
|
|
* Disassembler styling using libopcodes. GDB now supports
|
|
|
|
|
disassembler styling using libopcodes. This is only available for
|
|
|
|
|
some targets (currently x86 and RISC-V). For unsupported targets
|
|
|
|
|
Python Pygments is still used. For supported targets, libopcodes
|
|
|
|
|
styling is used by default.
|
|
|
|
|
|
2022-07-26 23:10:58 +08:00
|
|
|
* The Windows native target now supports target async.
|
|
|
|
|
|
binutils, gdb: support zstd compressed debug sections
PR29397 PR29563: Add new configure option --with-zstd which defaults to
auto. If pkgconfig/libzstd.pc is found, define HAVE_ZSTD and support
zstd compressed debug sections for most tools.
* bfd: for addr2line, objdump --dwarf, gdb, etc
* gas: support --compress-debug-sections=zstd
* ld: support ELFCOMPRESS_ZSTD input and --compress-debug-sections=zstd
* objcopy: support ELFCOMPRESS_ZSTD input for
--decompress-debug-sections and --compress-debug-sections=zstd
* gdb: support ELFCOMPRESS_ZSTD input. The bfd change references zstd
symbols, so gdb has to link against -lzstd in this patch.
If zstd is not supported, ELFCOMPRESS_ZSTD input triggers an error. We
can avoid HAVE_ZSTD if binutils-gdb imports zstd/ like zlib/, but this
is too heavyweight, so don't do it for now.
```
% ld/ld-new a.o
ld/ld-new: a.o: section .debug_abbrev is compressed with zstd, but BFD is not built with zstd support
...
% ld/ld-new a.o --compress-debug-sections=zstd
ld/ld-new: --compress-debug-sections=zstd: ld is not built with zstd support
% binutils/objcopy --compress-debug-sections=zstd a.o b.o
binutils/objcopy: --compress-debug-sections=zstd: binutils is not built with zstd support
% binutils/objcopy b.o --decompress-debug-sections
binutils/objcopy: zstd.o: section .debug_abbrev is compressed with zstd, but BFD is not built with zstd support
...
```
2022-09-27 10:50:13 +08:00
|
|
|
* gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.
|
|
|
|
|
|
gdb: disassembler opcode display formatting
This commit changes the format of 'disassemble /r' to match GNU
objdump. Specifically, GDB will now display the instruction bytes in
as 'objdump --wide --disassemble' does.
Here is an example for RISC-V before this patch:
(gdb) disassemble /r 0x0001018e,0x0001019e
Dump of assembler code from 0x1018e to 0x1019e:
0x0001018e <call_me+66>: 03 26 84 fe lw a2,-24(s0)
0x00010192 <call_me+70>: 83 25 c4 fe lw a1,-20(s0)
0x00010196 <call_me+74>: 61 65 lui a0,0x18
0x00010198 <call_me+76>: 13 05 85 6a addi a0,a0,1704
0x0001019c <call_me+80>: f1 22 jal 0x10368 <printf>
End of assembler dump.
And here's an example after this patch:
(gdb) disassemble /r 0x0001018e,0x0001019e
Dump of assembler code from 0x1018e to 0x1019e:
0x0001018e <call_me+66>: fe842603 lw a2,-24(s0)
0x00010192 <call_me+70>: fec42583 lw a1,-20(s0)
0x00010196 <call_me+74>: 6561 lui a0,0x18
0x00010198 <call_me+76>: 6a850513 addi a0,a0,1704
0x0001019c <call_me+80>: 22f1 jal 0x10368 <printf>
End of assembler dump.
There are two differences here. First, the instruction bytes after
the patch are grouped based on the size of the instruction, and are
byte-swapped to little-endian order.
Second, after the patch, GDB now uses the bytes-per-line hint from
libopcodes to add whitespace padding after the opcode bytes, this
means that in most cases the instructions are nicely aligned.
It is still possible for a very long instruction to intrude into the
disassembled text space. The next example is x86-64, before the
patch:
(gdb) disassemble /r main
Dump of assembler code for function main:
0x0000000000401106 <+0>: 55 push %rbp
0x0000000000401107 <+1>: 48 89 e5 mov %rsp,%rbp
0x000000000040110a <+4>: c7 87 d8 00 00 00 01 00 00 00 movl $0x1,0xd8(%rdi)
0x0000000000401114 <+14>: b8 00 00 00 00 mov $0x0,%eax
0x0000000000401119 <+19>: 5d pop %rbp
0x000000000040111a <+20>: c3 ret
End of assembler dump.
And after the patch:
(gdb) disassemble /r main
Dump of assembler code for function main:
0x0000000000401106 <+0>: 55 push %rbp
0x0000000000401107 <+1>: 48 89 e5 mov %rsp,%rbp
0x000000000040110a <+4>: c7 87 d8 00 00 00 01 00 00 00 movl $0x1,0xd8(%rdi)
0x0000000000401114 <+14>: b8 00 00 00 00 mov $0x0,%eax
0x0000000000401119 <+19>: 5d pop %rbp
0x000000000040111a <+20>: c3 ret
End of assembler dump.
Most instructions are aligned, except for the very long instruction.
Notice too that for x86-64 libopcodes doesn't request that GDB group
the instruction bytes. This matches the behaviour of objdump.
In case the user really wants the old behaviour, I have added a new
modifier 'disassemble /b', this displays the instruction byte at a
time. For x86-64, which never groups instruction bytes, /b and /r are
equivalent, but for RISC-V, using /b gets the old layout back (except
that the whitespace for alignment is still present). Consider our
original RISC-V example, this time using /b:
(gdb) disassemble /b 0x0001018e,0x0001019e
Dump of assembler code from 0x1018e to 0x1019e:
0x0001018e <call_me+66>: 03 26 84 fe lw a2,-24(s0)
0x00010192 <call_me+70>: 83 25 c4 fe lw a1,-20(s0)
0x00010196 <call_me+74>: 61 65 lui a0,0x18
0x00010198 <call_me+76>: 13 05 85 6a addi a0,a0,1704
0x0001019c <call_me+80>: f1 22 jal 0x10368 <printf>
End of assembler dump.
Obviously, this patch is a potentially significant change to the
behaviour or /r. I could have added /b with the new behaviour and
left /r alone. However, personally, I feel the new behaviour is
significantly better than the old, hence, I made /r be what I consider
the "better" behaviour.
The reason I prefer the new behaviour is that, when I use /r, I almost
always want to manually decode the instruction for some reason, and
having the bytes displayed in "instruction order" rather than memory
order, just makes this easier.
The 'record instruction-history' command also takes a /r modifier, and
has been modified in the same way as disassemble; /r gets the new
behaviour, and /b has been added to retain the old behaviour.
Finally, the MI command -data-disassemble, is unchanged in behaviour,
this command now requests the raw bytes of the instruction, which is
equivalent to the /b modifier. This means that the MI output will
remain backward compatible.
2022-06-22 03:23:35 +08:00
|
|
|
* The format of 'disassemble /r' and 'record instruction-history /r'
|
|
|
|
|
has changed. The instruction bytes could now be grouped together,
|
|
|
|
|
and displayed in the endianness of the instruction. This is the
|
|
|
|
|
same layout as used by GNU objdump when disassembling.
|
|
|
|
|
|
|
|
|
|
There is now 'disassemble /b' and 'record instruction-history /b'
|
|
|
|
|
which will always display the instructions bytes one at a time in
|
|
|
|
|
memory order, that is, the byte at the lowest address first.
|
|
|
|
|
|
|
|
|
|
For both /r and /b GDB is now better at using whitespace in order to
|
|
|
|
|
align the disassembled instruction text.
|
|
|
|
|
|
2022-11-02 00:45:30 +08:00
|
|
|
* The TUI no longer styles the source and assembly code highlighted by
|
|
|
|
|
the current position indicator by default. You can however
|
|
|
|
|
re-enable styling using the new "set style tui-current-position"
|
|
|
|
|
command.
|
|
|
|
|
|
2022-11-02 21:48:42 +08:00
|
|
|
* New convenience variable $_inferior_thread_count contains the number
|
|
|
|
|
of live threads in the current inferior.
|
|
|
|
|
|
Show locno for 'multi location' breakpoint hit msg+conv var $_hit_bbnum $_hit_locno PR breakpoints/12464
This implements the request given in PR breakpoints/12464.
Before this patch, when a breakpoint that has multiple locations is reached,
GDB printed:
Thread 1 "zeoes" hit Breakpoint 1, some_func () at somefunc1.c:5
This patch changes the message so that bkpt_print_id prints the precise
encountered breakpoint:
Thread 1 "zeoes" hit Breakpoint 1.2, some_func () at somefunc1.c:5
In mi mode, bkpt_print_id also (optionally) prints a new table field "locno":
locno is printed when the breakpoint hit has more than one location.
Note that according to the GDB user manual node 'GDB/MI Development and Front
Ends', it is ok to add new fields without changing the MI version.
Also, when a breakpoint is reached, the convenience variables
$_hit_bpnum and $_hit_locno are set to the encountered breakpoint number
and location number.
$_hit_bpnum and $_hit_locno can a.o. be used in the command list of a
breakpoint, to disable the specific encountered breakpoint, e.g.
disable $_hit_bpnum.$_hit_locno
In case the breakpoint has only one location, $_hit_locno is set to
the value 1, so as to allow a command such as:
disable $_hit_bpnum.$_hit_locno
to disable the breakpoint even when the breakpoint has only one location.
This also fixes a strange behaviour: when a breakpoint X has only
one location,
enable|disable X.1
is accepted but transforms the breakpoint in a multiple locations
breakpoint having only one location.
The changes in RFA v4 handle the comments of Tom Tromey:
- Changed convenience var names from $bkptno/$locno to
$_hit_bpnum/$_hit_locno.
- updated the tests and user manual accordingly.
User manual also explictly describes that $_hit_locno is set to 1
for a breakpoint with a single location.
- The variable values are now set in bpstat_do_actions_1 so that
they are set for silent breakpoints, and when several breakpoints
are hit at the same time, that the variables are set to the printed
breakpoint.
The changes in RFA v3 handle the additional comments of Eli:
GDB/NEW:
- Use max 80-column
- Use 'code location' instead of 'location'.
- Fix typo $bkpno
- Ensure that disable $bkptno and disable $bkptno.$locno have
each their explanation inthe example
- Reworded the 'breakpoint-hit' paragraph.
gdb.texinfo:
- Use 'code location' instead of 'location'.
- Add a note to clarify the distinction between $bkptno and $bpnum.
- Use @kbd instead of examples with only one command.
Compared to RFA v1, the changes in v2 handle the comments given by
Keith Seitz and Eli Zaretskii:
- Use %s for the result of paddress
- Use bkptno_numopt_re instead of 2 different -re cases
- use C@t{++}
- Add index entries for $bkptno and $locno
- Added an example for "locno" in the mi interface
- Added examples in the Break command manual.
2020-05-24 04:27:28 +08:00
|
|
|
* When a breakpoint with multiple code locations is hit, GDB now prints
|
|
|
|
|
the code location using the syntax <breakpoint_number>.<location_number>
|
|
|
|
|
such as in:
|
|
|
|
|
Thread 1 "zeoes" hit Breakpoint 2.3, some_func () at zeoes.c:8
|
|
|
|
|
|
|
|
|
|
* When a breakpoint is hit, GDB now sets the convenience variables $_hit_bpnum
|
|
|
|
|
and $_hit_locno to the hit breakpoint number and code location number.
|
|
|
|
|
This allows to disable the last hit breakpoint using
|
|
|
|
|
(gdb) disable $_hit_bpnum
|
|
|
|
|
or disable only the specific breakpoint code location using
|
|
|
|
|
(gdb) disable $_hit_bpnum.$_hit_locno
|
|
|
|
|
These commands can be used inside the command list of a breakpoint to
|
|
|
|
|
automatically disable the just encountered breakpoint (or the just
|
|
|
|
|
encountered specific breakpoint code location).
|
|
|
|
|
When a breakpoint has only one location, $_hit_locno is set to 1 so that
|
|
|
|
|
(gdb) disable $_hit_bpnum.$_hit_locno
|
|
|
|
|
and
|
|
|
|
|
(gdb) disable $_hit_bpnum
|
|
|
|
|
are both disabling the breakpoint.
|
|
|
|
|
|
2022-04-01 18:59:29 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
maintenance set ignore-prologue-end-flag on|off
|
|
|
|
|
maintenance show ignore-prologue-end-flag
|
|
|
|
|
This setting, which is off by default, controls whether GDB ignores the
|
|
|
|
|
PROLOGUE-END flag from the line-table when skipping prologue. This can be
|
|
|
|
|
used to force GDB to use prologue analyzers if the line-table is constructed
|
|
|
|
|
from erroneous debug information.
|
|
|
|
|
|
2022-06-12 13:24:02 +08:00
|
|
|
set print nibbles [on|off]
|
|
|
|
|
show print nibbles
|
|
|
|
|
This controls whether the 'print/t' command will display binary values
|
|
|
|
|
in groups of four bits, known as "nibbles". The default is 'off'.
|
|
|
|
|
|
gdb: add support for disassembler styling using libopcodes
This commit extends GDB to make use of libopcodes styling support
where available, currently this is just i386 based architectures, and
RISC-V.
For architectures that don't support styling using libopcodes GDB will
fall back to using the Python Pygments package, when the package is
available.
The new libopcodes based styling has the disassembler identify parts
of the disassembled instruction, e.g. registers, immediates,
mnemonics, etc, and can style these components differently.
Additionally, as the styling is now done in GDB we can add settings to
allow the user to configure which colours are used right from the GDB
CLI.
There's some new maintenance commands:
maintenance set libopcodes-styling enabled on|off
maintenance show libopcodes-styling
These can be used to manually disable use of libopcodes styling. This
is a maintenance command as it's not anticipated that a user should
need to do this. But, this could be useful for testing, or, in some
rare cases, a user might want to override the Python hook used for
disassembler styling, and then disable libopcode styling so that GDB
falls back to using Python. Right now I would consider this second
use case a rare situation, which is why I think a maintenance command
is appropriate.
When libopcodes is being used for styling then the user can make use
of the following new styles:
set/show style disassembler comment
set/show style disassembler immediate
set/show style disassembler mnemonic
set/show style disassembler register
The disassembler also makes use of the 'address' and 'function'
styles to style some parts of the disassembler output. I have also
added the following aliases though:
set/show style disassembler address
set/show style disassembler symbol
these are aliases for:
set/show style address
set/show style function
respectively, and exist to make it easier for users to discover
disassembler related style settings. The 'address' style is used to
style numeric addresses in the disassembler output, while the 'symbol'
or 'function' style is used to style the names of symbols in
disassembler output.
As not every architecture supports libopcodes styling, the maintenance
setting 'libopcodes-styling enabled' has an "auto-off" type behaviour.
Consider this GDB session:
(gdb) show architecture
The target architecture is set to "auto" (currently "i386:x86-64").
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "on".
the setting defaults to "on" for architectures that support libopcodes
based styling.
(gdb) set architecture sparc
The target architecture is set to "sparc".
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "off" (not supported on architecture "sparc")
the setting will show as "off" if the user switches to an architecture
that doesn't support libopcodes styling. The underlying setting is
still "on" at this point though, if the user switches back to
i386:x86-64 then the setting would go back to being "on".
(gdb) maintenance set libopcodes-styling enabled off
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "off".
now the setting is "off" for everyone, even if the user switches back
to i386:x86-64 the setting will still show as "off".
(gdb) maintenance set libopcodes-styling enabled on
Use of libopcodes styling not supported on architecture "sparc".
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "off".
attempting to switch the setting "on" for an unsupported architecture
will give an error, and the setting will remain "off".
(gdb) set architecture auto
The target architecture is set to "auto" (currently "i386:x86-64").
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "off".
(gdb) maintenance set libopcodes-styling enabled on
(gdb) maintenance show libopcodes-styling enabled
Use of libopcodes styling support is "on".
the user will need to switch back to a supported architecture before
they can one again turn this setting "on".
2022-02-14 22:40:52 +08:00
|
|
|
maintenance set libopcodes-styling on|off
|
|
|
|
|
maintenance show libopcodes-styling
|
|
|
|
|
These can be used to force off libopcodes based styling, the Python
|
|
|
|
|
Pygments styling will then be used instead.
|
|
|
|
|
|
|
|
|
|
set style disassembler comment
|
|
|
|
|
show style disassembler comment
|
|
|
|
|
set style disassembler immediate
|
|
|
|
|
show style disassembler immediate
|
|
|
|
|
set style disassembler mnemonic
|
|
|
|
|
show style disassembler mnemonic
|
|
|
|
|
set style disassembler register
|
|
|
|
|
show style disassembler register
|
|
|
|
|
set style disassembler address
|
|
|
|
|
show style disassembler address
|
|
|
|
|
set style disassembler symbol
|
|
|
|
|
show style disassembler symbol
|
|
|
|
|
For targets that support libopcodes based styling, these settings
|
|
|
|
|
control how various aspects of the disassembler output are styled.
|
|
|
|
|
The 'disassembler address' and 'disassembler symbol' styles are
|
|
|
|
|
aliases for the 'address' and 'function' styles respectively.
|
|
|
|
|
|
2022-08-16 23:48:01 +08:00
|
|
|
maintenance print frame-id [ LEVEL ]
|
|
|
|
|
Print GDB's internal frame-id for the frame at LEVEL. If LEVEL is
|
|
|
|
|
not given, then print the frame-id for the currently selected frame.
|
|
|
|
|
|
2022-05-10 22:16:46 +08:00
|
|
|
set debug infcall on|off
|
|
|
|
|
show debug infcall
|
|
|
|
|
Print additional debug messages about inferior function calls.
|
|
|
|
|
|
2022-11-29 00:43:13 +08:00
|
|
|
set debug solib on|off
|
|
|
|
|
show debug solib
|
|
|
|
|
Print additional debug messages about shared library handling.
|
|
|
|
|
|
2022-11-02 00:45:30 +08:00
|
|
|
set style tui-current-position [on|off]
|
|
|
|
|
Whether to style the source and assembly code highlighted by the
|
|
|
|
|
TUI's current position indicator. The default is off.
|
|
|
|
|
|
GDB: Add a character string limiting option
This commit splits the `set/show print elements' option into two. We
retain `set/show print elements' for controlling how many elements of an
array we print, but a new `set/show print characters' setting is added
which is used for controlling how many characters of a string are
printed.
The motivation behind this change is to allow users a finer level of
control over how data is printed, reflecting that, although strings can
be thought of as arrays of characters, users often want to treat these
two things differently.
For compatibility reasons by default the `set/show print characters'
option is set to `elements', which makes the limit for character strings
follow the setting of the `set/show print elements' option, as it used
to. Using `set print characters' with any other value makes the limit
independent from the `set/show print elements' setting, however it can
be restored to the default with the `set print characters elements'
command at any time.
A corresponding `-characters' option for the `print' command is added,
with the same semantics, i.e. one can use `elements' to make a given
`print' invocation follow the limit of elements, be it set with the
`-elements' option also given with the same invocation or taken from the
`set/show print elements' setting, for characters as well regardless of
the current setting of the `set/show print characters' option.
The GDB changes are all pretty straightforward, just changing references
to the old 'print_max' to use a new `get_print_max_chars' helper which
figures out which of the two of `print_max' and `print_max_chars' values
to use.
Likewise, the documentation is just updated to reference the new setting
where appropriate.
To make people's life easier the message shown by `show print elements'
now indicates if the setting also applies to character strings:
(gdb) set print characters elements
(gdb) show print elements
Limit on string chars or array elements to print is 200.
(gdb) set print characters unlimited
(gdb) show print elements
Limit on array elements to print is 200.
(gdb)
and the help text shows the dependency as well:
(gdb) help set print elements
Set limit on array elements to print.
"unlimited" causes there to be no limit.
This setting also applies to string chars when "print characters"
is set to "elements".
(gdb)
In the testsuite there are two minor updates, one to add `-characters'
to the list of completions now shown for the `print' command, and a bare
minimum pair of checks for the right handling of `set print characters'
and `show print characters', copied from the corresponding checks for
`set print elements' and `show print elements' respectively.
Co-Authored-By: Maciej W. Rozycki <macro@embecosm.com>
Approved-By: Simon Marchi <simon.marchi@efficios.com>
2023-01-20 05:15:56 +08:00
|
|
|
set print characters LIMIT
|
|
|
|
|
show print characters
|
|
|
|
|
This new setting is like 'set print elements', but controls how many
|
|
|
|
|
characters of a string are printed. This functionality used to be
|
|
|
|
|
covered by 'set print elements', but it can be controlled separately
|
|
|
|
|
now. LIMIT can be set to a numerical value to request that particular
|
|
|
|
|
character count, to 'unlimited' to print all characters of a string,
|
|
|
|
|
or to 'elements', which is also the default, to follow the setting of
|
|
|
|
|
'set print elements' as it used to be.
|
|
|
|
|
|
|
|
|
|
print -characters LIMIT
|
|
|
|
|
This new option to the 'print' command has the same effect as a temporary
|
|
|
|
|
use of 'set print characters'.
|
|
|
|
|
|
gdb: Add support for DW_LNS_set_prologue_end in line-table
Add support for DW_LNS_set_prologue_end when building line-tables. This
attribute can be set by the compiler to indicate that an instruction is
an adequate place to set a breakpoint just after the prologue of a
function.
The compiler might set multiple prologue_end, but considering how
current skip_prologue_using_sal works, this commit modifies it to accept
the first instruction with this marker (if any) to be the place where a
breakpoint should be placed to be at the end of the prologue.
The need for this support came from a problematic usecase generated by
hipcc (i.e. clang). The problem is as follows: There's a function
(lets call it foo) which covers PC from 0xa800 to 0xa950. The body of
foo begins with a call to an inlined function, covering from 0xa800 to
0xa94c. The issue is that when placing a breakpoint at 'foo', GDB
inserts the breakpoint at 0xa818. The 0x18 offset is what GDB thinks is
foo's first address past the prologue.
Later, when hitting the breakpoint, GDB reports the stop within the
inlined function because the PC falls in its range while the user
expects to stop in FOO.
Looking at the line-table for this location, we have:
INDEX LINE ADDRESS IS-STMT
[...]
14 293 0x000000000000a66c Y
15 END 0x000000000000a6e0 Y
16 287 0x000000000000a800 Y
17 END 0x000000000000a818 Y
18 287 0x000000000000a824 Y
[...]
For comparison, let's look at llvm-dwarfdump's output for this CU:
Address Line Column File ISA Discriminator Flags
------------------ ------ ------ ------ --- ------------- -------------
[...]
0x000000000000a66c 293 12 2 0 0 is_stmt
0x000000000000a6e0 96 43 82 0 0 is_stmt
0x000000000000a6f8 102 18 82 0 0 is_stmt
0x000000000000a70c 102 24 82 0 0
0x000000000000a710 102 18 82 0 0
0x000000000000a72c 101 16 82 0 0 is_stmt
0x000000000000a73c 2915 50 83 0 0 is_stmt
0x000000000000a74c 110 1 1 0 0 is_stmt
0x000000000000a750 110 1 1 0 0 is_stmt end_sequence
0x000000000000a800 107 0 1 0 0 is_stmt
0x000000000000a800 287 12 2 0 0 is_stmt prologue_end
0x000000000000a818 114 59 81 0 0 is_stmt
0x000000000000a824 287 12 2 0 0 is_stmt
0x000000000000a828 100 58 82 0 0 is_stmt
[...]
The main difference we are interested in here is that llvm-dwarfdump's
output tells us that 0xa800 is an adequate place to place a breakpoint
past a function prologue. Since we know that foo covers from 0xa800 to
0xa94c, 0xa800 is the address at which the breakpoint should be placed
if the user wants to break in foo.
This commit proposes to add support for the prologue_end flag in the
line-program processing.
The processing of this prologue_end flag is made in skip_prologue_sal,
before it calls gdbarch_skip_prologue_noexcept. The intent is that if
the compiler gave information on where the prologue ends, we should use
this information and not try to rely on architecture dependent logic to
guess it.
The testsuite have been executed using this patch on GNU/Linux x86_64.
Testcases have been compiled with both gcc/g++ (verison 9.4.0) and
clang/clang++ (version 10.0.0) since at the time of writing GCC does not
set the prologue_end marker. Tests done with GCC 11.2.0 (not over the
entire testsuite) show that it does not emit this flag either.
No regression have been observed with GCC or Clang. Note that when
using Clang, this patch fixes a failure in
gdb.opt/inline-small-func.exp.
Change-Id: I720449a8a9b2e1fb45b54c6095d3b1e9da9152f8
2022-02-26 07:41:47 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
Allow to document user-defined aliases.
Compared to the previous version, this version fixes the comments reported by
Tom Tromey and ensures that the 'help some-user-documented-alias'
shows the alias definition to ensure the user understands this is an
alias even if specifically documented.
When using 'help ALIASNAME', GDB shows the help of the aliased command.
This is a good default behaviour.
However, GDB alias command allows to define aliases with arguments
possibly changing or tuning significantly the behaviour of
the aliased command. In such a case, showing the help of the aliased
command might not be ideal.
This is particularly true when defining an alias as a set of
nested 'with' followed by a last command to launch, such as:
(gdb) alias pp10 = with print pretty -- with print elements 10 -- print
Asking 'help pp10' shows the help of the 'with' command, which is
not particularly useful:
(gdb) help pp10
with, pp10, w
alias pp10 = with print pretty -- with print elements 10 -- print
Temporarily set SETTING to VALUE, run COMMAND, and restore SETTING.
Usage: with SETTING [VALUE] [-- COMMAND]
....
Such an alias can now be documented by the user:
(gdb) document pp10
>Pretty printing an expressiong, printing 10 elements.
>Usage: pp10 [PRINT-COMMAND-OPTIONS] EXP
>See 'help print' for more information.
>end
(gdb) help pp10
alias pp10 = with print pretty -- with print elements 10 -- print
Pretty printing an expressiong, printing 10 elements.
Usage: pp10 [PRINT-COMMAND-OPTIONS] EXP
See 'help print' for more information.
(gdb)
When a user-defined alias is documented specifically, help and apropos
use the provided alias documentation instead of the documentation of
the aliased command.
Such a documented alias is also not shown anymore in the help of the
aliased command, and the alias is not listed anymore in the help
of the aliased command. In particular for cases such as pp10 example above,
indicating that pp10 is an alias of the 'with' command is confusing.
2022-04-18 17:21:09 +08:00
|
|
|
document user-defined
|
|
|
|
|
It is now possible to document user-defined aliases.
|
|
|
|
|
When a user-defined alias is documented, the help and apropos commands
|
|
|
|
|
use the provided documentation instead of the documentation of the
|
|
|
|
|
aliased command.
|
|
|
|
|
Documenting a user-defined alias is particularly useful when the alias
|
|
|
|
|
is a set of nested 'with' commands to avoid showing the help of
|
|
|
|
|
the with command for an alias that will in fact launch the
|
|
|
|
|
last command given in the nested commands.
|
|
|
|
|
|
gdb: Add support for DW_LNS_set_prologue_end in line-table
Add support for DW_LNS_set_prologue_end when building line-tables. This
attribute can be set by the compiler to indicate that an instruction is
an adequate place to set a breakpoint just after the prologue of a
function.
The compiler might set multiple prologue_end, but considering how
current skip_prologue_using_sal works, this commit modifies it to accept
the first instruction with this marker (if any) to be the place where a
breakpoint should be placed to be at the end of the prologue.
The need for this support came from a problematic usecase generated by
hipcc (i.e. clang). The problem is as follows: There's a function
(lets call it foo) which covers PC from 0xa800 to 0xa950. The body of
foo begins with a call to an inlined function, covering from 0xa800 to
0xa94c. The issue is that when placing a breakpoint at 'foo', GDB
inserts the breakpoint at 0xa818. The 0x18 offset is what GDB thinks is
foo's first address past the prologue.
Later, when hitting the breakpoint, GDB reports the stop within the
inlined function because the PC falls in its range while the user
expects to stop in FOO.
Looking at the line-table for this location, we have:
INDEX LINE ADDRESS IS-STMT
[...]
14 293 0x000000000000a66c Y
15 END 0x000000000000a6e0 Y
16 287 0x000000000000a800 Y
17 END 0x000000000000a818 Y
18 287 0x000000000000a824 Y
[...]
For comparison, let's look at llvm-dwarfdump's output for this CU:
Address Line Column File ISA Discriminator Flags
------------------ ------ ------ ------ --- ------------- -------------
[...]
0x000000000000a66c 293 12 2 0 0 is_stmt
0x000000000000a6e0 96 43 82 0 0 is_stmt
0x000000000000a6f8 102 18 82 0 0 is_stmt
0x000000000000a70c 102 24 82 0 0
0x000000000000a710 102 18 82 0 0
0x000000000000a72c 101 16 82 0 0 is_stmt
0x000000000000a73c 2915 50 83 0 0 is_stmt
0x000000000000a74c 110 1 1 0 0 is_stmt
0x000000000000a750 110 1 1 0 0 is_stmt end_sequence
0x000000000000a800 107 0 1 0 0 is_stmt
0x000000000000a800 287 12 2 0 0 is_stmt prologue_end
0x000000000000a818 114 59 81 0 0 is_stmt
0x000000000000a824 287 12 2 0 0 is_stmt
0x000000000000a828 100 58 82 0 0 is_stmt
[...]
The main difference we are interested in here is that llvm-dwarfdump's
output tells us that 0xa800 is an adequate place to place a breakpoint
past a function prologue. Since we know that foo covers from 0xa800 to
0xa94c, 0xa800 is the address at which the breakpoint should be placed
if the user wants to break in foo.
This commit proposes to add support for the prologue_end flag in the
line-program processing.
The processing of this prologue_end flag is made in skip_prologue_sal,
before it calls gdbarch_skip_prologue_noexcept. The intent is that if
the compiler gave information on where the prologue ends, we should use
this information and not try to rely on architecture dependent logic to
guess it.
The testsuite have been executed using this patch on GNU/Linux x86_64.
Testcases have been compiled with both gcc/g++ (verison 9.4.0) and
clang/clang++ (version 10.0.0) since at the time of writing GCC does not
set the prologue_end marker. Tests done with GCC 11.2.0 (not over the
entire testsuite) show that it does not emit this flag either.
No regression have been observed with GCC or Clang. Note that when
using Clang, this patch fixes a failure in
gdb.opt/inline-small-func.exp.
Change-Id: I720449a8a9b2e1fb45b54c6095d3b1e9da9152f8
2022-02-26 07:41:47 +08:00
|
|
|
maintenance info line-table
|
|
|
|
|
Add a PROLOGUE-END column to the output which indicates that an
|
|
|
|
|
entry corresponds to an address where a breakpoint should be placed
|
|
|
|
|
to be at the first instruction past a function's prologue.
|
|
|
|
|
|
2022-11-29 00:43:13 +08:00
|
|
|
* Removed commands
|
|
|
|
|
|
|
|
|
|
set debug aix-solib on|off
|
|
|
|
|
show debug aix-solib
|
|
|
|
|
set debug solib-frv on|off
|
|
|
|
|
show debug solib-frv
|
|
|
|
|
Removed in favor of "set/show debug solib".
|
|
|
|
|
|
2022-09-23 17:04:58 +08:00
|
|
|
maintenance info program-spaces
|
|
|
|
|
This command now includes a 'Core File' column which indicates the
|
|
|
|
|
name of the core file associated with each program space.
|
|
|
|
|
|
2022-06-17 16:51:05 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
|
|
|
|
|
|
gdbserver/csky add csky gdbserver support
Add new files:
gdb/arch/csky.c
gdb/arch/csky.h
gdb/features/cskyv2-linux.c
gdbserver/linux-csky-low.cc
1. In gdb/arch/csky.c file, add function "csky_create_target_description()"
for csky_target::low_arch_setup(). later, it can be used for csky native gdb.
2. In gdb/features/cskyv2-linux.c file, create target_tdesc for csky, include
gprs, pc, hi, lo, float, vector and float control registers.
3. In gdbserver/linux-csky-low.cc file, using PTRACE_GET/SET_RGESET to
get/set registers. The main data structures in asm/ptrace.h are:
struct pt_regs {
unsigned long tls;
unsigned long lr;
unsigned long pc;
unsigned long sr;
unsigned long usp;
/*
* a0, a1, a2, a3:
* r0, r1, r2, r3
*/
unsigned long orig_a0;
unsigned long a0;
unsigned long a1;
unsigned long a2;
unsigned long a3;
/*
* r4 ~ r13
*/
unsigned long regs[10];
/* r16 ~ r30 */
unsigned long exregs[15];
unsigned long rhi;
unsigned long rlo;
unsigned long dcsr;
};
struct user_fp {
unsigned long vr[96];
unsigned long fcr;
unsigned long fesr;
unsigned long fid;
unsigned long reserved;
};
2022-09-13 11:20:54 +08:00
|
|
|
GNU/Linux/CSKY (gdbserver) csky*-*linux*
|
|
|
|
|
|
gdb: initial support for ROCm platform (AMDGPU) debugging
This patch adds the foundation for GDB to be able to debug programs
offloaded to AMD GPUs using the AMD ROCm platform [1]. The latest
public release of the ROCm release at the time of writing is 5.4, so
this is what this patch targets.
The ROCm platform allows host programs to schedule bits of code for
execution on GPUs or similar accelerators. The programs running on GPUs
are typically referred to as `kernels` (not related to operating system
kernels).
Programs offloaded with the AMD ROCm platform can be written in the HIP
language [2], OpenCL and OpenMP, but we're going to focus on HIP here.
The HIP language consists of a C++ Runtime API and kernel language.
Here's an example of a very simple HIP program:
#include "hip/hip_runtime.h"
#include <cassert>
__global__ void
do_an_addition (int a, int b, int *out)
{
*out = a + b;
}
int
main ()
{
int *result_ptr, result;
/* Allocate memory for the device to write the result to. */
hipError_t error = hipMalloc (&result_ptr, sizeof (int));
assert (error == hipSuccess);
/* Run `do_an_addition` on one workgroup containing one work item. */
do_an_addition<<<dim3(1), dim3(1), 0, 0>>> (1, 2, result_ptr);
/* Copy result from device to host. Note that this acts as a synchronization
point, waiting for the kernel dispatch to complete. */
error = hipMemcpyDtoH (&result, result_ptr, sizeof (int));
assert (error == hipSuccess);
printf ("result is %d\n", result);
assert (result == 3);
return 0;
}
This program can be compiled with:
$ hipcc simple.cpp -g -O0 -o simple
... where `hipcc` is the HIP compiler, shipped with ROCm releases. This
generates an ELF binary for the host architecture, containing another
ELF binary with the device code. The ELF for the device can be
inspected with:
$ roc-obj-ls simple
1 host-x86_64-unknown-linux file://simple#offset=8192&size=0
1 hipv4-amdgcn-amd-amdhsa--gfx906 file://simple#offset=8192&size=34216
$ roc-obj-extract 'file://simple#offset=8192&size=34216'
$ file simple-offset8192-size34216.co
simple-offset8192-size34216.co: ELF 64-bit LSB shared object, *unknown arch 0xe0* version 1, dynamically linked, with debug_info, not stripped
^
amcgcn architecture that my `file` doesn't know about ----´
Running the program gives the very unimpressive result:
$ ./simple
result is 3
While running, this host program has copied the device program into the
GPU's memory and spawned an execution thread on it. The goal of this
GDB port is to let the user debug host threads and these GPU threads
simultaneously. Here's a sample session using a GDB with this patch
applied:
$ ./gdb -q -nx --data-directory=data-directory ./simple
Reading symbols from ./simple...
(gdb) break do_an_addition
Function "do_an_addition" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (do_an_addition) pending.
(gdb) r
Starting program: /home/smarchi/build/binutils-gdb-amdgpu/gdb/simple
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff5db7640 (LWP 1082911)]
[New Thread 0x7ffef53ff640 (LWP 1082913)]
[Thread 0x7ffef53ff640 (LWP 1082913) exited]
[New Thread 0x7ffdecb53640 (LWP 1083185)]
[New Thread 0x7ffff54bf640 (LWP 1083186)]
[Thread 0x7ffdecb53640 (LWP 1083185) exited]
[Switching to AMDGPU Wave 2:2:1:1 (0,0,0)/0]
Thread 6 hit Breakpoint 1, do_an_addition (a=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
b=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
out=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>) at simple.cpp:24
24 *out = a + b;
(gdb) info inferiors
Num Description Connection Executable
* 1 process 1082907 1 (native) /home/smarchi/build/binutils-gdb-amdgpu/gdb/simple
(gdb) info threads
Id Target Id Frame
1 Thread 0x7ffff5dc9240 (LWP 1082907) "simple" 0x00007ffff5e9410b in ?? () from /opt/rocm-5.4.0/lib/libhsa-runtime64.so.1
2 Thread 0x7ffff5db7640 (LWP 1082911) "simple" __GI___ioctl (fd=3, request=3222817548) at ../sysdeps/unix/sysv/linux/ioctl.c:36
5 Thread 0x7ffff54bf640 (LWP 1083186) "simple" __GI___ioctl (fd=3, request=3222817548) at ../sysdeps/unix/sysv/linux/ioctl.c:36
* 6 AMDGPU Wave 2:2:1:1 (0,0,0)/0 do_an_addition (
a=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
b=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
out=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>) at simple.cpp:24
(gdb) bt
Python Exception <class 'gdb.error'>: Unhandled dwarf expression opcode 0xe1
#0 do_an_addition (a=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
b=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
out=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>) at simple.cpp:24
(gdb) continue
Continuing.
result is 3
warning: Temporarily disabling breakpoints for unloaded shared library "file:///home/smarchi/build/binutils-gdb-amdgpu/gdb/simple#offset=8192&size=67208"
[Thread 0x7ffff54bf640 (LWP 1083186) exited]
[Thread 0x7ffff5db7640 (LWP 1082911) exited]
[Inferior 1 (process 1082907) exited normally]
One thing to notice is the host and GPU threads appearing under
the same inferior. This is a design goal for us, as programmers tend to
think of the threads running on the GPU as part of the same program as
the host threads, so showing them in the same inferior in GDB seems
natural. Also, the host and GPU threads share a global memory space,
which fits the inferior model.
Another thing to notice is the error messages when trying to read
variables or printing a backtrace. This is expected for the moment,
since the AMD GPU compiler produces some DWARF that uses some
non-standard extensions:
https://llvm.org/docs/AMDGPUDwarfExtensionsForHeterogeneousDebugging.html
There were already some patches posted by Zoran Zaric earlier to make
GDB support these extensions:
https://inbox.sourceware.org/gdb-patches/20211105113849.118800-1-zoran.zaric@amd.com/
We think it's better to get the basic support for AMD GPU in first,
which will then give a better justification for GDB to support these
extensions.
GPU threads are named `AMDGPU Wave`: a wave is essentially a hardware
thread using the SIMT (single-instruction, multiple-threads) [3]
execution model.
GDB uses the amd-dbgapi library [4], included in the ROCm platform, for
a few things related to AMD GPU threads debugging. Different components
talk to the library, as show on the following diagram:
+---------------------------+ +-------------+ +------------------+
| GDB | amd-dbgapi target | <-> | AMD | | Linux kernel |
| +-------------------+ | Debugger | +--------+ |
| | amdgcn gdbarch | <-> | API | <=> | AMDGPU | |
| +-------------------+ | | | driver | |
| | solib-rocm | <-> | (dbgapi.so) | +--------+---------+
+---------------------------+ +-------------+
- The amd-dbgapi target is a target_ops implementation used to control
execution of GPU threads. While the debugging of host threads works
by using the ptrace / wait Linux kernel interface (as usual), control
of GPU threads is done through a special interface (dubbed `kfd`)
exposed by the `amdgpu` Linux kernel module. GDB doesn't interact
directly with `kfd`, but instead goes through the amd-dbgapi library
(AMD Debugger API on the diagram).
Since it provides execution control, the amd-dbgapi target should
normally be a process_stratum_target, not just a target_ops. More
on that later.
- The amdgcn gdbarch (describing the hardware architecture of the GPU
execution units) offloads some requests to the amd-dbgapi library,
so that knowledge about the various architectures doesn't need to be
duplicated and baked in GDB. This is for example for things like
the list of registers.
- The solib-rocm component is an solib provider that fetches the list of
code objects loaded on the device from the amd-dbgapi library, and
makes GDB read their symbols. This is very similar to other solib
providers that handle shared libraries, except that here the shared
libraries are the pieces of code loaded on the device.
Given that Linux host threads are managed by the linux-nat target, and
the GPU threads are managed by the amd-dbgapi target, having all threads
appear in the same inferior requires the two targets to be in that
inferior's target stack. However, there can only be one
process_stratum_target in a given target stack, since there can be only
one target per slot. To achieve it, we therefore resort the hack^W
solution of placing the amd-dbgapi target in the arch_stratum slot of
the target stack, on top of the linux-nat target. Doing so allows the
amd-dbgapi target to intercept target calls and handle them if they
concern GPU threads, and offload to beneath otherwise. See
amd_dbgapi_target::fetch_registers for a simple example:
void
amd_dbgapi_target::fetch_registers (struct regcache *regcache, int regno)
{
if (!ptid_is_gpu (regcache->ptid ()))
{
beneath ()->fetch_registers (regcache, regno);
return;
}
// handle it
}
ptids of GPU threads are crafted with the following pattern:
(pid, 1, wave id)
Where pid is the inferior's pid and "wave id" is the wave handle handed
to us by the amd-dbgapi library (in practice, a monotonically
incrementing integer). The idea is that on Linux systems, the
combination (pid != 1, lwp == 1) is not possible. lwp == 1 would always
belong to the init process, which would also have pid == 1 (and it's
improbable for the init process to offload work to the GPU and much less
for the user to debug it). We can therefore differentiate GPU and
non-GPU ptids this way. See ptid_is_gpu for more details.
Note that we believe that this scheme could break down in the context of
containers, where the initial process executed in a container has pid 1
(in its own pid namespace). For instance, if you were to execute a ROCm
program in a container, then spawn a GDB in that container and attach to
the process, it will likely not work. This is a known limitation. A
workaround for this is to have a dummy process (like a shell) fork and
execute the program of interest.
The amd-dbgapi target watches native inferiors, and "attaches" to them
using amd_dbgapi_process_attach, which gives it a notifier fd that is
registered in the event loop (see enable_amd_dbgapi). Note that this
isn't the same "attach" as in PTRACE_ATTACH, but being ptrace-attached
is a precondition for amd_dbgapi_process_attach to work. When the
debugged process enables the ROCm runtime, the amd-dbgapi target gets
notified through that fd, and pushes itself on the target stack of the
inferior. The amd-dbgapi target is then able to intercept target_ops
calls. If the debugged process disables the ROCm runtime, the
amd-dbgapi target unpushes itself from the target stack.
This way, the amd-dbgapi target's footprint stays minimal when debugging
a process that doesn't use the AMD ROCm platform, it does not intercept
target calls.
The amd-dbgapi library is found using pkg-config. Since enabling
support for the amdgpu architecture (amdgpu-tdep.c) depends on the
amd-dbgapi library being present, we have the following logic for
the interaction with --target and --enable-targets:
- if the user explicitly asks for amdgcn support with
--target=amdgcn-*-* or --enable-targets=amdgcn-*-*, we probe for
the amd-dbgapi and fail if not found
- if the user uses --enable-targets=all, we probe for amd-dbgapi,
enable amdgcn support if found, disable amdgcn support if not found
- if the user uses --enable-targets=all and --with-amd-dbgapi=yes,
we probe for amd-dbgapi, enable amdgcn if found and fail if not found
- if the user uses --enable-targets=all and --with-amd-dbgapi=no,
we do not probe for amd-dbgapi, disable amdgcn support
- otherwise, amd-dbgapi is not probed for and support for amdgcn is not
enabled
Finally, a simple test is included. It only tests hitting a breakpoint
in device code and resuming execution, pretty much like the example
shown above.
[1] https://docs.amd.com/category/ROCm_v5.4
[2] https://docs.amd.com/bundle/HIP-Programming-Guide-v5.4
[3] https://en.wikipedia.org/wiki/Single_instruction,_multiple_threads
[4] https://docs.amd.com/bundle/ROCDebugger-API-Guide-v5.4
Change-Id: I591edca98b8927b1e49e4b0abe4e304765fed9ee
Co-Authored-By: Zoran Zaric <zoran.zaric@amd.com>
Co-Authored-By: Laurent Morichetti <laurent.morichetti@amd.com>
Co-Authored-By: Tony Tye <Tony.Tye@amd.com>
Co-Authored-By: Lancelot SIX <lancelot.six@amd.com>
Co-Authored-By: Pedro Alves <pedro@palves.net>
2023-01-04 04:07:07 +08:00
|
|
|
AMDGPU amdgcn-*-*
|
|
|
|
|
|
Show locno for 'multi location' breakpoint hit msg+conv var $_hit_bbnum $_hit_locno PR breakpoints/12464
This implements the request given in PR breakpoints/12464.
Before this patch, when a breakpoint that has multiple locations is reached,
GDB printed:
Thread 1 "zeoes" hit Breakpoint 1, some_func () at somefunc1.c:5
This patch changes the message so that bkpt_print_id prints the precise
encountered breakpoint:
Thread 1 "zeoes" hit Breakpoint 1.2, some_func () at somefunc1.c:5
In mi mode, bkpt_print_id also (optionally) prints a new table field "locno":
locno is printed when the breakpoint hit has more than one location.
Note that according to the GDB user manual node 'GDB/MI Development and Front
Ends', it is ok to add new fields without changing the MI version.
Also, when a breakpoint is reached, the convenience variables
$_hit_bpnum and $_hit_locno are set to the encountered breakpoint number
and location number.
$_hit_bpnum and $_hit_locno can a.o. be used in the command list of a
breakpoint, to disable the specific encountered breakpoint, e.g.
disable $_hit_bpnum.$_hit_locno
In case the breakpoint has only one location, $_hit_locno is set to
the value 1, so as to allow a command such as:
disable $_hit_bpnum.$_hit_locno
to disable the breakpoint even when the breakpoint has only one location.
This also fixes a strange behaviour: when a breakpoint X has only
one location,
enable|disable X.1
is accepted but transforms the breakpoint in a multiple locations
breakpoint having only one location.
The changes in RFA v4 handle the comments of Tom Tromey:
- Changed convenience var names from $bkptno/$locno to
$_hit_bpnum/$_hit_locno.
- updated the tests and user manual accordingly.
User manual also explictly describes that $_hit_locno is set to 1
for a breakpoint with a single location.
- The variable values are now set in bpstat_do_actions_1 so that
they are set for silent breakpoints, and when several breakpoints
are hit at the same time, that the variables are set to the printed
breakpoint.
The changes in RFA v3 handle the additional comments of Eli:
GDB/NEW:
- Use max 80-column
- Use 'code location' instead of 'location'.
- Fix typo $bkpno
- Ensure that disable $bkptno and disable $bkptno.$locno have
each their explanation inthe example
- Reworded the 'breakpoint-hit' paragraph.
gdb.texinfo:
- Use 'code location' instead of 'location'.
- Add a note to clarify the distinction between $bkptno and $bpnum.
- Use @kbd instead of examples with only one command.
Compared to RFA v1, the changes in v2 handle the comments given by
Keith Seitz and Eli Zaretskii:
- Use %s for the result of paddress
- Use bkptno_numopt_re instead of 2 different -re cases
- use C@t{++}
- Add index entries for $bkptno and $locno
- Added an example for "locno" in the mi interface
- Added examples in the Break command manual.
2020-05-24 04:27:28 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** The async record stating the stopped reason 'breakpoint-hit' now
|
|
|
|
|
contains an optional field locno giving the code location number
|
|
|
|
|
when the breakpoint has multiple code locations.
|
|
|
|
|
|
gdb/python: add gdb.format_address function
Add a new function, gdb.format_address, which is a wrapper around
GDB's print_address function.
This method takes an address, and returns a string with the format:
ADDRESS <SYMBOL+OFFSET>
Where, ADDRESS is the original address, formatted as hexadecimal,
SYMBOL is a symbol with an address lower than ADDRESS, and OFFSET is
the offset from SYMBOL to ADDRESS in decimal.
If there's no SYMBOL suitably close to ADDRESS then the
<SYMBOL+OFFSET> part is not included.
This is useful if a user wants to write a Python script that
pretty-prints addresses, the user no longer needs to do manual symbol
lookup, or worry about correctly formatting addresses.
Additionally, there are some settings that effect how GDB picks
SYMBOL, and whether the file name and line number should be included
with the SYMBOL name, the gdb.format_address function ensures that the
users Python script also benefits from these settings.
The gdb.format_address by default selects SYMBOL from the current
inferiors program space, and address is formatted using the
architecture for the current inferior. However, a user can also
explicitly pass a program space and architecture like this:
gdb.format_address(ADDRESS, PROGRAM_SPACE, ARCHITECTURE)
In order to format an address for a different inferior.
Notes on the implementation:
In py-arch.c I extended arch_object_to_gdbarch to add an assertion for
the type of the PyObject being worked on. Prior to this commit all
uses of arch_object_to_gdbarch were guaranteed to pass this function a
gdb.Architecture object, but, with this commit, this might not be the
case.
So, with this commit I've made it a requirement that the PyObject be a
gdb.Architecture, and this is checked with the assert. And in order
that callers from other files can check if they have a
gdb.Architecture object, I've added the new function
gdbpy_is_architecture.
In py-progspace.c I've added two new function, the first
progspace_object_to_program_space, converts a PyObject of type
gdb.Progspace to the associated program_space pointer, and
gdbpy_is_progspace checks if a PyObject is a gdb.Progspace or not.
2021-10-23 16:59:25 +08:00
|
|
|
* Python API
|
|
|
|
|
|
2022-06-07 03:07:37 +08:00
|
|
|
** GDB will now reformat the doc string for gdb.Command and
|
|
|
|
|
gdb.Parameter sub-classes to remove unnecessary leading
|
|
|
|
|
whitespace from each line before using the string as the help
|
|
|
|
|
output.
|
|
|
|
|
|
gdb/python: add gdb.format_address function
Add a new function, gdb.format_address, which is a wrapper around
GDB's print_address function.
This method takes an address, and returns a string with the format:
ADDRESS <SYMBOL+OFFSET>
Where, ADDRESS is the original address, formatted as hexadecimal,
SYMBOL is a symbol with an address lower than ADDRESS, and OFFSET is
the offset from SYMBOL to ADDRESS in decimal.
If there's no SYMBOL suitably close to ADDRESS then the
<SYMBOL+OFFSET> part is not included.
This is useful if a user wants to write a Python script that
pretty-prints addresses, the user no longer needs to do manual symbol
lookup, or worry about correctly formatting addresses.
Additionally, there are some settings that effect how GDB picks
SYMBOL, and whether the file name and line number should be included
with the SYMBOL name, the gdb.format_address function ensures that the
users Python script also benefits from these settings.
The gdb.format_address by default selects SYMBOL from the current
inferiors program space, and address is formatted using the
architecture for the current inferior. However, a user can also
explicitly pass a program space and architecture like this:
gdb.format_address(ADDRESS, PROGRAM_SPACE, ARCHITECTURE)
In order to format an address for a different inferior.
Notes on the implementation:
In py-arch.c I extended arch_object_to_gdbarch to add an assertion for
the type of the PyObject being worked on. Prior to this commit all
uses of arch_object_to_gdbarch were guaranteed to pass this function a
gdb.Architecture object, but, with this commit, this might not be the
case.
So, with this commit I've made it a requirement that the PyObject be a
gdb.Architecture, and this is checked with the assert. And in order
that callers from other files can check if they have a
gdb.Architecture object, I've added the new function
gdbpy_is_architecture.
In py-progspace.c I've added two new function, the first
progspace_object_to_program_space, converts a PyObject of type
gdb.Progspace to the associated program_space pointer, and
gdbpy_is_progspace checks if a PyObject is a gdb.Progspace or not.
2021-10-23 16:59:25 +08:00
|
|
|
** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE),
|
|
|
|
|
that formats ADDRESS as 'address <symbol+offset>', where symbol is
|
|
|
|
|
looked up in PROGSPACE, and ARCHITECTURE is used to format address.
|
|
|
|
|
This is the same format that GDB uses when printing address, symbol,
|
|
|
|
|
and offset information from the disassembler.
|
|
|
|
|
|
2022-05-25 00:15:17 +08:00
|
|
|
** New function gdb.current_language that returns the name of the
|
|
|
|
|
current language. Unlike gdb.parameter('language'), this will
|
|
|
|
|
never return 'auto'.
|
|
|
|
|
|
|
|
|
|
** New method gdb.Frame.language that returns the name of the
|
|
|
|
|
frame's language.
|
|
|
|
|
|
gdb/python: implement the print_insn extension language hook
This commit extends the Python API to include disassembler support.
The motivation for this commit was to provide an API by which the user
could write Python scripts that would augment the output of the
disassembler.
To achieve this I have followed the model of the existing libopcodes
disassembler, that is, instructions are disassembled one by one. This
does restrict the type of things that it is possible to do from a
Python script, i.e. all additional output has to fit on a single line,
but this was all I needed, and creating something more complex would,
I think, require greater changes to how GDB's internal disassembler
operates.
The disassembler API is contained in the new gdb.disassembler module,
which defines the following classes:
DisassembleInfo
Similar to libopcodes disassemble_info structure, has read-only
properties: address, architecture, and progspace. And has methods:
__init__, read_memory, and is_valid.
Each time GDB wants an instruction disassembled, an instance of
this class is passed to a user written disassembler function, by
reading the properties, and calling the methods (and other support
methods in the gdb.disassembler module) the user can perform and
return the disassembly.
Disassembler
This is a base-class which user written disassemblers should
inherit from. This base class provides base implementations of
__init__ and __call__ which the user written disassembler should
override.
DisassemblerResult
This class can be used to hold the result of a call to the
disassembler, it's really just a wrapper around a string (the text
of the disassembled instruction) and a length (in bytes). The user
can return an instance of this class from Disassembler.__call__ to
represent the newly disassembled instruction.
The gdb.disassembler module also provides the following functions:
register_disassembler
This function registers an instance of a Disassembler sub-class
as a disassembler, either for one specific architecture, or, as a
global disassembler for all architectures.
builtin_disassemble
This provides access to GDB's builtin disassembler. A common
use case that I see is augmenting the existing disassembler output.
The user code can call this function to have GDB disassemble the
instruction in the normal way. The user gets back a
DisassemblerResult object, which they can then read in order to
augment the disassembler output in any way they wish.
This function also provides a mechanism to intercept the
disassemblers reads of memory, thus the user can adjust what GDB
sees when it is disassembling.
The included documentation provides a more detailed description of the
API.
There is also a new CLI command added:
maint info python-disassemblers
This command is defined in the Python gdb.disassemblers module, and
can be used to list the currently registered Python disassemblers.
2021-09-18 01:12:34 +08:00
|
|
|
** New Python API for wrapping GDB's disassembler:
|
|
|
|
|
|
|
|
|
|
- gdb.disassembler.register_disassembler(DISASSEMBLER, ARCH).
|
|
|
|
|
DISASSEMBLER is a sub-class of gdb.disassembler.Disassembler.
|
|
|
|
|
ARCH is either None or a string containing a bfd architecture
|
|
|
|
|
name. DISASSEMBLER is registered as a disassembler for
|
|
|
|
|
architecture ARCH, or for all architectures if ARCH is None.
|
|
|
|
|
The previous disassembler registered for ARCH is returned, this
|
|
|
|
|
can be None if no previous disassembler was registered.
|
|
|
|
|
|
|
|
|
|
- gdb.disassembler.Disassembler is the class from which all
|
|
|
|
|
disassemblers should inherit. Its constructor takes a string,
|
|
|
|
|
a name for the disassembler, which is currently only used in
|
|
|
|
|
some debug output. Sub-classes should override the __call__
|
|
|
|
|
method to perform disassembly, invoking __call__ on this base
|
|
|
|
|
class will raise an exception.
|
|
|
|
|
|
|
|
|
|
- gdb.disassembler.DisassembleInfo is the class used to describe
|
|
|
|
|
a single disassembly request from GDB. An instance of this
|
|
|
|
|
class is passed to the __call__ method of
|
|
|
|
|
gdb.disassembler.Disassembler and has the following read-only
|
|
|
|
|
attributes: 'address', and 'architecture', as well as the
|
|
|
|
|
following method: 'read_memory'.
|
|
|
|
|
|
|
|
|
|
- gdb.disassembler.builtin_disassemble(INFO, MEMORY_SOURCE),
|
|
|
|
|
calls GDB's builtin disassembler on INFO, which is a
|
|
|
|
|
gdb.disassembler.DisassembleInfo object. MEMORY_SOURCE is
|
|
|
|
|
optional, its default value is None. If MEMORY_SOURCE is not
|
|
|
|
|
None then it must be an object that has a 'read_memory' method.
|
|
|
|
|
|
|
|
|
|
- gdb.disassembler.DisassemblerResult is a class that can be used
|
|
|
|
|
to wrap the result of a call to a Disassembler. It has
|
|
|
|
|
read-only attributes 'length' and 'string'.
|
|
|
|
|
|
2022-06-21 02:32:52 +08:00
|
|
|
** gdb.Objfile now has an attribute named "is_file". This is True
|
|
|
|
|
if the objfile comes from a file, and False otherwise.
|
|
|
|
|
|
2022-06-06 23:54:45 +08:00
|
|
|
** New function gdb.print_options that returns a dictionary of the
|
|
|
|
|
prevailing print options, in the form accepted by
|
|
|
|
|
gdb.Value.format_string.
|
|
|
|
|
|
|
|
|
|
** gdb.Value.format_string now uses the format provided by 'print',
|
|
|
|
|
if it is called during a 'print' or other similar operation.
|
|
|
|
|
|
2022-06-07 21:05:02 +08:00
|
|
|
** gdb.Value.format_string now accepts the 'summary' keyword. This
|
|
|
|
|
can be used to request a shorter representation of a value, the
|
|
|
|
|
way that 'set print frame-arguments scalars' does.
|
|
|
|
|
|
gdb/python: Add BreakpointLocation type
PR python/18385
v7:
This version addresses the issues pointed out by Tom.
Added nullchecks for Python object creations.
Changed from using PyLong_FromLong to the gdb_py-versions.
Re-factored some code to make it look more cohesive.
Also added the more safe Python reference count decrement PY_XDECREF,
even though the BreakpointLocation type is never instantiated by the
user (explicitly documented in the docs) decrementing < 0 is made
impossible with the safe call.
Tom pointed out that using the policy class explicitly to decrement a
reference counted object was not the way to go, so this has instead been
wrapped in a ref_ptr that handles that for us in blocpy_dealloc.
Moved macro from py-internal to py-breakpoint.c.
Renamed section at the bottom of commit message "Patch Description".
v6:
This version addresses the points Pedro gave in review to this patch.
Added the attributes `function`, `fullname` and `thread_groups`
as per request by Pedro with the argument that it more resembles the
output of the MI-command "-break-list". Added documentation for these attributes.
Cleaned up left overs from copy+paste in test suite, removed hard coding
of line numbers where possible.
Refactored some code to use more c++-y style range for loops
wrt to breakpoint locations.
Changed terminology, naming was very inconsistent. Used a variety of "parent",
"owner". Now "owner" is the only term used, and the field in the
gdb_breakpoint_location_object now also called "owner".
v5:
Changes in response to review by Tom Tromey:
- Replaced manual INCREF/DECREF calls with
gdbpy_ref ptrs in places where possible.
- Fixed non-gdb style conforming formatting
- Get parent of bploc increases ref count of parent.
- moved bploc Python definition to py-breakpoint.c
The INCREF of self in bppy_get_locations is due
to the individual locations holding a reference to
it's owner. This is decremented at de-alloc time.
The reason why this needs to be here is, if the user writes
for instance;
py loc = gdb.breakpoints()[X].locations[Y]
The breakpoint owner object is immediately going
out of scope (GC'd/dealloced), and the location
object requires it to be alive for as long as it is alive.
Thanks for your review, Tom!
v4:
Fixed remaining doc issues as per request
by Eli.
v3:
Rewritten commit message, shortened + reworded,
added tests.
Patch Description
Currently, the Python API lacks the ability to
query breakpoints for their installed locations,
and subsequently, can't query any information about them, or
enable/disable individual locations.
This patch solves this by adding Python type gdb.BreakpointLocation.
The type is never instantiated by the user of the Python API directly,
but is produced by the gdb.Breakpoint.locations attribute returning
a list of gdb.BreakpointLocation.
gdb.Breakpoint.locations:
The attribute for retrieving the currently installed breakpoint
locations for gdb.Breakpoint. Matches behavior of
the "info breakpoints" command in that it only
returns the last known or currently inserted breakpoint locations.
BreakpointLocation contains 7 attributes
6 read-only attributes:
owner: location owner's Python companion object
source: file path and line number tuple: (string, long) / None
address: installed address of the location
function: function name where location was set
fullname: fullname where location was set
thread_groups: thread groups (inferiors) where location was set.
1 writeable attribute:
enabled: get/set enable/disable this location (bool)
Access/calls to these, can all throw Python exceptions (documented in
the online documentation), and that's due to the nature
of how breakpoint locations can be invalidated
"behind the scenes", either by them being removed
from the original breakpoint or changed,
like for instance when a new symbol file is loaded, at
which point all breakpoint locations are re-created by GDB.
Therefore this patch has chosen to be non-intrusive:
it's up to the Python user to re-request the locations if
they become invalid.
Also there's event handlers that handle new object files etc, if a Python
user is storing breakpoint locations in some larger state they've
built up, refreshing the locations is easy and it only comes
with runtime overhead when the Python user wants to use them.
gdb.BreakpointLocation Python type
struct "gdbpy_breakpoint_location_object" is found in python-internal.h
Its definition, layout, methods and functions
are found in the same file as gdb.Breakpoint (py-breakpoint.c)
1 change was also made to breakpoint.h/c to make it possible
to enable and disable a bp_location* specifically,
without having its LOC_NUM, as this number
also can change arbitrarily behind the scenes.
Updated docs & news file as per request.
Testsuite: tests the .source attribute and the disabling of
individual locations.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=18385
Change-Id: I302c1c50a557ad59d5d18c88ca19014731d736b0
2022-06-07 19:57:48 +08:00
|
|
|
** New Python type gdb.BreakpointLocation.
|
|
|
|
|
The new attribute 'locations' of gdb.Breakpoint returns a list of
|
|
|
|
|
gdb.BreakpointLocation objects specifying the locations where the
|
|
|
|
|
breakpoint is inserted into the debuggee.
|
|
|
|
|
|
gdb/python: restrict the names accepted by gdb.register_window_type
I noticed that, from Python, I could register a new TUI window that
had whitespace in its name, like this:
gdb.register_window_type('my window', MyWindowType)
however, it is not possible to then use this window in a new TUI
layout, e.g.:
(gdb) tui new-layout foo my window 1 cmd 1
Unknown window "my"
(gdb) tui new-layout foo "my window" 1 cmd 1
Unknown window ""my"
(gdb) tui new-layout foo my\ window 1 cmd 1
Unknown window "my\"
GDB clearly uses the whitespace to split the incoming command line.
I could fix this by trying to add a mechanism by which we can use
whitespace within a window name, but it seems like an easier solution
if we just forbid whitespace within a window name. Not only is this
easier, but I think this is probably the better solution, identifier
names with spaces in would mean we'd need to audit all the places a
window name could be printed and ensure that the use of a space didn't
make the output ambiguous.
So, having decided to disallow whitespace, I then thought about other
special characters. We currently accept anything as a window name,
and I wondered if this was a good idea.
My concerns were about how special characters used in a window name
might cause confusion, for example, we allow '$' in window names,
which is maybe fine now, but what if one day we wanted to allow
variable expansion when creating new layouts? Or what about starting
a window name with '-'? We already support a '-horizontal' option,
what if we want to add more in the future? Or use of the special
character '{' which has special meaning within a new layout?
In the end I figured it might make sense to place some restrictive
rules in place, and then relax the rules later if/when users complain,
we can consider each relaxation as its requested.
So, I propose that window names should match this regular expression:
[a-zA-Z][-_.a-zA-Z0-9]*
There is a chance that there is user code in the wild which will break
with the addition of this change, but hopefully adapting to the new
restrictions shouldn't be too difficult.
2022-09-14 20:51:28 +08:00
|
|
|
** The gdb.register_window_type method now restricts the set of
|
|
|
|
|
acceptable window names. The first character of a window's name
|
|
|
|
|
must start with a character in the set [a-zA-Z], every subsequent
|
|
|
|
|
character of a window's name must be in the set [-_.a-zA-Z0-9].
|
|
|
|
|
|
2022-06-17 16:51:05 +08:00
|
|
|
* New features in the GDB remote stub, GDBserver
|
|
|
|
|
|
|
|
|
|
** GDBserver is now supported on LoongArch GNU/Linux.
|
gdbserver/csky add csky gdbserver support
Add new files:
gdb/arch/csky.c
gdb/arch/csky.h
gdb/features/cskyv2-linux.c
gdbserver/linux-csky-low.cc
1. In gdb/arch/csky.c file, add function "csky_create_target_description()"
for csky_target::low_arch_setup(). later, it can be used for csky native gdb.
2. In gdb/features/cskyv2-linux.c file, create target_tdesc for csky, include
gprs, pc, hi, lo, float, vector and float control registers.
3. In gdbserver/linux-csky-low.cc file, using PTRACE_GET/SET_RGESET to
get/set registers. The main data structures in asm/ptrace.h are:
struct pt_regs {
unsigned long tls;
unsigned long lr;
unsigned long pc;
unsigned long sr;
unsigned long usp;
/*
* a0, a1, a2, a3:
* r0, r1, r2, r3
*/
unsigned long orig_a0;
unsigned long a0;
unsigned long a1;
unsigned long a2;
unsigned long a3;
/*
* r4 ~ r13
*/
unsigned long regs[10];
/* r16 ~ r30 */
unsigned long exregs[15];
unsigned long rhi;
unsigned long rlo;
unsigned long dcsr;
};
struct user_fp {
unsigned long vr[96];
unsigned long fcr;
unsigned long fesr;
unsigned long fid;
unsigned long reserved;
};
2022-09-13 11:20:54 +08:00
|
|
|
|
|
|
|
|
** GDBserver is now supported on CSKY GNU/Linux.
|
2022-06-17 16:51:05 +08:00
|
|
|
|
2022-07-14 15:00:00 +08:00
|
|
|
* LoongArch floating-point support
|
|
|
|
|
|
|
|
|
|
GDB now supports floating-point on LoongArch GNU/Linux.
|
|
|
|
|
|
gdb: initial support for ROCm platform (AMDGPU) debugging
This patch adds the foundation for GDB to be able to debug programs
offloaded to AMD GPUs using the AMD ROCm platform [1]. The latest
public release of the ROCm release at the time of writing is 5.4, so
this is what this patch targets.
The ROCm platform allows host programs to schedule bits of code for
execution on GPUs or similar accelerators. The programs running on GPUs
are typically referred to as `kernels` (not related to operating system
kernels).
Programs offloaded with the AMD ROCm platform can be written in the HIP
language [2], OpenCL and OpenMP, but we're going to focus on HIP here.
The HIP language consists of a C++ Runtime API and kernel language.
Here's an example of a very simple HIP program:
#include "hip/hip_runtime.h"
#include <cassert>
__global__ void
do_an_addition (int a, int b, int *out)
{
*out = a + b;
}
int
main ()
{
int *result_ptr, result;
/* Allocate memory for the device to write the result to. */
hipError_t error = hipMalloc (&result_ptr, sizeof (int));
assert (error == hipSuccess);
/* Run `do_an_addition` on one workgroup containing one work item. */
do_an_addition<<<dim3(1), dim3(1), 0, 0>>> (1, 2, result_ptr);
/* Copy result from device to host. Note that this acts as a synchronization
point, waiting for the kernel dispatch to complete. */
error = hipMemcpyDtoH (&result, result_ptr, sizeof (int));
assert (error == hipSuccess);
printf ("result is %d\n", result);
assert (result == 3);
return 0;
}
This program can be compiled with:
$ hipcc simple.cpp -g -O0 -o simple
... where `hipcc` is the HIP compiler, shipped with ROCm releases. This
generates an ELF binary for the host architecture, containing another
ELF binary with the device code. The ELF for the device can be
inspected with:
$ roc-obj-ls simple
1 host-x86_64-unknown-linux file://simple#offset=8192&size=0
1 hipv4-amdgcn-amd-amdhsa--gfx906 file://simple#offset=8192&size=34216
$ roc-obj-extract 'file://simple#offset=8192&size=34216'
$ file simple-offset8192-size34216.co
simple-offset8192-size34216.co: ELF 64-bit LSB shared object, *unknown arch 0xe0* version 1, dynamically linked, with debug_info, not stripped
^
amcgcn architecture that my `file` doesn't know about ----´
Running the program gives the very unimpressive result:
$ ./simple
result is 3
While running, this host program has copied the device program into the
GPU's memory and spawned an execution thread on it. The goal of this
GDB port is to let the user debug host threads and these GPU threads
simultaneously. Here's a sample session using a GDB with this patch
applied:
$ ./gdb -q -nx --data-directory=data-directory ./simple
Reading symbols from ./simple...
(gdb) break do_an_addition
Function "do_an_addition" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (do_an_addition) pending.
(gdb) r
Starting program: /home/smarchi/build/binutils-gdb-amdgpu/gdb/simple
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff5db7640 (LWP 1082911)]
[New Thread 0x7ffef53ff640 (LWP 1082913)]
[Thread 0x7ffef53ff640 (LWP 1082913) exited]
[New Thread 0x7ffdecb53640 (LWP 1083185)]
[New Thread 0x7ffff54bf640 (LWP 1083186)]
[Thread 0x7ffdecb53640 (LWP 1083185) exited]
[Switching to AMDGPU Wave 2:2:1:1 (0,0,0)/0]
Thread 6 hit Breakpoint 1, do_an_addition (a=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
b=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
out=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>) at simple.cpp:24
24 *out = a + b;
(gdb) info inferiors
Num Description Connection Executable
* 1 process 1082907 1 (native) /home/smarchi/build/binutils-gdb-amdgpu/gdb/simple
(gdb) info threads
Id Target Id Frame
1 Thread 0x7ffff5dc9240 (LWP 1082907) "simple" 0x00007ffff5e9410b in ?? () from /opt/rocm-5.4.0/lib/libhsa-runtime64.so.1
2 Thread 0x7ffff5db7640 (LWP 1082911) "simple" __GI___ioctl (fd=3, request=3222817548) at ../sysdeps/unix/sysv/linux/ioctl.c:36
5 Thread 0x7ffff54bf640 (LWP 1083186) "simple" __GI___ioctl (fd=3, request=3222817548) at ../sysdeps/unix/sysv/linux/ioctl.c:36
* 6 AMDGPU Wave 2:2:1:1 (0,0,0)/0 do_an_addition (
a=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
b=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
out=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>) at simple.cpp:24
(gdb) bt
Python Exception <class 'gdb.error'>: Unhandled dwarf expression opcode 0xe1
#0 do_an_addition (a=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
b=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>,
out=<error reading variable: DWARF-2 expression error: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_OP_bit_piece.>) at simple.cpp:24
(gdb) continue
Continuing.
result is 3
warning: Temporarily disabling breakpoints for unloaded shared library "file:///home/smarchi/build/binutils-gdb-amdgpu/gdb/simple#offset=8192&size=67208"
[Thread 0x7ffff54bf640 (LWP 1083186) exited]
[Thread 0x7ffff5db7640 (LWP 1082911) exited]
[Inferior 1 (process 1082907) exited normally]
One thing to notice is the host and GPU threads appearing under
the same inferior. This is a design goal for us, as programmers tend to
think of the threads running on the GPU as part of the same program as
the host threads, so showing them in the same inferior in GDB seems
natural. Also, the host and GPU threads share a global memory space,
which fits the inferior model.
Another thing to notice is the error messages when trying to read
variables or printing a backtrace. This is expected for the moment,
since the AMD GPU compiler produces some DWARF that uses some
non-standard extensions:
https://llvm.org/docs/AMDGPUDwarfExtensionsForHeterogeneousDebugging.html
There were already some patches posted by Zoran Zaric earlier to make
GDB support these extensions:
https://inbox.sourceware.org/gdb-patches/20211105113849.118800-1-zoran.zaric@amd.com/
We think it's better to get the basic support for AMD GPU in first,
which will then give a better justification for GDB to support these
extensions.
GPU threads are named `AMDGPU Wave`: a wave is essentially a hardware
thread using the SIMT (single-instruction, multiple-threads) [3]
execution model.
GDB uses the amd-dbgapi library [4], included in the ROCm platform, for
a few things related to AMD GPU threads debugging. Different components
talk to the library, as show on the following diagram:
+---------------------------+ +-------------+ +------------------+
| GDB | amd-dbgapi target | <-> | AMD | | Linux kernel |
| +-------------------+ | Debugger | +--------+ |
| | amdgcn gdbarch | <-> | API | <=> | AMDGPU | |
| +-------------------+ | | | driver | |
| | solib-rocm | <-> | (dbgapi.so) | +--------+---------+
+---------------------------+ +-------------+
- The amd-dbgapi target is a target_ops implementation used to control
execution of GPU threads. While the debugging of host threads works
by using the ptrace / wait Linux kernel interface (as usual), control
of GPU threads is done through a special interface (dubbed `kfd`)
exposed by the `amdgpu` Linux kernel module. GDB doesn't interact
directly with `kfd`, but instead goes through the amd-dbgapi library
(AMD Debugger API on the diagram).
Since it provides execution control, the amd-dbgapi target should
normally be a process_stratum_target, not just a target_ops. More
on that later.
- The amdgcn gdbarch (describing the hardware architecture of the GPU
execution units) offloads some requests to the amd-dbgapi library,
so that knowledge about the various architectures doesn't need to be
duplicated and baked in GDB. This is for example for things like
the list of registers.
- The solib-rocm component is an solib provider that fetches the list of
code objects loaded on the device from the amd-dbgapi library, and
makes GDB read their symbols. This is very similar to other solib
providers that handle shared libraries, except that here the shared
libraries are the pieces of code loaded on the device.
Given that Linux host threads are managed by the linux-nat target, and
the GPU threads are managed by the amd-dbgapi target, having all threads
appear in the same inferior requires the two targets to be in that
inferior's target stack. However, there can only be one
process_stratum_target in a given target stack, since there can be only
one target per slot. To achieve it, we therefore resort the hack^W
solution of placing the amd-dbgapi target in the arch_stratum slot of
the target stack, on top of the linux-nat target. Doing so allows the
amd-dbgapi target to intercept target calls and handle them if they
concern GPU threads, and offload to beneath otherwise. See
amd_dbgapi_target::fetch_registers for a simple example:
void
amd_dbgapi_target::fetch_registers (struct regcache *regcache, int regno)
{
if (!ptid_is_gpu (regcache->ptid ()))
{
beneath ()->fetch_registers (regcache, regno);
return;
}
// handle it
}
ptids of GPU threads are crafted with the following pattern:
(pid, 1, wave id)
Where pid is the inferior's pid and "wave id" is the wave handle handed
to us by the amd-dbgapi library (in practice, a monotonically
incrementing integer). The idea is that on Linux systems, the
combination (pid != 1, lwp == 1) is not possible. lwp == 1 would always
belong to the init process, which would also have pid == 1 (and it's
improbable for the init process to offload work to the GPU and much less
for the user to debug it). We can therefore differentiate GPU and
non-GPU ptids this way. See ptid_is_gpu for more details.
Note that we believe that this scheme could break down in the context of
containers, where the initial process executed in a container has pid 1
(in its own pid namespace). For instance, if you were to execute a ROCm
program in a container, then spawn a GDB in that container and attach to
the process, it will likely not work. This is a known limitation. A
workaround for this is to have a dummy process (like a shell) fork and
execute the program of interest.
The amd-dbgapi target watches native inferiors, and "attaches" to them
using amd_dbgapi_process_attach, which gives it a notifier fd that is
registered in the event loop (see enable_amd_dbgapi). Note that this
isn't the same "attach" as in PTRACE_ATTACH, but being ptrace-attached
is a precondition for amd_dbgapi_process_attach to work. When the
debugged process enables the ROCm runtime, the amd-dbgapi target gets
notified through that fd, and pushes itself on the target stack of the
inferior. The amd-dbgapi target is then able to intercept target_ops
calls. If the debugged process disables the ROCm runtime, the
amd-dbgapi target unpushes itself from the target stack.
This way, the amd-dbgapi target's footprint stays minimal when debugging
a process that doesn't use the AMD ROCm platform, it does not intercept
target calls.
The amd-dbgapi library is found using pkg-config. Since enabling
support for the amdgpu architecture (amdgpu-tdep.c) depends on the
amd-dbgapi library being present, we have the following logic for
the interaction with --target and --enable-targets:
- if the user explicitly asks for amdgcn support with
--target=amdgcn-*-* or --enable-targets=amdgcn-*-*, we probe for
the amd-dbgapi and fail if not found
- if the user uses --enable-targets=all, we probe for amd-dbgapi,
enable amdgcn support if found, disable amdgcn support if not found
- if the user uses --enable-targets=all and --with-amd-dbgapi=yes,
we probe for amd-dbgapi, enable amdgcn if found and fail if not found
- if the user uses --enable-targets=all and --with-amd-dbgapi=no,
we do not probe for amd-dbgapi, disable amdgcn support
- otherwise, amd-dbgapi is not probed for and support for amdgcn is not
enabled
Finally, a simple test is included. It only tests hitting a breakpoint
in device code and resuming execution, pretty much like the example
shown above.
[1] https://docs.amd.com/category/ROCm_v5.4
[2] https://docs.amd.com/bundle/HIP-Programming-Guide-v5.4
[3] https://en.wikipedia.org/wiki/Single_instruction,_multiple_threads
[4] https://docs.amd.com/bundle/ROCDebugger-API-Guide-v5.4
Change-Id: I591edca98b8927b1e49e4b0abe4e304765fed9ee
Co-Authored-By: Zoran Zaric <zoran.zaric@amd.com>
Co-Authored-By: Laurent Morichetti <laurent.morichetti@amd.com>
Co-Authored-By: Tony Tye <Tony.Tye@amd.com>
Co-Authored-By: Lancelot SIX <lancelot.six@amd.com>
Co-Authored-By: Pedro Alves <pedro@palves.net>
2023-01-04 04:07:07 +08:00
|
|
|
* AMD GPU ROCm debugging support
|
|
|
|
|
|
|
|
|
|
GDB now supports debugging programs offloaded to AMD GPUs using the ROCm
|
|
|
|
|
platform.
|
|
|
|
|
|
2022-03-20 13:17:42 +08:00
|
|
|
*** Changes in GDB 12
|
2021-07-04 01:52:20 +08:00
|
|
|
|
2022-03-04 00:47:00 +08:00
|
|
|
* DBX mode is deprecated, and will be removed in GDB 13
|
|
|
|
|
|
2022-03-08 21:42:16 +08:00
|
|
|
* GDB 12 is the last release of GDB that will support building against
|
|
|
|
|
Python 2. From GDB 13, it will only be possible to build GDB itself
|
|
|
|
|
with Python 3 support.
|
|
|
|
|
|
2021-09-08 22:20:29 +08:00
|
|
|
* The disable-randomization setting now works on Windows.
|
|
|
|
|
|
2022-02-25 08:42:22 +08:00
|
|
|
* Improved C++ template support
|
|
|
|
|
|
|
|
|
|
GDB now treats functions/types involving C++ templates like it does function
|
|
|
|
|
overloads. Users may omit parameter lists to set breakpoints on families of
|
|
|
|
|
template functions, including types/functions composed of multiple template types:
|
|
|
|
|
|
|
|
|
|
(gdb) break template_func(template_1, int)
|
|
|
|
|
|
|
|
|
|
The above will set breakpoints at every function `template_func' where
|
|
|
|
|
the first function parameter is any template type named `template_1' and
|
|
|
|
|
the second function parameter is `int'.
|
|
|
|
|
|
|
|
|
|
TAB completion also gains similar improvements.
|
|
|
|
|
|
2022-02-23 03:22:14 +08:00
|
|
|
* The FreeBSD native target now supports async mode.
|
|
|
|
|
|
2021-11-26 22:31:18 +08:00
|
|
|
* Configure changes
|
|
|
|
|
|
|
|
|
|
--enable-threading
|
|
|
|
|
|
|
|
|
|
Enable or disable multithreaded symbol loading. This is enabled
|
|
|
|
|
by default, but passing --disable-threading or --enable-threading=no
|
|
|
|
|
to configure will disable it.
|
|
|
|
|
|
|
|
|
|
Disabling this can cause a performance penalty when there are a lot of
|
|
|
|
|
symbols to load, but is useful for debugging purposes.
|
|
|
|
|
|
2018-04-26 23:21:34 +08:00
|
|
|
* New commands
|
|
|
|
|
|
gdb: print backtrace on fatal SIGSEGV
This commit adds a new maintenance feature, the ability to print
a (limited) backtrace if GDB dies due to a fatal signal.
The backtrace is produced using the backtrace and backtrace_symbols_fd
functions which are declared in the execinfo.h header, and both of
which are async signal safe. A configure check has been added to
check for these features, if they are not available then the new code
is not compiled into GDB and the backtrace will not be printed.
The motivation for this new feature is to aid in debugging GDB in
situations where GDB has crashed at a users site, but the user is
reluctant to share core files, possibly due to concerns about what
might be in the memory image within the core file. Such a user might
be happy to share a simple backtrace that was written to stderr.
The production of the backtrace is on by default, but can switched off
using the new commands:
maintenance set backtrace-on-fatal-signal on|off
maintenance show backtrace-on-fatal-signal
Right now, I have hooked this feature in to GDB's existing handling of
SIGSEGV only, but this will be extended to more signals in a later
commit.
One additional change I have made in this commit is that, when we
decide GDB should terminate due to the fatal signal, we now
raise the same fatal signal rather than raising SIGABRT.
Currently, this is only effecting our handling of SIGSEGV. So,
previously, if GDB hit a SEGV then we would terminate GDB with a
SIGABRT. After this commit we will terminate GDB with a SIGSEGV.
This feels like an improvement to me, we should still get a core dump,
but in many shells, the user will see a more specific message once GDB
exits, in bash for example "Segmentation fault" rather than "Aborted".
Finally then, here is an example of the output a user would see if GDB
should hit an internal SIGSEGV:
Fatal signal: Segmentation fault
----- Backtrace -----
./gdb/gdb[0x8078e6]
./gdb/gdb[0x807b20]
/lib64/libpthread.so.0(+0x14b20)[0x7f6648c92b20]
/lib64/libc.so.6(__poll+0x4f)[0x7f66484d3a5f]
./gdb/gdb[0x1540f4c]
./gdb/gdb[0x154034a]
./gdb/gdb[0x9b002d]
./gdb/gdb[0x9b014d]
./gdb/gdb[0x9b1aa6]
./gdb/gdb[0x9b1b0c]
./gdb/gdb[0x41756d]
/lib64/libc.so.6(__libc_start_main+0xf3)[0x7f66484041a3]
./gdb/gdb[0x41746e]
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
Segmentation fault (core dumped)
It is disappointing that backtrace_symbols_fd does not actually map
the addresses back to symbols, this appears, in part, to be due to GDB
not being built with -rdynamic as the manual page for
backtrace_symbols_fd suggests, however, even when I do add -rdynamic
to the build of GDB I only see symbols for some addresses.
We could potentially look at alternative libraries to provide the
backtrace (e.g. libunwind) however, the solution presented here, which
is available as part of glibc is probably a good baseline from which
we might improve things in future.
2021-06-10 23:57:24 +08:00
|
|
|
maint set backtrace-on-fatal-signal on|off
|
|
|
|
|
maint show backtrace-on-fatal-signal
|
|
|
|
|
This setting is 'on' by default. When 'on' GDB will print a limited
|
|
|
|
|
backtrace to stderr in the situation where GDB terminates with a
|
|
|
|
|
fatal signal. This only supported on some platforms where the
|
|
|
|
|
backtrace and backtrace_symbols_fd functions are available.
|
|
|
|
|
|
2018-04-26 23:21:34 +08:00
|
|
|
set source open on|off
|
|
|
|
|
show source open
|
|
|
|
|
This setting, which is on by default, controls whether GDB will try
|
|
|
|
|
to open source code files. Switching this off will stop GDB trying
|
|
|
|
|
to open and read source code files, which can be useful if the files
|
|
|
|
|
are located over a slow network connection.
|
|
|
|
|
|
2021-09-14 02:53:05 +08:00
|
|
|
set varsize-limit
|
|
|
|
|
show varsize-limit
|
|
|
|
|
These are now deprecated aliases for "set max-value-size" and
|
|
|
|
|
"show max-value-size".
|
|
|
|
|
|
2021-08-30 20:24:12 +08:00
|
|
|
task apply [all | TASK-IDS...] [FLAG]... COMMAND
|
|
|
|
|
Like "thread apply", but applies COMMAND to Ada tasks.
|
|
|
|
|
|
2021-08-31 03:58:48 +08:00
|
|
|
watch [...] task ID
|
|
|
|
|
Watchpoints can now be restricted to a specific Ada task.
|
|
|
|
|
|
gdb: print backtrace for internal error/warning
This commit builds on previous work to allow GDB to print a backtrace
of itself when GDB encounters an internal-error or internal-warning.
This fixes PR gdb/26377.
There's not many places where we call internal_warning, and I guess in
most cases the user would probably continue their debug session. And
so, in order to avoid cluttering up the output, by default, printing
of a backtrace is off for internal-warnings.
In contrast, printing of a backtrace is on by default for
internal-errors, as I figure that in most cases hitting an
internal-error is going to be the end of the debug session.
Whether a backtrace is printed or not can be controlled with the new
settings:
maintenance set internal-error backtrace on|off
maintenance show internal-error backtrace
maintenance set internal-warning backtrace on|off
maintenance show internal-warning backtrace
Here is an example of what an internal-error now looks like with the
backtrace included:
(gdb) maintenance internal-error blah
../../src.dev-3/gdb/maint.c:82: internal-error: blah
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0x5c61ca gdb_internal_backtrace_1
../../src.dev-3/gdb/bt-utils.c:123
0x5c626d _Z22gdb_internal_backtracev
../../src.dev-3/gdb/bt-utils.c:165
0xe33237 internal_vproblem
../../src.dev-3/gdb/utils.c:393
0xe33539 _Z15internal_verrorPKciS0_P13__va_list_tag
../../src.dev-3/gdb/utils.c:470
0x1549652 _Z14internal_errorPKciS0_z
../../src.dev-3/gdbsupport/errors.cc:55
0x9c7982 maintenance_internal_error
../../src.dev-3/gdb/maint.c:82
0x636f57 do_simple_func
../../src.dev-3/gdb/cli/cli-decode.c:97
.... snip, lots more backtrace lines ....
---------------------
../../src.dev-3/gdb/maint.c:82: internal-error: blah
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
../../src.dev-3/gdb/maint.c:82: internal-error: blah
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
My hope is that this backtrace might make it slightly easier to
diagnose GDB issues if all that is provided is the console output, I
find that we frequently get reports of an assert being hit that is
located in pretty generic code (frame.c, value.c, etc) and it is not
always obvious how we might have arrived at the assert.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=26377
2021-08-13 01:24:59 +08:00
|
|
|
maint set internal-error backtrace on|off
|
|
|
|
|
maint show internal-error backtrace
|
|
|
|
|
maint set internal-warning backtrace on|off
|
|
|
|
|
maint show internal-warning backtrace
|
|
|
|
|
GDB can now print a backtrace of itself when it encounters either an
|
|
|
|
|
internal-error, or an internal-warning. This is on by default for
|
|
|
|
|
internal-error and off by default for internal-warning.
|
|
|
|
|
|
2021-11-25 14:49:16 +08:00
|
|
|
set logging on|off
|
|
|
|
|
Deprecated and replaced by "set logging enabled on|off".
|
|
|
|
|
|
|
|
|
|
set logging enabled on|off
|
|
|
|
|
show logging enabled
|
|
|
|
|
These commands set or show whether logging is enabled or disabled.
|
|
|
|
|
|
2021-12-18 19:19:12 +08:00
|
|
|
exit
|
|
|
|
|
You can now exit GDB by using the new command "exit", in addition to
|
|
|
|
|
the existing "quit" command.
|
|
|
|
|
|
2021-11-12 18:30:27 +08:00
|
|
|
set debug threads on|off
|
|
|
|
|
show debug threads
|
|
|
|
|
Print additional debug messages about thread creation and deletion.
|
|
|
|
|
|
2021-12-22 23:33:38 +08:00
|
|
|
set debug linux-nat on|off
|
|
|
|
|
show debug linux-nat
|
|
|
|
|
These new commands replaced the old 'set debug lin-lwp' and 'show
|
|
|
|
|
debug lin-lwp' respectively. Turning this setting on prints debug
|
|
|
|
|
messages relating to GDB's handling of native Linux inferiors.
|
|
|
|
|
|
2021-11-26 21:51:36 +08:00
|
|
|
maint flush source-cache
|
|
|
|
|
Flush the contents of the source code cache.
|
|
|
|
|
|
2021-11-26 23:13:43 +08:00
|
|
|
maint set gnu-source-highlight enabled on|off
|
|
|
|
|
maint show gnu-source-highlight enabled
|
|
|
|
|
Whether GDB should use the GNU Source Highlight library for adding
|
|
|
|
|
styling to source code. When off, the library will not be used, even
|
|
|
|
|
when available. When GNU Source Highlight isn't used, or can't add
|
|
|
|
|
styling to a particular source file, then the Python Pygments
|
|
|
|
|
library will be used instead.
|
|
|
|
|
|
gdb: add the 'set/show suppress-cli-notifications' command
GDB already has a flag to suppress printing notification events, such
as thread and inferior context switches, on the CLI. This is used
internally when executing commands. Make the flag available to the
user via a new command. This is expected to be useful in scripts.
For instance, suppose that when Inferior 1 gets to a certain state,
you want to add and set up a new inferior using the commands below,
but you also want to have a reduced/clean output.
define do-setup
printf "Setting up Inferior 2...\n"
add-inferior -exec a.out
inferior 2
break file.c:3
run
inferior 1
printf "Done\n"
end
Currently, GDB prints
(gdb) do-setup
Setting up Inferior 2...
[New inferior 2]
Added inferior 2 on connection 1 (native)
[Switching to inferior 2 [<null>] (/tmp/a.out)]
Breakpoint 2 at 0x1155: file file.c, line 3.
Thread 2.1 "a.out" hit Breakpoint 2, main () at file.c:3
3 return 0;
[Switching to inferior 1 [process 7670] (/tmp/test)]
[Switching to thread 1.1 (process 7670)]
#0 main () at test.c:2
2 int a = 1;
Done
GDB's Python API make it possible to capture and return GDB's output,
but this does not work for all the streams. In particular, CLI
notification events are not captured:
(gdb) python gdb.execute("do-setup", False, True)
[Switching to inferior 2 [<null>] (/tmp/a.out)]
Thread 2.1 "a.out" hit Breakpoint 2, main () at file.c:3
3 return 0;
[Switching to inferior 1 [process 8263] (/tmp/test)]
[Switching to thread 1.1 (process 8263)]
#0 main () at test.c:2
2 int a = 1;
You can use the new "set suppress-cli-notifications" command to
suppress the output:
(gdb) set suppress-cli-notifications on
(gdb) do-setup
Setting up Inferior 2...
[New inferior 2]
Added inferior 2 on connection 1 (native)
Breakpoint 2 at 0x1155: file file.c, line 3.
Done
2022-02-07 15:26:56 +08:00
|
|
|
set suppress-cli-notifications (on|off)
|
|
|
|
|
show suppress-cli-notifications
|
|
|
|
|
This controls whether printing the notifications is suppressed for CLI.
|
|
|
|
|
CLI notifications occur when you change the selected context
|
|
|
|
|
(i.e., the current inferior, thread and/or the frame), or when
|
|
|
|
|
the program being debugged stops (e.g., because of hitting a
|
|
|
|
|
breakpoint, completing source-stepping, an interrupt, etc.).
|
|
|
|
|
|
gdb: use python to colorize disassembler output
This commit adds styling support to the disassembler output, as such
two new commands are added to GDB:
set style disassembler enabled on|off
show style disassembler enabled
In this commit I make use of the Python Pygments package to provide
the styling. I did investigate making use of libsource-highlight,
however, I found the highlighting results to be inferior to those of
Pygments; only some mnemonics were highlighted, and highlighting of
register names such as r9d and r8d (on x86-64) was incorrect.
To enable disassembler highlighting via Pygments, I've added a new
extension language hook, which is then implemented for Python. This
hook is very similar to the existing hook for source code
colorization.
One possibly odd choice I made with the new hook is to pass a
gdb.Architecture through, even though this is currently unused. The
reason this argument is not used is that, currently, styling is
performed identically for all architectures.
However, even though the Python function used to perform styling of
disassembly output is not part of any documented API, I don't want
to close the door on a user overriding this function to provide
architecture specific styling. To do this, the user would inevitably
require access to the gdb.Architecture, and so I decided to add this
field now.
The styling is applied within gdb_disassembler::print_insn, to achieve
this, gdb_disassembler now writes its output into a temporary buffer,
styling is then applied to the contents of this buffer. Finally the
gdb_disassembler buffer is copied out to its final destination stream.
There's a new test to check that the disassembler output includes some
escape sequences, though I don't check for specific colours; the
precise colors will depend on which instructions are in the
disassembler output, and, I guess, how pygments is configured.
The only negative change with this commit is how we currently style
addresses in GDB.
Currently, when the disassembler wants to print an address, we call
back into GDB, and GDB prints the address value using the `address`
styling, and the symbol name using `function` styling. After this
commit, if pygments is used, then all disassembler styling is done
through pygments, and this include the address and symbol name parts
of the disassembler output.
I don't know how much of an issue this will be for people. There's
already some precedent for this in GDB when we look at source styling.
For example, function names in styled source listings are not styled
using the `function` style, but instead, either GNU Source Highlight,
or pygments gets to decide how the function name should be styled.
If the Python pygments library is not present then GDB will continue
to behave as it always has, the disassembler output is mostly
unstyled, but the address and symbols are styled using the `address`
and `function` styles, as they are today.
However, if the user does `set style disassembler enabled off`, then
all disassembler styling is switched off. This obviously covers the
use of pygments, but also includes the minimal styling done by GDB
when pygments is not available.
2021-10-26 00:26:57 +08:00
|
|
|
set style disassembler enabled on|off
|
|
|
|
|
show style disassembler enabled
|
|
|
|
|
If GDB is compiled with Python support, and the Python Pygments
|
|
|
|
|
package is available, then, when this setting is on, disassembler
|
|
|
|
|
output will have styling applied.
|
|
|
|
|
|
Handle non-ASCII identifiers in Ada
Ada allows non-ASCII identifiers, and GNAT supports several such
encodings. This patch adds the corresponding support to gdb.
GNAT encodes non-ASCII characters using special symbol names.
For character sets like Latin-1, where all characters are a single
byte, it uses a "U" followed by the hex for the character. So, for
example, thorn would be encoded as "Ufe" (0xFE being lower case
thorn).
For wider characters, despite what the manual says (it claims
Shift-JIS and EUC can be used), in practice recent versions only
support Unicode. Here, characters in the base plane are represented
using "Wxxxx" and characters outside the base plane using
"WWxxxxxxxx".
GNAT has some further quirks here. Ada is case-insensitive, and GNAT
emits symbols that have been case-folded. For characters in ASCII,
and for all characters in non-Unicode character sets, lower case is
used. For Unicode, however, characters that fit in a single byte are
converted to lower case, but all others are converted to upper case.
Furthermore, there is a bug in GNAT where two symbols that differ only
in the case of "Y WITH DIAERESIS" (and potentially others, I did not
check exhaustively) can be used in one program. I chose to omit
handling this case from gdb, on the theory that it is hard to figure
out the logic, and anyway if the bug is ever fixed, we'll regret
having a heuristic.
This patch introduces a new "ada source-charset" setting. It defaults
to Latin-1, as that is GNAT's default. This setting controls how "U"
characters are decoded -- W/WW are always handled as UTF-32.
The ada_tag_name_from_tsd change is needed because this function will
read memory from the inferior and interpret it -- and this caused an
encoding failure on PPC when running a test that tries to read
uninitialized memory.
This patch implements its own UTF-32-based case folder. This avoids
host platform quirks, and is relatively simple. A short Python
program to generate the case-folding table is included. It simply
relies on whatever version of Unicode is used by the host Python,
which seems basically acceptable.
Test cases for UTF-8, Latin-1, and Latin-3 are included. This
exercises most of the new code paths, aside from Y WITH DIAERESIS as
noted above.
2022-02-04 01:42:07 +08:00
|
|
|
set ada source-charset
|
|
|
|
|
show ada source-charset
|
|
|
|
|
Set the character set encoding that is assumed for Ada symbols. Valid
|
|
|
|
|
values for this follow the values that can be passed to the GNAT
|
|
|
|
|
compiler via the '-gnati' option. The default is ISO-8859-1.
|
|
|
|
|
|
gdb: move some commands into the tui namespace
There are a lot of tui related commands that live in the top-level
command name space, e.g. layout, focus, refresh, winheight.
Having them at the top level means less typing for the user, which is
good, but, I think, makes command discovery harder.
In this commit, I propose moving all of the above mentioned commands
into the tui namespace, so 'layout' becomes 'tui layout', etc. But I
will then add aliases so that the old commands will still work,
e.g. I'll make 'layout' an alias for 'tui layout'.
The benefit I see in this work is that tui related commands can be
more easily discovered by typing 'tui ' and then tab-completing. Also
the "official" command is now a tui-sub-command, this is visible in,
for example, the help output, e.g.:
(gdb) help layout
tui layout, layout
Change the layout of windows.
Usage: tui layout prev | next | LAYOUT-NAME
List of tui layout subcommands:
tui layout asm -- Apply the "asm" layout.
tui layout next -- Apply the next TUI layout.
tui layout prev -- Apply the previous TUI layout.
tui layout regs -- Apply the TUI register layout.
tui layout split -- Apply the "split" layout.
tui layout src -- Apply the "src" layout.
Which I think is a good thing, it makes it clearer that this is a tui
command.
I've added a NEWS entry and updated the docs to mention the new and
old command names, with the new name being mentioned first.
2022-01-25 01:23:20 +08:00
|
|
|
tui layout
|
|
|
|
|
tui focus
|
|
|
|
|
tui refresh
|
|
|
|
|
tui window height
|
|
|
|
|
These are the new names for the old 'layout', 'focus', 'refresh',
|
|
|
|
|
and 'winheight' tui commands respectively. The old names still
|
|
|
|
|
exist as aliases to these new commands.
|
|
|
|
|
|
gdb/tui: add new 'tui window width' command and 'winwidth' alias
This commit adds a new command 'tui window width', and an alias
'winwidth'. This command is equivalent to the old 'winheight'
command (which was recently renamed 'tui window height').
Even though I recently moved the old tui commands under the tui
namespace, and I would strongly encourage all new tui commands to be
added as 'tui ....' only (users can create their own top-level aliases
if they want), I'm breaking that suggestion here, and adding a
'winwidth' alias.
Given that we already have 'winheight' and have done for years, it
just didn't seem right to no have the matching 'winwidth'.
You might notice in the test that the window resizing doesn't quite
work right. I setup a horizontal layout, then grow and shrink the
windows. At the end of the test the windows should be back to their
original size...
... they are not. This isn't my fault, honest! GDB's window resizing
is a little ... temperamental, and is prone to getting things slightly
wrong during resizes, off by 1 type things. This is true for height
resizing, as well as the new width resizing.
Later patches in this series will rework the resizing algorithm, which
should improve things in this area. For now, I'm happy that the width
resizing is as good as the height resizing, given the existing quirks.
For the docs side I include a paragraph that explains how multiple
windows are required before the width can be adjusted. For
completeness, I've added the same paragraph to the winheight
description. With the predefined layouts this extra paragraph is not
really needed for winheight, as there are always multiple windows on
the screen. However, with custom layouts, this might not be true, so
adding the paragraph seems like a good idea.
As for the changes in gdb itself, I've mostly just taken the existing
height adjustment code, changed the name to make it generic 'size'
adjustment, and added a boolean flag to indicate if we are adjusting
the width or the height.
2022-01-25 06:02:59 +08:00
|
|
|
tui window width
|
|
|
|
|
winwidth
|
|
|
|
|
The new command 'tui window width', and the alias 'winwidth' allow
|
|
|
|
|
the width of a tui window to be adjusted when windows are laid out
|
|
|
|
|
in horizontal mode.
|
|
|
|
|
|
gdb/tui: add a tui debugging flag
This commit adds 'set debug tui on|off' and 'show debug tui'. This
commit adds the control variable, and the printing macros in
tui/tui.h. I've then added some uses of these in tui.c and
tui-layout.c.
To help produce more useful debug output in tui-layout.c, I've added
some helper member functions in the class tui_layout_split, and also
moved the size_info struct out of tui_layout_split::apply into the
tui_layout_split class.
If tui debug is not turned on, then there should be no user visible
changes after this commit.
One thing to note is that, due to the way that the tui terminal is
often cleared, the only way I've found this useful is when I do:
(gdb) tui enable
(gdb) set logging file /path/to/file
(gdb) set logging debugredirect on
(gdb) set logging enable on
Additionally, gdb has some quirks when it comes to setting up logging
redirect and switching interpreters. Thus, the above only really
works if the logging is enabled after the tui is enabled, and disabled
again before the tui is disabled.
Enabling logging and switching interpreters can cause undefined
results, including crashes. This is an existing bug in gdb[1], and
has nothing directly to do with tui debug, but it is worth mentioning
here I think.
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=28948
2022-01-27 02:52:56 +08:00
|
|
|
set debug tui on|off
|
|
|
|
|
show debug tui
|
|
|
|
|
Control the display of debug output about GDB's tui.
|
|
|
|
|
|
gdb: make packet_command function available outside remote.c
In a later commit I will add a Python API to access the 'maint packet'
functionality, that is, sending a user specified packet to the target.
To make implementing this easier, this commit refactors how this
command is currently implemented so that the packet_command function
is now global.
The new global send_remote_packet function takes an object that is an
implementation of an abstract interface. Two functions within this
interface are then called, one just before a packet is sent to the
remote target, and one when the reply has been received from the
remote target. Using an interface object in this way allows (1) for
the error checking to be done before the first callback is made, this
means we only print out what packet it being sent once we know we are
going to actually send it, and (2) we don't need to make a copy of the
reply if all we want to do is print it.
One user visible changes after this commit are the error
messages, which I've changed to be less 'maint packet' command
focused, this will make them (I hope) better for when
send_remote_packet can be called from Python code.
So: "command can only be used with remote target"
Becomes: "packets can only be sent to a remote target"
And: "remote-packet command requires packet text as argument"
Becomes: "a remote packet must not be empty"
Additionally, in this commit, I've added support for packet replies
that contain binary data. Before this commit, the code that printed
the reply treated the reply as a C string, it assumed that the string
only contained printable characters, and had a null character only at
the end.
One way to show the problem with this is if we try to read the auxv
data from a remote target, the auxv data is binary, so, before this
commit:
(gdb) target remote :54321
...
(gdb) maint packet qXfer:auxv:read::0,1000
sending: "qXfer:auxv:read::0,1000"
received: "l!"
(gdb)
And after this commit:
(gdb) target remote :54321
...
(gdb) maint packet qXfer:auxv:read::0,1000
sending: "qXfer:auxv:read::0,1000"
received: "l!\x00\x00\x00\x00\x00\x00\x00\x00\xf0\xfc\xf7\xff\x7f\x00\x00\x10\x00\x00\x00\x00\x00\x00\x00\xff\xf>
(gdb)
The binary contents of the reply are now printed as escaped hex.
2021-08-31 21:04:11 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
2022-02-18 04:43:59 +08:00
|
|
|
print
|
|
|
|
|
Printing of floating-point values with base-modifying formats like
|
|
|
|
|
/x has been changed to display the underlying bytes of the value in
|
|
|
|
|
the desired base. This was GDB's documented behavior, but was never
|
|
|
|
|
implemented correctly.
|
|
|
|
|
|
gdb: make packet_command function available outside remote.c
In a later commit I will add a Python API to access the 'maint packet'
functionality, that is, sending a user specified packet to the target.
To make implementing this easier, this commit refactors how this
command is currently implemented so that the packet_command function
is now global.
The new global send_remote_packet function takes an object that is an
implementation of an abstract interface. Two functions within this
interface are then called, one just before a packet is sent to the
remote target, and one when the reply has been received from the
remote target. Using an interface object in this way allows (1) for
the error checking to be done before the first callback is made, this
means we only print out what packet it being sent once we know we are
going to actually send it, and (2) we don't need to make a copy of the
reply if all we want to do is print it.
One user visible changes after this commit are the error
messages, which I've changed to be less 'maint packet' command
focused, this will make them (I hope) better for when
send_remote_packet can be called from Python code.
So: "command can only be used with remote target"
Becomes: "packets can only be sent to a remote target"
And: "remote-packet command requires packet text as argument"
Becomes: "a remote packet must not be empty"
Additionally, in this commit, I've added support for packet replies
that contain binary data. Before this commit, the code that printed
the reply treated the reply as a C string, it assumed that the string
only contained printable characters, and had a null character only at
the end.
One way to show the problem with this is if we try to read the auxv
data from a remote target, the auxv data is binary, so, before this
commit:
(gdb) target remote :54321
...
(gdb) maint packet qXfer:auxv:read::0,1000
sending: "qXfer:auxv:read::0,1000"
received: "l!"
(gdb)
And after this commit:
(gdb) target remote :54321
...
(gdb) maint packet qXfer:auxv:read::0,1000
sending: "qXfer:auxv:read::0,1000"
received: "l!\x00\x00\x00\x00\x00\x00\x00\x00\xf0\xfc\xf7\xff\x7f\x00\x00\x10\x00\x00\x00\x00\x00\x00\x00\xff\xf>
(gdb)
The binary contents of the reply are now printed as escaped hex.
2021-08-31 21:04:11 +08:00
|
|
|
maint packet
|
|
|
|
|
This command can now print a reply, if the reply includes
|
|
|
|
|
non-printable characters. Any non-printable characters are printed
|
|
|
|
|
as escaped hex, e.g. \x?? where '??' is replaces with the value of
|
|
|
|
|
the non-printable character.
|
|
|
|
|
|
2021-12-06 18:23:42 +08:00
|
|
|
clone-inferior
|
|
|
|
|
The clone-inferior command now ensures that the TTY, CMD and ARGS
|
|
|
|
|
settings are copied from the original inferior to the new one.
|
|
|
|
|
All modifications to the environment variables done using the 'set
|
|
|
|
|
environment' or 'unset environment' commands are also copied to the new
|
|
|
|
|
inferior.
|
|
|
|
|
|
2021-12-22 23:33:38 +08:00
|
|
|
set debug lin-lwp on|off
|
|
|
|
|
show debug lin-lwp
|
|
|
|
|
These commands have been removed from GDB. The new command 'set
|
|
|
|
|
debug linux-nat' and 'show debug linux-nat' should be used
|
|
|
|
|
instead.
|
|
|
|
|
|
2022-01-25 05:25:38 +08:00
|
|
|
info win
|
|
|
|
|
This command now includes information about the width of the tui
|
|
|
|
|
windows in its output.
|
|
|
|
|
|
gdb: move some commands into the tui namespace
There are a lot of tui related commands that live in the top-level
command name space, e.g. layout, focus, refresh, winheight.
Having them at the top level means less typing for the user, which is
good, but, I think, makes command discovery harder.
In this commit, I propose moving all of the above mentioned commands
into the tui namespace, so 'layout' becomes 'tui layout', etc. But I
will then add aliases so that the old commands will still work,
e.g. I'll make 'layout' an alias for 'tui layout'.
The benefit I see in this work is that tui related commands can be
more easily discovered by typing 'tui ' and then tab-completing. Also
the "official" command is now a tui-sub-command, this is visible in,
for example, the help output, e.g.:
(gdb) help layout
tui layout, layout
Change the layout of windows.
Usage: tui layout prev | next | LAYOUT-NAME
List of tui layout subcommands:
tui layout asm -- Apply the "asm" layout.
tui layout next -- Apply the next TUI layout.
tui layout prev -- Apply the previous TUI layout.
tui layout regs -- Apply the TUI register layout.
tui layout split -- Apply the "split" layout.
tui layout src -- Apply the "src" layout.
Which I think is a good thing, it makes it clearer that this is a tui
command.
I've added a NEWS entry and updated the docs to mention the new and
old command names, with the new name being mentioned first.
2022-01-25 01:23:20 +08:00
|
|
|
layout
|
|
|
|
|
focus
|
|
|
|
|
refresh
|
|
|
|
|
winheight
|
|
|
|
|
These commands are now aliases for the 'tui layout', 'tui focus',
|
|
|
|
|
'tui refresh', and 'tui window height' commands respectively.
|
|
|
|
|
|
2022-02-17 01:07:18 +08:00
|
|
|
* GDB's Ada parser now supports an extension for specifying the exact
|
|
|
|
|
byte contents of a floating-point literal. This can be useful for
|
|
|
|
|
setting floating-point registers to a precise value without loss of
|
|
|
|
|
precision. The syntax is an extension of the based literal syntax.
|
|
|
|
|
Use, e.g., "16lf#0123abcd#" -- the number of "l"s controls the width
|
|
|
|
|
of the floating-point type, and the "f" is the marker for floating
|
|
|
|
|
point.
|
|
|
|
|
|
2022-02-25 01:25:51 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** The '-add-inferior' with no option flags now inherits the
|
|
|
|
|
connection of the current inferior, this restores the behaviour of
|
|
|
|
|
GDB as it was prior to GDB 10.
|
|
|
|
|
|
2022-03-02 19:11:47 +08:00
|
|
|
** The '-add-inferior' command now accepts a '--no-connection'
|
|
|
|
|
option, which causes the new inferior to start without a
|
|
|
|
|
connection.
|
|
|
|
|
|
gdb/mi: fix breakpoint script field output
The "script" field, output whenever information about a breakpoint with
commands is output, uses wrong MI syntax.
$ ./gdb -nx -q --data-directory=data-directory -x script -i mi
=thread-group-added,id="i1"
=breakpoint-created,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x000000000000111d",func="main",file="test.c",fullname="/home/simark/build/binutils-gdb-one-target/gdb/test.c",line="3",thread-groups=["i1"],times="0",original-location="main"}
=breakpoint-modified,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x000000000000111d",func="main",file="test.c",fullname="/home/simark/build/binutils-gdb-one-target/gdb/test.c",line="3",thread-groups=["i1"],times="0",script={"aaa","bbb","ccc"},original-location="main"}
(gdb)
-break-info
^done,BreakpointTable={nr_rows="1",nr_cols="6",hdr=[{width="7",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="18",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x000000000000111d",func="main",file="test.c",fullname="/home/simark/build/binutils-gdb-one-target/gdb/test.c",line="3",thread-groups=["i1"],times="0",script={"aaa","bbb","ccc"},original-location="main"}]}
(gdb)
In both the =breakpoint-modified and -break-info output, we have:
script={"aaa","bbb","ccc"}
According to the output syntax [1], curly braces means tuple, and a
tuple contains key=value pairs. This looks like it should be a list,
but uses curly braces by mistake. This would make more sense:
script=["aaa","bbb","ccc"]
Fix it, keeping the backwards compatibility by introducing a new MI
version (MI4), in exactly the same way as was done when fixing
multi-locations breakpoint output in [2].
- Add a fix_breakpoint_script_output uiout flag. MI uiouts will use
this flag if the version is >= 4.
- Add a fix_breakpoint_script_output_globally variable and the
-fix-breakpoint-script-output MI command to set it, if frontends want
to use the fixed output for this without using the newer MI version.
- When emitting the script field, use list instead of tuple, if we want
the fixed output (depending on the two criteria above)
-
[1] https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GDB_002fMI-Output-Syntax
[2] https://gitlab.com/gnutools/binutils-gdb/-/commit/b4be1b0648608a2578bbed39841c8ee411773edd
Change-Id: I7113c6892832c8d6805badb06ce42496677e2242
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=24285
2022-08-11 03:38:19 +08:00
|
|
|
** The default version of the MI interpreter is now 4 (-i=mi4).
|
|
|
|
|
|
|
|
|
|
** The "script" field in breakpoint output (which is syntactically
|
|
|
|
|
incorrect in MI 3 and below) has changed in MI 4 to become a list.
|
|
|
|
|
This affects the following commands and events:
|
|
|
|
|
|
|
|
|
|
- -break-insert
|
|
|
|
|
- -break-info
|
|
|
|
|
- =breakpoint-created
|
|
|
|
|
- =breakpoint-modified
|
|
|
|
|
|
|
|
|
|
The -fix-breakpoint-script-output command can be used to enable
|
|
|
|
|
this behavior with previous MI versions.
|
|
|
|
|
|
2022-02-11 20:17:56 +08:00
|
|
|
* New targets
|
|
|
|
|
|
2022-03-16 21:39:17 +08:00
|
|
|
GNU/Linux/LoongArch loongarch*-*-linux*
|
|
|
|
|
|
|
|
|
|
* Removed targets
|
|
|
|
|
|
|
|
|
|
S+core score-*-*
|
2022-02-11 20:17:56 +08:00
|
|
|
|
2021-07-30 19:56:34 +08:00
|
|
|
* Python API
|
|
|
|
|
|
|
|
|
|
** New function gdb.add_history(), which takes a gdb.Value object
|
|
|
|
|
and adds the value it represents to GDB's history list. An
|
|
|
|
|
integer, the index of the new item in the history list, is
|
|
|
|
|
returned.
|
|
|
|
|
|
2022-01-24 23:19:43 +08:00
|
|
|
** New function gdb.history_count(), which returns the number of
|
|
|
|
|
values in GDB's value history.
|
|
|
|
|
|
gdb/python: add a new gdb_exiting event
Add a new event, gdb.events.gdb_exiting, which is called once GDB
decides it is going to exit.
This event is not triggered in the case that GDB performs a hard
abort, for example, when handling an internal error and the user
decides to quit the debug session, or if GDB hits an unexpected,
fatal, signal.
This event is triggered if the user just types 'quit' at the command
prompt, or if GDB is run with '-batch' and has processed all of the
required commands.
The new event type is gdb.GdbExitingEvent, and it has a single
attribute exit_code, which is the value that GDB is about to exit
with.
The event is triggered before GDB starts dismantling any of its own
internal state, so, my expectation is that most Python calls should
work just fine at this point.
When considering this functionality I wondered about using the
'atexit' Python module. However, this is triggered when the Python
environment is shut down, which is done from a final cleanup. At
this point we don't know for sure what other GDB state has already
been cleaned up.
2021-09-07 18:45:55 +08:00
|
|
|
** New gdb.events.gdb_exiting event. This event is called with a
|
|
|
|
|
gdb.GdbExitingEvent object which has the read-only attribute
|
|
|
|
|
'exit_code', which contains the value of the GDB exit code. This
|
|
|
|
|
event is triggered once GDB decides it is going to exit, but
|
|
|
|
|
before GDB starts to clean up its internal state.
|
|
|
|
|
|
2021-09-15 20:34:14 +08:00
|
|
|
** New function gdb.architecture_names(), which returns a list
|
|
|
|
|
containing all of the possible Architecture.name() values. Each
|
|
|
|
|
entry is a string.
|
|
|
|
|
|
2021-10-23 00:49:19 +08:00
|
|
|
** New function gdb.Architecture.integer_type(), which returns an
|
|
|
|
|
integer type given a size and a signed-ness.
|
|
|
|
|
|
gdb/python: introduce gdb.TargetConnection object type
This commit adds a new object type gdb.TargetConnection. This new
type represents a connection within GDB (a connection as displayed by
'info connections').
There's three ways to find a gdb.TargetConnection, there's a new
'gdb.connections()' function, which returns a list of all currently
active connections.
Or you can read the new 'connection' property on the gdb.Inferior
object type, this contains the connection for that inferior (or None
if the inferior has no connection, for example, it is exited).
Finally, there's a new gdb.events.connection_removed event registry,
this emits a new gdb.ConnectionEvent whenever a connection is removed
from GDB (this can happen when all inferiors using a connection exit,
though this is not always the case, depending on the connection type).
The gdb.ConnectionEvent has a 'connection' property, which is the
gdb.TargetConnection being removed from GDB.
The gdb.TargetConnection has an 'is_valid()' method. A connection
object becomes invalid when the underlying connection is removed from
GDB (as discussed above, this might be when all inferiors using a
connection exit, or it might be when the user explicitly replaces a
connection in GDB by issuing another 'target' command).
The gdb.TargetConnection has the following read-only properties:
'num': The number for this connection,
'type': e.g. 'native', 'remote', 'sim', etc
'description': The longer description as seen in the 'info
connections' command output.
'details': A string or None. Extra details for the connection, for
example, a remote connection's details might be
'hostname:port'.
2021-09-01 22:33:19 +08:00
|
|
|
** New gdb.TargetConnection object type that represents a connection
|
2021-08-31 21:04:36 +08:00
|
|
|
(as displayed by the 'info connections' command). A sub-class,
|
|
|
|
|
gdb.RemoteTargetConnection, is used to represent 'remote' and
|
|
|
|
|
'extended-remote' connections.
|
gdb/python: introduce gdb.TargetConnection object type
This commit adds a new object type gdb.TargetConnection. This new
type represents a connection within GDB (a connection as displayed by
'info connections').
There's three ways to find a gdb.TargetConnection, there's a new
'gdb.connections()' function, which returns a list of all currently
active connections.
Or you can read the new 'connection' property on the gdb.Inferior
object type, this contains the connection for that inferior (or None
if the inferior has no connection, for example, it is exited).
Finally, there's a new gdb.events.connection_removed event registry,
this emits a new gdb.ConnectionEvent whenever a connection is removed
from GDB (this can happen when all inferiors using a connection exit,
though this is not always the case, depending on the connection type).
The gdb.ConnectionEvent has a 'connection' property, which is the
gdb.TargetConnection being removed from GDB.
The gdb.TargetConnection has an 'is_valid()' method. A connection
object becomes invalid when the underlying connection is removed from
GDB (as discussed above, this might be when all inferiors using a
connection exit, or it might be when the user explicitly replaces a
connection in GDB by issuing another 'target' command).
The gdb.TargetConnection has the following read-only properties:
'num': The number for this connection,
'type': e.g. 'native', 'remote', 'sim', etc
'description': The longer description as seen in the 'info
connections' command output.
'details': A string or None. Extra details for the connection, for
example, a remote connection's details might be
'hostname:port'.
2021-09-01 22:33:19 +08:00
|
|
|
|
|
|
|
|
** The gdb.Inferior type now has a 'connection' property which is an
|
|
|
|
|
instance of gdb.TargetConnection, the connection used by this
|
|
|
|
|
inferior. This can be None if the inferior has no connection.
|
|
|
|
|
|
|
|
|
|
** New 'gdb.events.connection_removed' event registry, which emits a
|
|
|
|
|
'gdb.ConnectionEvent' when a connection is removed from GDB.
|
|
|
|
|
This event has a 'connection' property, a gdb.TargetConnection
|
|
|
|
|
object for the connection being removed.
|
|
|
|
|
|
|
|
|
|
** New gdb.connections() function that returns a list of all
|
|
|
|
|
currently active connections.
|
|
|
|
|
|
2021-08-31 21:04:36 +08:00
|
|
|
** New gdb.RemoteTargetConnection.send_packet(PACKET) method. This
|
|
|
|
|
is equivalent to the existing 'maint packet' CLI command; it
|
|
|
|
|
allows a user specified packet to be sent to the remote target.
|
|
|
|
|
|
2022-01-12 19:52:19 +08:00
|
|
|
** New function gdb.host_charset(), returns a string, which is the
|
|
|
|
|
name of the current host charset.
|
|
|
|
|
|
2022-01-05 02:00:52 +08:00
|
|
|
** New gdb.set_parameter(NAME, VALUE). This sets the gdb parameter
|
|
|
|
|
NAME to VALUE.
|
|
|
|
|
|
|
|
|
|
** New gdb.with_parameter(NAME, VALUE). This returns a context
|
|
|
|
|
manager that temporarily sets the gdb parameter NAME to VALUE,
|
|
|
|
|
then resets it when the context is exited.
|
|
|
|
|
|
2022-01-24 23:29:49 +08:00
|
|
|
** The gdb.Value.format_string method now takes a 'styling'
|
|
|
|
|
argument, which is a boolean. When true, the returned string can
|
|
|
|
|
include escape sequences to apply styling. The styling will only
|
|
|
|
|
be present if styling is otherwise turned on in GDB (see 'help
|
|
|
|
|
set styling'). When false, which is the default if the argument
|
|
|
|
|
is not given, then no styling is applied to the returned string.
|
|
|
|
|
|
gdb/python: Add gdb.InferiorThread.details attribute
This adds a new read-only attribute gdb.InferiorThread.details, this
attribute contains a string, the results of target_extra_thread_info
for the thread, or None, if target_extra_thread_info returns nullptr.
As the string returned by target_extra_thread_info is unstructured,
this attribute is only really useful for echoing straight through to
the user, but, if a user wants to write a command that displays the
same, or a similar 'Thread Id' to the one seen in 'info threads', then
they need access to this string.
Given that the string produced by target_extra_thread_info varies by
target, there's only minimal testing of this attribute, I check that
the attribute can be accessed, and that the return value is either
None, or a string.
2022-02-15 01:02:03 +08:00
|
|
|
** New read-only attribute gdb.InferiorThread.details, which is
|
|
|
|
|
either a string, containing additional, target specific thread
|
|
|
|
|
state information, or None, if there is no such additional
|
|
|
|
|
information.
|
|
|
|
|
|
2022-02-25 18:54:04 +08:00
|
|
|
** New read-only attribute gdb.Type.is_scalar, which is True for
|
|
|
|
|
scalar types, and False for all other types.
|
|
|
|
|
|
2021-11-30 22:35:44 +08:00
|
|
|
** New read-only attribute gdb.Type.is_signed. This attribute
|
|
|
|
|
should only be read when Type.is_scalar is True, and will be True
|
|
|
|
|
for signed types, and False for all other types. Attempting to
|
|
|
|
|
read this attribute for non-scalar types will raise a ValueError.
|
|
|
|
|
|
gdb/python/mi: create MI commands using python
This commit allows a user to create custom MI commands using Python
similarly to what is possible for Python CLI commands.
A new subclass of mi_command is defined for Python MI commands,
mi_command_py. A new file, gdb/python/py-micmd.c contains the logic
for Python MI commands.
This commit is based on work linked too from this mailing list thread:
https://sourceware.org/pipermail/gdb/2021-November/049774.html
Which has also been previously posted to the mailing list here:
https://sourceware.org/pipermail/gdb-patches/2019-May/158010.html
And was recently reposted here:
https://sourceware.org/pipermail/gdb-patches/2022-January/185190.html
The version in this patch takes some core code from the previously
posted patches, but also has some significant differences, especially
after the feedback given here:
https://sourceware.org/pipermail/gdb-patches/2022-February/185767.html
A new MI command can be implemented in Python like this:
class echo_args(gdb.MICommand):
def invoke(self, args):
return { 'args': args }
echo_args("-echo-args")
The 'args' parameter (to the invoke method) is a list
containing (almost) all command line arguments passed to the MI
command (--thread and --frame are handled before the Python code is
called, and removed from the args list). This list can be empty if
the MI command was passed no arguments.
When used within gdb the above command produced output like this:
(gdb)
-echo-args a b c
^done,args=["a","b","c"]
(gdb)
The 'invoke' method of the new command must return a dictionary. The
keys of this dictionary are then used as the field names in the mi
command output (e.g. 'args' in the above).
The values of the result returned by invoke can be dictionaries,
lists, iterators, or an object that can be converted to a string.
These are processed recursively to create the mi output. And so, this
is valid:
class new_command(gdb.MICommand):
def invoke(self,args):
return { 'result_one': { 'abc': 123, 'def': 'Hello' },
'result_two': [ { 'a': 1, 'b': 2 },
{ 'c': 3, 'd': 4 } ] }
Which produces output like:
(gdb)
-new-command
^done,result_one={abc="123",def="Hello"},result_two=[{a="1",b="2"},{c="3",d="4"}]
(gdb)
I have required that the fields names used in mi result output must
match the regexp: "^[a-zA-Z][-_a-zA-Z0-9]*$" (without the quotes).
This restriction was never written down anywhere before, but seems
sensible to me, and we can always loosen this rule later if it proves
to be a problem. Much harder to try and add a restriction later, once
people are already using the API.
What follows are some details about how this implementation differs
from the original patch that was posted to the mailing list.
In this patch, I have changed how the lifetime of the Python
gdb.MICommand objects is managed. In the original patch, these object
were kept alive by an owned reference within the mi_command_py object.
As such, the Python object would not be deleted until the
mi_command_py object itself was deleted.
This caused a problem, the mi_command_py were held in the global mi
command table (in mi/mi-cmds.c), which, as a global, was not cleared
until program shutdown. By this point the Python interpreter has
already been shutdown. Attempting to delete the mi_command_py object
at this point was causing GDB to try and invoke Python code after
finalising the Python interpreter, and we would crash.
To work around this problem, the original patch added code in
python/python.c that would search the mi command table, and delete the
mi_command_py objects before the Python environment was finalised.
In contrast, in this patch, I have added a new global dictionary to
the gdb module, gdb._mi_commands. We already have several such global
data stores related to pretty printers, and frame unwinders.
The MICommand objects are placed into the new gdb.mi_commands
dictionary, and it is this reference that keeps the objects alive.
When GDB's Python interpreter is shut down gdb._mi_commands is deleted,
and any MICommand objects within it are deleted at this point.
This change avoids having to make the mi_cmd_table global, and walk
over it from within GDB's python related code.
This patch handles command redefinition entirely within GDB's python
code, though this does impose one small restriction which is not
present in the original code (detailed below), I don't think this is a
big issue. However, the original patch relied on being able to
finish executing the mi_command::do_invoke member function after the
mi_command object had been deleted. Though continuing to execute a
member function after an object is deleted is well defined, it is
also (IMHO) risky, its too easy for someone to later add a use of the
object without realising that the object might sometimes, have been
deleted. The new patch avoids this issue.
The one restriction that is added to avoid this, is that an MICommand
object can't be reinitialised with a different command name, so:
(gdb) python cmd = MyMICommand("-abc")
(gdb) python cmd.__init__("-def")
can't reinitialize object with a different command name
This feels like a pretty weird edge case, and I'm happy to live with
this restriction.
I have also changed how the memory is managed for the command name.
In the most recently posted patch series, the command name is moved
into a subclass of mi_command, the python mi_command_py, which
inherits from mi_command is then free to use a smart pointer to manage
the memory for the name.
In this patch, I leave the mi_command class unchanged, and instead
hold the memory for the name within the Python object, as the lifetime
of the Python object always exceeds the c++ object stored in the
mi_cmd_table. This adds a little more complexity in py-micmd.c, but
leaves the mi_command class nice and simple.
Next, this patch adds some extra functionality, there's a
MICommand.name read-only attribute containing the name of the command,
and a read-write MICommand.installed attribute that can be used to
install (make the command available for use) and uninstall (remove the
command from the mi_cmd_table so it can't be used) the command. This
attribute will be automatically updated if a second command replaces
an earlier command.
This patch adds additional error handling, and makes more use the
gdbpy_handle_exception function.
Co-Authored-By: Jan Vrany <jan.vrany@labware.com>
2020-06-23 21:45:38 +08:00
|
|
|
** It is now possible to add GDB/MI commands implemented in Python.
|
|
|
|
|
|
2021-10-29 04:52:28 +08:00
|
|
|
* New features in the GDB remote stub, GDBserver
|
|
|
|
|
|
|
|
|
|
** GDBserver is now supported on OpenRISC GNU/Linux.
|
|
|
|
|
|
|
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
GNU/Linux/OpenRISC or1k*-*-linux*
|
|
|
|
|
|
2021-07-04 01:52:20 +08:00
|
|
|
*** Changes in GDB 11
|
2020-09-13 10:43:47 +08:00
|
|
|
|
2021-05-06 05:07:38 +08:00
|
|
|
* The 'set disassembler-options' command now supports specifying options
|
|
|
|
|
for the ARC target.
|
|
|
|
|
|
2020-06-16 02:54:00 +08:00
|
|
|
* GDB now supports general memory tagging functionality if the underlying
|
|
|
|
|
architecture supports the proper primitives and hooks. Currently this is
|
|
|
|
|
enabled only for AArch64 MTE.
|
|
|
|
|
|
|
|
|
|
This includes:
|
|
|
|
|
|
|
|
|
|
- Additional information when the inferior crashes with a SIGSEGV caused by
|
|
|
|
|
a memory tag violation.
|
|
|
|
|
|
|
|
|
|
- A new modifier 'm' for the "x" command, which displays allocation tags for a
|
|
|
|
|
particular memory range.
|
|
|
|
|
|
|
|
|
|
- Display of memory tag mismatches by "print", for addresses and
|
|
|
|
|
pointers, if memory tagging is supported by the architecture.
|
|
|
|
|
|
2020-11-24 11:08:05 +08:00
|
|
|
* Building GDB now requires GMP (The GNU Multiple Precision Arithmetic
|
|
|
|
|
Library).
|
|
|
|
|
|
Add MI "-break-insert --qualified"
Currently -break-insert always creates a wildmatching breakpoint, and
there's no way to ask for a fullname match. To address that, this
patch adds the equivalent of "break -qualified" to MI:
"-break-insert --qualified".
For the testcase, curiously, it doesn't look like we have _any_
testcase that tests a breakpoint with multiple locations, and, the
existing mi_create_breakpoint / mi_make_breakpoint procedures are only
good for breakpoints with a single location. This patch thus adds a
few new companion routines to mi-support.exp for breakpoints with
multiple locations: mi_create_breakpoint_multi,
mi_make_breakpoint_loc, mi_make_breakpoint_multi.
gdb/ChangeLog:
* NEWS: Document "-break-insert --qualified".
* mi/mi-cmd-break.c (mi_cmd_break_insert_1): Handle "--qualified".
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI Breakpoint Commands): Document
"-break-insert --qualified" and "-dprintf-insert --qualified".
gdb/testsuite/ChangeLog:
* gdb.mi/mi-break-qualified.cc: New file.
* gdb.mi/mi-break-qualified.exp: New file.
* lib/mi-support.exp (mi_create_breakpoint_multi)
(mi_make_breakpoint_loc, mi_make_breakpoint_multi): New
procedures.
(mi_create_breakpoint_1): New, factored out from
mi_create_breakpoint.
2020-09-14 01:02:19 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** '-break-insert --qualified' and '-dprintf-insert --qualified'
|
|
|
|
|
|
|
|
|
|
The MI -break-insert and -dprintf-insert commands now support a
|
|
|
|
|
new "--qualified" option that makes GDB interpret a specified
|
|
|
|
|
function name as a complete fully-qualified name. This is the
|
|
|
|
|
equivalent of the CLI's "break -qualified" and "dprintf
|
|
|
|
|
-qualified".
|
|
|
|
|
|
2021-05-06 16:13:06 +08:00
|
|
|
** '-break-insert --force-condition' and '-dprintf-insert --force-condition'
|
|
|
|
|
|
|
|
|
|
The MI -break-insert and -dprintf-insert commands now support a
|
|
|
|
|
'--force-condition' flag to forcibly define a condition even when
|
|
|
|
|
the condition is invalid at all locations of the breakpoint. This
|
|
|
|
|
is equivalent to the '-force-condition' flag of the CLI's "break"
|
|
|
|
|
command.
|
|
|
|
|
|
2021-05-06 16:13:06 +08:00
|
|
|
** '-break-condition --force'
|
|
|
|
|
|
|
|
|
|
The MI -break-condition command now supports a '--force' flag to
|
|
|
|
|
forcibly define a condition even when the condition is invalid at
|
|
|
|
|
all locations of the selected breakpoint. This is equivalent to
|
|
|
|
|
the '-force' flag of the CLI's "cond" command.
|
|
|
|
|
|
gdb/mi: add new --group-by-objfile flag for -file-list-exec-source-files
This commit adds a new option '--group-by-objfile' to the MI command
-file-list-exec-source-files. With this option the output format is
changed; instead of a single list of source files the results are now
a list of objfiles. For each objfile all of the source files
associated with that objfile are listed.
Here is an example of the new output format taken from the
documentation (the newlines are added just for readability):
-file-list-exec-source-files --group-by-objfile
^done,files=[{filename="/tmp/info-sources/test.x",
debug-info="fully-read",
sources=[{file="test.c",
fullname="/tmp/info-sources/test.c",
debug-fully-read="true"},
{file="/usr/include/stdc-predef.h",
fullname="/usr/include/stdc-predef.h",
debug-fully-read="true"},
{file="header.h",
fullname="/tmp/info-sources/header.h",
debug-fully-read="true"}]},
{filename="/lib64/ld-linux-x86-64.so.2",
debug-info="none",
sources=[]},
{filename="system-supplied DSO at 0x7ffff7fcf000",
debug-info="none",
sources=[]},
{filename="/tmp/info-sources/libhelper.so",
debug-info="fully-read",
sources=[{file="helper.c",
fullname="/tmp/info-sources/helper.c",
debug-fully-read="true"},
{file="/usr/include/stdc-predef.h",
fullname="/usr/include/stdc-predef.h",
debug-fully-read="true"},
{file="header.h",
fullname="/tmp/info-sources/header.h",
debug-fully-read="true"}]},
{filename="/lib64/libc.so.6",
debug-info="none",
sources=[]}]
In the above output the 'debug-info' field associated with each
objfile will have one of the values 'none', 'partially-read', or
'fully-read'. For example, /lib64/libc.so.6 has the value 'none',
this indicates that this object file has no debug information
associated with it, unsurprisingly then, the sources list of this
object file is empty.
An object file that was compiled with debug, for example
/tmp/info-sources/libhelper.so, has the value 'fully-read' above
indicating that this object file does have debug information, and the
information is fully read into GDB. At different times this field
might have the value 'partially-read' indicating that that the object
file has debug information, but it has not been fully read into GDB
yet.
Source files can appear at most once for any single objfile, but can
appear multiple times in total, if the same source file is part of
multiple objfiles, for example /tmp/info-sources/header.h in the above
output.
The new output format is hidden behind a command option to ensure that
the default output is unchanged, this ensures backward compatibility.
The behaviour of the CLI "info sources" command is unchanged after
this commit.
gdb/ChangeLog:
* NEWS: Mention additions to -file-list-exec-source-files.
* mi/mi-cmd-file.c (mi_cmd_file_list_exec_source_files): Add
--group-by-objfile option.
* symtab.c (isrc_flag_option_def): Rename to...
(isrc_match_flag_option_def): ...this.
(info_sources_option_defs): Rename to...
(info_sources_match_option_defs): ...this, and update to rename of
isrc_flag_option_def.
(struct filename_grouping_opts): New struct.
(isrc_grouping_flag_option_def): New type.
(info_sources_grouping_option_defs): New static global.
(make_info_sources_options_def_group): Update to return two option
groups.
(info_sources_command_completer): Update for changes to
make_info_sources_options_def_group.
(info_sources_worker): Add extra parameter, use this to display
alternative output format.
(info_sources_command): Pass extra parameter to
info_sources_worker.
(_initialize_symtab): Update for changes to
make_info_sources_options_def_group.
* symtab.h (info_sources_worker): Add extra parameter.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI File Commands): Document --group-by-objfile
extension for -file-list-exec-source-files.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-info-sources.exp: Add additional tests.
2021-05-18 21:18:22 +08:00
|
|
|
** '-file-list-exec-source-files [--group-by-objfile]
|
|
|
|
|
[--basename | --dirname]
|
|
|
|
|
[--] [REGEXP]'
|
gdb/mi: add regexp filtering to -file-list-exec-source-files
This commit extends the existing MI command
-file-list-exec-source-files to provide the same regular expression
based filtering that the equivalent CLI command "info sources"
provides.
The new command syntax is:
-file-list-exec-source-files [--basename | --dirname] [--] [REGEXP]
All options are optional, which ensures the command is backward
compatible.
As part of this work I have unified the CLI and MI code.
As a result of the unified code I now provide additional information
in the MI command output, there is now a new field 'debug-fully-read'
included with each source file. This field which has the values
'true' or 'false', indicates if the source file is from a compilation
unit that has had its debug information fully read. However, as this
is additional information, a well written front-end should just ignore
this field if it doesn't understand it, so things should still be
backward compatible.
gdb/ChangeLog:
* NEWS: Mention additions to -file-list-exec-source-files.
* mi/mi-cmd-file.c (print_partial_file_name): Delete.
(mi_cmd_file_list_exec_source_files): Rewrite to handle command
options, and make use of info_sources_worker.
* symtab.c (struct info_sources_filter): Moved to symtab.h.
(info_sources_filter::print): Take uiout argument, produce output
through uiout.
(struct output_source_filename_data)
<output_source_filename_data>: Take uiout argument, store into
m_uiout. <output>: Rewrite comment, add additional arguments to
declaration. <operator()>: Send more arguments to
output. <m_uiout>: New member variable.
(output_source_filename_data::output): Take extra arguments,
produce output through m_uiout, and structure for MI.
(output_source_filename_data::print_header): Produce output
through m_uiout.
(info_sources_worker): New function, the implementation is taken
from info_sources_command, but modified so produce output through
a ui_out.
(info_sources_command): The second half of this function has gone
to become info_sources_worker.
* symtab.h (struct info_sources_filter): Moved from symtab.c, add
extra parameter to print member function.
(info_sources_worker): Declare.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI File Commands): Document extensions to
-file-list-exec-source-files.
gdb/testsuite/ChangeLog:
* gdb.dwarf2/dw2-filename.exp: Update expected results.
* gdb.mi/mi-file.exp: Likewise.
* gdb.mi/mi-info-sources-base.c: New file.
* gdb.mi/mi-info-sources.c: New file.
* gdb.mi/mi-info-sources.exp: New file.
2021-05-18 20:46:19 +08:00
|
|
|
|
|
|
|
|
The existing -file-list-exec-source-files command now takes an
|
|
|
|
|
optional REGEXP which is used to filter the source files that are
|
|
|
|
|
included in the results.
|
|
|
|
|
|
|
|
|
|
By default REGEXP is matched against the full filename of the
|
|
|
|
|
source file. When one of --basename or --dirname is given then
|
|
|
|
|
REGEXP is only matched against the specified part of the full
|
|
|
|
|
source filename.
|
|
|
|
|
|
gdb/mi: add new --group-by-objfile flag for -file-list-exec-source-files
This commit adds a new option '--group-by-objfile' to the MI command
-file-list-exec-source-files. With this option the output format is
changed; instead of a single list of source files the results are now
a list of objfiles. For each objfile all of the source files
associated with that objfile are listed.
Here is an example of the new output format taken from the
documentation (the newlines are added just for readability):
-file-list-exec-source-files --group-by-objfile
^done,files=[{filename="/tmp/info-sources/test.x",
debug-info="fully-read",
sources=[{file="test.c",
fullname="/tmp/info-sources/test.c",
debug-fully-read="true"},
{file="/usr/include/stdc-predef.h",
fullname="/usr/include/stdc-predef.h",
debug-fully-read="true"},
{file="header.h",
fullname="/tmp/info-sources/header.h",
debug-fully-read="true"}]},
{filename="/lib64/ld-linux-x86-64.so.2",
debug-info="none",
sources=[]},
{filename="system-supplied DSO at 0x7ffff7fcf000",
debug-info="none",
sources=[]},
{filename="/tmp/info-sources/libhelper.so",
debug-info="fully-read",
sources=[{file="helper.c",
fullname="/tmp/info-sources/helper.c",
debug-fully-read="true"},
{file="/usr/include/stdc-predef.h",
fullname="/usr/include/stdc-predef.h",
debug-fully-read="true"},
{file="header.h",
fullname="/tmp/info-sources/header.h",
debug-fully-read="true"}]},
{filename="/lib64/libc.so.6",
debug-info="none",
sources=[]}]
In the above output the 'debug-info' field associated with each
objfile will have one of the values 'none', 'partially-read', or
'fully-read'. For example, /lib64/libc.so.6 has the value 'none',
this indicates that this object file has no debug information
associated with it, unsurprisingly then, the sources list of this
object file is empty.
An object file that was compiled with debug, for example
/tmp/info-sources/libhelper.so, has the value 'fully-read' above
indicating that this object file does have debug information, and the
information is fully read into GDB. At different times this field
might have the value 'partially-read' indicating that that the object
file has debug information, but it has not been fully read into GDB
yet.
Source files can appear at most once for any single objfile, but can
appear multiple times in total, if the same source file is part of
multiple objfiles, for example /tmp/info-sources/header.h in the above
output.
The new output format is hidden behind a command option to ensure that
the default output is unchanged, this ensures backward compatibility.
The behaviour of the CLI "info sources" command is unchanged after
this commit.
gdb/ChangeLog:
* NEWS: Mention additions to -file-list-exec-source-files.
* mi/mi-cmd-file.c (mi_cmd_file_list_exec_source_files): Add
--group-by-objfile option.
* symtab.c (isrc_flag_option_def): Rename to...
(isrc_match_flag_option_def): ...this.
(info_sources_option_defs): Rename to...
(info_sources_match_option_defs): ...this, and update to rename of
isrc_flag_option_def.
(struct filename_grouping_opts): New struct.
(isrc_grouping_flag_option_def): New type.
(info_sources_grouping_option_defs): New static global.
(make_info_sources_options_def_group): Update to return two option
groups.
(info_sources_command_completer): Update for changes to
make_info_sources_options_def_group.
(info_sources_worker): Add extra parameter, use this to display
alternative output format.
(info_sources_command): Pass extra parameter to
info_sources_worker.
(_initialize_symtab): Update for changes to
make_info_sources_options_def_group.
* symtab.h (info_sources_worker): Add extra parameter.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI File Commands): Document --group-by-objfile
extension for -file-list-exec-source-files.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-info-sources.exp: Add additional tests.
2021-05-18 21:18:22 +08:00
|
|
|
When the optional --group-by-objfile flag is used the output
|
|
|
|
|
format is changed, the results are now a list of object files
|
|
|
|
|
(executable and libraries) with the source files that are
|
|
|
|
|
associated with each object file.
|
|
|
|
|
|
gdb/mi: add regexp filtering to -file-list-exec-source-files
This commit extends the existing MI command
-file-list-exec-source-files to provide the same regular expression
based filtering that the equivalent CLI command "info sources"
provides.
The new command syntax is:
-file-list-exec-source-files [--basename | --dirname] [--] [REGEXP]
All options are optional, which ensures the command is backward
compatible.
As part of this work I have unified the CLI and MI code.
As a result of the unified code I now provide additional information
in the MI command output, there is now a new field 'debug-fully-read'
included with each source file. This field which has the values
'true' or 'false', indicates if the source file is from a compilation
unit that has had its debug information fully read. However, as this
is additional information, a well written front-end should just ignore
this field if it doesn't understand it, so things should still be
backward compatible.
gdb/ChangeLog:
* NEWS: Mention additions to -file-list-exec-source-files.
* mi/mi-cmd-file.c (print_partial_file_name): Delete.
(mi_cmd_file_list_exec_source_files): Rewrite to handle command
options, and make use of info_sources_worker.
* symtab.c (struct info_sources_filter): Moved to symtab.h.
(info_sources_filter::print): Take uiout argument, produce output
through uiout.
(struct output_source_filename_data)
<output_source_filename_data>: Take uiout argument, store into
m_uiout. <output>: Rewrite comment, add additional arguments to
declaration. <operator()>: Send more arguments to
output. <m_uiout>: New member variable.
(output_source_filename_data::output): Take extra arguments,
produce output through m_uiout, and structure for MI.
(output_source_filename_data::print_header): Produce output
through m_uiout.
(info_sources_worker): New function, the implementation is taken
from info_sources_command, but modified so produce output through
a ui_out.
(info_sources_command): The second half of this function has gone
to become info_sources_worker.
* symtab.h (struct info_sources_filter): Moved from symtab.c, add
extra parameter to print member function.
(info_sources_worker): Declare.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI File Commands): Document extensions to
-file-list-exec-source-files.
gdb/testsuite/ChangeLog:
* gdb.dwarf2/dw2-filename.exp: Update expected results.
* gdb.mi/mi-file.exp: Likewise.
* gdb.mi/mi-info-sources-base.c: New file.
* gdb.mi/mi-info-sources.c: New file.
* gdb.mi/mi-info-sources.exp: New file.
2021-05-18 20:46:19 +08:00
|
|
|
The results from -file-list-exec-source-files now include a
|
|
|
|
|
'debug-fully-read' field which takes the value 'true' or 'false'.
|
|
|
|
|
A 'true' value indicates the source file is from a compilation
|
|
|
|
|
unit that has had its debug information fully read in by GDB, a
|
|
|
|
|
value of 'false' indicates GDB has only performed a partial scan
|
|
|
|
|
of the debug information so far.
|
|
|
|
|
|
2020-08-22 00:16:49 +08:00
|
|
|
* GDB now supports core file debugging for x86_64 Cygwin programs.
|
|
|
|
|
|
2020-09-25 21:50:56 +08:00
|
|
|
* GDB will now look for the .gdbinit file in a config directory before
|
|
|
|
|
looking for ~/.gdbinit. The file is searched for in the following
|
|
|
|
|
locations: $XDG_CONFIG_HOME/gdb/gdbinit, $HOME/.config/gdb/gdbinit,
|
|
|
|
|
$HOME/.gdbinit. On Apple hosts the search order is instead:
|
|
|
|
|
$HOME/Library/Preferences/gdb/gdbinit, $HOME/.gdbinit.
|
|
|
|
|
|
2020-11-24 11:08:42 +08:00
|
|
|
* GDB now supports fixed point types which are described in DWARF
|
|
|
|
|
as base types with a fixed-point encoding. Additionally, support
|
|
|
|
|
for the DW_AT_GNU_numerator and DW_AT_GNU_denominator has also
|
|
|
|
|
been added.
|
|
|
|
|
|
|
|
|
|
For Ada, this allows support for fixed point types without requiring
|
|
|
|
|
the use of the GNAT encoding (based on information added to the type's
|
|
|
|
|
name following a GNAT-specific format).
|
|
|
|
|
|
2020-09-25 23:28:05 +08:00
|
|
|
* GDB will now load and process commands from ~/.config/gdb/gdbearlyinit
|
|
|
|
|
or ~/.gdbearlyinit if these files are present. These files are
|
|
|
|
|
processed earlier than any of the other initialization files and
|
|
|
|
|
can affect parts of GDB's startup that previously had already been
|
|
|
|
|
completed before the initialization files were read, for example
|
|
|
|
|
styling of the initial GDB greeting.
|
|
|
|
|
|
|
|
|
|
* GDB now has two new options "--early-init-command" and
|
|
|
|
|
"--early-init-eval-command" with corresponding short options "-eix"
|
|
|
|
|
and "-eiex" that allow options (that would normally appear in a
|
|
|
|
|
gdbearlyinit file) to be passed on the command line.
|
|
|
|
|
|
gdb/riscv: add support for vector registers in target descriptions
This commit adds support to RISC-V GDB for vector registers in the
incoming target description.
The vector registers should be described in a feature called
"org.gnu.gdb.riscv.vector", and should contain the register v0 to
v31. There's no restriction on the size or type of these registers,
so the target description can set these up as it requires.
However, if the target feature is present then all of the registers
must be present, and they must all be the same size, these
requirements are, I believe, inline with the RISC-V vector extension.
The DWARF register numbers for the vector registers have been added,
and the code to map between GDB's internal numbering and the DWARF
numbering has been updated.
I have not yet added a feature/riscv/*.xml file for the vector
extension, the consequence of this is that we can't, right now, detect
vector registers on a native target, this patch is all about
supporting vectors on a remote target.
It is worth noting that I don't actually have access to a RISC-V
target with vectors, so the only testing that this patch has had has
been done using 'set tdesc filename ....' to load a target description
to which I have manually added the vector feature. This has shown
that the vector register feature can be successfully parsed, and that
the registers show up in the expected register groups.
Additionally, the RISC-V vector extension is currently at v0.10, which
is also the v1.0 draft release. However, this extension is not yet
finalised. It is possible (but unlikely I think) that the register
set could change between now and the final release of the vector
extension. If this were to happen then we would potentially end up
changing the requirements for the new org.gnu.gdb.riscv.vector
feature. I really don't think it is likely that the register set will
change this late in the process, and even if it did, changing the
feature requirements will not be a problem as far as I am
concerned (when the alternative is GDB just continues without this
feature for now).
gdb/ChangeLog:
* NEWS: Mention new target feature name.
* arch/riscv.c (riscv_create_target_description): GDB doesn't
currently create target descriptions containing vector registers.
* arch/riscv.h (struct riscv_gdbarch_features) <vlen>: New member
variable.
<operator==>: Also compare vlen.
<hash>: Also include vlen.
* riscv-tdep.c (riscv_feature_name_vector): New static global.
(struct riscv_vector_feature): New struct.
(riscv_vector_feature): New static global.
(riscv_register_reggroup_p): Ensure vector registers are part of
the 'all' group, and part of the 'vector' group.
(riscv_dwarf_reg_to_regnum): Handle vector registers.
(riscv_gdbarch_init): Check vector register feature.
* riscv-tdep.h: Add vector registers to GDB's internal register
numbers, and to the DWARF register numbers.
gdb/doc/ChangeLog:
* gdb.texinfo (RISC-V Features): Mention vector register feature.
2021-05-04 18:41:09 +08:00
|
|
|
* For RISC-V targets, the target feature "org.gnu.gdb.riscv.vector" is
|
|
|
|
|
now understood by GDB, and can be used to describe the vector
|
|
|
|
|
registers of a target. The precise requirements of this register
|
|
|
|
|
feature are documented in the GDB manual.
|
|
|
|
|
|
[ARM] Add support for M-profile MVE extension
This patch adds support for the M-profile MVE extension, which includes the
following:
- New M-profile XML feature m-profile-mve
- MVE vector predication status and control register (VPR)
- p0 pseudo register (contained in the VPR)
- q0 ~ q7 pseudo vector registers
- New feature bits
- Documentation update
Pseudo register p0 is the least significant bits of vpr and can be accessed
as $p0 or displayed through $vpr. For more information about the register
layout, please refer to [1].
The q0 ~ q7 registers map back to the d0 ~ d15 registers, two d registers
per q register.
The register dump looks like this:
(gdb) info reg all
r0 0x0 0
r1 0x0 0
r2 0x0 0
r3 0x0 0
r4 0x0 0
r5 0x0 0
r6 0x0 0
r7 0x0 0
r8 0x0 0
r9 0x0 0
r10 0x0 0
r11 0x0 0
r12 0x0 0
sp 0x0 0x0 <__Vectors>
lr 0xffffffff -1
pc 0xd0c 0xd0c <Reset_Handler>
xpsr 0x1000000 16777216
d0 0 (raw 0x0000000000000000)
d1 0 (raw 0x0000000000000000)
d2 0 (raw 0x0000000000000000)
d3 0 (raw 0x0000000000000000)
d4 0 (raw 0x0000000000000000)
d5 0 (raw 0x0000000000000000)
d6 0 (raw 0x0000000000000000)
d7 0 (raw 0x0000000000000000)
d8 0 (raw 0x0000000000000000)
d9 0 (raw 0x0000000000000000)
d10 0 (raw 0x0000000000000000)
d11 0 (raw 0x0000000000000000)
d12 0 (raw 0x0000000000000000)
d13 0 (raw 0x0000000000000000)
d14 0 (raw 0x0000000000000000)
d15 0 (raw 0x0000000000000000)
fpscr 0x0 0
vpr 0x0 [ P0=0 MASK01=0 MASK23=0 ]
s0 0 (raw 0x00000000)
s1 0 (raw 0x00000000)
s2 0 (raw 0x00000000)
s3 0 (raw 0x00000000)
s4 0 (raw 0x00000000)
s5 0 (raw 0x00000000)
s6 0 (raw 0x00000000)
s7 0 (raw 0x00000000)
s8 0 (raw 0x00000000)
s9 0 (raw 0x00000000)
s10 0 (raw 0x00000000)
s11 0 (raw 0x00000000)
s12 0 (raw 0x00000000)
s13 0 (raw 0x00000000)
s14 0 (raw 0x00000000)
s15 0 (raw 0x00000000)
s16 0 (raw 0x00000000)
s17 0 (raw 0x00000000)
s18 0 (raw 0x00000000)
s19 0 (raw 0x00000000)
s20 0 (raw 0x00000000)
s21 0 (raw 0x00000000)
s22 0 (raw 0x00000000)
s23 0 (raw 0x00000000)
s24 0 (raw 0x00000000)
s25 0 (raw 0x00000000)
s26 0 (raw 0x00000000)
s27 0 (raw 0x00000000)
s28 0 (raw 0x00000000)
s29 0 (raw 0x00000000)
s30 0 (raw 0x00000000)
s31 0 (raw 0x00000000)
q0 {u8 = {0x0 <repeats 16 times>}, u16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, u32 = {0x0, 0x0, 0x0, 0x0}, u64 = {0x0, 0x0}, f32 = {0x0, 0x0, 0x0, 0x0}, f64 = {0x0, 0x0}}
q1 {u8 = {0x0 <repeats 16 times>}, u16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, u32 = {0x0, 0x0, 0x0, 0x0}, u64 = {0x0, 0x0}, f32 = {0x0, 0x0, 0x0, 0x0}, f64 = {0x0, 0x0}}
q2 {u8 = {0x0 <repeats 16 times>}, u16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, u32 = {0x0, 0x0, 0x0, 0x0}, u64 = {0x0, 0x0}, f32 = {0x0, 0x0, 0x0, 0x0}, f64 = {0x0, 0x0}}
q3 {u8 = {0x0 <repeats 16 times>}, u16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, u32 = {0x0, 0x0, 0x0, 0x0}, u64 = {0x0, 0x0}, f32 = {0x0, 0x0, 0x0, 0x0}, f64 = {0x0, 0x0}}
q4 {u8 = {0x0 <repeats 16 times>}, u16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, u32 = {0x0, 0x0, 0x0, 0x0}, u64 = {0x0, 0x0}, f32 = {0x0, 0x0, 0x0, 0x0}, f64 = {0x0, 0x0}}
q5 {u8 = {0x0 <repeats 16 times>}, u16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, u32 = {0x0, 0x0, 0x0, 0x0}, u64 = {0x0, 0x0}, f32 = {0x0, 0x0, 0x0, 0x0}, f64 = {0x0, 0x0}}
q6 {u8 = {0x0 <repeats 16 times>}, u16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, u32 = {0x0, 0x0, 0x0, 0x0}, u64 = {0x0, 0x0}, f32 = {0x0, 0x0, 0x0, 0x0}, f64 = {0x0, 0x0}}
q7 {u8 = {0x0 <repeats 16 times>}, u16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, u32 = {0x0, 0x0, 0x0, 0x0}, u64 = {0x0, 0x0}, f32 = {0x0, 0x0, 0x0, 0x0}, f64 = {0x0, 0x0}}
p0 0x0 0
Built and regtested with a simulator.
[1] https://developer.arm.com/documentation/ddi0553/bn
Co-Authored-By: Luis Machado <luis.machado@linaro.org>
2021-07-21 23:33:44 +08:00
|
|
|
* For ARM targets, the "org.gnu.gdb.arm.m-profile-mve" feature is now
|
|
|
|
|
supported by GDB and describes a new VPR register from the ARM MVE
|
|
|
|
|
(Helium) extension. See the GDB manual for more information.
|
|
|
|
|
|
2021-06-05 00:12:41 +08:00
|
|
|
* TUI improvements
|
|
|
|
|
|
|
|
|
|
** TUI windows now support mouse actions. The mouse wheel scrolls
|
|
|
|
|
the appropriate window.
|
|
|
|
|
|
|
|
|
|
** Key combinations that do not have a specific action on the
|
|
|
|
|
focused window are passed to GDB. For example, you now can use
|
|
|
|
|
Ctrl-Left/Ctrl-Right to move between words in the command window
|
|
|
|
|
regardless of which window is in focus. Previously you would
|
|
|
|
|
need to focus on the command window for such key combinations to
|
|
|
|
|
work.
|
|
|
|
|
|
2020-10-05 00:41:56 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
set debug event-loop
|
|
|
|
|
show debug event-loop
|
|
|
|
|
Control the display of debug output about GDB's event loop.
|
|
|
|
|
|
2020-06-16 02:54:00 +08:00
|
|
|
set print memory-tag-violations
|
|
|
|
|
show print memory-tag-violations
|
|
|
|
|
Control whether to display additional information about memory tag violations
|
|
|
|
|
when printing pointers and addresses. Architecture support for memory
|
|
|
|
|
tagging is required for this option to have an effect.
|
|
|
|
|
|
2020-11-21 03:08:06 +08:00
|
|
|
maintenance flush symbol-cache
|
|
|
|
|
maintenance flush register-cache
|
|
|
|
|
These new commands are equivalent to the already existing commands
|
|
|
|
|
'maintenance flush-symbol-cache' and 'flushregs' respectively.
|
|
|
|
|
|
2020-11-21 03:34:21 +08:00
|
|
|
maintenance flush dcache
|
|
|
|
|
A new command to flush the dcache.
|
|
|
|
|
|
2021-02-13 00:10:56 +08:00
|
|
|
maintenance info target-sections
|
|
|
|
|
Print GDB's internal target sections table.
|
|
|
|
|
|
gdb: call post_create_inferior at end of follow_fork_inferior
GDB doesn't handle well the case of an inferior using the JIT interface
to register JIT-ed objfiles and forking. If an inferior registers a
code object using the JIT interface and then forks, the child process
conceptually has the same code object loaded, so GDB should look it up
and learn about it (it currently doesn't).
To achieve this, I think it would make sense to have the
inferior_created observable called when an inferior is created due to a
fork in follow_fork_inferior. The inferior_created observable is
currently called both after starting a new inferior and after attaching
to an inferior, allowing various sub-components to learn about that new
executing inferior. We can see handling a fork child just like
attaching to it, so any work done when attaching should also be done in
the case of a fork child.
Instead of just calling the inferior_created observable, this patch
makes follow_fork_inferior call the whole post_create_inferior function.
This way, the attach and follow-fork code code paths are more alike.
Given that post_create_inferior calls solib_create_inferior_hook,
follow_fork_inferior doesn't need to do it itself, so those calls to
solib_create_inferior_hook are removed.
One question you may have: why not just call post_create_inferior at the
places where solib_create_inferior_hook is currently called, instead of
after target_follow_fork?
- there's something fishy for the second solib_create_inferior_hook
call site: at this point we have switched the current program space
to the child's, but not the current inferior nor the current thread.
So solib_create_inferior_hook (and everything under, including
check_for_thread_db, for example) is called with inferior 1 as the
current inferior and inferior 2's program space as the current
program space. I think that's wrong, because at this point we are
setting up inferior 2, and all that code relies on the current
inferior. We could just add a switch_to_thread call before it to
make inferior 2 the current one, but there are other problems (see
below).
- solib_create_inferior_hook is currently not called on the
`follow_child && detach_fork` path. I think we need to call it,
because we still get a new inferior in that case (even though we
detach the parent). If we only call post_create_inferior where
solib_create_inferior_hook used to be called, then the JIT
subcomponent doesn't get informed about the new inferior, and that
introduces a failure in the new gdb.base/jit-elf-fork.exp test.
- if we try to put the post_create_inferior just after the
switch_to_thread that was originally at line 662, or just before the
call to target_follow_fork, we introduce a subtle failure in
gdb.threads/fork-thread-pending.exp. What happens then is that
libthread_db gets loaded (somewhere under post_create_inferior)
before the linux-nat target learns about the LWPs (which happens in
linux_nat_target::follow_fork). As a result, the ALL_LWPS loop in
try_thread_db_load_1 doesn't see the child LWP, and the thread-db
target doesn't have the chance to fill in thread_info::priv. A bit
later, when the test does "info threads", and
thread_db_target::pid_to_str is called, the thread-db target doesn't
recognize the thread as one of its own, and delegates the request to
the target below. Because the pid_to_str output is not the expected
one, the test fails.
This tells me that we need to call the process target's follow_fork
first, to make the process target create the necessary LWP and thread
structures. Then, we can call post_create_inferior to let the other
components of GDB do their thing.
But then you may ask: check_for_thread_db is already called today,
somewhere under solib_create_inferior_hook, and that is before
target_follow_fork, why don't we see this ordering problem!? Well,
because of the first bullet point: when check_for_thread_db /
thread_db_load are called, the current inferior is (erroneously)
inferior 1, the parent. Because libthread_db is already loaded for
the parent, thread_db_load early returns. check_for_thread_db later
gets called by linux_nat_target::follow_fork. At this point, the
current inferior is the correct one and the child's LWP exists, so
all is well.
Since we now call post_create_inferior after target_follow_fork, which
calls the inferior_created observable, which calls check_for_thread_db,
I don't think linux_nat_target needs to explicitly call
check_for_thread_db itself, so that is removed.
In terms of testing, this patch adds a new gdb.base/jit-elf-fork.exp
test. It makes an inferior register a JIT code object and then fork.
It then verifies that whatever the detach-on-fork and follow-fork-child
parameters are, GDB knows about the JIT code object in all the inferiors
that survive the fork. It verifies that the inferiors can unload that
code object.
There isn't currently a way to get visibility into GDB's idea of the JIT
code objects for each inferior. For the purpose of this test, add the
"maintenance info jit" command. There isn't much we can print about the
JIT code objects except their load address. So the output looks a bit
bare, but it's good enough for the test.
gdb/ChangeLog:
* NEWS: Mention "maint info jit" command.
* infrun.c (follow_fork_inferior): Don't call
solib_create_inferior_hook, call post_create_inferior if a new
inferior was created.
* jit.c (maint_info_jit_cmd): New.
(_initialize_jit): Register new command.
* linux-nat.c (linux_nat_target::follow_fork): Don't call
check_for_thread_db.
* linux-nat.h (check_for_thread_db): Remove declaration.
* linux-thread-db.c (check_thread_signals): Make static.
gdb/doc/ChangeLog:
* gdb.texinfo (Maintenance Commands): Mention "maint info jit".
gdb/testsuite/ChangeLog:
* gdb.base/jit-elf-fork-main.c: New test.
* gdb.base/jit-elf-fork-solib.c: New test.
* gdb.base/jit-elf-fork.exp: New test.
Change-Id: I9a192e55b8a451c00e88100669283fc9ca60de5c
2021-04-07 02:31:50 +08:00
|
|
|
maintenance info jit
|
|
|
|
|
Print the JIT code objects in the inferior known to GDB.
|
|
|
|
|
|
2020-06-16 02:54:00 +08:00
|
|
|
memory-tag show-logical-tag POINTER
|
|
|
|
|
Print the logical tag for POINTER.
|
|
|
|
|
memory-tag with-logical-tag POINTER TAG
|
|
|
|
|
Print POINTER with logical tag TAG.
|
|
|
|
|
memory-tag show-allocation-tag ADDRESS
|
|
|
|
|
Print the allocation tag for ADDRESS.
|
|
|
|
|
memory-tag set-allocation-tag ADDRESS LENGTH TAGS
|
|
|
|
|
Set the allocation tag for [ADDRESS, ADDRESS + LENGTH) to TAGS.
|
|
|
|
|
memory-tag check POINTER
|
|
|
|
|
Validate that POINTER's logical tag matches the allocation tag.
|
|
|
|
|
|
2020-07-06 03:02:40 +08:00
|
|
|
set startup-quietly on|off
|
|
|
|
|
show startup-quietly
|
|
|
|
|
When 'on', this causes GDB to act as if "-silent" were passed on the
|
|
|
|
|
command line. This command needs to be added to an early
|
|
|
|
|
initialization file (e.g. ~/.config/gdb/gdbearlyinit) in order to
|
|
|
|
|
affect GDB.
|
|
|
|
|
|
2021-04-17 19:10:23 +08:00
|
|
|
set print type hex on|off
|
|
|
|
|
show print type hex
|
|
|
|
|
When 'on', the 'ptype' command uses hexadecimal notation to print sizes
|
|
|
|
|
and offsets of struct members. When 'off', decimal notation is used.
|
|
|
|
|
|
2020-08-27 23:53:13 +08:00
|
|
|
set python ignore-environment on|off
|
|
|
|
|
show python ignore-environment
|
|
|
|
|
When 'on', this causes GDB's builtin Python to ignore any
|
2021-04-29 17:29:41 +08:00
|
|
|
environment variables that would otherwise affect how Python
|
2020-08-27 23:53:13 +08:00
|
|
|
behaves. This command needs to be added to an early initialization
|
|
|
|
|
file (e.g. ~/.config/gdb/gdbearlyinit) in order to affect GDB.
|
|
|
|
|
|
|
|
|
|
set python dont-write-bytecode auto|on|off
|
|
|
|
|
show python dont-write-bytecode
|
|
|
|
|
When 'on', this causes GDB's builtin Python to not write any
|
|
|
|
|
byte-code (.pyc files) to disk. This command needs to be added to
|
|
|
|
|
an early initialization file (e.g. ~/.config/gdb/gdbearlyinit) in
|
|
|
|
|
order to affect GDB. When 'off' byte-code will always be written.
|
|
|
|
|
When set to 'auto' (the default) Python will check the
|
2021-04-29 17:29:41 +08:00
|
|
|
PYTHONDONTWRITEBYTECODE environment variable.
|
2020-08-27 23:53:13 +08:00
|
|
|
|
gdb/breakpoint: add flags to 'condition' and 'break' commands to force condition
The previous patch made it possible to define a condition if it's
valid at some locations. If the condition is invalid at all of the
locations, it's rejected. However, there may be cases where the user
knows the condition *will* be valid at a location in the future,
e.g. due to a shared library load.
To make it possible that such condition can be defined, this patch
adds an optional '-force' flag to the 'condition' command, and,
respectively, a '-force-condition' flag to the 'break'command. When
the force flag is passed, the condition is not rejected even when it
is invalid for all the current locations (note that all the locations
would be internally disabled in this case).
For instance:
(gdb) break test.c:5
Breakpoint 1 at 0x1155: file test.c, line 5.
(gdb) cond 1 foo == 42
No symbol "foo" in current context.
Defining the condition was not possible because 'foo' is not
available. The user can override this behavior with the '-force'
flag:
(gdb) cond -force 1 foo == 42
warning: failed to validate condition at location 1.1, disabling:
No symbol "foo" in current context.
(gdb) info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep y <MULTIPLE>
stop only if foo == 42
1.1 N 0x0000000000001155 in main at test.c:5
Now the condition is accepted, but the location is automatically
disabled. If a future location has a context in which 'foo' is
available, that location would be enabled.
For the 'break' command, -force-condition has the same result:
(gdb) break test.c:5 -force-condition if foo == 42
warning: failed to validate condition at location 0x1169, disabling:
No symbol "foo" in current context.
Breakpoint 1 at 0x1169: file test.c, line 5.
gdb/ChangeLog:
2020-10-27 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
* breakpoint.h (set_breakpoint_condition): Add a new bool parameter.
* breakpoint.c: Update the help text of the 'condition' and 'break'
commands.
(set_breakpoint_condition): Take a new bool parameter
to control whether condition definition should be forced even when
the condition expression is invalid in all of the current locations.
(condition_command): Update the call to 'set_breakpoint_condition'.
(find_condition_and_thread): Take the "-force-condition" flag into
account.
* linespec.c (linespec_keywords): Add "-force-condition" as an
element.
(FORCE_KEYWORD_INDEX): New #define.
(linespec_lexer_lex_keyword): Update to consider "-force-condition"
as a keyword.
* ada-lang.c (create_ada_exception_catchpoint): Ditto.
* guile/scm-breakpoint.c (gdbscm_set_breakpoint_condition_x): Ditto.
* python/py-breakpoint.c (bppy_set_condition): Ditto.
* NEWS: Mention the changes to the 'break' and 'condition' commands.
gdb/testsuite/ChangeLog:
2020-10-27 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
* gdb.base/condbreak-multi-context.exp: Expand to test forcing
the condition.
* gdb.linespec/cpcompletion.exp: Update to consider the
'-force-condition' keyword.
* gdb.linespec/explicit.exp: Ditto.
* lib/completion-support.exp: Ditto.
gdb/doc/ChangeLog:
2020-10-27 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
* gdb.texinfo (Set Breaks): Document the '-force-condition' flag
of the 'break'command.
* gdb.texinfo (Conditions): Document the '-force' flag of the
'condition' command.
2020-10-27 17:56:03 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
|
|
|
|
break [PROBE_MODIFIER] [LOCATION] [thread THREADNUM]
|
|
|
|
|
[-force-condition] [if CONDITION]
|
|
|
|
|
This command would previously refuse setting a breakpoint if the
|
|
|
|
|
CONDITION expression is invalid at a location. It now accepts and
|
|
|
|
|
defines the breakpoint if there is at least one location at which
|
|
|
|
|
the CONDITION is valid. The locations for which the CONDITION is
|
|
|
|
|
invalid, are automatically disabled. If CONDITION is invalid at all
|
|
|
|
|
of the locations, setting the breakpoint is still rejected. However,
|
|
|
|
|
the '-force-condition' flag can be used in this case for forcing GDB to
|
|
|
|
|
define the breakpoint, making all the current locations automatically
|
|
|
|
|
disabled. This may be useful if the user knows the condition will
|
|
|
|
|
become meaningful at a future location, e.g. due to a shared library
|
|
|
|
|
load.
|
|
|
|
|
|
|
|
|
|
condition [-force] N COND
|
|
|
|
|
The behavior of this command is changed the same way for the 'break'
|
|
|
|
|
command as explained above. The '-force' flag can be used to force
|
|
|
|
|
GDB into defining the condition even when COND is invalid for all the
|
|
|
|
|
current locations of breakpoint N.
|
|
|
|
|
|
2020-11-21 03:08:06 +08:00
|
|
|
flushregs
|
|
|
|
|
maintenance flush-symbol-cache
|
|
|
|
|
These commands are deprecated in favor of the new commands
|
|
|
|
|
'maintenance flush register-cache' and 'maintenance flush
|
|
|
|
|
symbol-cache' respectively.
|
|
|
|
|
|
gdb: add new version style
This commit adds a new 'version' style, which replaces the hard coded
styling currently used for GDB's version string. GDB's version number
is displayed:
1. In the output of 'show version', and
2. When GDB starts up (without the --quiet option).
This new style can only ever affect the first of these two cases as
the second case is printed before GDB has processed any initialization
files, or processed any GDB commands passed on the command line.
However, because the first case exists I think this commit makes
sense, it means the style is no longer hard coded into GDB, and we can
add some tests that the style can be enabled/disabled correctly.
This commit is an alternative to a patch Tom posted here:
https://sourceware.org/pipermail/gdb-patches/2020-June/169820.html
I've used the style name 'version' instead of 'startup' to reflect
what the style is actually used for. If other parts of the startup
text end up being highlighted I imagine they would get their own
styles based on what is being highlighted. I feel this is more inline
with the other style names that are already in use within GDB.
I also decoupled adding this style from the idea of startup options,
and the possibility of auto-saving startup options. Those ideas can
be explored in later patches.
This commit should probably be considered only a partial solution to
issue PR cli/25956. The colours of the style are no longer hard
coded, however, it is still impossible to change the styling of the
version string displayed during startup, so in one sense, the styling
of that string is still "hard coded". A later patch will hopefully
extend GDB to allow it to adjust the version styling before the
initial version string is printed.
gdb/ChangeLog:
PR cli/25956
* cli/cli-style.c: Add 'cli/cli-setshow.h' include.
(version_style): Define.
(cli_style_option::cli_style_option): Add intensity parameter, and
use as appropriate.
(_initialize_cli_style): Register version style set/show commands.
* cli/cli-style.h (cli_style_option): Add intensity parameter.
(version_style): Declare.
* top.c (print_gdb_version): Use version_stype, and styled_string
to print the GDB version string.
gdb/doc/ChangeLog:
PR cli/25956
* gdb.texinfo (Output Styling): Document version style.
gdb/testsuite/ChangeLog:
PR cli/25956
* gdb.base/style.exp (run_style_tests): Add version string test.
(test_startup_version_string): Use version style name.
* lib/gdb-utils.exp (style): Handle version style name.
2021-01-14 04:08:51 +08:00
|
|
|
set style version foreground COLOR
|
|
|
|
|
set style version background COLOR
|
|
|
|
|
set style version intensity VALUE
|
|
|
|
|
Control the styling of GDB's version number text.
|
|
|
|
|
|
2021-01-07 04:58:04 +08:00
|
|
|
inferior [ID]
|
|
|
|
|
When the ID parameter is omitted, then this command prints information
|
|
|
|
|
about the current inferior. When the ID parameter is present, the
|
|
|
|
|
behavior of the command is unchanged and have the inferior ID become
|
|
|
|
|
the current inferior.
|
|
|
|
|
|
gdb: change 'maint info section' to use command options
The 'maintenance info sections' command currently takes a list of
filters on the command line. It can also accept the magic string
'ALLOBJ' which acts more like a command line flag, telling the command
to print information about all objfiles.
The manual has this to say about the options and filters:
... In addition, 'maint info sections' provides the following
command options (which may be arbitrarily combined): ...
Implying (to me at least) that I can do this:
(gdb) maint info sections ALLOBJ READONLY
to list all the read-only sections from all currently loaded object
files.
Unfortunately, this doesn't work. The READONLY filter will work, but
ALLOBJ will not be detected correctly.
It would be fairly simple to fix the ALLOBJ detection. However, I
dislike this mixing of command options (ALLOBJ) with command data (the
filters, e.g. READONLY, etc).
As this is a maintenance command, so not really intended for end
users, I think we can be a little more aggressive in "fixing" the
option parsing. So that's what I do in this commit.
The ALLOBJ mechanism is replaced with a real command
option (-all-objects). The rest of the command operates just as
before. The example above would now become:
(gdb) maint info sections -all-objects READONLY
The manual has been updated, and I added a NEWS entry to document the
change.
gdb/ChangeLog:
* NEWS: Mention changes to 'maint info sections'.
* maint.c (match_substring): Return a bool, fix whitespace issue.
(struct single_bfd_flag_info): New struct.
(bfd_flag_info): New static global.
(match_bfd_flags): Return a bool, use bfd_flag_info.
(print_bfd_flags): Use bfd_flag_info.
(maint_print_section_info): Delete trailing whitespace.
(struct maint_info_sections_opts): New struct.
(maint_info_sections_option_defs): New static global.
(maint_info_sections_completer): New function.
(maintenance_info_sections): Use option parsing mechanism.
(_initialize_maint_cmds): Register command completer.
gdb/doc/ChangeLog:
* gdb.texinfo (Files): Update documentation for 'maint info
sections'.
gdb/testsuite/ChangeLog:
* gdb.base/maint-info-sections.exp: Update expected output, and
add additional tests. Again.
2021-02-05 21:51:34 +08:00
|
|
|
maintenance info sections
|
|
|
|
|
The ALLOBJ keyword has been replaced with an -all-objects command
|
|
|
|
|
line flag. It is now possible to filter which sections are printed
|
|
|
|
|
even when -all-objects is passed.
|
|
|
|
|
|
2021-04-17 19:10:23 +08:00
|
|
|
ptype[/FLAGS] TYPE | EXPRESSION
|
|
|
|
|
The 'ptype' command has two new flags. When '/x' is set, hexadecimal
|
|
|
|
|
notation is used when printing sizes and offsets of struct members.
|
|
|
|
|
When '/d' is set, decimal notation is used when printing sizes and
|
|
|
|
|
offsets of struct members. Default behavior is given by 'show print
|
|
|
|
|
type hex'.
|
|
|
|
|
|
gdb: change info sources to group results by objfile
Currently the 'info sources' command lists all of the known source
files together, regardless of their source, e.g. here is a session
debugging a test application that makes use of a shared library:
(gdb) info sources
Source files for which symbols have been read in:
/tmp/info-sources/test.c, /usr/include/stdc-predef.h,
/tmp/info-sources/header.h, /tmp/info-sources/helper.c
Source files for which symbols will be read in on demand:
(gdb)
In this commit I change the format of the 'info sources' results so
that the results are grouped by the object file that uses that source
file. Here's the same session with the new output format:
(gdb) info sources
/tmp/info-sources/test.x:
/tmp/info-sources/test.c, /usr/include/stdc-predef.h,
/tmp/info-sources/header.h
/lib64/ld-linux-x86-64.so.2:
(Objfile has no debug information.)
system-supplied DSO at 0x7ffff7fcf000:
(Objfile has no debug information.)
/tmp/info-sources/libhelper.so:
/tmp/info-sources/helper.c, /usr/include/stdc-predef.h,
/tmp/info-sources/header.h
/lib64/libc.so.6:
(Objfile has no debug information.)
(gdb)
Notice that in the new output some source files are repeated,
e.g. /tmp/info-sources/header.h, as multiple objfiles use this source
file.
Further, some object files are tagged with the message '(Objfile has
no debug information.)', it is also possible to see the message '(Full
debug information has not yet been read for this file.)', which is
printed when some symtabs within an objfile have not yet been
expanded.
All of the existing regular expression based filtering still works.
An original version of this patch added the new format as an option to
'info sources', however, it was felt that the new layout was so much
better than the old style that GDB should just switch to the new
result format completely.
gdb/ChangeLog:
* NEWS: Mention changes to 'info sources'.
* symtab.c (info_sources_filter::print): Delete.
(struct output_source_filename_data) <print_header>: Delete
declaration. <printed_filename_p>: New member function.
(output_source_filename_data::print_header): Delete.
(info_sources_worker): Update group-by-objfile style output to
make it CLI suitable, simplify non-group-by-objfile now this is
only used from the MI.
(info_sources_command): Make group-by-objfile be the default for
CLI info sources command.
* symtab.h (struct info_sources_filter) <print>: Delete.
gdb/doc/ChangeLog:
* gdb.texinfo (Symbols): Document new output format for 'info
sources'.
gdb/testsuite/ChangeLog:
* gdb.base/info_sources_2-header.h: New file.
* gdb.base/info_sources_2-lib.c: New file.
* gdb.base/info_sources_2-test.c: New file.
* gdb.base/info_sources_2.exp: New file.
2021-05-18 21:27:25 +08:00
|
|
|
info sources
|
|
|
|
|
The info sources command output has been restructured. The results
|
|
|
|
|
are now based around a list of objfiles (executable and libraries),
|
|
|
|
|
and for each objfile the source files that are part of that objfile
|
|
|
|
|
are listed.
|
|
|
|
|
|
2021-02-10 10:08:47 +08:00
|
|
|
* Removed targets and native configurations
|
|
|
|
|
|
|
|
|
|
ARM Symbian arm*-*-symbianelf*
|
|
|
|
|
|
2020-06-16 02:54:00 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
qMemTags
|
|
|
|
|
Request the remote to send allocation tags for a particular memory range.
|
|
|
|
|
QMemTags
|
|
|
|
|
Request the remote to store the specified allocation tags to the requested
|
|
|
|
|
memory range.
|
|
|
|
|
|
2021-04-29 01:32:37 +08:00
|
|
|
* Guile API
|
|
|
|
|
|
|
|
|
|
** Improved support for rvalue reference values:
|
|
|
|
|
TYPE_CODE_RVALUE_REF is now exported as part of the API and the
|
|
|
|
|
value-referenced-value procedure now handles rvalue reference
|
|
|
|
|
values.
|
|
|
|
|
|
2021-04-29 01:32:56 +08:00
|
|
|
** New procedures for obtaining value variants:
|
|
|
|
|
value-reference-value, value-rvalue-reference-value and
|
|
|
|
|
value-const-value.
|
2021-04-29 01:32:47 +08:00
|
|
|
|
2021-06-09 21:56:11 +08:00
|
|
|
** Temporary breakpoints can now be created with make-breakpoint and
|
|
|
|
|
tested for using breakpoint-temporary?.
|
|
|
|
|
|
2021-05-14 17:56:31 +08:00
|
|
|
* Python API
|
|
|
|
|
|
|
|
|
|
** Inferior objects now contain a read-only 'connection_num' attribute that
|
|
|
|
|
gives the connection number as seen in 'info connections' and
|
|
|
|
|
'info inferiors'.
|
|
|
|
|
|
2021-05-27 05:01:59 +08:00
|
|
|
** New method gdb.Frame.level() which returns the stack level of the
|
|
|
|
|
frame object.
|
|
|
|
|
|
|
|
|
|
** New method gdb.PendingFrame.level() which returns the stack level
|
|
|
|
|
of the frame object.
|
|
|
|
|
|
2021-05-05 22:26:28 +08:00
|
|
|
** When hitting a catchpoint, the Python API will now emit a
|
|
|
|
|
gdb.BreakpointEvent rather than a gdb.StopEvent. The
|
|
|
|
|
gdb.Breakpoint attached to the event will have type BP_CATCHPOINT.
|
|
|
|
|
|
2021-06-05 00:12:41 +08:00
|
|
|
** Python TUI windows can now receive mouse click events. If the
|
|
|
|
|
Window object implements the click method, it is called for each
|
|
|
|
|
mouse click event in this window.
|
|
|
|
|
|
2020-09-13 10:43:47 +08:00
|
|
|
*** Changes in GDB 10
|
2019-12-12 04:44:47 +08:00
|
|
|
|
2020-07-09 23:43:13 +08:00
|
|
|
* There are new feature names for ARC targets: "org.gnu.gdb.arc.core"
|
|
|
|
|
and "org.gnu.gdb.arc.aux". The old names are still supported but
|
|
|
|
|
must be considered obsolete. They will be deprecated after some
|
|
|
|
|
grace period.
|
|
|
|
|
|
2020-05-11 04:22:01 +08:00
|
|
|
* Help and apropos commands will now show the documentation of a
|
|
|
|
|
command only once, even if that command has one or more aliases.
|
|
|
|
|
These commands now show the command name, then all of its aliases,
|
|
|
|
|
and finally the description of the command.
|
|
|
|
|
|
|
|
|
|
* 'help aliases' now shows only the user defined aliases. GDB predefined
|
|
|
|
|
aliases are shown together with their aliased command.
|
|
|
|
|
|
2020-02-27 06:40:49 +08:00
|
|
|
* GDB now supports debuginfod, an HTTP server for distributing ELF/DWARF
|
|
|
|
|
debugging information as well as source code.
|
|
|
|
|
|
|
|
|
|
When built with debuginfod, GDB can automatically query debuginfod
|
|
|
|
|
servers for the separate debug files and source code of the executable
|
|
|
|
|
being debugged.
|
|
|
|
|
|
|
|
|
|
To build GDB with debuginfod, pass --with-debuginfod to configure (this
|
|
|
|
|
requires libdebuginfod, the debuginfod client library).
|
|
|
|
|
|
|
|
|
|
debuginfod is distributed with elfutils, starting with version 0.178.
|
|
|
|
|
|
|
|
|
|
You can get the latest version from https://sourceware.org/elfutils.
|
|
|
|
|
|
2020-08-13 02:46:13 +08:00
|
|
|
* Multi-target debugging support
|
|
|
|
|
|
|
|
|
|
GDB now supports debugging multiple target connections
|
|
|
|
|
simultaneously. For example, you can now have each inferior
|
|
|
|
|
connected to different remote servers running in different machines,
|
|
|
|
|
or have one inferior debugging a local native process, an inferior
|
|
|
|
|
debugging a core dump, etc.
|
|
|
|
|
|
|
|
|
|
This support is experimental and comes with some limitations -- you
|
|
|
|
|
can only resume multiple targets simultaneously if all targets
|
|
|
|
|
support non-stop mode, and all remote stubs or servers must support
|
|
|
|
|
the same set of remote protocol features exactly. See also "info
|
|
|
|
|
connections" and "add-inferior -no-connection" below, and "maint set
|
|
|
|
|
target-non-stop" in the user manual.
|
|
|
|
|
|
2020-02-19 09:24:37 +08:00
|
|
|
* New features in the GDB remote stub, GDBserver
|
|
|
|
|
|
2020-10-07 23:13:33 +08:00
|
|
|
** GDBserver is now supported on ARC GNU/Linux.
|
|
|
|
|
|
2020-02-19 09:24:37 +08:00
|
|
|
** GDBserver is now supported on RISC-V GNU/Linux.
|
|
|
|
|
|
2020-06-13 04:06:46 +08:00
|
|
|
** GDBserver no longer supports these host triplets:
|
|
|
|
|
|
|
|
|
|
i[34567]86-*-lynxos*
|
|
|
|
|
powerpc-*-lynxos*
|
|
|
|
|
i[34567]86-*-nto*
|
|
|
|
|
bfin-*-*linux*
|
|
|
|
|
crisv32-*-linux*
|
|
|
|
|
cris-*-linux*
|
|
|
|
|
m32r*-*-linux*
|
|
|
|
|
tilegx-*-linux*
|
|
|
|
|
arm*-*-mingw32ce*
|
|
|
|
|
i[34567]86-*-mingw32ce*
|
|
|
|
|
|
2020-01-07 03:25:23 +08:00
|
|
|
* Debugging MS-Windows processes now sets $_exitsignal when the
|
|
|
|
|
inferior is terminated by a signal, instead of setting $_exitcode.
|
|
|
|
|
|
2019-12-20 08:24:22 +08:00
|
|
|
* Multithreaded symbol loading has now been enabled by default on systems
|
|
|
|
|
that support it (see entry for GDB 9, below), providing faster
|
|
|
|
|
performance for programs with many symbols.
|
|
|
|
|
|
2020-01-17 22:28:09 +08:00
|
|
|
* The $_siginfo convenience variable now also works on Windows targets,
|
|
|
|
|
and will display the EXCEPTION_RECORD of the last handled exception.
|
|
|
|
|
|
2020-02-23 02:48:26 +08:00
|
|
|
* TUI windows can now be arranged horizontally.
|
gdb: Allow GDB to _not_ load a previous command history
This commit aims to give a cleaner mechanism by which the user can
prevent GDB from trying to load any previous command history.
Currently the user can change the path to the history file, either
using a command line flag, or by setting the GDBHISTFILE environment
variable, and if the path is set to a non-existent file, then
obviously GDB wont load any command history. However, this feels like
a bit of a bodge, I'd like to add an official mechanism by which we
can disable command history loading.
Why would we want to prevent command history loading? The specific
use case I have is GDB starting with a CWD that is a network mounted
directory, and there is no command history present. Still GDB will
access the network in order to check for the file. In my particular
use case I'm actually starting a large number of GDB instances in
parallel, all in the same network mounted directory, the large number
of network accesses looking for this file introduces a noticeable
delay at GDB startup.
The approach I'm proposing here is a slight adjustment to the current
rules for setting up the history filename. Currently, if a user does
this, they see an error:
(gdb) set history filename
Argument required (filename to set it to.).
However, if a user does this:
$ GDBHISTFILE= gdb --quiet
(gdb) set history save on
(gdb) q
warning: Could not rename -gdb18416~ to : No such file or directory
So, we already have a bug in this area. My plan is to allow the empty
filename to be accepted, and for this to mean, neither load, nor save
the command history.
This does mean that we now have two mechanisms to prevent saving the
command history:
(gdb) set history filename
or
(gdb) set history save off
But the only way to prevent loading the command history is to set the
filename to the empty string _before_ you get to a GDB prompt, either
using a command line option, or the environment variable.
I've updated some of the show commands, for example this session:
(gdb) set history filename
(gdb) show history filename
There is no filename currently set for recording the command history in.
(gdb) show history save
Saving of the history record on exit is off.
(gdb) set history save on
(gdb) show history save
Saving of the history is disabled due to the value of 'history filename'.
(gdb) set history filename /tmp/hist
(gdb) show history save
Saving of the history record on exit is on.
I've updated the manual, and added some tests.
gdb/ChangeLog:
* NEWS: Mention new behaviour of the history filename.
* top.c (write_history_p): Add comment.
(show_write_history_p): Add header comment, give a different
message when history writing is on, but the history filename is
empty.
(history_filename): Add comment.
(history_filename_empty): New function.
(show_history_filename): Add header comment, give a different
message when the filename is empty.
(init_history): Compare history_filename against nullptr, and only
read history if the filename is not empty.
(set_history_filename): Add header comment, and only make
non-empty filenames absolute.
(init_main): Make the filename argument to 'set history filename'
optional.
gdb/doc/ChangeLog:
* gdb.texinfo (Command History): Extend description for
GDBHISTFILE and GDBHISTSIZE, add detail about the filename for
'set history filename' being optional. Describe the effect of an
empty history filename on 'set history save on'.
gdb/testsuite/ChangeLog:
* gdb.base/default.exp: Remove test of 'set history filename'.
* gdb.base/gdbinit-history.exp: Add tests for setting the history
filename to the empty string.
* lib/gdb.exp (gdb_init): Unset environment variables GDBHISTFILE
and GDBHISTSIZE.
Change-Id: Ia586e4311182fac99113b60f11ef8a11fbd5450b
2020-01-23 02:21:58 +08:00
|
|
|
|
|
|
|
|
* The command history filename can now be set to the empty string
|
|
|
|
|
either using 'set history filename' or by setting 'GDBHISTFILE=' in
|
|
|
|
|
the environment. The effect of setting this filename to the empty
|
|
|
|
|
string is that GDB will not try to load any previous command
|
|
|
|
|
history.
|
2020-01-27 05:04:04 +08:00
|
|
|
|
|
|
|
|
* On Windows targets, it is now possible to debug 32-bit programs with a
|
|
|
|
|
64-bit GDB.
|
2020-02-23 02:48:26 +08:00
|
|
|
|
2019-12-21 21:47:17 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
set exec-file-mismatch -- Set exec-file-mismatch handling (ask|warn|off).
|
|
|
|
|
show exec-file-mismatch -- Show exec-file-mismatch handling (ask|warn|off).
|
Make exec-file-mismatch compare build IDs
The patch makes GDB do exec-file-mismatch validation by comparing
build IDs instead of the current method of comparing filenames.
Currently, the exec-file-mismatch feature simply compares filenames to
decide whether the exec file loaded in gdb and the exec file the
target reports is running match. This causes false positives when
remote debugging, because it'll often be the case that the paths in
the host and the target won't match. And of course misses the case of
the files having the same name but being actually different files
(e.g., different builds).
This also broke many testcases when running against gdbserver, causing
tests to be skipped like (here native-extended-gdbserver):
(gdb) run
Starting program: /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/argv0-symlink/argv0-symlink-filelink
warning: Mismatch between current exec-file /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/argv0-symlink/argv0-symlink-filelink
and automatically determined exec-file /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/argv0-symlink/argv0-symlink
exec-file-mismatch handling is currently "ask"
Load new symbol table from "/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/argv0-symlink/argv0-symlink"? (y or n) UNTESTED: gdb.base/argv0-symlink.exp: could not run to main
or to fail like (here native-gdbserver):
(gdb) spawn /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/../../gdbserver/gdbserver --once localhost:2346 /home/pedro/gdb/binutils-gdb/build/gdb/te
stsuite/outputs/gdb.btrace/buffer-size/skip_btrace_tests-19968.x
Process /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.btrace/buffer-size/skip_btrace_tests-19968.x created; pid = 20040
Listening on port 2346
target remote localhost:2346
Remote debugging using localhost:2346
warning: Mismatch between current exec-file /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/temp/19968/skip_btrace_tests-19968.x
and automatically determined exec-file /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.btrace/buffer-size/skip_btrace_tests-19968.x
exec-file-mismatch handling is currently "ask"
Load new symbol table from "/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.btrace/buffer-size/skip_btrace_tests-19968.x"? (y or n) Quit
(gdb) UNSUPPORTED: gdb.btrace/buffer-size.exp: target does not support record-btrace
The former case is about GDB not realizing the two files are the same,
because one of the them is a symlink to the other. The latter case is
about GDB realizing that one file is a copy of the other.
Over the years, the toolchain has settled on build ID matching being
the canonical method to match core dumps to executables, and
executables with no debug info to their debug info.
This patch makes us use build IDs to match the running image of a
binary with its version loaded in gdb, which may or may not have debug
info. This is very much like the core dump/executable matching.
The change to gdb_bfd_open is necessary to get rid of the "transfers
from remote targets can be slow" warning when we open the remote file
to read its build ID:
(gdb) r
Starting program: /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/break/break
Reading /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/argv0-symlink/argv0-symlink from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
warning: Mismatch between current exec-file /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/break/break
and automatically determined exec-file /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/argv0-symlink/argv0-symlink
exec-file-mismatch handling is currently "ask"
Load new symbol table from "/home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/argv0-symlink/argv0-symlink"? (y or n)
While trying this out, I was worried that bfd would read a lot of
stuff from the binary in order to extract the build ID, making it
potentially slow, but turns out we don't read all that much. Maybe a
couple hundred bytes, and most of it seemingly is the read-ahead
cache. So I'm not worried about that. Otherwise I'd consider whether
a new qXfer:buildid:read would be better. But I'm happy that we
seemingly don't need to worry about it.
gdb/ChangeLog:
2020-05-19 Pedro Alves <palves@redhat.com>
* NEWS (set exec-file-mismatch): Adjust entry.
* exec.c: Include "build-id.h".
(validate_exec_file): Try to match build IDs instead of filenames.
* gdb_bfd.c (struct gdb_bfd_open_closure): New.
(gdb_bfd_iovec_fileio_open): Adjust to use gdb_bfd_open_closure
and pass down 'warn_if_slow'.
(gdb_bfd_open): Add 'warn_if_slow' parameter. Use
gdb_bfd_open_closure to pass it down.
* gdb_bfd.h (gdb_bfd_open): Add 'warn_if_slow' parameter.
gdb/doc/ChangeLog:
2020-05-19 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Attach): Update exec-file-mismatch description to
mention build IDs.
(Separate Debug Files): Add "build id" anchor.
2020-05-20 01:36:24 +08:00
|
|
|
Set or show the option 'exec-file-mismatch'. When GDB attaches to a
|
|
|
|
|
running process, this new option indicates whether to detect
|
|
|
|
|
a mismatch between the current executable file loaded by GDB and the
|
|
|
|
|
executable file used to start the process. If 'ask', the default,
|
|
|
|
|
display a warning and ask the user whether to load the process
|
|
|
|
|
executable file; if 'warn', just display a warning; if 'off', don't
|
|
|
|
|
attempt to detect a mismatch.
|
2019-12-21 21:47:17 +08:00
|
|
|
|
2020-02-23 02:48:26 +08:00
|
|
|
tui new-layout NAME WINDOW WEIGHT [WINDOW WEIGHT]...
|
|
|
|
|
Define a new TUI layout, specifying its name and the windows that
|
|
|
|
|
will be displayed.
|
|
|
|
|
|
gdb: New maintenance command to print XML target description
This commit adds a new maintenance command that dumps the current
target description as an XML document. This is a maintenance command
as I currently only see this being useful for GDB developers, or for
people debugging a new remote target.
By default the command will print whatever the current target
description is, whether this was delivered by the remote, loaded by
the user from a file, or if it is a built in target within GDB.
The command can also take an optional filename argument. In this case
GDB loads a target description from the file, and then reprints it.
This could be useful for testing GDB's parsing of target descriptions,
or to check that GDB can successfully parse a particular XML
description.
It is worth noting that the XML description printed will not be an
exact copy of the document fed into GDB. For example this minimal
input file:
<target>
<feature name="abc">
<reg name="r1" bitsize="32"/>
</feature>
</target>
Will produce this output:
(gdb) maint print xml-tdesc path/to/file.xml
<?xml version="1.0"?>
<!DOCTYPE target SYSTEM "gdb-target.dtd">
<target>
<feature name="abc">
<reg name="r1" bitsize="32" type="int" regnum="0"/>
</feature>
</target>
Notice that GDB filled in both the 'type' and 'regnum' fields of the
<reg>. I think this is actually a positive as it means we get to
really understand how GDB processed the document, if GDB made some
assumptions that differ to those the user expected then hopefully this
will bring those issues to the users attention.
To implement this I have tweaked the output produced by the
print_xml_feature which is defined within the gdbsupport/ directory.
The changes I have made to this class are:
1. The <architecture>...</architecture> tags are now not produced if
the architecture name is NULL.
2. The <osabi>...</osabi> tags get a newline at the end.
3. And, the whole XML document is indented using white space in a
nested fashion (as in the example output above).
I think that these changes should be fine, the print_xml_feature class
is used:
1. In gdbserver to generate an XML document to send as the target
description to GDB.
2. In GDB as part of a self-check function, a target_desc is
converted to XML then parsed back into a target_desc. We then check
the before and after target_desc objects are the same.
3. In the new 'maint print xml-tdesc' command.
In all of these use cases adding the extra white space should be fine.
gdbsupport/ChangeLog:
* tdesc.cc (print_xml_feature::visit_pre): Use add_line to add
output content, and call indent as needed in all overloaded
variants.
(print_xml_feature::visit_post): Likewise.
(print_xml_feature::visit): Likewise.
(print_xml_feature::add_line): Two new overloaded functions.
* tdesc.h (print_xml_feature::indent): New member function.
(print_xml_feature::add_line): Two new overloaded member
functions.
(print_xml_feature::m_depth): New member variable.
gdb/ChangeLog:
* target-descriptions.c (tdesc_architecture_name): Protect against
NULL pointer dereference.
(maint_print_xml_tdesc_cmd): New function.
(_initialize_target_descriptions): Register new 'maint print
xml-tdesc' command and give it the filename completer.
* NEWS: Mention new 'maint print xml-tdesc' command.
gdb/testsuite/ChangeLog:
* gdb.xml/tdesc-reload.c: New file.
* gdb.xml/tdesc-reload.exp: New file.
* gdb.xml/maint-xml-dump-01.xml: New file.
* gdb.xml/maint-xml-dump-02.xml: New file.
* gdb.xml/maint-xml-dump.exp: New file.
gdb/doc/ChangeLog:
* gdb.texinfo (Maintenance Commands): Document new 'maint print
xml-desc' command.
2020-06-10 06:08:54 +08:00
|
|
|
maintenance print xml-tdesc [FILE]
|
|
|
|
|
Prints the current target description as an XML document. If the
|
|
|
|
|
optional FILE is provided (which is an XML target description) then
|
|
|
|
|
the target description is read from FILE into GDB, and then
|
|
|
|
|
reprinted.
|
|
|
|
|
|
2020-07-04 13:09:20 +08:00
|
|
|
maintenance print core-file-backed-mappings
|
|
|
|
|
Prints file-backed mappings loaded from a core file's note section.
|
|
|
|
|
Output is expected to be similar to that of "info proc mappings".
|
|
|
|
|
|
gdb/fortran: Add support for Fortran array slices at the GDB prompt
This commit brings array slice support to GDB.
WARNING: This patch contains a rather big hack which is limited to
Fortran arrays, this can be seen in gdbtypes.c and f-lang.c. More
details on this below.
This patch rewrites two areas of GDB's Fortran support, the code to
extract an array slice, and the code to print an array.
After this commit a user can, from the GDB prompt, ask for a slice of
a Fortran array and should get the correct result back. Slices can
(optionally) have the lower bound, upper bound, and a stride
specified. Slices can also have a negative stride.
Fortran has the concept of repacking array slices. Within a compiled
Fortran program if a user passes a non-contiguous array slice to a
function then the compiler may have to repack the slice, this involves
copying the elements of the slice to a new area of memory before the
call, and copying the elements back to the original array after the
call. Whether repacking occurs will depend on which version of
Fortran is being used, and what type of function is being called.
This commit adds support for both packed, and unpacked array slicing,
with the default being unpacked.
With an unpacked array slice, when the user asks for a slice of an
array GDB creates a new type that accurately describes where the
elements of the slice can be found within the original array, a
value of this type is then returned to the user. The address of an
element within the slice will be equal to the address of an element
within the original array.
A user can choose to select packed array slices instead using:
(gdb) set fortran repack-array-slices on|off
(gdb) show fortran repack-array-slices
With packed array slices GDB creates a new type that reflects how the
elements of the slice would look if they were laid out in contiguous
memory, allocates a value of this type, and then fetches the elements
from the original array and places then into the contents buffer of
the new value.
One benefit of using packed slices over unpacked slices is the memory
usage, taking a small slice of N elements from a large array will
require (in GDB) N * ELEMENT_SIZE bytes of memory, while an unpacked
array will also include all of the "padding" between the
non-contiguous elements. There are new tests added that highlight
this difference.
There is also a new debugging flag added with this commit that
introduces these commands:
(gdb) set debug fortran-array-slicing on|off
(gdb) show debug fortran-array-slicing
This prints information about how the array slices are being built.
As both the repacking, and the array printing requires GDB to walk
through a multi-dimensional Fortran array visiting each element, this
commit adds the file f-array-walk.h, which introduces some
infrastructure to support this process. This means the array printing
code in f-valprint.c is significantly reduced.
The only slight issue with this commit is the "rather big hack" that I
mentioned above. This hack allows us to handle one specific case,
array slices with negative strides. This is something that I don't
believe the current GDB value contents model will allow us to
correctly handle, and rather than rewrite the value contents code
right now, I'm hoping to slip this hack in as a work around.
The problem is that, as I see it, the current value contents model
assumes that an object base address will be the lowest address within
that object, and that the contents of the object start at this base
address and occupy the TYPE_LENGTH bytes after that.
( We do have the embedded_offset, which is used for C++ sub-classes,
such that an object can start at some offset from the content buffer,
however, the assumption that the object then occupies the next
TYPE_LENGTH bytes is still true within GDB. )
The problem is that Fortran arrays with a negative stride don't follow
this pattern. In this case the base address of the object points to
the element with the highest address, the contents of the array then
start at some offset _before_ the base address, and proceed for one
element _past_ the base address.
As the stride for such an array would be negative then, in theory the
TYPE_LENGTH for this type would also be negative. However, in many
places a value in GDB will degrade to a pointer + length, and the
length almost always comes from the TYPE_LENGTH.
It is my belief that in order to correctly model this case the value
content handling of GDB will need to be reworked to split apart the
value's content buffer (which is a block of memory with a length), and
the object's in memory base address and length, which could be
negative.
Things are further complicated because arrays with negative strides
like this are always dynamic types. When a value has a dynamic type
and its base address needs resolving we actually store the address of
the object within the resolved dynamic type, not within the value
object itself.
In short I don't currently see an easy path to cleanly support this
situation within GDB. And so I believe that leaves two options,
either add a work around, or catch cases where the user tries to make
use of a negative stride, or access an array with a negative stride,
and throw an error.
This patch currently goes with adding a work around, which is that
when we resolve a dynamic Fortran array type, if the stride is
negative, then we adjust the base address to point to the lowest
address required by the array. The printing and slicing code is aware
of this adjustment and will correctly slice and print Fortran arrays.
Where this hack will show through to the user is if they ask for the
address of an array in their program with a negative array stride, the
address they get from GDB will not match the address that would be
computed within the Fortran program.
gdb/ChangeLog:
* Makefile.in (HFILES_NO_SRCDIR): Add f-array-walker.h.
* NEWS: Mention new options.
* f-array-walker.h: New file.
* f-lang.c: Include 'gdbcmd.h' and 'f-array-walker.h'.
(repack_array_slices): New static global.
(show_repack_array_slices): New function.
(fortran_array_slicing_debug): New static global.
(show_fortran_array_slicing_debug): New function.
(value_f90_subarray): Delete.
(skip_undetermined_arglist): Delete.
(class fortran_array_repacker_base_impl): New class.
(class fortran_lazy_array_repacker_impl): New class.
(class fortran_array_repacker_impl): New class.
(fortran_value_subarray): Complete rewrite.
(set_fortran_list): New static global.
(show_fortran_list): Likewise.
(_initialize_f_language): Register new commands.
(fortran_adjust_dynamic_array_base_address_hack): New function.
* f-lang.h (fortran_adjust_dynamic_array_base_address_hack):
Declare.
* f-valprint.c: Include 'f-array-walker.h'.
(class fortran_array_printer_impl): New class.
(f77_print_array_1): Delete.
(f77_print_array): Delete.
(fortran_print_array): New.
(f_value_print_inner): Update to call fortran_print_array.
* gdbtypes.c: Include 'f-lang.h'.
(resolve_dynamic_type_internal): Call
fortran_adjust_dynamic_array_base_address_hack.
gdb/testsuite/ChangeLog:
* gdb.fortran/array-slices-bad.exp: New file.
* gdb.fortran/array-slices-bad.f90: New file.
* gdb.fortran/array-slices-sub-slices.exp: New file.
* gdb.fortran/array-slices-sub-slices.f90: New file.
* gdb.fortran/array-slices.exp: Rewrite tests.
* gdb.fortran/array-slices.f90: Rewrite tests.
* gdb.fortran/vla-sizeof.exp: Correct expected results.
gdb/doc/ChangeLog:
* gdb.texinfo (Debugging Output): Document 'set/show debug
fortran-array-slicing'.
(Special Fortran Commands): Document 'set/show fortran
repack-array-slices'.
2020-10-08 23:45:59 +08:00
|
|
|
set debug fortran-array-slicing on|off
|
|
|
|
|
show debug fortran-array-slicing
|
|
|
|
|
Print debugging when taking slices of Fortran arrays.
|
|
|
|
|
|
|
|
|
|
set fortran repack-array-slices on|off
|
|
|
|
|
show fortran repack-array-slices
|
|
|
|
|
When taking slices from Fortran arrays and strings, if the slice is
|
|
|
|
|
non-contiguous within the original value then, when this option is
|
|
|
|
|
on, the new value will be repacked into a single contiguous value.
|
|
|
|
|
When this option is off, then the value returned will consist of a
|
|
|
|
|
descriptor that describes the slice within the memory of the
|
|
|
|
|
original parent value.
|
|
|
|
|
|
2019-06-25 06:50:29 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
|
|
|
|
alias [-a] [--] ALIAS = COMMAND [DEFAULT-ARGS...]
|
|
|
|
|
The alias command can now specify default args for an alias.
|
|
|
|
|
GDB automatically prepends the alias default args to the argument list
|
|
|
|
|
provided explicitly by the user.
|
|
|
|
|
For example, to have a backtrace with full details, you can define
|
|
|
|
|
an alias 'bt_ALL' as
|
|
|
|
|
'alias bt_ALL = backtrace -entry-values both -frame-arg all
|
|
|
|
|
-past-main -past-entry -full'.
|
|
|
|
|
Alias default arguments can also use a set of nested 'with' commands,
|
|
|
|
|
e.g. 'alias pp10 = with print pretty -- with print elem 10 -- print'
|
|
|
|
|
defines the alias pp10 that will pretty print a maximum of 10 elements
|
|
|
|
|
of the given expression (if the expression is an array).
|
|
|
|
|
|
2020-02-19 09:24:37 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
GNU/Linux/RISC-V (gdbserver) riscv*-*-linux*
|
2020-08-05 00:01:55 +08:00
|
|
|
BPF bpf-unknown-none
|
2020-09-25 19:40:42 +08:00
|
|
|
Z80 z80-unknown-*
|
2020-02-19 09:24:37 +08:00
|
|
|
|
2020-02-23 02:48:26 +08:00
|
|
|
* Python API
|
|
|
|
|
|
|
|
|
|
** gdb.register_window_type can be used to implement new TUI windows
|
|
|
|
|
in Python.
|
|
|
|
|
|
2020-04-25 03:40:31 +08:00
|
|
|
** Dynamic types can now be queried. gdb.Type has a new attribute,
|
|
|
|
|
"dynamic", and gdb.Type.sizeof can be None for a dynamic type. A
|
|
|
|
|
field of a dynamic type may have None for its "bitpos" attribute
|
|
|
|
|
as well.
|
|
|
|
|
|
2020-04-28 22:54:17 +08:00
|
|
|
** Commands written in Python can be in the "TUI" help class by
|
|
|
|
|
registering with the new constant gdb.COMMAND_TUI.
|
|
|
|
|
|
2020-06-08 06:07:52 +08:00
|
|
|
** New method gdb.PendingFrame.architecture () to retrieve the
|
|
|
|
|
architecture of the pending frame.
|
|
|
|
|
|
gdb/python: Add gdb.Architecture.registers method
This commit adds a new method gdb.Architecture.registers that returns
an object of the new type gdb.RegisterDescriptorIterator. This
iterator returns objects of the new type gdb.RegisterDescriptor.
A RegisterDescriptor is not a way to read the value of a register,
this is already covered by Frame.read_register, a RegisterDescriptor
is simply a way to discover from Python, which registers are
available for a given architecture.
I did consider just returning a string, the name of each register,
instead of a RegisterDescriptor, however, I'm aware that it we don't
want to break the existing Python API in any way, so if I return just
a string now, but in the future we want more information about a
register then we would have to add a second API to get that
information. By going straight to a descriptor object now, it is easy
to add additional properties in the future should we wish to.
Right now the only property of a register that a user can access is
the name of the register.
In future we might want to be able to ask the register about is
register groups, or its type.
gdb/ChangeLog:
* Makefile.in (SUBDIR_PYTHON_SRCS): Add py-registers.c
* python/py-arch.c (archpy_registers): New function.
(arch_object_methods): Add 'registers' method.
* python/py-registers.c: New file.
* python/python-internal.h
(gdbpy_new_register_descriptor_iterator): Declare.
(gdbpy_initialize_registers): Declare.
* python/python.c (do_start_initialization): Call
gdbpy_initialize_registers.
* NEWS: Mention additions to the Python API.
gdb/testsuite/ChangeLog:
* gdb.python/py-arch-reg-names.exp: New file.
gdb/doc/ChangeLog:
* python.texi (Python API): Add new section the menu.
(Frames In Python): Add new @anchor.
(Architectures In Python): Document new registers method.
(Registers In Python): New section.
2020-06-06 00:52:10 +08:00
|
|
|
** New gdb.Architecture.registers method that returns a
|
|
|
|
|
gdb.RegisterDescriptorIterator object, an iterator that returns
|
|
|
|
|
gdb.RegisterDescriptor objects. The new RegisterDescriptor is a
|
|
|
|
|
way to query the registers available for an architecture.
|
|
|
|
|
|
2020-06-07 17:08:01 +08:00
|
|
|
** New gdb.Architecture.register_groups method that returns a
|
|
|
|
|
gdb.RegisterGroupIterator object, an iterator that returns
|
|
|
|
|
gdb.RegisterGroup objects. The new RegisterGroup is a way to
|
|
|
|
|
discover the available register groups.
|
|
|
|
|
|
guile: Add support for Guile 2.2.
This primarily updates code that uses the I/O port API of Guile.
gdb/ChangeLog
2020-06-28 Ludovic Courtès <ludo@gnu.org>
Doug Evans <dje@google.com>
PR gdb/21104
* guile/scm-ports.c (USING_GUILE_BEFORE_2_2): New macro.
(ioscm_memory_port)[read_buf_size, write_buf_size]: Wrap in #if
USING_GUILE_BEFORE_2_2.
(stdio_port_desc, memory_port_desc) [!USING_GUILE_BEFORE_2_2]:
Change type to 'scm_t_port_type *'.
(natural_buffer_size) [!USING_GUILE_BEFORE_2_2]: New variable.
(ioscm_open_port) [USING_GUILE_BEFORE_2_2]: Add 'stream'
parameter and honor it. Update callers.
(ioscm_open_port) [!USING_GUILE_BEFORE_2_2]: New function.
(ioscm_read_from_port, ioscm_write) [!USING_GUILE_BEFORE_2_2]: New
functions.
(ioscm_fill_input, ioscm_input_waiting, ioscm_flush): Wrap in #if
USING_GUILE_BEFORE_2_2.
(ioscm_init_gdb_stdio_port) [!USING_GUILE_BEFORE_2_2]: Use
'ioscm_read_from_port'. Call 'scm_set_port_read_wait_fd'.
(ioscm_init_stdio_buffers) [!USING_GUILE_BEFORE_2_2]: New function.
(gdbscm_stdio_port_p) [!USING_GUILE_BEFORE_2_2]: Use 'SCM_PORTP'
and 'SCM_PORT_TYPE'.
(gdbscm_memory_port_end_input, gdbscm_memory_port_seek)
(ioscm_reinit_memory_port): Wrap in #if USING_GUILE_BEFORE_2_2.
(gdbscm_memory_port_read, gdbscm_memory_port_write)
(gdbscm_memory_port_seek, gdbscm_memory_port_close)
[!USING_GUILE_BEFORE_2_2]: New functions.
(gdbscm_memory_port_print): Remove use of 'SCM_PTOB_NAME'.
(ioscm_init_memory_port_type) [!USING_GUILE_BEFORE_2_2]: Use
'gdbscm_memory_port_read'.
Wrap 'scm_set_port_end_input', 'scm_set_port_flush', and
'scm_set_port_free' calls in #if USING_GUILE_BEFORE_2_2.
(gdbscm_get_natural_buffer_sizes) [!USING_GUILE_BEFORE_2_2]: New
function.
(ioscm_init_memory_port): Remove.
(ioscm_init_memory_port_stream): New function
(ioscm_init_memory_port_buffers) [USING_GUILE_BEFORE_2_2]: New
function.
(gdbscm_memory_port_read_buffer_size) [!USING_GUILE_BEFORE_2_2]:
Return scm_from_uint (0).
(gdbscm_set_memory_port_read_buffer_size_x)
[!USING_GUILE_BEFORE_2_2]: Call 'scm_setvbuf'.
(gdbscm_memory_port_write_buffer_size) [!USING_GUILE_BEFORE_2_2]:
Return scm_from_uint (0).
(gdbscm_set_memory_port_write_buffer_size_x)
[!USING_GUILE_BEFORE_2_2]: Call 'scm_setvbuf'.
* configure.ac (try_guile_versions): Add "guile-2.2".
* configure: Regenerate.
* NEWS: Add entry.
gdb/testsuite/ChangeLog
2020-06-28 Ludovic Courtès <ludo@gnu.org>
* gdb.guile/scm-error.exp ("source $remote_guile_file_1"): Relax
error regexp to match on Guile 2.2.
gdb/doc/ChangeLog
2020-06-28 Ludovic Courtès <ludo@gnu.org>
* guile.texi (Memory Ports in Guile): Mark
'memory-port-read-buffer-size',
'set-memory-port-read-buffer-size!',
'memory-port-write-buffer-size',
'set-memory-port-read-buffer-size!' as deprecated.
* doc/guile.texi (Guile Introduction): Clarify which Guile
versions are supported.
Change-Id: Ib119b10a2787446e0ae482a5e1b36d809c44bb31
2020-06-28 22:25:39 +08:00
|
|
|
* Guile API
|
|
|
|
|
|
2020-06-28 22:25:40 +08:00
|
|
|
** GDB can now be built with GNU Guile 3.0 and 2.2 in addition to 2.0.
|
guile: Add support for Guile 2.2.
This primarily updates code that uses the I/O port API of Guile.
gdb/ChangeLog
2020-06-28 Ludovic Courtès <ludo@gnu.org>
Doug Evans <dje@google.com>
PR gdb/21104
* guile/scm-ports.c (USING_GUILE_BEFORE_2_2): New macro.
(ioscm_memory_port)[read_buf_size, write_buf_size]: Wrap in #if
USING_GUILE_BEFORE_2_2.
(stdio_port_desc, memory_port_desc) [!USING_GUILE_BEFORE_2_2]:
Change type to 'scm_t_port_type *'.
(natural_buffer_size) [!USING_GUILE_BEFORE_2_2]: New variable.
(ioscm_open_port) [USING_GUILE_BEFORE_2_2]: Add 'stream'
parameter and honor it. Update callers.
(ioscm_open_port) [!USING_GUILE_BEFORE_2_2]: New function.
(ioscm_read_from_port, ioscm_write) [!USING_GUILE_BEFORE_2_2]: New
functions.
(ioscm_fill_input, ioscm_input_waiting, ioscm_flush): Wrap in #if
USING_GUILE_BEFORE_2_2.
(ioscm_init_gdb_stdio_port) [!USING_GUILE_BEFORE_2_2]: Use
'ioscm_read_from_port'. Call 'scm_set_port_read_wait_fd'.
(ioscm_init_stdio_buffers) [!USING_GUILE_BEFORE_2_2]: New function.
(gdbscm_stdio_port_p) [!USING_GUILE_BEFORE_2_2]: Use 'SCM_PORTP'
and 'SCM_PORT_TYPE'.
(gdbscm_memory_port_end_input, gdbscm_memory_port_seek)
(ioscm_reinit_memory_port): Wrap in #if USING_GUILE_BEFORE_2_2.
(gdbscm_memory_port_read, gdbscm_memory_port_write)
(gdbscm_memory_port_seek, gdbscm_memory_port_close)
[!USING_GUILE_BEFORE_2_2]: New functions.
(gdbscm_memory_port_print): Remove use of 'SCM_PTOB_NAME'.
(ioscm_init_memory_port_type) [!USING_GUILE_BEFORE_2_2]: Use
'gdbscm_memory_port_read'.
Wrap 'scm_set_port_end_input', 'scm_set_port_flush', and
'scm_set_port_free' calls in #if USING_GUILE_BEFORE_2_2.
(gdbscm_get_natural_buffer_sizes) [!USING_GUILE_BEFORE_2_2]: New
function.
(ioscm_init_memory_port): Remove.
(ioscm_init_memory_port_stream): New function
(ioscm_init_memory_port_buffers) [USING_GUILE_BEFORE_2_2]: New
function.
(gdbscm_memory_port_read_buffer_size) [!USING_GUILE_BEFORE_2_2]:
Return scm_from_uint (0).
(gdbscm_set_memory_port_read_buffer_size_x)
[!USING_GUILE_BEFORE_2_2]: Call 'scm_setvbuf'.
(gdbscm_memory_port_write_buffer_size) [!USING_GUILE_BEFORE_2_2]:
Return scm_from_uint (0).
(gdbscm_set_memory_port_write_buffer_size_x)
[!USING_GUILE_BEFORE_2_2]: Call 'scm_setvbuf'.
* configure.ac (try_guile_versions): Add "guile-2.2".
* configure: Regenerate.
* NEWS: Add entry.
gdb/testsuite/ChangeLog
2020-06-28 Ludovic Courtès <ludo@gnu.org>
* gdb.guile/scm-error.exp ("source $remote_guile_file_1"): Relax
error regexp to match on Guile 2.2.
gdb/doc/ChangeLog
2020-06-28 Ludovic Courtès <ludo@gnu.org>
* guile.texi (Memory Ports in Guile): Mark
'memory-port-read-buffer-size',
'set-memory-port-read-buffer-size!',
'memory-port-write-buffer-size',
'set-memory-port-read-buffer-size!' as deprecated.
* doc/guile.texi (Guile Introduction): Clarify which Guile
versions are supported.
Change-Id: Ib119b10a2787446e0ae482a5e1b36d809c44bb31
2020-06-28 22:25:39 +08:00
|
|
|
|
|
|
|
|
** Procedures 'memory-port-read-buffer-size',
|
|
|
|
|
'set-memory-port-read-buffer-size!', 'memory-port-write-buffer-size',
|
|
|
|
|
and 'set-memory-port-write-buffer-size!' are deprecated. When
|
|
|
|
|
using Guile 2.2 and later, users who need to control the size of
|
|
|
|
|
a memory port's internal buffer can use the 'setvbuf' procedure.
|
|
|
|
|
|
2019-12-12 04:44:47 +08:00
|
|
|
*** Changes in GDB 9
|
2019-02-27 12:59:50 +08:00
|
|
|
|
2019-06-07 01:10:14 +08:00
|
|
|
* 'thread-exited' event is now available in the annotations interface.
|
|
|
|
|
|
2019-03-30 17:58:33 +08:00
|
|
|
* New built-in convenience variables $_gdb_major and $_gdb_minor
|
|
|
|
|
provide the GDB version. They are handy for conditionally using
|
|
|
|
|
features available only in or since specific GDB versions, in
|
|
|
|
|
scripts that should work error-free with many different versions,
|
|
|
|
|
such as in system-wide init files.
|
|
|
|
|
|
2019-04-28 20:44:44 +08:00
|
|
|
* New built-in convenience functions $_gdb_setting, $_gdb_setting_str,
|
|
|
|
|
$_gdb_maint_setting and $_gdb_maint_setting_str provide access to values
|
|
|
|
|
of the GDB settings and the GDB maintenance settings. They are handy
|
|
|
|
|
for changing the logic of user defined commands depending on the
|
|
|
|
|
current GDB settings.
|
|
|
|
|
|
2019-03-26 04:23:26 +08:00
|
|
|
* GDB now supports Thread Local Storage (TLS) variables on several
|
|
|
|
|
FreeBSD architectures (amd64, i386, powerpc, riscv). Other
|
|
|
|
|
architectures require kernel changes. TLS is not yet supported for
|
|
|
|
|
amd64 and i386 process core dumps.
|
|
|
|
|
|
2019-08-07 16:47:57 +08:00
|
|
|
* Support for Pointer Authentication (PAC) on AArch64 Linux. Return
|
|
|
|
|
addresses that required unmasking are shown in the backtrace with the
|
|
|
|
|
postfix [PAC].
|
2019-03-27 00:44:04 +08:00
|
|
|
|
2019-05-28 04:53:12 +08:00
|
|
|
* Two new convenience functions $_cimag and $_creal that extract the
|
2019-03-14 21:58:58 +08:00
|
|
|
imaginary and real parts respectively from complex numbers.
|
|
|
|
|
|
2019-06-15 02:30:17 +08:00
|
|
|
* New built-in convenience variables $_shell_exitcode and $_shell_exitsignal
|
|
|
|
|
provide the exitcode or exit status of the shell commands launched by
|
|
|
|
|
GDB commands such as "shell", "pipe" and "make".
|
|
|
|
|
|
2019-09-29 01:30:08 +08:00
|
|
|
* The command define-prefix can now define user defined prefix commands.
|
|
|
|
|
User defined commands can now be defined using these user defined prefix
|
|
|
|
|
commands.
|
|
|
|
|
|
|
|
|
|
* Command names can now use the . character.
|
|
|
|
|
|
2019-08-20 23:24:37 +08:00
|
|
|
* The RX port now supports XML target descriptions.
|
|
|
|
|
|
Output the Ada task name in more messages.
With this patch, we e.g. get:
[Switching to task 2 "task_list(1)"]
[Current task is 2 "task_list(1)"]
instead of
[Switching to task 2]
[Current task is 2]
The logic to produce the taskno optionally followed
by the task name has been factorized in the task_to_str function.
Task names are output between double quotes in the new messages,
similarly to what GDB does for thread names.
However, no quotes are put around task names in 'info tasks' Name column.
This was discussed with Tom, that preferred no quotes there, while I
was more in favour of visual consistency.
I discussed with a few more users, which led to (exactly) 50% preferring
quotes and 50% preferring no quotes :).
To arrive to the decision to remove the quotes, the following "killing args"
were used:
* To have quotes or to not have quotes, that is the question; yes
but not *THE* question :).
* If there is not a clear majority that prefers quotes, better to
not disturb the existing user basis for a (somewhat) irrelevant
aspect.
* The opinion of the reviewer has more weight.
So, compared to the previous version, this version remotes the quotes
in 'info tasks'.
It improves the alignement of 'info tasks' output.
With this patch, we get:
(gdb) info task
ID TID P-ID Pri State Name
* 1 555555759030 48 Runnable main_task
2 555555759e30 1 48 Selective Wait mit
(gdb)
instead of
(gdb) info task
ID TID P-ID Pri State Name
* 1 555555759030 48 Runnable main_task
2 555555759e30 1 48 Selective Wait mit
(gdb)
(e.g. the first one properly shows parent and priority under the
correct header).
This is version 4 of the 'task name' patch.
Compared to version 3, the changes are:
output task names between quotes but not in 'info tasks'
gdb/ChangeLog
2019-09-12 Philippe Waroquiers <philippe.waroquiers@skynet.be>
* NEWS: Announce that Ada task names are now shown at more places,
and between quotes (except in info task output).
* gdb/ada-tasks.c (task_to_str): New function.
(display_current_task_id): Call task_to_str.
(task_command_1): Likewise.
(print_ada_task_info): In non-mi mode, Properly align headers and data
when task-id length is > 9 (9 is the default for a 32 bits CORE_ADDR).
gdb/doc/ChangeLog
2019-09-12 Philippe Waroquiers <philippe.waroquiers@skynet.be>
* gdb.texinfo (Ada Tasks): Tell the task name is printed, update
examples.
gdb/testsuite/ChangeLog
2019-09-12 Philippe Waroquiers <philippe.waroquiers@skynet.be>
* gdb.ada/rdv_wait.exp: Update to new task names.
* gdb.base/task_switch_in_core.exp: Likewise.
* gdb.base/info_sources_base.c: Likewise.
2019-06-09 01:47:51 +08:00
|
|
|
* GDB now shows the Ada task names at more places, e.g. in task switching
|
|
|
|
|
messages.
|
|
|
|
|
|
2019-09-15 04:28:51 +08:00
|
|
|
* GDB can now be compiled with Python 3 on Windows.
|
|
|
|
|
|
Add $_ada_exception convenience variable
This adds the $_ada_exception convenience variable. It is set by the
Ada exception catchpoints, and holds the address of the exception
currently being thrown. This is useful because it allows more
fine-grained filtering of exceptions than is possible using the
existing "catch" syntax.
This also simplifies Ada catchpoints somewhat; because the catchpoint
must now carry the "kind", it's possible to remove many helper
functions.
gdb/ChangeLog
2019-10-02 Tom Tromey <tromey@adacore.com>
* NEWS: Add $_ada_exception entry.
* ada-lang.c (struct ada_catchpoint): Add constructor.
<m_kind>: New member.
(allocate_location_exception, re_set_exception): Remove
"ex" parameter.
(should_stop_exception): Compute $_ada_exception.
(check_status_exception, print_it_exception)
(print_one_exception, print_mention_exception): Remove
"ex" parameter.
(allocate_location_catch_exception, re_set_catch_exception)
(check_status_exception, print_it_catch_exception)
(print_one_catch_exception, print_mention_catch_exception)
(print_recreate_catch_exception)
(allocate_location_catch_exception_unhandled)
(re_set_catch_exception_unhandled)
(check_status_exception, print_it_catch_exception_unhandled)
(print_one_catch_exception_unhandled)
(print_mention_catch_exception_unhandled)
(print_recreate_catch_exception_unhandled)
(allocate_location_catch_assert, re_set_catch_assert)
(check_status_assert, print_it_catch_assert)
(print_one_catch_assert, print_mention_catch_assert)
(print_recreate_catch_assert)
(allocate_location_catch_handlers, re_set_catch_handlers)
(check_status_handlers, print_it_catch_handlers)
(print_one_catch_handlers, print_mention_catch_handlers)
(print_recreate_catch_handlers): Remove.
(create_ada_exception_catchpoint): Update.
(initialize_ada_catchpoint_ops): Update.
gdb/doc/ChangeLog
2019-10-02 Tom Tromey <tromey@adacore.com>
* gdb.texinfo (Set Catchpoints, Convenience Vars): Document
$_ada_exception.
gdb/testsuite/ChangeLog
2019-10-02 Tom Tromey <tromey@adacore.com>
* gdb.ada/catch_ex_std.exp: Add $_ada_exception test.
2019-06-01 04:50:23 +08:00
|
|
|
* New convenience variable $_ada_exception holds the address of the
|
|
|
|
|
Ada exception being thrown. This is set by Ada-related catchpoints.
|
|
|
|
|
|
2019-09-03 06:31:10 +08:00
|
|
|
* GDB can now place breakpoints on nested functions and subroutines in
|
|
|
|
|
Fortran code. The '::' operator can be used between parent and
|
|
|
|
|
child scopes when placing breakpoints, for example:
|
|
|
|
|
|
|
|
|
|
(gdb) break outer_function::inner_function
|
|
|
|
|
|
|
|
|
|
The 'outer_function::' prefix is only needed if 'inner_function' is
|
|
|
|
|
not visible in the current scope.
|
|
|
|
|
|
2019-10-13 20:12:34 +08:00
|
|
|
* In addition to the system-wide gdbinit file, if configured with
|
|
|
|
|
--with-system-gdbinit-dir, GDB will now also load files in that directory
|
|
|
|
|
as system gdbinit files, unless the -nx or -n flag is provided. Files
|
|
|
|
|
with extensions .gdb, .py and .scm are supported as long as GDB was
|
|
|
|
|
compiled with support for that language.
|
|
|
|
|
|
2019-11-27 05:59:36 +08:00
|
|
|
* GDB now supports multithreaded symbol loading for higher performance.
|
|
|
|
|
This feature is still in testing, so it is disabled by default. You
|
|
|
|
|
can turn it on using 'maint set worker-threads unlimited'.
|
|
|
|
|
|
2019-04-01 15:59:53 +08:00
|
|
|
* Python API
|
|
|
|
|
|
|
|
|
|
** The gdb.Value type has a new method 'format_string' which returns a
|
|
|
|
|
string representing the value. The formatting is controlled by the
|
|
|
|
|
optional keyword arguments: 'raw', 'pretty_arrays', 'pretty_structs',
|
|
|
|
|
'array_indexes', 'symbols', 'unions', 'deref_refs', 'actual_objects',
|
|
|
|
|
'static_members', 'max_elements', 'repeat_threshold', and 'format'.
|
|
|
|
|
|
2019-05-24 05:37:29 +08:00
|
|
|
** gdb.Type has a new property 'objfile' which returns the objfile the
|
|
|
|
|
type was defined in.
|
|
|
|
|
|
2019-05-05 05:48:36 +08:00
|
|
|
** The frame information printed by the python frame filtering code
|
|
|
|
|
is now consistent with what the 'backtrace' command prints when
|
|
|
|
|
there are no filters, or when the 'backtrace' '-no-filters' option
|
|
|
|
|
is given.
|
|
|
|
|
|
2019-07-31 00:04:37 +08:00
|
|
|
** The new function gdb.lookup_static_symbol can be used to look up
|
|
|
|
|
symbols with static linkage.
|
|
|
|
|
|
2019-10-15 23:18:26 +08:00
|
|
|
** The new function gdb.lookup_static_symbols can be used to look up
|
|
|
|
|
all static symbols with static linkage.
|
|
|
|
|
|
2019-06-26 04:45:41 +08:00
|
|
|
** gdb.Objfile has new methods 'lookup_global_symbol' and
|
|
|
|
|
'lookup_static_symbol' to lookup a symbol from this objfile only.
|
|
|
|
|
|
2019-08-02 06:22:28 +08:00
|
|
|
** gdb.Block now supports the dictionary syntax for accessing symbols in
|
|
|
|
|
this block (e.g. block['local_variable']).
|
|
|
|
|
|
2019-04-24 05:43:24 +08:00
|
|
|
* New commands
|
|
|
|
|
|
2019-05-04 21:39:27 +08:00
|
|
|
| [COMMAND] | SHELL_COMMAND
|
|
|
|
|
| -d DELIM COMMAND DELIM SHELL_COMMAND
|
|
|
|
|
pipe [COMMAND] | SHELL_COMMAND
|
|
|
|
|
pipe -d DELIM COMMAND DELIM SHELL_COMMAND
|
|
|
|
|
Executes COMMAND and sends its output to SHELL_COMMAND.
|
|
|
|
|
With no COMMAND, repeat the last executed command
|
|
|
|
|
and send its output to SHELL_COMMAND.
|
|
|
|
|
|
2019-09-29 01:30:08 +08:00
|
|
|
define-prefix COMMAND
|
|
|
|
|
Define or mark a command as a user-defined prefix command.
|
|
|
|
|
|
Introduce the "with" command
( See original discussion and prototype here:
https://sourceware.org/ml/gdb-patches/2019-05/msg00570.html )
(gdb) help with
Temporarily set SETTING to VALUE, run COMMAND, and restore SETTING.
Usage: with SETTING [VALUE] [-- COMMAND]
Usage: w SETTING [VALUE] [-- COMMAND]
With no COMMAND, repeats the last executed command.
SETTING is any setting you can change with the "set" subcommands.
E.g.:
with language pascal -- print obj
with print elements unlimited -- print obj
As can be seen above, the "with" command is just like "set", but
instead of setting the setting permanently, it sets the setting, runs
a command and then restores the setting.
(gdb) p g_s
$1 = {a = 1, b = 2, c = 3}
(gdb) with language ada -- print g_s
$2 = (a => 1, b => 2, c => 3)
Warning: the current language does not match this frame.
(gdb) show language
The current source language is "auto; currently c".
(gdb) with print elements 100 -- with print object on -- print 1
$3 = 1
You can shorten things a bit though, as long as unambiguous. So this:
(gdb) with print elements 100 -- with print object off -- print 1
is the same as:
(gdb) w p el 100 -- w p o 0 -- p 1
Note that the patch adds a "w" alias for "with", as "w" is not
currently taken:
(gdb) w
Ambiguous command "w": watch, wh, whatis, where, while, while-stepping, winheight, ws.
Let me know if you'd prefer to reserve "w" for one of the other
commands above. IMHO, this command will end up being used frequently
enough that it deserves the "w" shorthand.
A nice feature is that this is fully integrated with TAB-completion:
(gdb) with p[TAB]
pagination print prompt python
(gdb) with print [TAB]
address max-depth static-members
array max-symbolic-offset symbol
array-indexes null-stop symbol-filename
asm-demangle object symbol-loading
demangle pascal_static-members thread-events
elements pretty type
entry-values raw union
frame-arguments repeats vtbl
inferior-events sevenbit-strings
(gdb) with print [TAB]
(gdb) with print elements unlimited -- thread apply all -[TAB]
-ascending -c -q -s
(gdb) with print elements unlimited -- print -[TAB]
-address -max-depth -repeats -vtbl
-array -null-stop -static-members
-array-indexes -object -symbol
-elements -pretty -union
The main advantage of this new command compared to command options,
like the new "print -OPT", is that this command works with any
setting, and, it works nicely when you want to override a setting
while running a user-defined command, like:
(gdb) with print pretty -- usercmd
The disadvantage is that it isn't as compact or easy to type. I think
of command options and this command as complementary. I think that
even with this new command, it makes sense to continue developing the
command options in the direction of exposing most-oft-used settings as
command options.
Inspired by Philippe's "/" command proposal, if no command is
specified, then the last command is re-invoked, under the overridden
setting:
(gdb) p g_s
$1 = {a = 1, b = 2, c = 3}
(gdb) with language ada
$2 = (a => 1, b => 2, c => 3)
Warning: the current language does not match this frame.
Note: "with" requires "--" to separate the setting from the command.
It might be possible to do without that, but, I haven't tried it yet,
and I think that this can go in without it. We can always downgrade
to making "--" optional if we manage to make it work.
On to the patch itself, the implementation of the command is simpler
than one might expect. A few details:
- I factored out a bit from pipe_command into repeat_previous
directly, because otherwise I'd need to copy&paste the same code and
same error message in the with command.
- The parse_cli_var_uinteger / parse_cli_var_zuinteger_unlimited /
do_set_command changes are necessary since we can now pass an empty
string as argument.
- do_show_command was split in two, as a FIXME comment suggests, but
for a different reason: we need to get a string version of a "set"
command's value, and we already had code for that in
do_show_command. That code is now factored out to the new
get_setshow_command_value_string function.
- There's a new "maint with" command added too:
(gdb) help maint with
Like "with", but works with "maintenance set" variables.
Usage: maintenance with SETTING [VALUE] [-- COMMAND]
With no COMMAND, repeats the last executed command.
SETTING is any setting you can change with the "maintenance set"
subcommands.
"with" and "maint with" share 99% of the implementation.
This might be useful on its own, but it's also useful for testing,
since with this, we can use the "maint set/show test-settings"
settings for exercising the "with" machinery with all the command
type variants (all enum var_types). This is done in the new
gdb/base/with.exp testcase.
The documentation bits are originally based on Philippe's docs for the
"/" command, hence the attribution in the ChangeLog.
gdb/ChangeLog:
2019-07-03 Pedro Alves <palves@redhat.com>
* NEWS (New commands): Mention "with" and "maint with".
* cli/cli-cmds.c (with_command_1, with_command_completer_1)
(with_command, with_command_completer): New.
(pipe_command): Adjust to new repeat_previous
interface.
(_initialize_cli_cmds): Install the "with" command and its "w"
alias.
* cli/cli-cmds.h (with_command_1, with_command_completer_1): New
declarations.
* cli/cli-setshow.c (parse_cli_var_uinteger)
(parse_cli_var_zuinteger_unlimited, do_set_command): Handle empty
argument strings for all var_types.
(get_setshow_command_value_string): New, factored out from ...
(do_show_command): ... this.
* cli/cli-setshow.h: Include <string>.
(get_setshow_command_value_string): Declare.
* command.h (repeat_previous): Now returns const char *. Adjust
comment.
* maint.c: Include "cli/cli-cmds.h".
(maintenance_with_cmd, maintenance_with_cmd_completer): New.
(_initialize_maint_cmds): Register the "maintenance with" command.
* top.c (repeat_previous): Move bits from pipe_command here:
Return the saved command line, if any; error out if there's no
command to relaunch.
gdb/doc/ChangeLog:
2019-07-03 Pedro Alves <palves@redhat.com>
Philippe Waroquiers <philippe.waroquiers@skynet.be>
* gdb.texinfo (Command Settings): New node documenting the general
concept of settings, how to change them, and the new "with"
command.
(Maintenance Commands): Document "maint with".
gdb/testsuite/ChangeLog:
2019-07-03 Pedro Alves <palves@redhat.com>
* gdb.base/with.c: New file.
* gdb.base/with.exp: New file.
2019-07-03 20:34:20 +08:00
|
|
|
with SETTING [VALUE] [-- COMMAND]
|
|
|
|
|
w SETTING [VALUE] [-- COMMAND]
|
|
|
|
|
Temporarily set SETTING, run COMMAND, and restore SETTING.
|
|
|
|
|
Usage: with SETTING -- COMMAND
|
|
|
|
|
With no COMMAND, repeats the last executed command.
|
|
|
|
|
SETTING is any GDB setting you can change with the "set"
|
|
|
|
|
subcommands. For example, 'with language c -- print someobj'
|
|
|
|
|
temporarily switches to the C language in order to print someobj.
|
|
|
|
|
Settings can be combined: 'w lang c -- w print elements unlimited --
|
|
|
|
|
usercmd' switches to the C language and runs usercmd with no limit
|
|
|
|
|
of array elements to print.
|
|
|
|
|
|
|
|
|
|
maint with SETTING [VALUE] [-- COMMAND]
|
|
|
|
|
Like "with", but works with "maintenance set" settings.
|
|
|
|
|
|
2019-04-24 05:43:24 +08:00
|
|
|
set may-call-functions [on|off]
|
|
|
|
|
show may-call-functions
|
|
|
|
|
This controls whether GDB will attempt to call functions in
|
|
|
|
|
the program, such as with expressions in the print command. It
|
|
|
|
|
defaults to on. Calling functions in the program being debugged
|
|
|
|
|
can have undesired side effects. It is now possible to forbid
|
|
|
|
|
such function calls. If function calls are forbidden, GDB will throw
|
|
|
|
|
an error when a command (such as print expression) calls a function
|
|
|
|
|
in the program.
|
|
|
|
|
|
2019-05-16 03:06:59 +08:00
|
|
|
set print finish [on|off]
|
|
|
|
|
show print finish
|
|
|
|
|
This controls whether the `finish' command will display the value
|
|
|
|
|
that is returned by the current function. When `off', the value is
|
|
|
|
|
still entered into the value history, but it is not printed. The
|
|
|
|
|
default is `on'.
|
|
|
|
|
|
2019-05-09 03:59:50 +08:00
|
|
|
set print max-depth
|
|
|
|
|
show print max-depth
|
|
|
|
|
Allows deeply nested structures to be simplified when printing by
|
|
|
|
|
replacing deeply nested parts (beyond the max-depth) with ellipses.
|
|
|
|
|
The default max-depth is 20, but this can be set to unlimited to get
|
|
|
|
|
the old behavior back.
|
|
|
|
|
|
2019-08-08 02:50:54 +08:00
|
|
|
set print raw-values [on|off]
|
|
|
|
|
show print raw-values
|
|
|
|
|
By default, GDB applies the enabled pretty printers when printing a
|
|
|
|
|
value. This allows to ignore the enabled pretty printers for a series
|
|
|
|
|
of commands. The default is 'off'.
|
|
|
|
|
|
2019-05-22 20:40:20 +08:00
|
|
|
set logging debugredirect [on|off]
|
|
|
|
|
By default, GDB debug output will go to both the terminal and the logfile.
|
|
|
|
|
Set if you want debug output to go only to the log file.
|
|
|
|
|
|
2019-06-04 03:51:56 +08:00
|
|
|
set style title foreground COLOR
|
|
|
|
|
set style title background COLOR
|
|
|
|
|
set style title intensity VALUE
|
|
|
|
|
Control the styling of titles.
|
|
|
|
|
|
|
|
|
|
set style highlight foreground COLOR
|
|
|
|
|
set style highlight background COLOR
|
|
|
|
|
set style highlight intensity VALUE
|
|
|
|
|
Control the styling of highlightings.
|
|
|
|
|
|
2019-03-17 04:36:57 +08:00
|
|
|
maint set worker-threads
|
|
|
|
|
maint show worker-threads
|
|
|
|
|
Control the number of worker threads that can be used by GDB. The
|
2019-11-27 05:59:36 +08:00
|
|
|
default is 0. "unlimited" lets GDB choose a number that is
|
2019-03-17 04:36:57 +08:00
|
|
|
reasonable. Currently worker threads are only used when demangling
|
|
|
|
|
the names of linker symbols.
|
|
|
|
|
|
2019-11-10 05:13:13 +08:00
|
|
|
set style tui-border foreground COLOR
|
|
|
|
|
set style tui-border background COLOR
|
|
|
|
|
Control the styling of TUI borders.
|
|
|
|
|
|
|
|
|
|
set style tui-active-border foreground COLOR
|
|
|
|
|
set style tui-active-border background COLOR
|
|
|
|
|
Control the styling of the active TUI border.
|
|
|
|
|
|
2019-07-03 20:34:19 +08:00
|
|
|
maint set test-settings KIND
|
|
|
|
|
maint show test-settings KIND
|
2019-06-13 07:06:52 +08:00
|
|
|
A set of commands used by the testsuite for exercising the settings
|
|
|
|
|
infrastructure.
|
|
|
|
|
|
Make TUI resizing tests more robust
As Sergio pointed out, the TUI resizing tests are flaky. Debugging
this showed three main problems.
1. expect's "stty" command processes its arguments one-by-one. So,
rather than requesting a single resize, it sends two separate resize
requests (one for rows and one for columns). This means gdb sees two
SIGWINCH signals and resizes the terminal twice.
I consider this a bug in expect, but I couldn't readily see how to
report a bug; and anyway the fix wouldn't propagate very quickly.
This patch works around this problem by explicitly doing two separate
resizes (so it will be robust if expect ever does change); and then by
waiting for each resize to complete before continuing.
2. gdb uses curses to drive the console rendering. Currently the test
suite looks for terminal text insertion sequences to decide when a
command has completed. However, it turns out that, sometimes, curses
can output things in non-obvious ways. I didn't debug into curses but
I guess this can happen due to output optimizations. No matter the
reason, sometimes the current approach of only tracking text
insertions is not enough to detect that gdb has finished rendering.
This patch fixes this problem by arranging to detect the termination
output after any curses command, not just insertion.
3. Detecting when a resize has completed is tricky. In fact, I could
not find a way to reliably do this.
This patch fixes this problem by adding a special maint
"tui-resize-message" setting to gdb. When this is enabled, gdb will
print a message after each SIGWINCH has been fully processed. The
test suite enables this mode and then waits for the message in order
to know when control can be returned to the calling test.
This patch also adds a timeout, to avoid the situation where the
terminal code fails to notice a change for some reason. This lets the
test at least try to continue.
gdb/ChangeLog
2019-11-12 Tom Tromey <tom@tromey.com>
* tui/tui-win.c (resize_message): New global.
(show_tui_resize_message): New function.
(tui_async_resize_screen): Print message if requested.
(_initialize_tui_win): Add tui-resize-message setting.
* NEWS: Add entry for new commands.
gdb/doc/ChangeLog
2019-11-12 Tom Tromey <tom@tromey.com>
* gdb.texinfo (Maintenance Commands): Document new command.
gdb/testsuite/ChangeLog
2019-11-12 Tom Tromey <tom@tromey.com>
* lib/tuiterm.exp (_accept): Add wait_for parameter. Check output
after any command. Expect prompt after WAIT_FOR is seen.
(enter_tui): Enable resize messages.
(command): Expect command in output.
(get_line): Avoid error when cursor appears to be off-screen.
(dump_screen): Include screen size in title.
(_do_resize): New proc, from "resize".
(resize): Rewrite. Do resize in two steps.
* gdb.tui/empty.exp (layouts): Fix entries.
(check_boxes): Remove xfail.
(check_text): Dump screen on failure.
Change-Id: I420e0259cb99b21adcd28f671b99161eefa7a51d
2019-08-17 05:16:12 +08:00
|
|
|
maint set tui-resize-message [on|off]
|
|
|
|
|
maint show tui-resize-message
|
|
|
|
|
Control whether GDB prints a message each time the terminal is
|
|
|
|
|
resized when in TUI mode. This is primarily useful for testing the
|
|
|
|
|
TUI.
|
|
|
|
|
|
2019-05-05 05:48:36 +08:00
|
|
|
set print frame-info [short-location|location|location-and-address
|
|
|
|
|
|source-and-location|source-line|auto]
|
|
|
|
|
show print frame-info
|
|
|
|
|
This controls what frame information is printed by the commands printing
|
|
|
|
|
a frame. This setting will e.g. influence the behaviour of 'backtrace',
|
|
|
|
|
'frame', 'stepi'. The python frame filtering also respect this setting.
|
|
|
|
|
The 'backtrace' '-frame-info' option can override this global setting.
|
|
|
|
|
|
2019-07-12 07:06:00 +08:00
|
|
|
set tui compact-source
|
|
|
|
|
show tui compact-source
|
|
|
|
|
|
|
|
|
|
Enable the "compact" display mode for the TUI source window. The
|
|
|
|
|
compact display uses only as much space as is needed for the line
|
|
|
|
|
numbers in the current file, and only a single space to separate the
|
|
|
|
|
line numbers from the source.
|
|
|
|
|
|
2019-07-10 04:38:59 +08:00
|
|
|
info modules [-q] [REGEXP]
|
|
|
|
|
Return a list of Fortran modules matching REGEXP, or all modules if
|
|
|
|
|
no REGEXP is given.
|
|
|
|
|
|
gdb: Add new commands to list module variables and functions
This patch adds two new commands "info module functions" and "info
module variables". These commands list all of the functions and
variables grouped by module and then by file.
For example:
(gdb) info module functions
All functions in all modules:
Module "mod1":
File /some/path/gdb/testsuite/gdb.fortran/info-types.f90:
35: void mod1::__copy_mod1_M1t1(Type m1t1, Type m1t1);
25: void mod1::sub_m1_a(integer(kind=4));
31: integer(kind=4) mod1::sub_m1_b(void);
Module "mod2":
File /some/path/gdb/testsuite/gdb.fortran/info-types.f90:
41: void mod2::sub_m2_a(integer(kind=4), logical(kind=4));
49: logical(kind=4) mod2::sub_m2_b(real(kind=4));
The new commands take set of flags that allow the output to be
filtered, the user can filter by variable/function name, type, or
containing module.
As GDB doesn't currently track the relationship between a module and
the variables or functions within it in the symbol table, so I filter
based on the module prefix in order to find the functions or variables
in each module. What this makes clear is that a user could get this
same information using "info variables" and simply provide the prefix
themselves, for example:
(gdb) info module functions -m mod1 _a
All functions matching regular expression "_a",
in all modules matching regular expression "mod1":
Module "mod1":
File /some/path/gdb/testsuite/gdb.fortran/info-types.f90:
25: void mod1::sub_m1_a(integer(kind=4));
Is similar to:
(gdb) info functions mod1::.*_a.*
All functions matching regular expression "mod1::.*_a":
File /some/path/gdb/testsuite/gdb.fortran/info-types.f90:
25: void mod1::sub_m1_a(integer(kind=4));
The benefits I see for a separate command are that the user doesn't
have to think (or know) about the module prefix format, nor worry
about building a proper regexp. The user can also easily scan across
modules without having to build complex regexps.
The new function search_module_symbols is extern in this patch despite
only being used within symtab.c, this is because a later patch in this
series will also be using this function from outside symtab.c.
This patch is a new implementation of an idea originally worked on by
Mark O'Connor, Chris January, David Lecomber, and Xavier Oro from ARM.
gdb/ChangeLog:
* symtab.c (info_module_cmdlist): New variable.
(info_module_command): New function.
(search_module_symbols): New function.
(info_module_subcommand): New function.
(struct info_modules_var_func_options): New struct.
(info_modules_var_func_options_defs): New variable.
(make_info_modules_var_func_options_def_group): New function.
(info_module_functions_command): New function.
(info_module_variables_command): New function.
(info_module_var_func_command_completer): New function.
(_initialize_symtab): Register new 'info module functions' and
'info module variables' commands.
* symtab.h (typedef symbol_search_in_module): New typedef.
(search_module_symbols): Declare new function.
* NEWS: Mention new commands.
gdb/doc/ChangeLog:
* gdb.texinfo (Symbols): Document new 'info module variables' and
'info module functions' commands.
gdb/testsuite/ChangeLog:
* gdb.fortran/info-modules.exp: Update expected results, and add
additional tests for 'info module functinos', and 'info module
variables'.
* gdb.fortran/info-types.exp: Update expected results.
* gdb.fortran/info-types.f90: Extend testcase with additional
module variables and functions.
Change-Id: I8c2960640e2e101b77eff54027d687e21ec22e2b
2019-07-10 22:54:03 +08:00
|
|
|
info module functions [-q] [-m MODULE_REGEXP] [-t TYPE_REGEXP] [REGEXP]
|
|
|
|
|
Return a list of functions within all modules, grouped by module.
|
|
|
|
|
The list of functions can be restricted with the optional regular
|
|
|
|
|
expressions. MODULE_REGEXP matches against the module name,
|
|
|
|
|
TYPE_REGEXP matches against the function type signature, and REGEXP
|
|
|
|
|
matches against the function name.
|
|
|
|
|
|
|
|
|
|
info module variables [-q] [-m MODULE_REGEXP] [-t TYPE_REGEXP] [REGEXP]
|
|
|
|
|
Return a list of variables within all modules, grouped by module.
|
|
|
|
|
The list of variables can be restricted with the optional regular
|
|
|
|
|
expressions. MODULE_REGEXP matches against the module name,
|
|
|
|
|
TYPE_REGEXP matches against the variable type, and REGEXP matches
|
|
|
|
|
against the variable name.
|
|
|
|
|
|
2019-11-25 23:27:44 +08:00
|
|
|
set debug remote-packet-max-chars
|
|
|
|
|
show debug remote-packet-max-chars
|
|
|
|
|
Controls the number of characters to output in a remote packet when using
|
|
|
|
|
"set debug remote".
|
|
|
|
|
The default is 512 bytes.
|
|
|
|
|
|
2020-01-11 04:06:15 +08:00
|
|
|
info connections
|
|
|
|
|
Lists the target connections currently in use.
|
|
|
|
|
|
2019-06-04 03:51:56 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
|
|
|
|
help
|
|
|
|
|
The "help" command uses the title style to enhance the
|
|
|
|
|
readibility of its output by styling the classes and
|
|
|
|
|
command names.
|
|
|
|
|
|
|
|
|
|
apropos [-v] REGEXP
|
|
|
|
|
Similarly to "help", the "apropos" command also uses the
|
|
|
|
|
title style for the command names. "apropos" accepts now
|
|
|
|
|
a flag "-v" (verbose) to show the full documentation
|
|
|
|
|
of matching commands and to use the highlight style to mark
|
|
|
|
|
the documentation parts matching REGEXP.
|
|
|
|
|
|
2019-06-11 03:41:51 +08:00
|
|
|
printf
|
|
|
|
|
eval
|
|
|
|
|
The GDB printf and eval commands can now print C-style and Ada-style
|
|
|
|
|
string convenience variables without calling functions in the program.
|
|
|
|
|
This allows to do formatted printing of strings without having
|
|
|
|
|
a running inferior, or when debugging a core dump.
|
|
|
|
|
|
2019-08-04 03:20:44 +08:00
|
|
|
info sources [-dirname | -basename] [--] [REGEXP]
|
|
|
|
|
This command has now optional arguments to only print the files
|
|
|
|
|
whose names match REGEXP. The arguments -dirname and -basename
|
|
|
|
|
allow to restrict matching respectively to the dirname and basename
|
|
|
|
|
parts of the files.
|
|
|
|
|
|
2019-06-04 03:51:56 +08:00
|
|
|
show style
|
|
|
|
|
The "show style" and its subcommands are now styling
|
|
|
|
|
a style name in their output using its own style, to help
|
|
|
|
|
the user visualize the different styles.
|
|
|
|
|
|
2019-05-05 05:48:36 +08:00
|
|
|
set print frame-arguments
|
|
|
|
|
The new value 'presence' indicates to only indicate the presence of
|
|
|
|
|
arguments using ..., instead of printing argument names and values.
|
|
|
|
|
|
2019-06-13 07:06:53 +08:00
|
|
|
set print raw-frame-arguments
|
|
|
|
|
show print raw-frame-arguments
|
|
|
|
|
|
|
|
|
|
These commands replace the similarly-named "set/show print raw
|
|
|
|
|
frame-arguments" commands (now with a dash instead of a space). The
|
|
|
|
|
old commands are now deprecated and may be removed in a future
|
|
|
|
|
release.
|
2019-06-04 03:51:56 +08:00
|
|
|
|
2020-01-11 04:06:15 +08:00
|
|
|
add-inferior [-no-connection]
|
|
|
|
|
The add-inferior command now supports a "-no-connection" flag that
|
|
|
|
|
makes the new inferior start with no target connection associated.
|
|
|
|
|
By default, the new inferior inherits the target connection of the
|
|
|
|
|
current inferior. See also "info connections".
|
|
|
|
|
|
|
|
|
|
info inferior
|
|
|
|
|
This command's output now includes a new "Connection" column
|
|
|
|
|
indicating which target connection an inferior is bound to. See
|
|
|
|
|
"info connections" above.
|
|
|
|
|
|
2019-06-13 07:06:54 +08:00
|
|
|
maint test-options require-delimiter
|
|
|
|
|
maint test-options unknown-is-error
|
|
|
|
|
maint test-options unknown-is-operand
|
|
|
|
|
maint show test-options-completion-result
|
|
|
|
|
Commands used by the testsuite to validate the command options
|
|
|
|
|
framework.
|
|
|
|
|
|
2019-07-24 06:01:03 +08:00
|
|
|
focus, winheight, +, -, >, <
|
|
|
|
|
These commands are now case-sensitive.
|
|
|
|
|
|
2019-06-13 07:06:54 +08:00
|
|
|
* New command options, command completion
|
|
|
|
|
|
|
|
|
|
GDB now has a standard infrastructure to support dash-style command
|
|
|
|
|
options ('-OPT'). One benefit is that commands that use it can
|
|
|
|
|
easily support completion of command line arguments. Try "CMD
|
|
|
|
|
-[TAB]" or "help CMD" to find options supported by a command. Over
|
|
|
|
|
time, we intend to migrate most commands to this infrastructure. A
|
|
|
|
|
number of commands got support for new command options in this
|
|
|
|
|
release:
|
|
|
|
|
|
|
|
|
|
** The "print" and "compile print" commands now support a number of
|
|
|
|
|
options that allow overriding relevant global print settings as
|
|
|
|
|
set by "set print" subcommands:
|
|
|
|
|
|
|
|
|
|
-address [on|off]
|
|
|
|
|
-array [on|off]
|
|
|
|
|
-array-indexes [on|off]
|
|
|
|
|
-elements NUMBER|unlimited
|
|
|
|
|
-null-stop [on|off]
|
|
|
|
|
-object [on|off]
|
|
|
|
|
-pretty [on|off]
|
2019-08-08 02:50:54 +08:00
|
|
|
-raw-values [on|off]
|
2019-06-13 07:06:54 +08:00
|
|
|
-repeats NUMBER|unlimited
|
|
|
|
|
-static-members [on|off]
|
|
|
|
|
-symbol [on|off]
|
|
|
|
|
-union [on|off]
|
|
|
|
|
-vtbl [on|off]
|
|
|
|
|
|
|
|
|
|
Note that because the "print"/"compile print" commands accept
|
|
|
|
|
arbitrary expressions which may look like options (including
|
|
|
|
|
abbreviations), if you specify any command option, then you must
|
|
|
|
|
use a double dash ("--") to mark the end of argument processing.
|
|
|
|
|
|
|
|
|
|
** The "backtrace" command now supports a number of options that
|
|
|
|
|
allow overriding relevant global print settings as set by "set
|
|
|
|
|
backtrace" and "set print" subcommands:
|
|
|
|
|
|
|
|
|
|
-entry-values no|only|preferred|if-needed|both|compact|default
|
|
|
|
|
-frame-arguments all|scalars|none
|
|
|
|
|
-raw-frame-arguments [on|off]
|
2019-05-05 05:48:36 +08:00
|
|
|
-frame-info auto|source-line|location|source-and-location
|
|
|
|
|
|location-and-address|short-location
|
2019-06-13 07:06:54 +08:00
|
|
|
-past-main [on|off]
|
|
|
|
|
-past-entry [on|off]
|
|
|
|
|
|
|
|
|
|
In addition, the full/no-filters/hide qualifiers are now also
|
|
|
|
|
exposed as command options too:
|
|
|
|
|
|
|
|
|
|
-full
|
|
|
|
|
-no-filters
|
|
|
|
|
-hide
|
|
|
|
|
|
|
|
|
|
** The "frame apply", "tfaas" and "faas" commands similarly now
|
|
|
|
|
support the following options:
|
|
|
|
|
|
|
|
|
|
-past-main [on|off]
|
|
|
|
|
-past-entry [on|off]
|
|
|
|
|
|
2019-08-04 03:20:44 +08:00
|
|
|
** The new "info sources" options -dirname and -basename options
|
|
|
|
|
are using the standard '-OPT' infrastructure.
|
|
|
|
|
|
2019-06-13 07:06:54 +08:00
|
|
|
All options above can also be abbreviated. The argument of boolean
|
|
|
|
|
(on/off) options can be 0/1 too, and also the argument is assumed
|
|
|
|
|
"on" if omitted. This allows writing compact command invocations,
|
|
|
|
|
like for example:
|
|
|
|
|
|
2019-08-08 02:50:54 +08:00
|
|
|
(gdb) p -ra -p -o 0 -- *myptr
|
2019-06-13 07:06:54 +08:00
|
|
|
|
|
|
|
|
The above is equivalent to:
|
|
|
|
|
|
2019-08-08 02:50:54 +08:00
|
|
|
(gdb) print -raw-values -pretty -object off -- *myptr
|
2019-06-13 07:06:54 +08:00
|
|
|
|
2019-07-12 04:02:59 +08:00
|
|
|
** The "info types" command now supports the '-q' flag to disable
|
|
|
|
|
printing of some header information in a similar fashion to "info
|
|
|
|
|
variables" and "info functions".
|
|
|
|
|
|
gdb: Add new -n flag to some info commands
The 'info variables', its alias 'whereis', and 'info functions' all
include non-debug symbols in the output by default. The list of
non-debug symbols can sometimes be quite long, resulting in the
debug symbol based results being scrolled off the screen.
This commit adds a '-n' flag to all of the commands listed above that
excludes the non-debug symbols from the results, leaving just the
debug symbol based results.
gdb/ChangeLog:
* cli/cli-utils.c (info_print_options_defs): Delete.
(make_info_print_options_def_group): Delete.
(extract_info_print_options): Delete.
(info_print_command_completer): Delete.
(info_print_args_help): Add extra parameter, and optionally
include text about -n flag.
* cli/cli-utils.h (struct info_print_options): Delete.
(extract_info_print_options): Delete declaration.
(info_print_command_completer): Delete declaration.
(info_print_args_help): Add extra parameter, extend header
comment.
* python/python.c (gdbpy_rbreak): Pass additional parameter to
search_symbols.
* stack.c (struct info_print_options): New type.
(info_print_options_defs): New file scoped variable.
(make_info_print_options_def_group): New static function.
(info_print_command_completer): New static function.
(info_locals_command): Update to use new local functions.
(info_args_command): Likewise.
(_initialize_stack): Add extra parameter to calls to
info_print_args_help.
* symtab.c (search_symbols): Add extra parameter, use this to
possibly excluse non-debug symbols.
(symtab_symbol_info): Add extra parameter, which is passed on to
search_symbols.
(struct info_print_options): New type.
(info_print_options_defs): New file scoped variable.
(make_info_print_options_def_group): New static function.
(info_print_command_completer): New static function.
(info_variables_command): Update to use local functions, and pass
extra parameter through to symtab_symbol_info.
(info_functions_command): Likewise.
(info_types_command): Pass additional argument through to
symtab_symbol_info.
(rbreak_command): Pass extra argument to search_symbols.
(_initialize_symtab): Add extra arguments for calls to
info_print_args_help, and update help text for 'info variables',
'whereis', and 'info functions' commands.
* symtab.h (search_symbols): Add extra argument to declaration.
* NEWS: Mention new flags.
gdb/doc/ChangeLog:
* gdb.texinfo (Symbols): Add information about the -n flag to
"info variables" and "info functions".
gdb/testsuite/ChangeLog:
* gdb.base/info-fun.exp: Extend to test the -n flag for 'info
functions'. Reindent as needed.
* gdb.base/info-var-f1.c: New file.
* gdb.base/info-var-f2.c: New file.
* gdb.base/info-var.exp: New file.
* gdb.base/info-var.h: New file.
2019-07-22 23:53:06 +08:00
|
|
|
** The "info variables", "info functions", and "whereis" commands
|
|
|
|
|
now take a '-n' flag that excludes non-debug symbols (symbols
|
|
|
|
|
from the symbol table, not from the debug info such as DWARF)
|
|
|
|
|
from the results.
|
|
|
|
|
|
2019-06-13 07:06:54 +08:00
|
|
|
* Completion improvements
|
|
|
|
|
|
|
|
|
|
** GDB can now complete the options of the "thread apply all" and
|
|
|
|
|
"taas" commands, and their "-ascending" option can now be
|
|
|
|
|
abbreviated.
|
|
|
|
|
|
2019-07-11 22:39:55 +08:00
|
|
|
** GDB can now complete the options of the "info threads", "info
|
|
|
|
|
functions", "info variables", "info locals", and "info args"
|
|
|
|
|
commands.
|
2019-07-02 23:34:31 +08:00
|
|
|
|
2019-06-13 07:06:54 +08:00
|
|
|
** GDB can now complete the options of the "compile file" and
|
|
|
|
|
"compile code" commands. The "compile file" command now
|
|
|
|
|
completes on filenames.
|
|
|
|
|
|
|
|
|
|
** GDB can now complete the backtrace command's
|
|
|
|
|
"full/no-filters/hide" qualifiers.
|
|
|
|
|
|
|
|
|
|
* In settings, you can now abbreviate "unlimited".
|
|
|
|
|
|
|
|
|
|
E.g., "set print elements u" is now equivalent to "set print
|
|
|
|
|
elements unlimited".
|
|
|
|
|
|
2019-05-17 17:58:23 +08:00
|
|
|
* New MI commands
|
|
|
|
|
|
|
|
|
|
-complete
|
|
|
|
|
This lists all the possible completions for the rest of the line, if it
|
|
|
|
|
were to be given as a command itself. This is intended for use by MI
|
|
|
|
|
frontends in cases when separate CLI and MI channels cannot be used.
|
|
|
|
|
|
gdb/mi: New commands to catch C++ exceptions
Adds some MI commands to catch C++ exceptions. The new commands are
-catch-throw, -catch-rethrow, and -catch-catch, these all correspond
to the CLI commands 'catch throw', 'catch rethrow', and 'catch catch'.
Each MI command takes two optional arguments, '-t' has the effect of
calling 'tcatch' instead of 'catch', for example:
(gdb)
-catch-throw -t
Is the same as:
(gdb) tcatch throw
There is also a '-r REGEXP' argument that can supply a regexp to match
against the exception type, so:
(gdb)
-catch-catch -r PATTERN
Is the same as:
(gdb) catch catch PATTERN
The change in print_mention_exception_catchpoint might seem a little
strange; changing the output from using ui_out::field_int and
ui_out::text to using ui_out::message.
The print_mention_exception_catchpoint is used as the 'print_mention'
method for the exception catchpoint breakpoint object. Most of the
other 'print_mention' methods (see breakpoint.c) use either
printf_filtered, of ui_out::message. Using field_int was causing an
unexpected field to be added to the MI output. Here's the output
without the change in print_mention_exception_catchpoint:
(gdb)
-catch-throw
^done,bkptno="1",bkpt={number="1",type="breakpoint",disp="keep",
enabled="y",addr="0x00000000004006c0",
what="exception throw",catch-type="throw",
thread-groups=["i1"],times="0"}
Notice the breakpoint number appears in both the 'bkptno' field, and
the 'number' field within the 'bkpt' tuple. Here's the output with
the change in print_mention_exception_catchpoint:
(gdb)
-catch-throw
^done,bkpt={number="1",type="breakpoint",disp="keep",
enabled="y",addr="0x00000000004006c0",
what="exception throw",catch-type="throw",
thread-groups=["i1"],times="0"}
gdb/ChangeLog:
* NEWS: Mention new MI commands.
* break-catch-throw.c (enum exception_event_kind): Move to
breakpoint.h.
(print_mention_exception_catchpoint): Output text as a single
message.
(catch_exception_command_1): Rename to...
(catch_exception_event): ...this, make non-static, update header
command, and change some parameter types.
(catch_catch_command): Update for changes to
catch_exception_command_1.
(catch_throw_command): Likewise.
(catch_rethrow_command): Likewise.
* breakpoint.c (enum exception_event_kind): Delete.
* breakpoint.h (enum exception_event_kind): Moved here from
break-catch-throw.c.
(catch_exception_event): Declare.
* mi/mi-cmd-catch.c (mi_cmd_catch_exception_event): New function.
(mi_cmd_catch_throw): New function.
(mi_cmd_catch_rethrow): New function.
(mi_cmd_catch_catch): New function.
* mi/mi-cmds.c (mi_cmds): Add 'catch-throw', 'catch-rethrow', and
'catch-catch' entries.
* mi/mi-cmds.h (mi_cmd_catch_throw): Declare.
(mi_cmd_catch_rethrow): Declare.
(mi_cmd_catch_catch): Declare.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI Catchpoint Commands): Add menu entry to new
node.
(C++ Exception GDB/MI Catchpoint Commands): New node to describe
new MI commands.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-catch-cpp-exceptions.cc: New file.
* gdb.mi/mi-catch-cpp-exceptions.exp: New file.
* lib/mi-support.exp (mi_expect_stop): Handle 'exception-caught'
as a stop reason.
2019-05-09 02:01:36 +08:00
|
|
|
-catch-throw, -catch-rethrow, and -catch-catch
|
|
|
|
|
These can be used to catch C++ exceptions in a similar fashion to
|
|
|
|
|
the CLI commands 'catch throw', 'catch rethrow', and 'catch catch'.
|
|
|
|
|
|
gdb/mi: Add new commands -symbol-info-{functions,variables,types}
Add new MI commands -symbol-info-functions, -symbol-info-variables,
and -symbol-info-types which correspond to the CLI commands 'info
functions', 'info variables', and 'info types' respectively.
gdb/ChangeLog:
* mi/mi-cmds.c (mi_cmds): Add '-symbol-info-functions',
'-symbol-info-types', and '-symbol-info-variables'.
* mi/mi-cmds.h (mi_cmd_symbol_info_functions): Declare.
(mi_cmd_symbol_info_types): Declare.
(mi_cmd_symbol_info_variables): Declare.
* mi/mi-symbol-cmds.c: Add 'source.h' and 'mi-getopt.h' includes.
(output_debug_symbol): New function.
(output_nondebug_symbol): New function.
(mi_symbol_info): New function.
(mi_info_functions_or_variables): New function.
(mi_cmd_symbol_info_functions): New function.
(mi_cmd_symbol_info_types): New function.
(mi_cmd_symbol_info_variables): New function.
* NEWS: Mention new commands.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-sym-info-1.c: New file.
* gdb.mi/mi-sym-info-2.c: New file.
* gdb.mi/mi-sym-info.exp: New file.
gdb/doc/ChangeLog:
* doc/gdb.texinfo (GDB/MI Symbol Query): Document new MI command
-symbol-info-functions, -symbol-info-types, and
-symbol-info-variables.
Change-Id: Ic2fc6a6750bbce91cdde2344791014e5ef45642d
2019-09-25 06:35:47 +08:00
|
|
|
-symbol-info-functions, -symbol-info-types, and -symbol-info-variables
|
|
|
|
|
These commands are the MI equivalent of the CLI commands 'info
|
|
|
|
|
functions', 'info types', and 'info variables' respectively.
|
|
|
|
|
|
2019-10-04 05:12:09 +08:00
|
|
|
-symbol-info-modules, this is the MI equivalent of the CLI 'info
|
|
|
|
|
modules' command.
|
|
|
|
|
|
2019-10-05 00:59:51 +08:00
|
|
|
-symbol-info-module-functions and -symbol-info-module-variables.
|
|
|
|
|
These commands are the MI equivalent of the CLI commands 'info
|
|
|
|
|
module functions' and 'info module variables'.
|
|
|
|
|
|
2019-08-16 17:19:18 +08:00
|
|
|
* Other MI changes
|
|
|
|
|
|
2019-09-21 07:23:15 +08:00
|
|
|
** The default version of the MI interpreter is now 3 (-i=mi3).
|
|
|
|
|
|
|
|
|
|
** The output of information about multi-location breakpoints (which is
|
|
|
|
|
syntactically incorrect in MI 2) has changed in MI 3. This affects
|
|
|
|
|
the following commands and events:
|
|
|
|
|
|
|
|
|
|
- -break-insert
|
|
|
|
|
- -break-info
|
|
|
|
|
- =breakpoint-created
|
|
|
|
|
- =breakpoint-modified
|
|
|
|
|
|
|
|
|
|
The -fix-multi-location-breakpoint-output command can be used to enable
|
|
|
|
|
this behavior with previous MI versions.
|
|
|
|
|
|
2019-08-16 17:19:18 +08:00
|
|
|
** Backtraces and frames include a new optional field addr_flags which is
|
|
|
|
|
given after the addr field. On AArch64 this contains PAC if the address
|
|
|
|
|
has been masked in the frame. On all other targets the field is not
|
|
|
|
|
present.
|
|
|
|
|
|
2019-05-22 20:40:20 +08:00
|
|
|
* Testsuite
|
|
|
|
|
|
|
|
|
|
The testsuite now creates the files gdb.cmd (containing the arguments
|
|
|
|
|
used to launch GDB) and gdb.in (containing all the commands sent to
|
|
|
|
|
GDB) in the output directory for each test script. Multiple invocations
|
|
|
|
|
are appended with .1, .2, .3 etc.
|
|
|
|
|
|
2019-08-01 23:51:15 +08:00
|
|
|
* Building GDB and GDBserver now requires GNU make >= 3.82.
|
|
|
|
|
|
|
|
|
|
Using another implementation of the make program or an earlier version of
|
|
|
|
|
GNU make to build GDB or GDBserver is not supported.
|
|
|
|
|
|
2019-04-22 03:58:49 +08:00
|
|
|
* Building GDB now requires GNU readline >= 7.0.
|
|
|
|
|
|
|
|
|
|
GDB now bundles GNU readline 8.0, but if you choose to use
|
|
|
|
|
--with-system-readline, only readline >= 7.0 can be used.
|
|
|
|
|
|
2019-09-11 07:25:35 +08:00
|
|
|
* The TUI SingleKey keymap is now named "SingleKey". This can be used
|
|
|
|
|
from .inputrc to bind keys in this keymap. This feature is only
|
|
|
|
|
available when gdb is built against GNU readline 8.0 or later.
|
|
|
|
|
|
Remove Cell Broadband Engine debugging support
This patch implements removal of Cell/B.E. support, including
- Support for the spu-*-* target
- Support for native stand-alone SPU debugging
- Support for integrated debugging of combined PPU/SPU applications
- Remote debugging (gdbserver) support for all the above.
The patch also removes the TARGET_OBJECT_SPU target object type,
as this is available only on Cell/B.E. targets, including
- Native Linux support
- Core file support (including core file generation)
- Remote target support, including removal of the qXfer:spu:read
and qXfer:spu:write remote protocal packets and associated
support in gdbserver.
gdb/ChangeLog
2019-09-20 Ulrich Weigand <uweigand@de.ibm.com>
* NEWS: Mention that Cell/B.E. debugging support was removed.
* MAINTAINERS: Remove spu target.
* config/djgpp/fnchange.lst: Remove entries for removed files.
* Makefile.in (ALL_TARGET_OBS): Remove solib-spu.o,
spu-multiarch.o, and spu-tdep.o.
(HFILES_NO_SRCDIR): Remove solib-spu.h and spu-tdep.h.
(ALLDEPFILES): Remove solib-spu.c, spu-linux-nat.c,
spu-multiarch.c, and spu-tdep.c.
* spu-linux-nat.c: Remove file.
* spu-multiarch.c: Remove file.
* spu-tdep.c: Remove file.
* spu-tdep.h: Remove file.
* solib-spu.c: Remove file.
* solib-spu.h: Remove file.
* configure.host (powerpc64*-*-linux*): Remove Cell/B.E. support.
* configure.nat (spu-linux): Remove.
* configure.tgt (powerpc*-*-linux*): Remove solib-spu.o and
solib-multiarch.o from gdb_target_obs.
(spu*-*-*): Remove.
* arch/ppc-linux-common.h (struct ppc_linux_features): Remove "cell"
feature flag.
(ppc_linux_no_features): Update.
* arch/ppc-linux-common.c (ppc_linux_match_description): Remove
Cell/B.E. support.
* arch/ppc-linux-tdesc.h (tdesc_powerpc_cell32l): Remove declaration.
(tdesc_powerpc_cell64l): Likewise.
* nat/ppc-linux.h (PPC_FEATURE_CELL): Remove.
* ppc-linux-nat.c (ppc_linux_nat_target::read_description): Remove
Cell/B.E. support.
* ppc-linux-tdep.h: Do not include "solib-spu.h" or "spu-tdep.h".
Do not include "features/rs6000/powerpc-cell32l.c" or
"features/rs6000/powerpc-cell64l.c".
(ppc_linux_spu_section): Remove.
(ppc_linux_core_read_description): Remove Cell/B.E. support.
(spe_context_objfile, spe_context_lm_addr, spe_context_offset,
spe_context_cache_ptid, spe_context_cache_ptid): Remove.
(ppc_linux_spe_context_lookup): Remove.
(ppc_linux_spe_context_inferior_created): Remove.
(ppc_linux_spe_context_solib_loaded): Remove.
(ppc_linux_spe_context_solib_unloaded): Remove.
(ppc_linux_spe_context): Remove.
(struct ppu2spu_cache): Remove.
(ppu2spu_prev_arch, ppu2spu_this_id, ppu2spu_prev_register): Remove.
(struct ppu2spu_data): Remove.
(ppu2spu_unwind_register, ppu2spu_sniffer, ppu2spu_dealloc_cache,
ppu2spu_unwind): Remove.
(ppc_linux_init_abi): Remove Cell/B.E. support.
* rs6000-tdep.h (rs6000_gdbarch_init): Remove Cell/B.E. support.
* features/Makefile (rs6000/powerpc-cell32l-expedite): Remove.
(rs6000/powerpc-cell64l-expedite): Likewise
(WHICH): Remove rs6000/powerpc-cell32l and rs6000/powerpc-cell64l.
(XMLTOC): Remove rs6000/powerpc-cell32l.xml and
rs6000/powerpc-cell64l.xml.
* features/rs6000/powerpc-cell32l.xml: Remove.
* features/rs6000/powerpc-cell64l.xml: Likewise.
* features/rs6000/powerpc-cell32l.c: Remove generated file.
* features/rs6000/powerpc-cell64l.c: Likewise.
* regformats/rs6000/powerpc-cell32l.dat: Remove generated file.
* regformats/rs6000/powerpc-cell64l.dat: Likewise.
* regformats/reg-spu.dat: Remove.
* target.h (enum target_object): Remove TARGET_OBJECT_SPU.
* corelow.c (struct spuid_list): Remove.
(add_to_spuid_list): Remove.
(core_target::xfer_partial): Remove support for TARGET_OBJECT_SPU.
* remote.c (PACKET_qXfer_spu_read, PACKET_qXfer_spu_write): Remove.
(remote_protocol_features): Remove associated entries.
(_initialize_remote): No longer initialize them.
(remote_target::xfer_partial): Remove support for TARGET_OBJECT_SPU.
* linux-nat.c (SPUFS_MAGIC): Remove.
(linux_proc_xfer_spu): Remove.
(spu_enumerate_spu_ids): Remove.
(linux_nat_target::xfer_partial): Remove support for TARGET_OBJECT_SPU.
* linux-tdep.c (-linux_spu_make_corefile_notes): Remove.
(linux_make_corefile_notes): No longer call it.
* regcache.c (cooked_read_test): Remove bfd_arch_spu special case.
(cooked_write_test): Likewise.
gdb/doc/ChangeLog
2019-09-20 Ulrich Weigand <uweigand@de.ibm.com>
* doc/gdb.texinfo (Remote Configuration): Remove documentation for
qXfer:spu:read and qXfer:spu:write.
(General Query Packets): Likewise.
(Cell Broadband Engine SPU architecture): Remove subsection.
gdb/gdbserver/ChangeLog
2019-09-20 Ulrich Weigand <uweigand@de.ibm.com>
* configure.srv (ipa_ppc_linux_regobj): Remove powerpc-cell32l-ipa.o
and powerpc-cell64l-ipa.o.
(powerpc*-*-linux*): Remove powerpc-cell32l.o and powerpc-cell64l.o
from srv_regobj. Remove rs6000/powerpc-cell32l.xml and
rs6000/powerpc-cell64l.xml from srv_xmlfiles.
(spu*-*-*): Remove.
* spu-low.c: Remove file.
* linux-ppc-low.c (INSTR_SC, NR_spu_run): Remove.
(parse_spufs_run): Remove.
(ppc_get_pc): Remove Cell/B.E. support.
(ppc_set_pc): Likewise.
(ppc_breakpoint_at): Likewise.
(ppc_arch_setup): Likewise.
(ppc_get_ipa_tdesc_idx): Do not handle tdesc_powerpc_cell64l or
tdesc_powerpc_cell32l.
(initialize_low_arch): Do not call init_registers_powerpc_cell64l
or init_registers_powerpc_cell32l.
* linux-ppc-ipa.c (get_ipa_tdesc): Do not handle PPC_TDESC_CELL.
(initialize_low_tracepoint): Do not call init_registers_powerpc_cell64l
or init_registers_powerpc_cell32l.
* linux-ppc-tdesc-init.h (PPC_TDESC_CELL): Mark as unused.
(init_registers_powerpc_cell32l): Remove prototype.
(init_registers_powerpc_cell64l): Likewise.
* target.h (struct target_ops): Remove qxfer_spu member.
* server.c (handle_qxfer_spu): Remove.
(qxfer_packets): Remove entry for "spu".
(handle_query): No longer support qXfer:spu:read or qXfer:spu:write.
* linux-low.c (SPUFS_MAGIC): Remove.
(spu_enumerate_spu_ids): Remove.
(linux_qxfer_spu): Remove.
(linux_target_ops): Remove qxfer_spu member.
* lynx-low.c (lynx_target_ops): Remove qxfer_spu member.
* nto-low.c (nto_target_ops): Remove qxfer_spu member.
* win32-low.c (win32_target_ops): Remove qxfer_spu member.
gdb/testsuite/ChangeLog
2019-09-20 Ulrich Weigand <uweigand@de.ibm.com>
* gdb.arch/spu-info.exp: Remove file.
* gdb.arch/spu-info.c: Remove file.
* gdb.arch/spu-ls.exp: Remove file.
* gdb.arch/spu-ls.c: Remove file.
* gdb.asm/asm-source.exp: Remove support for spu*-*-*.
* gdb.asm/spu.inc: Remove file.
* gdb.base/dump.exp: Remove support for spu*-*-*.
* gdb.base/stack-checking.exp: Likewise.
* gdb.base/overlays.exp: Likewise.
* gdb.base/ovlymgr.c: Likewise.
* gdb.base/spu.ld: Remove file.
* gdb.cp/bs15503.exp: Remove support for spu*-*-*.
* gdb.cp/cpexprs.exp: Likewise.
* gdb.cp/exception.exp: Likewise.
* gdb.cp/gdb2495.exp: Likewise.
* gdb.cp/mb-templates.exp: Likewise.
* gdb.cp/pr9167.exp: Likewise.
* gdb.cp/userdef.exp: Likewise.
* gdb.xml/tdesc-regs.exp: Remove support for spu*-*-*.
* gdb.cell: Remove directory.
* lib/cell.exp: Remove file.
2019-09-21 05:06:57 +08:00
|
|
|
* Removed targets and native configurations
|
|
|
|
|
|
|
|
|
|
GDB no longer supports debugging the Cell Broadband Engine. This includes
|
|
|
|
|
both debugging standalone Cell/B.E. SPU applications and integrated debugging
|
|
|
|
|
of Cell/B.E. applications that use both the PPU and SPU architectures.
|
|
|
|
|
|
2019-09-24 00:54:42 +08:00
|
|
|
* New Simulators
|
|
|
|
|
|
|
|
|
|
TI PRU pru-*-elf
|
|
|
|
|
|
2019-11-05 01:13:14 +08:00
|
|
|
* Removed targets and native configurations
|
|
|
|
|
|
|
|
|
|
Solaris 10 i?86-*-solaris2.10, x86_64-*-solaris2.10,
|
|
|
|
|
sparc*-*-solaris2.10
|
|
|
|
|
|
2019-02-27 12:59:50 +08:00
|
|
|
*** Changes in GDB 8.3
|
2018-07-04 23:48:05 +08:00
|
|
|
|
[PowerPC] Add support for HTM registers
This patch adds support for Hardware Transactional Memory registers
for the powerpc linux native and core file targets, and for the
pwoerpc linux server stub.
These registers include both the HTM special-purpose registers (TFHAR,
TEXASR and TFIAR) as well as the set of registers that are
checkpointed (saved) when a transaction is initiated, which the
processor restores in the event of a transaction failure.
The set of checkpointed general-purpose registers is returned by the
linux kernel in the same format as the regular general-purpose
registers, defined in struct pt_regs. However, the architecture
specifies that only some of the registers present in pt_regs are
checkpointed (GPRs 0-31, CR, XER, LR and CTR). The kernel fills the
slots for MSR and NIP with other info. The other fields usually don't
have meaningful values. GDB doesn't define registers that are not
checkpointed in the architecture, but when generating a core file, GDB
fills the slot for the checkpointed MSR with the regular MSR. These
are usually similar, although some bits might be different, and in
some cases the checkpointed MSR will have a value of 0 in a
kernel-generated core-file. The checkpointed NIP is filled with TFHAR
by GDB in the core-file, which is what the kernel does. The other
fields are set to 0 by GDB.
Core files generated by the kernel have a note section for
checkpointed GPRs with the same size for both 32-bit and 64-bit
threads, and the values for the registers of a 32-bit thread are
squeezed in the first half, with no useful data in the second half.
GDB generates a smaller note section for 32-bit threads, but can read
both sizes.
The checkpointed XER is required to be 32-bit in the target
description documentation, even though the more recent ISAs define it
as 64-bit wide, since the high-order 32-bits are reserved, and because
in Linux there is no way to get a 64-bit checkpointed XER for 32-bit
threads. If this changes in the future, the target description
feature requirement can be relaxed to allow for a 64-bit checkpointed
XER.
Access to the checkpointed CR (condition register) can be confusing.
The architecture only specifies that CR fields 1 to 7 (the 24 least
significant bits) are checkpointed, but the kernel provides all 8
fields (32 bits). The value of field 0 is not masked by ptrace, so it
will sometimes show the result of some kernel operation, probably
treclaim., which sets this field.
The checkpointed registers are marked not to be saved and restored.
Inferior function calls during an active transaction don't work well,
and it's unclear what should be done in this case. TEXASR and TFIAR
can be altered asynchronously, during transaction failure recording,
so they are also not saved and restored. For consistency neither is
TFHAR.
Record and replay also doesn't work well when transactions are
involved. This patch doesn't address this, so the values of the HTM
SPRs will sometimes be innacurate when the record/relay target is
enabled. For instance, executing a "tbegin." alters TFHAR and TEXASR,
but these changes are not currently recorded.
Because the checkpointed registers are only available when a
transaction is active (or suspended), ptrace can return ENODATA when
gdb tries to read these registers and the inferior is not in a
transactional state. The registers are set to the unavailable state
when this happens. When gbd tries to write to one of these registers,
and it is unavailable, an error is raised.
The "fill" functions for checkpointed register sets in the server stub
are not implemented for the same reason as for the EBB register set,
since ptrace can also return ENODATA for checkpointed regsets. The
same issues with 'G' packets apply here.
Just like for the EBB registers, tracepoints will not mark the
checkpointed registers as unavailable if the inferior was not in a
transaction, so their content will also show 0 instead of
<unavailable> when inspecting trace data.
The new tests record the values of the regular registers before
stepping the inferior through a "tbegin." instruction to start a
transaction, then the checkpointed registers are checked against the
recorded pre-transactional values. New values are written to the
checkpointed registers and recorded, the inferior continues until the
transaction aborts (which is usually immediately when it is resumed),
and the regular registers are checked against the recorded values,
because the abort should have reverted the registers to these values.
Like for the EBB registers, target_store_registers will ignore the
checkpointed registers when called with -1 as the regno
argument (store all registers in one go).
gdb/ChangeLog:
2018-10-26 Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
* arch/ppc-linux-tdesc.h (tdesc_powerpc_isa207_htm_vsx32l)
(tdesc_powerpc_isa207_htm_vsx64l): Declare.
* arch/ppc-linux-common.h (PPC_LINUX_SIZEOF_TM_SPRREGSET)
(PPC32_LINUX_SIZEOF_CGPRREGSET, PPC64_LINUX_SIZEOF_CGPRREGSET)
(PPC_LINUX_SIZEOF_CFPRREGSET, PPC_LINUX_SIZEOF_CVMXREGSET)
(PPC_LINUX_SIZEOF_CVSXREGSET, PPC_LINUX_SIZEOF_CPPRREGSET)
(PPC_LINUX_SIZEOF_CDSCRREGSET, PPC_LINUX_SIZEOF_CTARREGSET):
Define.
(struct ppc_linux_features) <htm>: New field.
(ppc_linux_no_features): Add initializer for htm field.
* arch/ppc-linux-common.c (ppc_linux_match_description): Return
new tdescs.
* nat/ppc-linux.h (PPC_FEATURE2_HTM, NT_PPC_TM_CGPR)
(NT_PPC_TM_CFPR, NT_PPC_TM_CVMX, NT_PPC_TM_CVSX)
(NT_PPC_TM_SPR, NT_PPC_TM_CTAR, NT_PPC_TM_CPPR, NT_PPC_TM_CDSCR):
Define if not already defined.
* features/Makefile (WHICH): Add rs6000/powerpc-isa207-htm-vsx32l
and rs6000/powerpc-isa207-htm-vsx64l.
(XMLTOC): Add rs6000/powerpc-isa207-htm-vsx32l.xml and
rs6000/powerpc-isa207-htm-vsx64l.xml.
* features/rs6000/power-htm-spr.xml: New file.
* features/rs6000/power-htm-core.xml: New file.
* features/rs6000/power64-htm-core.xml: New file.
* features/rs6000/power-htm-fpu.xml: New file.
* features/rs6000/power-htm-altivec.xml: New file.
* features/rs6000/power-htm-vsx.xml: New file.
* features/rs6000/power-htm-ppr.xml: New file.
* features/rs6000/power-htm-dscr.xml: New file.
* features/rs6000/power-htm-tar.xml: New file.
* features/rs6000/powerpc-isa207-htm-vsx32l.xml: New file.
* features/rs6000/powerpc-isa207-htm-vsx64l.xml: New file.
* features/rs6000/powerpc-isa207-htm-vsx32l.c: Generate.
* features/rs6000/powerpc-isa207-htm-vsx64l.c: Generate.
* regformats/rs6000/powerpc-isa207-htm-vsx32l.dat: Generate.
* regformats/rs6000/powerpc-isa207-htm-vsx64l.dat: Generate.
* ppc-linux-nat.c (fetch_register, fetch_ppc_registers): Call
fetch_regset with HTM regsets.
(store_register, store_ppc_registers): Call store_regset with HTM
regsets.
(ppc_linux_nat_target::read_description): Set htm field in the
features struct if needed.
* ppc-linux-tdep.c: Include
features/rs6000/powerpc-isa207-htm-vsx32l.c and
features/rs6000/powerpc-isa207-htm-vsx64l.c.
(ppc32_regmap_tm_spr, ppc32_regmap_cgpr, ppc64_le_regmap_cgpr)
(ppc64_be_regmap_cgpr, ppc32_regmap_cfpr, ppc32_le_regmap_cvmx)
(ppc32_be_regmap_cvmx, ppc32_regmap_cvsx, ppc32_regmap_cppr)
(ppc32_regmap_cdscr, ppc32_regmap_ctar): New globals.
(ppc32_linux_tm_sprregset, ppc32_linux_cgprregset)
(ppc64_be_linux_cgprregset, ppc64_le_linux_cgprregset)
(ppc32_linux_cfprregset, ppc32_le_linux_cvmxregset)
(ppc32_be_linux_cvmxregset, ppc32_linux_cvsxregset)
(ppc32_linux_cpprregset, ppc32_linux_cdscrregset)
(ppc32_linux_ctarregset): New globals.
(ppc_linux_cgprregset, ppc_linux_cvmxregset): New functions.
(ppc_linux_collect_core_cpgrregset): New function.
(ppc_linux_iterate_over_regset_sections): Call back with the htm
regsets.
(ppc_linux_core_read_description): Check if the tm spr section is
present and set htm in the features struct.
(_initialize_ppc_linux_tdep): Call
initialize_tdesc_powerpc_isa207_htm_vsx32l and
initialize_tdesc_powerpc_isa207_htm_vsx64l.
* ppc-linux-tdep.h (ppc_linux_cgprregset, ppc_linux_cvmxregset):
Declare.
(ppc32_linux_tm_sprregset, ppc32_linux_cfprregset)
(ppc32_linux_cvsxregset, ppc32_linux_cpprregset)
(ppc32_linux_cdscrregset, ppc32_linux_ctarregset): Declare.
* ppc-tdep.h (struct gdbarch_tdep) <have_htm_spr, have_htm_core>:
New fields.
<have_htm_fpu, have_htm_altivec, have_htm_vsx>:
Likewise.
<ppc_cppr_regnum, ppc_cdscr_regnum, ppc_ctar_regnum>: Likewise.
<ppc_cdl0_regnum, ppc_cvsr0_regnum, ppc_cefpr0_regnum>: Likewise.
(enum) <PPC_TFHAR_REGNUM, PPC_TEXASR_REGNUM, PPC_TFIAR_REGNUM>:
New enum fields.
<PPC_CR0_REGNUM, PPC_CCR_REGNUM, PPC_CXER_REGNUM>: Likewise.
<PPC_CLR_REGNUM, PPC_CCTR_REGNUM, PPC_CF0_REGNUM>: Likewise.
<PPC_CFPSCR_REGNUM, PPC_CVR0_REGNUM, PPC_CVSCR_REGNUM>: Likewise.
<PPC_CVRSAVE_REGNUM, PPC_CVSR0_UPPER_REGNUM>: Likewise.
<PPC_CPPR_REGNUM, PPC_CDSCR_REGNUM>: Likewise.
<PPC_CTAR_REGNUM>: Likewise.
(PPC_IS_TMSPR_REGNUM, PPC_IS_CKPTGP_REGNUM, PPC_IS_CKPTFP_REGNUM)
(PPC_IS_CKPTVMX_REGNUM, PPC_IS_CKPTVSX_REGNUM): Define.
* rs6000-tdep.c (IS_CDFP_PSEUDOREG, IS_CVSX_PSEUDOREG)
(IS_CEFP_PSEUDOREG): Define.
(rs6000_register_name): Hide the upper halves of checkpointed VSX
registers. Return names for the checkpointed DFP, VSX, and EFP
pseudo registers.
(rs6000_pseudo_register_type): Remove initial assert and raise an
internal error in the else clause instead. Return types for the
checkpointed DFP, VSX, and EFP pseudo registers.
(dfp_pseudo_register_read, dfp_pseudo_register_write): Handle
checkpointed DFP pseudo registers.
(vsx_pseudo_register_read, vsx_pseudo_register_write): Handle
checkpointed VSX pseudo registers.
(efp_pseudo_register_read, efp_pseudo_register_write): Rename
from efpr_pseudo_register_read and
efpr_pseudo_register_write. Handle checkpointed EFP pseudo
registers.
(rs6000_pseudo_register_read, rs6000_pseudo_register_write):
Handle checkpointed DFP, VSX, and EFP registers.
(dfp_ax_pseudo_register_collect, vsx_ax_pseudo_register_collect)
(efp_ax_pseudo_register_collect): New functions.
(rs6000_ax_pseudo_register_collect): Move DFP, VSX and EFP pseudo
register logic to new functions. Handle checkpointed DFP, VSX,
and EFP pseudo registers.
(rs6000_gdbarch_init): Look for and validate the htm features.
Include checkpointed DFP, VSX and EFP pseudo-registers.
* NEWS: Mention access to PPR, DSCR, TAR, EBB/PMU registers and
HTM registers.
gdb/gdbserver/ChangeLog:
2018-10-26 Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
* configure.srv (ipa_ppc_linux_regobj): Add
powerpc-isa207-htm-vsx32l-ipa.o and
powerpc-isa207-htm-vsx64l-ipa.o.
(powerpc*-*-linux*): Add powerpc-isa207-htm-vsx32l.o and
powerpc-isa207-htm-vsx64l.o to srv_regobj. Add
rs6000/power-htm-spr.xml, rs6000/power-htm-core.xml,
rs6000/power64-htm-core.xml, rs6000/power-htm-fpu.xml,
rs6000/power-htm-altivec.xml, rs6000/power-htm-vsx.xml,
rs6000/power-htm-ppr.xml, rs6000/power-htm-dscr.xml,
rs6000/power-htm-tar.xml, rs6000/powerpc-isa207-htm-vsx32l.xml,
and rs6000/powerpc-isa207-htm-vsx64l.xml to srv_xmlfiles.
* linux-ppc-tdesc-init.h (enum ppc_linux_tdesc)
<PPC_TDESC_ISA207_HTM_VSX>: New enum value.
(init_registers_powerpc_isa207_htm_vsx32l)
(init_registers_powerpc_isa207_htm_vsx64l): Declare.
* linux-ppc-low.c (ppc_fill_tm_sprregset, ppc_store_tm_sprregset)
(ppc_store_tm_cgprregset, ppc_store_tm_cfprregset)
(ppc_store_tm_cvrregset, ppc_store_tm_cvsxregset)
(ppc_store_tm_cpprregset, ppc_store_tm_cdscrregset)
(ppc_store_tm_ctarregset): New functions.
(ppc_regsets): Add entries for HTM regsets.
(ppc_arch_setup): Set htm in features struct when needed. Set
sizes for the HTM regsets.
(ppc_get_ipa_tdesc_idx): Return PPC_TDESC_ISA207_HTM_VSX.
(initialize_low_arch): Call
init_registers_powerpc_isa207_htm_vsx32l and
init_registers_powerpc_isa207_htm_vsx64l.
* linux-ppc-ipa.c (get_ipa_tdesc): Handle
PPC_TDESC_ISA207_HTM_VSX.
(initialize_low_tracepoint): Call
init_registers_powerpc_isa207_htm_vsx32l and
init_registers_powerpc_isa207_htm_vsx64l.
gdb/testsuite/ChangeLog:
2018-10-26 Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
* gdb.arch/powerpc-htm-regs.c: New file.
* gdb.arch/powerpc-htm-regs.exp: New file.
gdb/doc/ChangeLog:
2018-10-26 Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
* gdb.texinfo (PowerPC Features): Describe new features
"org.gnu.gdb.power.htm.spr", "org.gnu.gdb.power.htm.core",
"org.gnu.gdb.power.htm.fpu", "org.gnu.gdb.power.htm.altivec",
"org.gnu.gdb.power.htm.vsx", "org.gnu.gdb.power.htm.ppr",
"org.gnu.gdb.power.htm.dscr", "org.gnu.gdb.power.htm.tar".
2018-10-26 20:37:55 +08:00
|
|
|
* GDB and GDBserver now support access to additional registers on
|
|
|
|
|
PowerPC GNU/Linux targets: PPR, DSCR, TAR, EBB/PMU registers, and
|
|
|
|
|
HTM registers.
|
|
|
|
|
|
C++ compile support
This patch adds *basic* support for C++ to the compile feature. It does
most simple type conversions, including everything that C compile does and
your basic "with-classes" type of C++.
I've written a new compile-support.exp support file which adds a new test
facility for automating and simplifying "compile print" vs "compile code"
testing. See testsuite/lib/compile-support.exp and CompileExpression
for more on that. The tests use this facility extensively.
This initial support has several glaring omissions:
- No template support at all
I have follow-on patches for this, but they add much complexity
to this "basic" support. Consequently, they will be submitted separately.
- Cannot print functions
The code template needs tweaking, and I simply haven't gotten to it yet.
- So-called "special function" support is not included
Using constructors, destructors, operators, etc will not work. I have
follow-on patches for that, but they require some work because of the
recent churn in symbol searching.
- There are several test suite references to "compile/1234" bugs.
I will file bugs and update the test suite's bug references before pushing
these patches.
The test suite started as a copy of the original C-language support, but
I have written tests to exercise the basic functionality of the plug-in.
I've added a new option for outputting debug messages for C++ type-conversion
("debug compile-cplus-types").
gdb/ChangeLog:
* Makefile.in (SUBDIR_GCC_COMPILE_SRCS): Add compile-cplus-symbols.c
and compile-cplus-types.c.
(HFILES_NO_SRCDIR): Add gcc-cp-plugin.h.
* c-lang.c (cplus_language_defn): Set C++ compile functions.
* c-lang.h (cplus_get_compile_context, cplus_compute_program):
Declare.
* compile/compile-c-support.c: Include compile-cplus.h.
(load_libcompile): Templatize.
(get_compile_context): "New" function.
(c_get_compile_context): Use get_compile_context.
(cplus_get_compile_context): New function.
(cplus_push_user_expression, cplus_pop_user_expression)
(cplus_add_code_header, cplus_add_input, cplus_compile_program)
(cplus_compute_program): Define new structs/functions.
* compile/compile-cplus-symmbols.c: New file.
* compile/compile-cplus-types.c: New file.
* compile/compile-cplus.h: New file.
* compile/compile-internal.h (debug_compile_oracle, GCC_TYPE_NONE):
Declare.
* compile/compile-object-load.c (get_out_value_type): Use
strncmp_iw when comparing symbol names.
(compile_object_load): Add mst_bss and mst_data.
* compile/compile.c (_initialize_compile): Remove
-Wno-implicit-function-declaration from `compile_args'.
* compile/gcc-cp-plugin.h: New file.
* NEWS: Mention C++ compile support and new debug options.
gdb/testsuite/ChangeLog:
* gdb.compile/compile-cplus-anonymous.cc: New file.
* gdb.compile/compile-cplus-anonymous.exp: New file.
* gdb.compile/compile-cplus-array-decay.cc: New file.
* gdb.compile/compile-cplus-array-decay.exp: New file.
* gdb.compile/compile-cplus-inherit.cc: New file.
* gdb.compile/compile-cplus-inherit.exp: New file.
* gdb.compile/compile-cplus-member.cc: New file.
* gdb.compile/compile-cplus-member.exp: New file.
* gdb.compile/compile-cplus-method.cc: New file.
* gdb.compile/compile-cplus-method.exp: New file.
* gdb.compile/compile-cplus-mod.c: "New" file.
* gdb.compile/compile-cplus-namespace.cc: New file.
* gdb.compile/compile-cplus-namespace.exp: New file.
* gdb.compile/compile-cplus-nested.cc: New file.
* gdb.compile/compile-cplus-nested.exp: New file.
* gdb.compile/compile-cplus-print.c: "New" file.
* gdb.compile/compile-cplus-print.exp: "New" file.
* gdb.compile/compile-cplus-virtual.cc: New file.
* gdb.compile/compile-cplus-virtual.exp: New file.
* gdb.compile/compile-cplus.c: "New" file.
* gdb.compile/compile-cplus.exp: "New" file.
* lib/compile-support.exp: New file.
doc/ChangeLog:
* gdb.texinfo (Compiling and injecting code in GDB): Document
set/show "compile-oracle" and "compile-cplus-types" commands.
2018-08-30 06:12:24 +08:00
|
|
|
* GDB now has experimental support for the compilation and injection of
|
|
|
|
|
C++ source code into the inferior. This beta release does not include
|
|
|
|
|
support for several language features, such as templates, constructors,
|
|
|
|
|
and operators.
|
|
|
|
|
|
|
|
|
|
This feature requires GCC 7.1 or higher built with libcp1.so
|
|
|
|
|
(the C++ plug-in).
|
|
|
|
|
|
Implement IPv6 support for GDB/gdbserver
This patch implements IPv6 support for both GDB and gdbserver. Based
on my research, it is the fourth attempt to do that since 2006. Since
I used ideas from all of the previous patches, I also added their
authors's names on the ChangeLogs as a way to recognize their
efforts. For reference sake, you can find the previous attempts at:
https://sourceware.org/ml/gdb-patches/2006-09/msg00192.html
https://sourceware.org/ml/gdb-patches/2014-02/msg00248.html
https://sourceware.org/ml/gdb-patches/2016-02/msg00226.html
The basic idea behind the patch is to start using the new
'getaddrinfo'/'getnameinfo' calls, which are responsible for
translating names and addresses in a protocol-independent way. This
means that if we ever have a new version of the IP protocol, we won't
need to change the code again (or, at least, won't have to change the
majority of the code).
The function 'getaddrinfo' returns a linked list of possible addresses
to connect to. Dealing with multiple addresses proved to be a hard
task with the current TCP auto-retry mechanism implemented on
ser-tcp:net_open. For example, when gdbserver listened only on an
IPv4 socket:
$ ./gdbserver --once 127.0.0.1:1234 ./a.out
and GDB was instructed to try to connect to both IPv6 and IPv4
sockets:
$ ./gdb -ex 'target extended-remote localhost:1234' ./a.out
the user would notice a somewhat big delay before GDB was able to
connect to the IPv4 socket. This happened because GDB was trying to
connect to the IPv6 socket first, and had to wait until the connection
timed out before it tried to connect to the IPv4 socket.
For that reason, I had to rewrite the main loop and implement a new
method for handling multiple connections. After some discussion,
Pedro and I agreed on the following algorithm:
1) For each entry returned by 'getaddrinfo', we try to open a socket
and connect to it.
2.a) If we have a successful 'connect', we just use that connection.
2.b) If we don't have a successfull 'connect', but if we've got a
ECONNREFUSED (meaning the the connection was refused), we keep track
of this fact by using a flag.
2.c) If we don't have a successfull 'connect', but if we've got a
EINPROGRESS (meaning that the connection is in progress), we perform
a 'select' call on the socket until we have a result (either a
successful connection, or an error on the socket).
3) If tcp_auto_retry is true, and we haven't gotten a successful
connection, and at least one of our attempts failed with
ECONNREFUSED, then we wait a little bit (i.e., call
'wait_for_connect'), check to see if there was a
timeout/interruption (in which case we bail out), and then go back
to (1).
After multiple tests, I was able to connect without delay on the
scenario described above, and was also able to connect in all other
types of scenarios.
I also implemented some hostname parsing functions (along with their
corresponding unit tests) which are used to help GDB and gdbserver to
parse hostname strings provided by the user. These new functions are
living inside common/netstuff.[ch]. I've had to do that since IPv6
introduces a new URL scheme, which defines that square brackets can be
used to enclose the host part and differentiate it from the
port (e.g., "[::1]:1234" means "host ::1, port 1234"). I spent some
time thinking about a reasonable way to interpret what the user wants,
and I came up with the following:
- If the user has provided a prefix that doesn't specify the protocol
version (i.e., "tcp:" or "udp:"), or if the user has not provided
any prefix, don't make any assumptions (i.e., assume AF_UNSPEC when
dealing with 'getaddrinfo') *unless* the host starts with "[" (in
which case, assume it's an IPv6 host).
- If the user has provided a prefix that does specify the protocol
version (i.e., "tcp4:", "tcp6:", "udp4:" or "udp6:"), then respect
that.
This method doesn't follow strictly what RFC 2732 proposes (that
literal IPv6 addresses should be provided enclosed in "[" and "]")
because IPv6 addresses still can be provided without square brackets
in our case, but since we have prefixes to specify protocol versions I
think this is not an issue.
Another thing worth mentioning is the new 'GDB_TEST_SOCKETHOST'
testcase parameter, which makes it possible to specify the
hostname (without the port) to be used when testing GDB and
gdbserver. For example, to run IPv6 tests:
$ make check-gdb RUNTESTFLAGS='GDB_TEST_SOCKETHOST=tcp6:[::1]'
Or, to run IPv4 tests:
$ make check-gdb RUNTESTFLAGS='GDB_TEST_SOCKETHOST=tcp4:127.0.0.1'
This required a few changes on the gdbserver-base.exp, and also a
minimal adjustment on gdb.server/run-without-local-binary.exp.
Finally, I've implemented a new testcase,
gdb.server/server-connect.exp, which is supposed to run on the native
host and perform various "smoke tests" using different connection
methods.
This patch has been regression-tested on BuildBot and locally, and
also built using a x86_64-w64-mingw32 GCC, and no problems were found.
gdb/ChangeLog:
2018-07-11 Sergio Durigan Junior <sergiodj@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Paul Fertser <fercerpav@gmail.com>
Tsutomu Seki <sekiriki@gmail.com>
Pedro Alves <palves@redhat.com>
* Makefile.in (SUBDIR_UNITTESTS_SRCS): Add
'unittests/parse-connection-spec-selftests.c'.
(COMMON_SFILES): Add 'common/netstuff.c'.
(HFILES_NO_SRCDIR): Add 'common/netstuff.h'.
* NEWS (Changes since GDB 8.2): Mention IPv6 support.
* common/netstuff.c: New file.
* common/netstuff.h: New file.
* ser-tcp.c: Include 'netstuff.h' and 'wspiapi.h'.
(wait_for_connect): Update comment. New parameter
'gdb::optional<int> sock' instead of 'struct serial *scb'.
Use 'sock' directly instead of 'scb->fd'.
(try_connect): New function, with code from 'net_open'.
(net_open): Rewrite main loop to deal with multiple
sockets/addresses. Handle IPv6-style hostnames; implement
support for IPv6 connections.
* unittests/parse-connection-spec-selftests.c: New file.
gdb/gdbserver/ChangeLog:
2018-07-11 Sergio Durigan Junior <sergiodj@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Paul Fertser <fercerpav@gmail.com>
Tsutomu Seki <sekiriki@gmail.com>
* Makefile.in (SFILES): Add '$(srcdir)/common/netstuff.c'.
(OBS): Add 'common/netstuff.o'.
(GDBREPLAY_OBS): Likewise.
* gdbreplay.c: Include 'wspiapi.h' and 'netstuff.h'.
(remote_open): Implement support for IPv6
connections.
* remote-utils.c: Include 'netstuff.h', 'filestuff.h'
and 'wspiapi.h'.
(handle_accept_event): Accept connections from IPv6 sources.
(remote_prepare): Handle IPv6-style hostnames; implement
support for IPv6 connections.
(remote_open): Implement support for printing connections from
IPv6 sources.
gdb/testsuite/ChangeLog:
2018-07-11 Sergio Durigan Junior <sergiodj@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Paul Fertser <fercerpav@gmail.com>
Tsutomu Seki <sekiriki@gmail.com>
* README (Testsuite Parameters): Mention new 'GDB_TEST_SOCKETHOST'
parameter.
* boards/native-extended-gdbserver.exp: Do not set 'sockethost'
by default.
* boards/native-gdbserver.exp: Likewise.
* gdb.server/run-without-local-binary.exp: Improve regexp used
for detecting when a remote debugging connection succeeds.
* gdb.server/server-connect.exp: New file.
* lib/gdbserver-support.exp (gdbserver_default_get_comm_port):
Do not prefix the port number with ":".
(gdbserver_start): New global GDB_TEST_SOCKETHOST. Implement
support for detecting and using it. Add '$debughost_gdbserver'
to the list of arguments used to start gdbserver. Handle case
when gdbserver cannot resolve a network name.
gdb/doc/ChangeLog:
2018-07-11 Sergio Durigan Junior <sergiodj@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Paul Fertser <fercerpav@gmail.com>
Tsutomu Seki <sekiriki@gmail.com>
* gdb.texinfo (Remote Connection Commands): Add explanation
about new IPv6 support. Add new connection prefixes.
2018-05-18 13:29:24 +08:00
|
|
|
* GDB and GDBserver now support IPv6 connections. IPv6 addresses
|
|
|
|
|
can be passed using the '[ADDRESS]:PORT' notation, or the regular
|
|
|
|
|
'ADDRESS:PORT' method.
|
|
|
|
|
|
2018-08-08 06:15:28 +08:00
|
|
|
* DWARF index cache: GDB can now automatically save indices of DWARF
|
|
|
|
|
symbols on disk to speed up further loading of the same binaries.
|
|
|
|
|
|
2018-11-03 01:37:29 +08:00
|
|
|
* Ada task switching is now supported on aarch64-elf targets when
|
|
|
|
|
debugging a program using the Ravenscar Profile. For more information,
|
|
|
|
|
see the "Tasking Support when using the Ravenscar Profile" section
|
|
|
|
|
in the GDB user manual.
|
|
|
|
|
|
2018-08-29 23:11:50 +08:00
|
|
|
* GDB in batch mode now exits with status 1 if the last command to be
|
|
|
|
|
executed failed.
|
|
|
|
|
|
gdb/riscv: Add target description support
This commit adds target description support for riscv.
I've used the split feature approach for specifying the architectural
features, and the CSR feature is auto-generated from the riscv-opc.h
header file.
If the target doesn't provide a suitable target description then GDB
will build one by looking at the bfd headers.
This commit does not implement target description creation for the
Linux or FreeBSD native targets, both of these will need to add
read_description methods into their respective target classes, which
probe the target features, and then call
riscv_create_target_description to build a suitable target
description. Until this is done Linux and FreeBSD will get the same
default target description based on the bfd that bare-metal targets
get.
I've only added feature descriptions for 32 and 64 bit registers, 128
bit registers (for RISC-V) are not supported in the reset of GDB yet.
This commit removes the special reading of the MISA register in order
to establish the target features, this was only used for figuring out
the f-register size, and even that wasn't done consistently. We now
rely on the target to tell us what size of registers it has (or look
in the BFD as a last resort). The result of this is that we should
now support RV64 targets with 32-bit float, though I have not
extensively tested this combination yet.
* Makefile.in (ALL_TARGET_OBS): Add arch/riscv.o.
(HFILES_NO_SRCDIR): Add arch/riscv.h.
* arch/riscv.c: New file.
* arch/riscv.h: New file.
* configure.tgt: Add cpu_obs list of riscv, move riscv-tdep.o into
this list, and add arch/riscv.o.
* features/Makefile: Add riscv features.
* features/riscv/32bit-cpu.c: New file.
* features/riscv/32bit-cpu.xml: New file.
* features/riscv/32bit-csr.c: New file.
* features/riscv/32bit-csr.xml: New file.
* features/riscv/32bit-fpu.c: New file.
* features/riscv/32bit-fpu.xml: New file.
* features/riscv/64bit-cpu.c: New file.
* features/riscv/64bit-cpu.xml: New file.
* features/riscv/64bit-csr.c: New file.
* features/riscv/64bit-csr.xml: New file.
* features/riscv/64bit-fpu.c: New file.
* features/riscv/64bit-fpu.xml: New file.
* features/riscv/rebuild-csr-xml.sh: New file.
* riscv-tdep.c: Add 'arch/riscv.h' include.
(riscv_gdb_reg_names): Delete.
(csr_reggroup): New global.
(struct riscv_register_alias): Delete.
(struct riscv_register_feature): New structure.
(riscv_register_aliases): Delete.
(riscv_xreg_feature): New global.
(riscv_freg_feature): New global.
(riscv_virtual_feature): New global.
(riscv_csr_feature): New global.
(riscv_create_csr_aliases): New function.
(riscv_read_misa_reg): Delete.
(riscv_has_feature): Delete.
(riscv_isa_xlen): Simplify, just return cached xlen.
(riscv_isa_flen): Simplify, just return cached flen.
(riscv_has_fp_abi): Update for changes in struct gdbarch_tdep.
(riscv_register_name): Update to make use of tdesc_register_name.
Look up xreg and freg names in the new globals riscv_xreg_feature
and riscv_freg_feature. Don't supply csr aliases here.
(riscv_fpreg_q_type): Delete.
(riscv_register_type): Use tdesc_register_type in almost all
cases, override the returned type in a few specific cases only.
(riscv_print_one_register_info): Handle errors reading registers.
(riscv_register_reggroup_p): Use tdesc_register_in_reggroup_p for
registers that are otherwise unknown to GDB. Also check the
csr_reggroup.
(riscv_print_registers_info): Remove assert about upper register
number, and use gdbarch_register_reggroup_p instead of
short-cutting.
(riscv_find_default_target_description): New function.
(riscv_check_tdesc_feature): New function.
(riscv_add_reggroups): New function.
(riscv_setup_register_aliases): New function.
(riscv_init_reggroups): New function.
(_initialize_riscv_tdep): Add calls to setup CSR aliases, and
setup register groups. Register new riscv debug variable.
* riscv-tdep.h: Add 'arch/riscv.h' include.
(struct gdbarch_tdep): Remove abi union, and add
riscv_gdbarch_features field. Remove cached quad floating point
type, and provide initialisation for double type field.
* target-descriptions.c (maint_print_c_tdesc_cmd): Add riscv to
the list of targets using the feature based target descriptions.
* NEWS: Mention target description support.
gdb/doc/ChangeLog:
* gdb.texinfo (Standard Target Features): Add RISC-V Features
sub-section.
2018-10-29 23:10:52 +08:00
|
|
|
* The RISC-V target now supports target descriptions.
|
|
|
|
|
|
2018-12-14 03:36:42 +08:00
|
|
|
* System call catchpoints now support system call aliases on FreeBSD.
|
|
|
|
|
When the ABI of a system call changes in FreeBSD, this is
|
|
|
|
|
implemented by leaving a compatibility system call using the old ABI
|
|
|
|
|
at the existing number and allocating a new system call number for
|
|
|
|
|
the new ABI. For example, FreeBSD 12 altered the layout of 'struct
|
|
|
|
|
kevent' used by the 'kevent' system call. As a result, FreeBSD 12
|
|
|
|
|
kernels ship with both 'kevent' and 'freebsd11_kevent' system calls.
|
|
|
|
|
The 'freebsd11_kevent' system call is assigned an alias of 'kevent'
|
|
|
|
|
so that a system call catchpoint for the 'kevent' system call will
|
|
|
|
|
catch invocations of both the 'kevent' and 'freebsd11_kevent'
|
|
|
|
|
binaries. This ensures that 'kevent' system calls are caught for
|
|
|
|
|
binaries using either the old or new ABIs.
|
|
|
|
|
|
2018-11-27 07:19:17 +08:00
|
|
|
* Terminal styling is now available for the CLI and the TUI. GNU
|
|
|
|
|
Source Highlight can additionally be used to provide styling of
|
|
|
|
|
source code snippets. See the "set style" commands, below, for more
|
|
|
|
|
information.
|
|
|
|
|
|
gdb: Remove support for old mangling schemes
An upcoming sync with gcc's libiberty [1] will remove support for old
mangling schemes (GNU v2, Lucid, ARM, HP and EDG). It will remove the
cplus_demangle_opname function, so we need to get rid of its usages in
GDB (it's a GNU v2 specific function).
I think the changes are mostly relatively obvious, some hacks that were
necessary to support overloaded operators with GNU v2 mangling are not
needed anymore.
The change in stabsread.c is perhaps less obvious. I think we could get
rid of more code in that region that is specific to old mangling
schemes, but I chose to do only the minimal changes required to remove
the cplus_demangle_opname uses. There is also a detailed comment just
above that explaining how GNU v2 and v3 mangled symbols are handled, I
decided to leave it as-is, since I wasn't sure which part to remove,
change or leave there.
[1] The commit "Remove support for demangling GCC 2.x era mangling
schemes.", specifically.
gdb/ChangeLog:
* gdbtypes.c (check_stub_method_group): Remove handling of old
mangling schemes.
* linespec.c (find_methods): Likewise.
* stabsread.c (read_member_functions): Likewise.
* valops.c (search_struct_method): Likewise.
(value_struct_elt_for_reference): Likewise.
* NEWS: Mention this change.
gdb/testsuite/ChangeLog:
* gdb.cp/demangle.exp (test_gnu_style_demangling): Rename to...
(test_gnuv3_style_demangling): ... this.
(test_lucid_style_demangling): Remove.
(test_arm_style_demangling): Remove.
(test_hp_style_demangling): Remove.
(do_tests): Remove calls to the above.
gdb/doc/ChangeLog:
* gdb.texinfo (Print Settings): Remove mention of specific
demangle-style values, just refer to the in-process help.
2019-01-10 01:57:16 +08:00
|
|
|
* Removed support for old demangling styles arm, edg, gnu, hp and
|
|
|
|
|
lucid.
|
|
|
|
|
|
2018-07-13 05:02:14 +08:00
|
|
|
* New commands
|
|
|
|
|
|
C++ compile support
This patch adds *basic* support for C++ to the compile feature. It does
most simple type conversions, including everything that C compile does and
your basic "with-classes" type of C++.
I've written a new compile-support.exp support file which adds a new test
facility for automating and simplifying "compile print" vs "compile code"
testing. See testsuite/lib/compile-support.exp and CompileExpression
for more on that. The tests use this facility extensively.
This initial support has several glaring omissions:
- No template support at all
I have follow-on patches for this, but they add much complexity
to this "basic" support. Consequently, they will be submitted separately.
- Cannot print functions
The code template needs tweaking, and I simply haven't gotten to it yet.
- So-called "special function" support is not included
Using constructors, destructors, operators, etc will not work. I have
follow-on patches for that, but they require some work because of the
recent churn in symbol searching.
- There are several test suite references to "compile/1234" bugs.
I will file bugs and update the test suite's bug references before pushing
these patches.
The test suite started as a copy of the original C-language support, but
I have written tests to exercise the basic functionality of the plug-in.
I've added a new option for outputting debug messages for C++ type-conversion
("debug compile-cplus-types").
gdb/ChangeLog:
* Makefile.in (SUBDIR_GCC_COMPILE_SRCS): Add compile-cplus-symbols.c
and compile-cplus-types.c.
(HFILES_NO_SRCDIR): Add gcc-cp-plugin.h.
* c-lang.c (cplus_language_defn): Set C++ compile functions.
* c-lang.h (cplus_get_compile_context, cplus_compute_program):
Declare.
* compile/compile-c-support.c: Include compile-cplus.h.
(load_libcompile): Templatize.
(get_compile_context): "New" function.
(c_get_compile_context): Use get_compile_context.
(cplus_get_compile_context): New function.
(cplus_push_user_expression, cplus_pop_user_expression)
(cplus_add_code_header, cplus_add_input, cplus_compile_program)
(cplus_compute_program): Define new structs/functions.
* compile/compile-cplus-symmbols.c: New file.
* compile/compile-cplus-types.c: New file.
* compile/compile-cplus.h: New file.
* compile/compile-internal.h (debug_compile_oracle, GCC_TYPE_NONE):
Declare.
* compile/compile-object-load.c (get_out_value_type): Use
strncmp_iw when comparing symbol names.
(compile_object_load): Add mst_bss and mst_data.
* compile/compile.c (_initialize_compile): Remove
-Wno-implicit-function-declaration from `compile_args'.
* compile/gcc-cp-plugin.h: New file.
* NEWS: Mention C++ compile support and new debug options.
gdb/testsuite/ChangeLog:
* gdb.compile/compile-cplus-anonymous.cc: New file.
* gdb.compile/compile-cplus-anonymous.exp: New file.
* gdb.compile/compile-cplus-array-decay.cc: New file.
* gdb.compile/compile-cplus-array-decay.exp: New file.
* gdb.compile/compile-cplus-inherit.cc: New file.
* gdb.compile/compile-cplus-inherit.exp: New file.
* gdb.compile/compile-cplus-member.cc: New file.
* gdb.compile/compile-cplus-member.exp: New file.
* gdb.compile/compile-cplus-method.cc: New file.
* gdb.compile/compile-cplus-method.exp: New file.
* gdb.compile/compile-cplus-mod.c: "New" file.
* gdb.compile/compile-cplus-namespace.cc: New file.
* gdb.compile/compile-cplus-namespace.exp: New file.
* gdb.compile/compile-cplus-nested.cc: New file.
* gdb.compile/compile-cplus-nested.exp: New file.
* gdb.compile/compile-cplus-print.c: "New" file.
* gdb.compile/compile-cplus-print.exp: "New" file.
* gdb.compile/compile-cplus-virtual.cc: New file.
* gdb.compile/compile-cplus-virtual.exp: New file.
* gdb.compile/compile-cplus.c: "New" file.
* gdb.compile/compile-cplus.exp: "New" file.
* lib/compile-support.exp: New file.
doc/ChangeLog:
* gdb.texinfo (Compiling and injecting code in GDB): Document
set/show "compile-oracle" and "compile-cplus-types" commands.
2018-08-30 06:12:24 +08:00
|
|
|
set debug compile-cplus-types
|
|
|
|
|
show debug compile-cplus-types
|
|
|
|
|
Control the display of debug output about type conversion in the
|
2020-06-05 18:24:20 +08:00
|
|
|
C++ compile feature. Commands have no effect while compiling
|
C++ compile support
This patch adds *basic* support for C++ to the compile feature. It does
most simple type conversions, including everything that C compile does and
your basic "with-classes" type of C++.
I've written a new compile-support.exp support file which adds a new test
facility for automating and simplifying "compile print" vs "compile code"
testing. See testsuite/lib/compile-support.exp and CompileExpression
for more on that. The tests use this facility extensively.
This initial support has several glaring omissions:
- No template support at all
I have follow-on patches for this, but they add much complexity
to this "basic" support. Consequently, they will be submitted separately.
- Cannot print functions
The code template needs tweaking, and I simply haven't gotten to it yet.
- So-called "special function" support is not included
Using constructors, destructors, operators, etc will not work. I have
follow-on patches for that, but they require some work because of the
recent churn in symbol searching.
- There are several test suite references to "compile/1234" bugs.
I will file bugs and update the test suite's bug references before pushing
these patches.
The test suite started as a copy of the original C-language support, but
I have written tests to exercise the basic functionality of the plug-in.
I've added a new option for outputting debug messages for C++ type-conversion
("debug compile-cplus-types").
gdb/ChangeLog:
* Makefile.in (SUBDIR_GCC_COMPILE_SRCS): Add compile-cplus-symbols.c
and compile-cplus-types.c.
(HFILES_NO_SRCDIR): Add gcc-cp-plugin.h.
* c-lang.c (cplus_language_defn): Set C++ compile functions.
* c-lang.h (cplus_get_compile_context, cplus_compute_program):
Declare.
* compile/compile-c-support.c: Include compile-cplus.h.
(load_libcompile): Templatize.
(get_compile_context): "New" function.
(c_get_compile_context): Use get_compile_context.
(cplus_get_compile_context): New function.
(cplus_push_user_expression, cplus_pop_user_expression)
(cplus_add_code_header, cplus_add_input, cplus_compile_program)
(cplus_compute_program): Define new structs/functions.
* compile/compile-cplus-symmbols.c: New file.
* compile/compile-cplus-types.c: New file.
* compile/compile-cplus.h: New file.
* compile/compile-internal.h (debug_compile_oracle, GCC_TYPE_NONE):
Declare.
* compile/compile-object-load.c (get_out_value_type): Use
strncmp_iw when comparing symbol names.
(compile_object_load): Add mst_bss and mst_data.
* compile/compile.c (_initialize_compile): Remove
-Wno-implicit-function-declaration from `compile_args'.
* compile/gcc-cp-plugin.h: New file.
* NEWS: Mention C++ compile support and new debug options.
gdb/testsuite/ChangeLog:
* gdb.compile/compile-cplus-anonymous.cc: New file.
* gdb.compile/compile-cplus-anonymous.exp: New file.
* gdb.compile/compile-cplus-array-decay.cc: New file.
* gdb.compile/compile-cplus-array-decay.exp: New file.
* gdb.compile/compile-cplus-inherit.cc: New file.
* gdb.compile/compile-cplus-inherit.exp: New file.
* gdb.compile/compile-cplus-member.cc: New file.
* gdb.compile/compile-cplus-member.exp: New file.
* gdb.compile/compile-cplus-method.cc: New file.
* gdb.compile/compile-cplus-method.exp: New file.
* gdb.compile/compile-cplus-mod.c: "New" file.
* gdb.compile/compile-cplus-namespace.cc: New file.
* gdb.compile/compile-cplus-namespace.exp: New file.
* gdb.compile/compile-cplus-nested.cc: New file.
* gdb.compile/compile-cplus-nested.exp: New file.
* gdb.compile/compile-cplus-print.c: "New" file.
* gdb.compile/compile-cplus-print.exp: "New" file.
* gdb.compile/compile-cplus-virtual.cc: New file.
* gdb.compile/compile-cplus-virtual.exp: New file.
* gdb.compile/compile-cplus.c: "New" file.
* gdb.compile/compile-cplus.exp: "New" file.
* lib/compile-support.exp: New file.
doc/ChangeLog:
* gdb.texinfo (Compiling and injecting code in GDB): Document
set/show "compile-oracle" and "compile-cplus-types" commands.
2018-08-30 06:12:24 +08:00
|
|
|
for other languages.
|
|
|
|
|
|
2018-09-13 00:24:41 +08:00
|
|
|
set debug skip
|
|
|
|
|
show debug skip
|
|
|
|
|
Control whether debug output about files/functions skipping is
|
|
|
|
|
displayed.
|
|
|
|
|
|
2018-07-13 05:02:14 +08:00
|
|
|
frame apply [all | COUNT | -COUNT | level LEVEL...] [FLAG]... COMMAND
|
|
|
|
|
Apply a command to some frames.
|
|
|
|
|
FLAG arguments allow to control what output to produce and how to handle
|
|
|
|
|
errors raised when applying COMMAND to a frame.
|
|
|
|
|
|
|
|
|
|
taas COMMAND
|
|
|
|
|
Apply a command to all threads (ignoring errors and empty output).
|
|
|
|
|
Shortcut for 'thread apply all -s COMMAND'.
|
|
|
|
|
|
|
|
|
|
faas COMMAND
|
|
|
|
|
Apply a command to all frames (ignoring errors and empty output).
|
|
|
|
|
Shortcut for 'frame apply all -s COMMAND'.
|
|
|
|
|
|
|
|
|
|
tfaas COMMAND
|
|
|
|
|
Apply a command to all frames of all threads (ignoring errors and empty
|
|
|
|
|
output).
|
|
|
|
|
Shortcut for 'thread apply all -s frame apply all -s COMMAND'.
|
|
|
|
|
|
2018-07-13 19:01:16 +08:00
|
|
|
maint set dwarf unwinders (on|off)
|
|
|
|
|
maint show dwarf unwinders
|
|
|
|
|
Control whether DWARF unwinders can be used.
|
|
|
|
|
|
2018-09-19 05:05:48 +08:00
|
|
|
info proc files
|
|
|
|
|
Display a list of open files for a process.
|
|
|
|
|
|
2018-07-13 05:02:14 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
2019-01-10 05:37:52 +08:00
|
|
|
Changes to the "frame", "select-frame", and "info frame" CLI commands.
|
|
|
|
|
These commands all now take a frame specification which
|
|
|
|
|
is either a frame level, or one of the keywords 'level', 'address',
|
|
|
|
|
'function', or 'view' followed by a parameter. Selecting a frame by
|
|
|
|
|
address, or viewing a frame outside the current backtrace now
|
|
|
|
|
requires the use of a keyword. Selecting a frame by level is
|
|
|
|
|
unchanged. The MI comment "-stack-select-frame" is unchanged.
|
|
|
|
|
|
2018-08-30 03:51:26 +08:00
|
|
|
target remote FILENAME
|
|
|
|
|
target extended-remote FILENAME
|
|
|
|
|
If FILENAME is a Unix domain socket, GDB will attempt to connect
|
|
|
|
|
to this socket instead of opening FILENAME as a character device.
|
|
|
|
|
|
2018-07-02 05:02:41 +08:00
|
|
|
info args [-q] [-t TYPEREGEXP] [NAMEREGEXP]
|
|
|
|
|
info functions [-q] [-t TYPEREGEXP] [NAMEREGEXP]
|
|
|
|
|
info locals [-q] [-t TYPEREGEXP] [NAMEREGEXP]
|
|
|
|
|
info variables [-q] [-t TYPEREGEXP] [NAMEREGEXP]
|
|
|
|
|
These commands can now print only the searched entities
|
|
|
|
|
matching the provided regexp(s), giving a condition
|
|
|
|
|
on the entity names or entity types. The flag -q disables
|
|
|
|
|
printing headers or informations messages.
|
|
|
|
|
|
2018-10-28 22:30:45 +08:00
|
|
|
info functions
|
|
|
|
|
info types
|
|
|
|
|
info variables
|
|
|
|
|
rbreak
|
|
|
|
|
These commands now determine the syntax for the shown entities
|
|
|
|
|
according to the language chosen by `set language'. In particular,
|
|
|
|
|
`set language auto' means to automatically choose the language of
|
|
|
|
|
the shown entities.
|
|
|
|
|
|
2018-07-13 05:02:14 +08:00
|
|
|
thread apply [all | COUNT | -COUNT] [FLAG]... COMMAND
|
|
|
|
|
The 'thread apply' command accepts new FLAG arguments.
|
|
|
|
|
FLAG arguments allow to control what output to produce and how to handle
|
|
|
|
|
errors raised when applying COMMAND to a thread.
|
|
|
|
|
|
2018-09-03 09:41:41 +08:00
|
|
|
set tui tab-width NCHARS
|
|
|
|
|
show tui tab-width NCHARS
|
|
|
|
|
"set tui tab-width" replaces the "tabset" command, which has been deprecated.
|
|
|
|
|
|
2018-11-27 07:19:17 +08:00
|
|
|
set style enabled [on|off]
|
|
|
|
|
show style enabled
|
|
|
|
|
Enable or disable terminal styling. Styling is enabled by default
|
2019-02-22 02:20:21 +08:00
|
|
|
on most hosts, but disabled by default when in batch mode.
|
2018-11-27 07:19:17 +08:00
|
|
|
|
2019-03-09 04:54:07 +08:00
|
|
|
set style sources [on|off]
|
|
|
|
|
show style sources
|
|
|
|
|
Enable or disable source code styling. Source code styling is
|
|
|
|
|
enabled by default, but only takes effect if styling in general is
|
|
|
|
|
enabled, and if GDB was linked with GNU Source Highlight.
|
|
|
|
|
|
2018-11-27 07:19:17 +08:00
|
|
|
set style filename foreground COLOR
|
|
|
|
|
set style filename background COLOR
|
|
|
|
|
set style filename intensity VALUE
|
|
|
|
|
Control the styling of file names.
|
|
|
|
|
|
|
|
|
|
set style function foreground COLOR
|
|
|
|
|
set style function background COLOR
|
|
|
|
|
set style function intensity VALUE
|
|
|
|
|
Control the styling of function names.
|
|
|
|
|
|
|
|
|
|
set style variable foreground COLOR
|
|
|
|
|
set style variable background COLOR
|
|
|
|
|
set style variable intensity VALUE
|
|
|
|
|
Control the styling of variable names.
|
|
|
|
|
|
|
|
|
|
set style address foreground COLOR
|
|
|
|
|
set style address background COLOR
|
|
|
|
|
set style address intensity VALUE
|
|
|
|
|
Control the styling of addresses.
|
|
|
|
|
|
2018-08-14 21:13:28 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** The '-data-disassemble' MI command now accepts an '-a' option to
|
|
|
|
|
disassemble the whole function surrounding the given program
|
|
|
|
|
counter value or function name. Support for this feature can be
|
|
|
|
|
verified by using the "-list-features" command, which should
|
|
|
|
|
contain "data-disassemble-a-option".
|
|
|
|
|
|
2018-08-22 17:42:38 +08:00
|
|
|
** Command responses and notifications that include a frame now include
|
|
|
|
|
the frame's architecture in a new "arch" attribute.
|
|
|
|
|
|
2018-08-10 04:37:45 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
GNU/Linux/RISC-V riscv*-*-linux*
|
2018-10-09 05:47:34 +08:00
|
|
|
FreeBSD/riscv riscv*-*-freebsd*
|
2018-08-10 04:37:45 +08:00
|
|
|
|
|
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
GNU/Linux/RISC-V riscv*-*-linux*
|
2018-07-25 17:45:26 +08:00
|
|
|
CSKY ELF csky*-*-elf
|
|
|
|
|
CSKY GNU/LINUX csky*-*-linux
|
2018-10-09 05:47:34 +08:00
|
|
|
FreeBSD/riscv riscv*-*-freebsd*
|
2019-03-13 04:56:53 +08:00
|
|
|
NXP S12Z s12z-*-elf
|
|
|
|
|
GNU/Linux/OpenRISC or1k*-*-linux*
|
2018-08-10 04:37:45 +08:00
|
|
|
|
2019-03-02 21:18:32 +08:00
|
|
|
* Removed targets
|
|
|
|
|
|
|
|
|
|
GDB no longer supports native debugging on versions of MS-Windows
|
|
|
|
|
before Windows XP.
|
|
|
|
|
|
2018-09-14 03:39:26 +08:00
|
|
|
* Python API
|
|
|
|
|
|
2019-02-22 08:22:13 +08:00
|
|
|
** GDB no longer supports Python versions less than 2.6.
|
|
|
|
|
|
2018-09-14 03:39:26 +08:00
|
|
|
** The gdb.Inferior type has a new 'progspace' property, which is the program
|
|
|
|
|
space associated to that inferior.
|
|
|
|
|
|
2018-09-14 03:40:41 +08:00
|
|
|
** The gdb.Progspace type has a new 'objfiles' method, which returns the list
|
|
|
|
|
of objfiles associated to that program space.
|
|
|
|
|
|
Update symbol domain and location values for Python
In the distant past, there was no distinction between domain_enum and
search_domain. At that point, there were two sets of enumerators in a
single enum -- which is why these were eventually split. This
confusion leaked out to the Python API as well, as noted in
PR python/21765.
This patch deprecates the constants that aren't useful to the Python
API. They are left in place for now, but removed from the
documentation. Also, their values are changed so that, if used, they
might work. Finally, missing domains and location constants are
added.
gdb/ChangeLog
2018-10-06 Tom Tromey <tom@tromey.com>
PR python/21765:
* python/py-symbol.c (gdbpy_initialize_symbols): Redefine
SYMBOL_VARIABLES_DOMAIN, SYMBOL_FUNCTIONS_DOMAIN,
SYMBOL_TYPES_DOMAIN. Define SYMBOL_MODULE_DOMAIN,
SYMBOL_COMMON_BLOCK_DOMAIN, SYMBOL_LOC_COMMON_BLOCK.
gdb/doc/ChangeLog
2018-10-06 Tom Tromey <tom@tromey.com>
PR python/21765:
* python.texi (Symbols In Python): Document the module and
common-block domains. Remove documentation for incorrect
domains.
2018-10-07 12:55:19 +08:00
|
|
|
** gdb.SYMBOL_LOC_COMMON_BLOCK, gdb.SYMBOL_MODULE_DOMAIN, and
|
|
|
|
|
gdb.SYMBOL_COMMON_BLOCK_DOMAIN were added to reflect changes to
|
|
|
|
|
the gdb core.
|
|
|
|
|
|
|
|
|
|
** gdb.SYMBOL_VARIABLES_DOMAIN, gdb.SYMBOL_FUNCTIONS_DOMAIN, and
|
|
|
|
|
gdb.SYMBOL_TYPES_DOMAIN are now deprecated. These were never
|
|
|
|
|
correct and did not work properly.
|
|
|
|
|
|
2019-02-17 09:31:51 +08:00
|
|
|
** The gdb.Value type has a new constructor, which is used to construct a
|
|
|
|
|
gdb.Value from a Python buffer object and a gdb.Type.
|
|
|
|
|
|
2018-08-19 05:32:46 +08:00
|
|
|
* Configure changes
|
|
|
|
|
|
|
|
|
|
--enable-ubsan
|
|
|
|
|
|
2018-10-10 01:51:33 +08:00
|
|
|
Enable or disable the undefined behavior sanitizer. This is
|
|
|
|
|
disabled by default, but passing --enable-ubsan=yes or
|
|
|
|
|
--enable-ubsan=auto to configure will enable it. Enabling this can
|
|
|
|
|
cause a performance penalty. The undefined behavior sanitizer was
|
|
|
|
|
first introduced in GCC 4.9.
|
2018-08-19 05:32:46 +08:00
|
|
|
|
2018-07-04 23:48:05 +08:00
|
|
|
*** Changes in GDB 8.2
|
2018-01-05 12:18:05 +08:00
|
|
|
|
GDB PR tdep/8282: MIPS: Wire in `set disassembler-options'
Implement MIPS target support for passing options to the disassembler,
complementing commit 65b48a81404c ("GDB: Add support for the new
set/show disassembler-options commands.").
This includes options that expect an argument, so adjust the generic
code and data structures used so as to handle such options. So as to
give backends syntax flexibility no specific delimiter has been defined
to separate options from their respective arguments, so it has to be
included as the last character of the option name. Completion code
however has not been adjusted and consequently option arguments cannot
be completed at this time.
Also the MIPS target has non-empty defaults for the options, so that ABI
names for the general-purpose registers respect our `set mips abi ...'
setting rather than always being determined from the ELF headers of the
binary file selected. Handle these defaults as implicit options, never
shown to the user and always prepended to the user-specified options, so
that the latters can override the defaults.
The resulting output for the MIPS target is as follows:
(gdb) show disassembler-options
The current disassembler options are ''
The following disassembler options are supported for use with the
'set disassembler-options <option>[,<option>...]' command:
no-aliases Use canonical instruction forms.
msa Recognize MSA instructions.
virt Recognize the virtualization ASE instructions.
xpa Recognize the eXtended Physical Address (XPA) ASE
instructions.
ginv Recognize the Global INValidate (GINV) ASE instructions.
gpr-names=ABI Print GPR names according to specified ABI.
Default: based on binary being disassembled.
fpr-names=ABI Print FPR names according to specified ABI.
Default: numeric.
cp0-names=ARCH Print CP0 register names according to specified architecture.
Default: based on binary being disassembled.
hwr-names=ARCH Print HWR names according to specified architecture.
Default: based on binary being disassembled.
reg-names=ABI Print GPR and FPR names according to specified ABI.
reg-names=ARCH Print CP0 register and HWR names according to specified
architecture.
For the options above, the following values are supported for "ABI":
numeric 32 n32 64
For the options above, the following values are supported for "ARCH":
numeric r3000 r3900 r4000 r4010 vr4100 vr4111 vr4120 r4300 r4400 r4600
r4650 r5000 vr5400 vr5500 r5900 r6000 rm7000 rm9000 r8000 r10000 r12000
r14000 r16000 mips5 mips32 mips32r2 mips32r3 mips32r5 mips32r6 mips64
mips64r2 mips64r3 mips64r5 mips64r6 interaptiv-mr2 sb1 loongson2e
loongson2f loongson3a octeon octeon+ octeon2 octeon3 xlr xlp
(gdb)
which corresponds to what `objdump --help' used to print for the MIPS
target, with minor formatting changes, most notably option argument
lists being wrapped, but also the amount of white space separating
options from the respective descriptions. The relevant part the new
code is now also used by `objdump --help', which means these formatting
changes apply to both outputs, except for argument list wrapping, which
is GDB-specific.
This also adds a separating new line between the heading and option
lists where descriptions are provided, hence:
(gdb) set architecture s390:31-bit
(gdb) show disassembler-options
The current disassembler options are ''
The following disassembler options are supported for use with the
'set disassembler-options <option>[,<option>...]' command:
esa Disassemble in ESA architecture mode
zarch Disassemble in z/Architecture mode
insnlength Print unknown instructions according to length from first two bits
(gdb)
but:
(gdb) set architecture powerpc:common
(gdb) show disassembler-options
The current disassembler options are ''
The following disassembler options are supported for use with the
'set disassembler-options <option>[,<option>...]' command:
403, 405, 440, 464, 476, 601, 603, 604, 620, 7400, 7410, 7450, 7455, 750cl,
821, 850, 860, a2, altivec, any, booke, booke32, cell, com, e200z4, e300,
e500, e500mc, e500mc64, e5500, e6500, e500x2, efs, efs2, power4, power5,
power6, power7, power8, power9, ppc, ppc32, 32, ppc64, 64, ppc64bridge,
ppcps, pwr, pwr2, pwr4, pwr5, pwr5x, pwr6, pwr7, pwr8, pwr9, pwrx, raw, spe,
spe2, titan, vle, vsx
(gdb)
Existing affected target backends have been adjusted accordingly.
This has been verified manually with:
(gdb) set architecture arm
(gdb) set architecture powerpc:common
(gdb) set architecture s390:31-bit
to cause no issues with the `show disassembler-options' and `set
disassembler-options' commands. A test case for the MIPS target has
also been provided, covering the default settings with ABI overrides as
well as disassembler option overrides.
2018-07-02 Maciej W. Rozycki <macro@mips.com>
Simon Marchi <simon.marchi@polymtl.ca>
include/
PR tdep/8282
* dis-asm.h (disasm_option_arg_t): New typedef.
(disasm_options_and_args_t): Likewise.
(disasm_options_t): Add `arg' member, document members.
(disassembler_options_mips): New prototype.
(disassembler_options_arm, disassembler_options_powerpc)
(disassembler_options_s390): Update prototypes.
opcodes/
PR tdep/8282
* mips-dis.c (mips_option_arg_t): New enumeration.
(mips_options): New variable.
(disassembler_options_mips): New function.
(print_mips_disassembler_options): Reimplement in terms of
`disassembler_options_mips'.
* arm-dis.c (disassembler_options_arm): Adapt to using the
`disasm_options_and_args_t' structure.
* ppc-dis.c (disassembler_options_powerpc): Likewise.
* s390-dis.c (disassembler_options_s390): Likewise.
gdb/
PR tdep/8282
* disasm.h (gdb_disassembler): Add
`m_disassembler_options_holder'. member
* disasm.c (get_all_disassembler_options): New function.
(gdb_disassembler::gdb_disassembler): Use it.
(gdb_buffered_insn_length_init_dis): Likewise.
(gdb_buffered_insn_length): Adjust accordingly.
(set_disassembler_options): Handle options with arguments.
(show_disassembler_options_sfunc): Likewise. Add a leading new
line if showing options with descriptions.
(disassembler_options_completer): Adapt to using the
`disasm_options_and_args_t' structure.
* mips-tdep.c (mips_disassembler_options): New variable.
(mips_disassembler_options_o32): Likewise.
(mips_disassembler_options_n32): Likewise.
(mips_disassembler_options_n64): Likewise.
(gdb_print_insn_mips): Don't set `disassembler_options'.
(gdb_print_insn_mips_n32, gdb_print_insn_mips_n64): Remove
functions.
(mips_gdbarch_init): Always set `gdbarch_print_insn' to
`gdb_print_insn_mips'. Set `gdbarch_disassembler_options',
`gdbarch_disassembler_options_implicit' and
`gdbarch_valid_disassembler_options'.
* arm-tdep.c (_initialize_arm_tdep): Adapt to using the
`disasm_options_and_args_t' structure.
* gdbarch.sh (disassembler_options_implicit): New `gdbarch'
method.
(valid_disassembler_options): Switch from `disasm_options_t' to
the `disasm_options_and_args_t' structure.
* NEWS: Document `set disassembler-options' support for the MIPS
target.
* gdbarch.h: Regenerate.
* gdbarch.c: Regenerate.
gdb/doc/
PR tdep/8282
* gdb.texinfo (Source and Machine Code): Document `set
disassembler-options' support for the MIPS target.
gdb/testsuite/
PR tdep/8282
* gdb.arch/mips-disassembler-options.exp: New test.
* gdb.arch/mips-disassembler-options.s: New test source.
2018-07-03 06:57:21 +08:00
|
|
|
* The 'set disassembler-options' command now supports specifying options
|
|
|
|
|
for the MIPS target.
|
|
|
|
|
|
2018-06-28 14:01:33 +08:00
|
|
|
* The 'symbol-file' command now accepts an '-o' option to add a relative
|
|
|
|
|
offset to all sections.
|
|
|
|
|
|
2018-06-28 14:33:17 +08:00
|
|
|
* Similarly, the 'add-symbol-file' command also accepts an '-o' option to add
|
|
|
|
|
a relative offset to all sections, but it allows to override the load
|
|
|
|
|
address of individual sections using '-s'.
|
|
|
|
|
|
2018-06-28 14:30:42 +08:00
|
|
|
* The 'add-symbol-file' command no longer requires the second argument
|
|
|
|
|
(address of the text section).
|
|
|
|
|
|
arch-utils: Make the last endianness actually chosen sticky
Use the last endianness explicitly selected, either by choosing a binary
file or with the `set endian' command, for future automatic selection.
As observed with the `gdb.base/step-over-no-symbols.exp' test case when
discarding the binary file even while connected to a live target the
endianness automatically selected is reset to the GDB target's default,
even if it does not match the endianness of the target being talked to.
For example with a little-endian MIPS target and the default endianness
being big we get this:
(gdb) file .../gdb/testsuite/outputs/gdb.base/step-over-no-symbols/step-over-no-symbols
Reading symbols from .../gdb/testsuite/outputs/gdb.base/step-over-no-symbols/step-over-no-symbols...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x400840: file .../gdb/testsuite/gdb.base/start.c, line 34.
[...]
(gdb) continue
Continuing.
Breakpoint 1, main () at .../gdb/testsuite/gdb.base/start.c:34
34 foo();
(gdb) delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) file
A program is being debugged already.
Are you sure you want to change the file? (y or n) y
No executable file now.
Discard symbol table from `.../gdb/testsuite/outputs/gdb.base/step-over-no-symbols/step-over-no-symbols'? (y or n) y
No symbol file now.
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: purging symbols
p /x $pc
$1 = 0x40084000
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: get before PC
break *$pc
Breakpoint 2 at 0x40084000
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: break *$pc
set displaced-stepping off
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: set displaced-stepping off
stepi
Warning:
Cannot insert breakpoint 2.
Cannot access memory at address 0x40084000
Command aborted.
(gdb) FAIL: gdb.base/step-over-no-symbols.exp: displaced=off: stepi
p /x $pc
$2 = 0x40084000
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: get after PC
FAIL: gdb.base/step-over-no-symbols.exp: displaced=off: advanced
Remote debugging from host ...
monitor exit
(gdb) Killing process(es): ...
testcase .../gdb/testsuite/gdb.base/step-over-no-symbols.exp completed in 2 seconds
which shows that with the removal of the executable debugged the
endianness of $pc still at `main' gets swapped and the value in that
register is now incorrectly interpreted as 0x40084000 rather than
0x400840 as shown earlier on with the `break' command. Consequently the
debug session no longer works as expected, until the endianness is
overridden with an explicit `set endian little' command.
This will happen while working with any target hardware whose endianness
does not match the default GDB target's endianness guessed and recorded
for a later use in `initialize_current_architecture'.
Given that within a single run of GDB it is more likely that consecutive
target connections will use the same endianness than that the endianness
will be swapped between connections, it makes sense to preserve the last
endianness explicitly selected as the automatic default. It will make a
session like above, where an executable is removed, work correctly and
will retain the endianness for a further reconnection to the target.
And the new automatic default will still be overridden by subsequently
choosing a binary to debug, or with an explicit `set endian' command.
With the change in place the test case above completes successfully:
(gdb) continue
Continuing.
Breakpoint 1, main () at .../gdb/testsuite/gdb.base/start.c:34
34 foo();
(gdb) delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) file
A program is being debugged already.
Are you sure you want to change the file? (y or n) y
No executable file now.
Discard symbol table from `.../gdb/testsuite/outputs/gdb.base/step-over-no-symbols/step-over-no-symbols'? (y or n) y
No symbol file now.
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: purging symbols
p /x $pc
warning: GDB can't find the start of the function at 0x400840.
GDB is unable to find the start of the function at 0x400840
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0x400840 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
$1 = 0x400840
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: get before PC
break *$pc
Breakpoint 2 at 0x400840
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: break *$pc
set displaced-stepping off
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: set displaced-stepping off
stepi
warning: GDB can't find the start of the function at 0x4007f8.
0x004007f8 in ?? ()
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: stepi
p /x $pc
$2 = 0x4007f8
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: get after PC
PASS: gdb.base/step-over-no-symbols.exp: displaced=off: advanced
Remote debugging from host ...
monitor exit
(gdb) Killing process(es): ...
testcase .../gdb/testsuite/gdb.base/step-over-no-symbols.exp completed in 2 seconds
gdb/
* arch-utils.c (gdbarch_info_fill): Set `default_byte_order' to
the endianness selected.
* NEWS: Document `set endian auto' mode operation update.
gdb/doc/
* gdb.texinfo (Choosing Target Byte Order): Document endianness
selection details with the `set endian auto' mode.
gdb/testsuite
* gdb.base/endian.exp: New test.
* gdb.base/endian.c: New test source.
2018-05-31 22:15:35 +08:00
|
|
|
* The endianness used with the 'set endian auto' mode in the absence of
|
|
|
|
|
an executable selected for debugging is now the last endianness chosen
|
|
|
|
|
either by one of the 'set endian big' and 'set endian little' commands
|
|
|
|
|
or by inferring from the last executable used, rather than the startup
|
|
|
|
|
default.
|
|
|
|
|
|
2018-04-25 22:52:00 +08:00
|
|
|
* The pager now allows a "c" response, meaning to disable the pager
|
|
|
|
|
for the rest of the current command.
|
|
|
|
|
|
2018-04-14 01:26:05 +08:00
|
|
|
* The commands 'info variables/functions/types' now show the source line
|
|
|
|
|
numbers of symbol definitions when available.
|
|
|
|
|
|
2018-01-10 05:35:17 +08:00
|
|
|
* 'info proc' now works on running processes on FreeBSD systems and core
|
|
|
|
|
files created on FreeBSD systems.
|
|
|
|
|
|
2018-04-21 03:40:29 +08:00
|
|
|
* C expressions can now use _Alignof, and C++ expressions can now use
|
|
|
|
|
alignof.
|
|
|
|
|
|
2018-08-22 16:17:24 +08:00
|
|
|
* Support for SVE on AArch64 Linux. Note that GDB does not detect changes to
|
|
|
|
|
the vector length while the process is running.
|
|
|
|
|
|
2018-03-04 13:25:33 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
set debug fbsd-nat
|
|
|
|
|
show debug fbsd-nat
|
|
|
|
|
Control display of debugging info regarding the FreeBSD native target.
|
|
|
|
|
|
2018-03-27 22:17:45 +08:00
|
|
|
set|show varsize-limit
|
|
|
|
|
This new setting allows the user to control the maximum size of Ada
|
|
|
|
|
objects being printed when those objects have a variable type,
|
|
|
|
|
instead of that maximum size being hardcoded to 65536 bytes.
|
|
|
|
|
|
2018-02-02 19:29:48 +08:00
|
|
|
set|show record btrace cpu
|
|
|
|
|
Controls the processor to be used for enabling errata workarounds for
|
|
|
|
|
branch trace decode.
|
|
|
|
|
|
2018-06-09 01:06:46 +08:00
|
|
|
maint check libthread-db
|
|
|
|
|
Run integrity checks on the current inferior's thread debugging
|
|
|
|
|
library
|
|
|
|
|
|
|
|
|
|
maint set check-libthread-db (on|off)
|
|
|
|
|
maint show check-libthread-db
|
|
|
|
|
Control whether to run integrity checks on inferior specific thread
|
|
|
|
|
debugging libraries as they are loaded. The default is not to
|
|
|
|
|
perform such checks.
|
|
|
|
|
|
2018-04-21 05:43:56 +08:00
|
|
|
* Python API
|
|
|
|
|
|
|
|
|
|
** Type alignment is now exposed via the "align" attribute of a gdb.Type.
|
|
|
|
|
|
2018-04-19 07:37:56 +08:00
|
|
|
** The commands attached to a breakpoint can be set by assigning to
|
|
|
|
|
the breakpoint's "commands" field.
|
|
|
|
|
|
2018-04-19 10:10:43 +08:00
|
|
|
** gdb.execute can now execute multi-line gdb commands.
|
|
|
|
|
|
2018-04-23 05:13:09 +08:00
|
|
|
** The new functions gdb.convenience_variable and
|
|
|
|
|
gdb.set_convenience_variable can be used to get and set the value
|
|
|
|
|
of convenience variables.
|
|
|
|
|
|
2018-04-27 06:51:40 +08:00
|
|
|
** A gdb.Parameter will no longer print the "set" help text on an
|
|
|
|
|
ordinary "set"; instead by default a "set" will be silent unless
|
|
|
|
|
the get_set_string method returns a non-empty string.
|
|
|
|
|
|
gdb: Initial baremetal riscv support
This commit introduces basic support for baremetal RiscV as a GDB
target. This target is currently only tested against the RiscV software
simulator, which is not included as part of this commit. The target has
been tested against the following RiscV variants: rv32im, rv32imc,
rv32imf, rv32imfc, rv64im, rv64imc, rv64imfd, rv64imfdc.
Across these variants we pass on average 34858 tests, and fail 272
tests, which is ~0.8%.
The RiscV has a feature of its ABI where structures with a single
floating point field, a single complex float field, or one float and
one integer field are treated differently for argument passing. The
new test gdb.base/infcall-nested-structs.exp is added to cover this
feature. As passing these structures should work on all targets then
I've made the test as a generic one, even though, for most targets,
there's probably nothing special about any of these cases.
gdb/ChangeLog:
* Makefile.in (ALL_TARGET_OBS): Add riscv-tdep.o
(HFILES_NO_SRCDIR): Add riscv-tdep.h.
(ALLDEPFILES): Add riscv-tdep.c
* configure.tgt: Add riscv support.
* riscv-tdep.c: New file.
* riscv-tdep.h: New file.
* NEWS: Mention new target.
* MAINTAINERS: Add entry for riscv.
gdb/testsuite/ChangeLog:
* gdb.base/infcall-nested-structs.exp: New file.
* gdb.base/infcall-nested-structs.c: New file.
* gdb.base/float.exp: Add riscv support.
2017-11-10 04:59:13 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
RiscV ELF riscv*-*-elf
|
|
|
|
|
|
2018-04-16 20:16:22 +08:00
|
|
|
* Removed targets and native configurations
|
|
|
|
|
|
|
|
|
|
m88k running OpenBSD m88*-*-openbsd*
|
2018-04-16 19:50:03 +08:00
|
|
|
SH-5/SH64 ELF sh64-*-elf*, SH-5/SH64 support in sh*
|
|
|
|
|
SH-5/SH64 running GNU/Linux SH-5/SH64 support in sh*-*-linux*
|
|
|
|
|
SH-5/SH64 running OpenBSD SH-5/SH64 support in sh*-*-openbsd*
|
2018-04-16 20:16:22 +08:00
|
|
|
|
2018-05-05 04:22:04 +08:00
|
|
|
* Aarch64/Linux hardware watchpoints improvements
|
|
|
|
|
|
|
|
|
|
Hardware watchpoints on unaligned addresses are now properly
|
|
|
|
|
supported when running Linux kernel 4.10 or higher: read and access
|
|
|
|
|
watchpoints are no longer spuriously missed, and all watchpoints
|
|
|
|
|
lengths between 1 and 8 bytes are supported. On older kernels,
|
|
|
|
|
watchpoints set on unaligned addresses are no longer missed, with
|
|
|
|
|
the tradeoff that there is a possibility of false hits being
|
|
|
|
|
reported.
|
|
|
|
|
|
2018-06-29 01:19:33 +08:00
|
|
|
* Configure changes
|
2018-06-29 00:32:13 +08:00
|
|
|
|
|
|
|
|
--enable-codesign=CERT
|
|
|
|
|
This can be used to invoke "codesign -s CERT" after building gdb.
|
|
|
|
|
This option is useful on macOS, where code signing is required for
|
|
|
|
|
gdb to work properly.
|
|
|
|
|
|
2018-06-29 01:19:33 +08:00
|
|
|
--disable-gdbcli has been removed
|
|
|
|
|
This is now silently accepted, but does nothing.
|
|
|
|
|
|
2018-01-05 12:18:05 +08:00
|
|
|
*** Changes in GDB 8.1
|
2017-04-17 22:30:29 +08:00
|
|
|
|
2017-12-27 22:36:31 +08:00
|
|
|
* GDB now supports dynamically creating arbitrary register groups specified
|
|
|
|
|
in XML target descriptions. This allows for finer grain grouping of
|
|
|
|
|
registers on systems with a large amount of registers.
|
|
|
|
|
|
Implement pahole-like 'ptype /o' option
This commit implements the pahole-like '/o' option for 'ptype', which
prints the offsets and sizes of struct fields, reporting whenever
there is a hole found.
The output is heavily based on pahole(1), with a few modifications
here and there to adjust it to our reality. Here's an example:
/* offset | size */ type = struct wer : public tuv {
public:
/* 32 | 24 */ struct tyu {
/* 32:31 | 4 */ int a1 : 1;
/* 32:28 | 4 */ int a2 : 3;
/* 32: 5 | 4 */ int a3 : 23;
/* 35: 3 | 1 */ char a4 : 2;
/* XXX 3-bit hole */
/* XXX 4-byte hole */
/* 40 | 8 */ int64_t a5;
/* 48:27 | 4 */ int a6 : 5;
/* 48:56 | 8 */ int64_t a7 : 3;
/* total size (bytes): 24 */
} a1;
/* total size (bytes): 56 */
}
A big part of this patch handles the formatting logic of 'ptype',
which is a bit messy. The code to handle bitfield offsets, however,
took some time to craft. My thanks to Pedro Alves for figuring things
out and pointing me to the right direction, as well as coming up with
a way to inspect the layout of structs with bitfields (see testcase
for comments).
After many discussions both on IRC and at the mailing list, I tried to
implement printing vtables and inherited classes. Unfortunately the
code grew too complex and there were still a few corner cases failing
so I had to drop the attempt. This should be implemented in a future
patch.
This patch is the start of a long-term work I'll do to flush the local
patches we carry for Fedora GDB. In this specific case, I'm aiming at
upstreaming the feature implemented by the 'pahole.py' script that is
shipped with Fedora GDB:
<https://src.fedoraproject.org/rpms/gdb/blob/master/f/gdb-archer.patch#_311>
This has been regression-tested on the BuildBot. There's a new
testcase for it, along with an update to the documentation. I also
thought it was worth mentioning this feature in the NEWS file.
gdb/ChangeLog:
2017-12-15 Sergio Durigan Junior <sergiodj@redhat.com>
Pedro Alves <palves@redhat.com>
PR cli/16224
* NEWS (Changes since GDB 8.0): Mention new '/o' flag.
* c-typeprint.c (OFFSET_SPC_LEN): New define.
(c_type_print_varspec_prefix): New argument 'struct
print_offset_data *'.
(c_type_print_base_1): New function and prototype.
(c_print_type_1): New function, with code from 'c_print_type'.
(c_print_type): Use 'c_print_type_1'.
(c_type_print_varspec_prefix): New argument 'struct
print_offset_data *'. Use it. Call 'c_type_print_base_1'
instead of 'c_print_type_base'.
(print_spaces_filtered_with_print_options): New function.
(output_access_specifier): Take new argument FLAGS. Modify
function to call 'print_spaces_filtered_with_print_options'.
(c_print_type_vtable_offset_marker): New function.
(c_print_type_union_field_offset): New function.
(c_print_type_struct_field_offset): New function.
(c_print_type_no_offsets): New function.
(c_type_print_base_struct_union): New argument 'struct
print_offset_data *'. Print offsets and sizes for
struct/union/class fields.
* typeprint.c (const struct type_print_options
type_print_raw_options): Initialize 'print_offsets'.
(static struct type_print_options default_ptype_flags):
Likewise.
(struct print_offset_data print_offset_default_data): New
variable.
(whatis_exp): Handle '/o' option.
(_initialize_typeprint): Add '/o' flag to ptype's help.
* typeprint.h (struct print_offset_data): New struct.
(struct type_print_options) <print_offsets>: New field.
gdb/testsuite/ChangeLog:
2017-12-15 Sergio Durigan Junior <sergiodj@redhat.com>
PR cli/16224
* gdb.base/ptype-offsets.cc: New file.
* gdb.base/ptype-offsets.exp: New file.
gdb/doc/ChangeLog:
2017-12-15 Sergio Durigan Junior <sergiodj@redhat.com>
PR cli/16224
* gdb.texinfo (ptype): Add documentation for new flag '/o'.
2017-11-21 05:34:59 +08:00
|
|
|
* The 'ptype' command now accepts a '/o' flag, which prints the
|
|
|
|
|
offsets and sizes of fields in a struct, like the pahole(1) tool.
|
|
|
|
|
|
Add support for the readnever concept
The purpose of this concept is to turn the load of debugging
information off, either globally (via the '--readnever' option), or
objfile-specific. The implementation proposed here is an extension of
the patch distributed with Fedora GDB; looking at the Fedora patch
itself and the history, one can see some reasons why it was never
resubmitted:
- The patch appears to have been introduced as a workaround, at
least initially;
- The patch is far from perfect, as it simply shunts the load of
DWARF debugging information, without really worrying about the
other debug format.
- Who really does non-symbolic debugging anyways?
One use of this feature is when a user simply wants to do the
following sequence: attach, dump core, detach. Loading the debugging
information in this case is an unnecessary cause of delay.
This patch expands the version shipped with Fedora GDB in order to
make the feature available for all the debuginfo backends, not only
for DWARF. It also implements a per-objfile flag which can be
activated by using the "-readnever" command when using the
'add-symbol-file' or 'symbol-file' commands.
It's also worth mentioning that this patch tests whether GDB correctly
fails to initialize if both '--readnow' and '--readnever' options are
passed.
Tested on the BuildBot.
gdb/ChangeLog:
2017-12-01 Andrew Cagney <cagney@redhat.com>
Joel Brobecker <brobecker@adacore.com>
Sergio Durigan Junior <sergiodj@redhat.com>
* NEWS (Changes since GDB 8.0: Mention new '--readnever'
feature.
* coffread.c (coff_symfile_read): Do not map over sections with
'coff_locate_sections' if readnever is on.
* dwarf2read.c (dwarf2_has_info): Return 0 if
readnever is on.
* elfread.c (elf_symfile_read): Do not map over sections with
'elf_locate_sections' if readnever is on.
* main.c (validate_readnow_readnever): New function.
(captured_main_1): Add support for --readnever.
(print_gdb_help): Document --readnever.
* objfile-flags.h (enum objfile_flag) <OBJF_READNEVER>: New
flag.
* symfile.c (readnever_symbol_files): New global.
(symbol_file_add_with_addrs): Set 'OBJF_READNEVER' when
'READNEVER_SYMBOL_FILES' is set.
(validate_readnow_readnever): New function.
(symbol_file_command): Handle '-readnever' option.
Call 'validate_readnow_readnever'.
(add_symbol_file_command): Handle '-readnever' option.
Call 'validate_readnow_readnever'.
(_initialize_symfile): Document new '-readnever' option for
both 'symbol-file' and 'add-symbol-file' commands.
* top.h (readnever_symbol_files): New extern global.
* xcoffread.c (xcoff_initial_scan): Do not read debug
information if readnever is on.
gdb/doc/ChangeLog:
2017-12-01 Andrew Cagney <cagney@redhat.com>
Joel Brobecker <brobecker@adacore.com>
Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.texinfo (File Options): Document --readnever.
(Commands to Specify Files): Likewise, for 'symbol-file' and
'add-symbol-file'.
gdb/testsuite/ChangeLog:
2017-12-01 Joel Brobecker <brobecker@adacore.com>
Sergio Durigan Junior <sergiodj@redhat.com>
Pedro Alves <palves@redhat.com>
* gdb.base/readnever.c, gdb.base/readnever.exp: New files.
2017-11-25 05:56:08 +08:00
|
|
|
* New "--readnever" command line option instructs GDB to not read each
|
|
|
|
|
symbol file's symbolic debug information. This makes startup faster
|
|
|
|
|
but at the expense of not being able to perform symbolic debugging.
|
|
|
|
|
This option is intended for use cases where symbolic debugging will
|
|
|
|
|
not be used, e.g., when you only need to dump the debuggee's core.
|
|
|
|
|
|
2017-11-22 20:53:43 +08:00
|
|
|
* GDB now uses the GNU MPFR library, if available, to emulate target
|
|
|
|
|
floating-point arithmetic during expression evaluation when the target
|
|
|
|
|
uses different floating-point formats than the host. At least version
|
|
|
|
|
3.1 of GNU MPFR is required.
|
|
|
|
|
|
2017-09-25 22:02:24 +08:00
|
|
|
* GDB now supports access to the guarded-storage-control registers and the
|
|
|
|
|
software-based guarded-storage broadcast control registers on IBM z14.
|
|
|
|
|
|
Implement the ability to set/unset environment variables to GDBserver when starting the inferior
This patch implements the ability to set/unset environment variables
on the remote target, mimicking what GDB already offers to the user.
There are two features present here: user-set and user-unset
environment variables.
User-set environment variables are only the variables that are
explicitly set by the user, using the 'set environment' command. This
means that variables that were already present in the environment when
starting GDB/GDBserver are not transmitted/considered by this feature.
User-unset environment variables are variables that are explicitly
unset by the user, using the 'unset environment' command.
The idea behind this patch is to store user-set and user-unset
environment variables in two separate sets, both part of gdb_environ.
Then, when extended_remote_create_inferior is preparing to start the
inferior, it will iterate over the two sets and set/unset variables
accordingly. Three new packets are introduced:
- QEnvironmentHexEncoded, which is used to set environment variables,
and contains an hex-encoded string in the format "VAR=VALUE" (VALUE
can be empty if the user set a variable with a null value, by doing
'set environment VAR=').
- QEnvironmentUnset, which is used to unset environment variables, and
contains an hex-encoded string in the format "VAR".
- QEnvironmentReset, which is always the first packet to be
transmitted, and is used to reset the environment, i.e., discard any
changes made by the user on previous runs.
The QEnvironmentHexEncoded packet is inspired on LLDB's extensions to
the RSP. Details about it can be seen here:
<https://raw.githubusercontent.com/llvm-mirror/lldb/master/docs/lldb-gdb-remote.txt>
I decided not to implement the QEnvironment packet because it is
considered deprecated by LLDB. This packet, on LLDB, serves the same
purpose of QEnvironmentHexEncoded, but sends the information using a
plain text, non-hex-encoded string.
The other two packets are new.
This patch also includes updates to the documentation, testsuite, and
unit tests, without introducing regressions.
gdb/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* NEWS (Changes since GDB 8.0): Add entry mentioning new support
for setting/unsetting environment variables on the remote target.
(New remote packets): Add entries for QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset.
* common/environ.c (gdb_environ::operator=): Extend method to
handle m_user_set_env_list and m_user_unset_env_list.
(gdb_environ::clear): Likewise.
(match_var_in_string): Change type of first parameter from 'char
*' to 'const char *'.
(gdb_environ::set): Extend method to handle
m_user_set_env_list and m_user_unset_env_list.
(gdb_environ::unset): Likewise.
(gdb_environ::clear_user_set_env): New method.
(gdb_environ::user_set_envp): Likewise.
(gdb_environ::user_unset_envp): Likewise.
* common/environ.h (gdb_environ): Handle m_user_set_env_list and
m_user_unset_env_list on move constructor/assignment.
(unset): Add new default parameter 'update_unset_list = true'.
(clear_user_set_env): New method.
(user_set_envp): Likewise.
(user_unset_envp): Likewise.
(m_user_set_env_list): New std::set.
(m_user_unset_env_list): Likewise.
* common/rsp-low.c (hex2str): New function.
(bin2hex): New overload for bin2hex function.
* common/rsp-low.c (hex2str): New prototype.
(str2hex): New overload prototype.
* remote.c: Include "environ.h". Add QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset.
(remote_protocol_features): Add QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset packets.
(send_environment_packet): New function.
(extended_remote_environment_support): Likewise.
(extended_remote_create_inferior): Call
extended_remote_environment_support.
(_initialize_remote): Add QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset packet configs.
* unittests/environ-selftests.c (gdb_selftest_env_var):
New variable.
(test_vector_initialization): New function.
(test_init_from_host_environ): Likewise.
(test_reinit_from_host_environ): Likewise.
(test_set_A_unset_B_unset_A_cannot_find_A_can_find_B):
Likewise.
(test_unset_set_empty_vector): Likewise.
(test_vector_clear): Likewise.
(test_std_move): Likewise.
(test_move_constructor):
(test_self_move): Likewise.
(test_set_unset_reset): Likewise.
(run_tests): Rewrite in terms of the functions above.
gdb/gdbserver/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* server.c (handle_general_set): Handle QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset packets.
(handle_query): Inform remote that QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset are supported.
gdb/doc/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.texinfo (set environment): Add @anchor. Explain that
environment variables set by the user are sent to GDBserver.
(unset environment): Likewise, but for unsetting variables.
(Connecting) <Remote Packet>: Add "environment-hex-encoded",
"QEnvironmentHexEncoded", "environment-unset", "QEnvironmentUnset",
"environment-reset" and "QEnvironmentReset" to the table.
(Remote Protocol) <QEnvironmentHexEncoded, QEnvironmentUnset,
QEnvironmentReset>: New item, explaining the packet.
gdb/testsuite/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.base/share-env-with-gdbserver.c: New file.
* gdb.base/share-env-with-gdbserver.exp: Likewise.
2017-06-30 03:06:07 +08:00
|
|
|
* On Unix systems, GDB now supports transmitting environment variables
|
|
|
|
|
that are to be set or unset to GDBserver. These variables will
|
|
|
|
|
affect the environment to be passed to the remote inferior.
|
|
|
|
|
|
|
|
|
|
To inform GDB of environment variables that are to be transmitted to
|
|
|
|
|
GDBserver, use the "set environment" command. Only user set
|
|
|
|
|
environment variables are sent to GDBserver.
|
|
|
|
|
|
|
|
|
|
To inform GDB of environment variables that are to be unset before
|
|
|
|
|
the remote inferior is started by the GDBserver, use the "unset
|
|
|
|
|
environment" command.
|
|
|
|
|
|
2017-11-24 23:21:16 +08:00
|
|
|
* Completion improvements
|
|
|
|
|
|
|
|
|
|
** GDB can now complete function parameters in linespecs and
|
|
|
|
|
explicit locations without quoting. When setting breakpoints,
|
|
|
|
|
quoting around functions names to help with TAB-completion is
|
|
|
|
|
generally no longer necessary. For example, this now completes
|
|
|
|
|
correctly:
|
|
|
|
|
|
|
|
|
|
(gdb) b function(in[TAB]
|
|
|
|
|
(gdb) b function(int)
|
|
|
|
|
|
|
|
|
|
Related, GDB is no longer confused with completing functions in
|
|
|
|
|
C++ anonymous namespaces:
|
|
|
|
|
|
|
|
|
|
(gdb) b (anon[TAB]
|
|
|
|
|
(gdb) b (anonymous namespace)::[TAB][TAB]
|
|
|
|
|
(anonymous namespace)::a_function()
|
|
|
|
|
(anonymous namespace)::b_function()
|
|
|
|
|
|
|
|
|
|
** GDB now has much improved linespec and explicit locations TAB
|
|
|
|
|
completion support, that better understands what you're
|
|
|
|
|
completing and offers better suggestions. For example, GDB no
|
|
|
|
|
longer offers data symbols as possible completions when you're
|
|
|
|
|
setting a breakpoint.
|
|
|
|
|
|
|
|
|
|
** GDB now TAB-completes label symbol names.
|
|
|
|
|
|
|
|
|
|
** The "complete" command now mimics TAB completion accurately.
|
|
|
|
|
|
2017-12-04 16:17:15 +08:00
|
|
|
* New command line options (gcore)
|
|
|
|
|
|
|
|
|
|
-a
|
|
|
|
|
Dump all memory mappings.
|
|
|
|
|
|
Make "break foo" find "A::foo", A::B::foo", etc. [C++ and wild matching]
This patch teaches GDB about setting breakpoints in all scopes
(namespaces and classes) by default.
Here's a contrived example:
(gdb) b func<tab>
(anonymous namespace)::A::function() Bn::(anonymous namespace)::B::function() function(int, int)
(anonymous namespace)::B::function() Bn::(anonymous namespace)::function() gdb::(anonymous namespace)::A::function()
(anonymous namespace)::B::function() const Bn::(anonymous namespace)::function(int, int) gdb::(anonymous namespace)::function()
(anonymous namespace)::function() Bn::B::func() gdb::(anonymous namespace)::function(int, int)
(anonymous namespace)::function(int, int) Bn::B::function() gdb::A::func()
A::func() Bn::func() gdb::A::function()
A::function() Bn::function() gdb::func()
B::func() Bn::function(int, int) gdb::function()
B::function() Bn::function(long) gdb::function(int, int)
B::function() const func() gdb::function(long)
B::function_const() const function()
(gdb) b function
Breakpoint 1 at 0x4005ce: function. (26 locations)
(gdb) b B::function<tab>
(anonymous namespace)::B::function() B::function() const Bn::B::function()
(anonymous namespace)::B::function() const B::function_const() const
B::function() Bn::(anonymous namespace)::B::function()
(gdb) b B::function
Breakpoint 1 at 0x40072c: B::function. (6 locations)
To get back the original behavior of interpreting the function name as
a fully-qualified name, you can use the new "-qualified" (or "-q")
option/flag (added by this commit). For example:
(gdb) b B::function
(anonymous namespace)::B::function() B::function() const Bn::B::function()
(anonymous namespace)::B::function() const B::function_const() const
B::function() Bn::(anonymous namespace)::B::function()
vs:
(gdb) b -qualified B::function
B::function() B::function() const B::function_const() const
I've chosen "-qualified" / "-q" because "-f" (for "full" or
"fully-qualified") is already taken for "-function".
Note: the "-qualified" option works with both linespecs and explicit
locations. I.e., these are equivalent:
(gdb) b -q func
(gdb) b -q -f func
and so are these:
(gdb) b -q filename.cc:func
(gdb) b -q -s filename.cc -f func
(gdb) b -s filename.cc -q -f func
(gdb) b -s filename.cc -f func -q
To better understand why I consider wild matching the better default,
consider what happens when we get to the point when _all_ of GDB is
wrapped under "namespace gdb {}". I have a patch series that does
that, and when I started debugging that GDB, I immediately became
frustrated. You'd have to write "b gdb::internal_error", "b
gdb::foo", "b gdb::bar", etc. etc., which gets annoying pretty
quickly. OTOH, consider how this makes it very easy to set
breakpoints in classes wrapped in anonymous namespaces. You just
don't think of them, GDB finds the symbols for you automatically.
(At the Cauldron a couple months ago, several people told me that they
run into a similar issue when debugging other C++ projects. One
example was when debugging LLVM, which puts all its code under the
"llvm" namespace.)
Implementation-wise, what the patch does is:
- makes C++ symbol name hashing only consider the last component of
a symbol name. (so that we can look up symbol names by
last-component name only).
- adds a C++ symbol name matcher for symbol_name_match_type::WILD,
which ignores missing leading specifiers / components.
- adjusts a few preexisting testsuite tests to use "-qualified" when
they mean it.
- adds new testsuite tests.
- adds unit tests.
Grows the gdb.linespec/ tests like this:
-# of expected passes 7823
+# of expected passes 8977
gdb/ChangeLog:
2017-11-29 Pedro Alves <palves@redhat.com>
* NEWS: Mention that breakpoints on C++ functions are now set on
on all namespaces/classes by default, and mention "break
-qualified".
* ax-gdb.c (agent_command_1): Adjust to pass a
symbol_name_match_type to new_linespec_location.
* breakpoint.c (parse_breakpoint_sals): Adjust to
get_linespec_location's return type change.
(strace_marker_create_sals_from_location): Adjust to pass a
symbol_name_match_type to new_linespec_location.
(strace_marker_decode_location): Adjust to get_linespec_location's
return type change.
(strace_command): Adjust to pass a symbol_name_match_type to
new_linespec_location.
(LOCATION_HELP_STRING): Add paragraph about wildmatching, and
mention "-qualified".
* c-lang.c (cplus_language_defn): Install cp_search_name_hash.
* completer.c (explicit_location_match_type::MATCH_QUALIFIED): New
enumerator.
(complete_address_and_linespec_locations): New parameter
'match_type'. Pass it down.
(explicit_options): Add "-qualified".
(collect_explicit_location_matches): Pass the requested match type
to the linespec completers. Handle MATCH_QUALIFIED.
(location_completer): Handle "-qualified" combined with linespecs.
* cp-support.c (cp_search_name_hash): New.
(cp_symbol_name_matches_1): Implement wild matching for C++.
(cp_fq_symbol_name_matches): Reimplement.
(cp_get_symbol_name_matcher): Return different matchers depending
on the lookup name's match type.
(selftests::test_cp_symbol_name_matches): Add wild matching tests.
* cp-support.h (cp_search_name_hash): New declaration.
* dwarf2read.c
(selftests::dw2_expand_symtabs_matching::test_symbols): Add
symbols.
(test_dw2_expand_symtabs_matching_symbol): Add wild matching
tests.
* guile/scm-breakpoint.c (gdbscm_register_breakpoint_x): Adjust to
pass a symbol_name_match_type to new_linespec_location.
* linespec.c (linespec_parse_basic): Lookup function symbols using
the parser's symbol name match type.
(convert_explicit_location_to_linespec): New
symbol_name_match_type parameter. Pass it down to
find_linespec_symbols.
(convert_explicit_location_to_sals): Pass the location's name
match type to convert_explicit_location_to_linespec.
(parse_linespec): New match_type parameter. Save it in the
parser.
(linespec_parser_new): Default to symbol_name_match_type::WILD.
(linespec_complete_function): New symbol_name_match_type
parameter. Use it.
(complete_linespec_component): Pass down the parser's recorded
name match type.
(linespec_complete_label): New symbol_name_match_type parameter.
Use it.
(linespec_complete): New symbol_name_match_type parameter. Save
it in the parser and pass it down. Adjust to
get_linespec_location's prototype change.
(find_function_symbols, find_linespec_symbols): New
symbol_name_match_type parameter. Pass it down instead of
assuming symbol_name_match_type::WILD.
* linespec.h (linespec_complete, linespec_complete_function)
(linespec_complete_label): New symbol_name_match_type parameter.
* location.c (event_location::linespec_location): Now a struct
linespec_location.
(EL_LINESPEC): Adjust.
(initialize_explicit_location): Default to
symbol_name_match_type::WILD.
(new_linespec_location): New symbol_name_match_type parameter.
Record it in the location.
(get_linespec_location): Now returns a struct linespec_location.
(new_explicit_location): Also copy func_name_match_type.
(explicit_to_string_internal)
(string_to_explicit_location): Handle "-qualified".
(copy_event_location): Adjust to LINESPEC_LOCATION type change.
Copy symbol_name_match_type fields.
(event_location_deleter::operator()): Adjust to LINESPEC_LOCATION
type change.
(event_location_to_string): Adjust to LINESPEC_LOCATION type
change. Handle "-qualfied".
(string_to_explicit_location): Handle "-qualified".
(string_to_event_location_basic): New symbol_name_match_type
parameter. Pass it down.
(string_to_event_location): Handle "-qualified".
* location.h (struct linespec_location): New.
(explicit_location::func_name_match_type): New field.
(new_linespec_location): Now returns a const linespec_location *.
(string_to_event_location_basic): New symbol_name_match_type
parameter.
(explicit_completion_info::saw_explicit_location_option): New
field.
* mi/mi-cmd-break.c (mi_cmd_break_insert_1): Adjust to pass a
symbol_name_match_type to new_linespec_location.
* python/py-breakpoint.c (bppy_init): Likewise.
* python/python.c (gdbpy_decode_line): Likewise.
gdb/testsuite/ChangeLog:
2017-11-29 Pedro Alves <palves@redhat.com>
* gdb.base/langs.exp: Use -qualified.
* gdb.cp/meth-typedefs.exp: Use -qualified, and add tests without
it.
* gdb.cp/namespace.exp: Use -qualified.
* gdb.linespec/cpcompletion.exp (overload-2, fqn, fqn-2)
(overload-3, template-overload, template-ret-type, const-overload)
(const-overload-quoted, anon-ns, ambiguous-prefix): New
procedures.
(test_driver): Call them.
* gdb.cp/save-bp-qualified.cc: New.
* gdb.cp/save-bp-qualified.exp: New.
* gdb.linespec/explicit.exp: Test -qualified.
* lib/completion-support.exp (completion::explicit_opts_list): Add
"-qualified".
* lib/gdb.exp (gdb_breakpoint): Handle "qualified".
gdb/doc/ChangeLog:
2017-11-29 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Linespec Locations): Document how "function" is
interpreted in C++ and Ada. Document "-qualified".
(Explicit Locations): Document how "-function" is interpreted in
C++ and Ada. Document "-qualified".
2017-11-30 03:33:23 +08:00
|
|
|
* Breakpoints on C++ functions are now set on all scopes by default
|
|
|
|
|
|
|
|
|
|
By default, breakpoints on functions/methods are now interpreted as
|
|
|
|
|
specifying all functions with the given name ignoring missing
|
|
|
|
|
leading scopes (namespaces and classes).
|
|
|
|
|
|
|
|
|
|
For example, assuming a C++ program with symbols named:
|
|
|
|
|
|
|
|
|
|
A::B::func()
|
|
|
|
|
B::func()
|
|
|
|
|
|
|
|
|
|
both commands "break func()" and "break B::func()" set a breakpoint
|
|
|
|
|
on both symbols.
|
|
|
|
|
|
|
|
|
|
You can use the new flag "-qualified" to override this. This makes
|
|
|
|
|
GDB interpret the specified function name as a complete
|
|
|
|
|
fully-qualified name instead. For example, using the same C++
|
|
|
|
|
program, the "break -q B::func" command sets a breakpoint on
|
2017-12-14 00:37:09 +08:00
|
|
|
"B::func", only. A parameter has been added to the Python
|
|
|
|
|
gdb.Breakpoint constructor to achieve the same result when creating
|
|
|
|
|
a breakpoint from Python.
|
Make "break foo" find "A::foo", A::B::foo", etc. [C++ and wild matching]
This patch teaches GDB about setting breakpoints in all scopes
(namespaces and classes) by default.
Here's a contrived example:
(gdb) b func<tab>
(anonymous namespace)::A::function() Bn::(anonymous namespace)::B::function() function(int, int)
(anonymous namespace)::B::function() Bn::(anonymous namespace)::function() gdb::(anonymous namespace)::A::function()
(anonymous namespace)::B::function() const Bn::(anonymous namespace)::function(int, int) gdb::(anonymous namespace)::function()
(anonymous namespace)::function() Bn::B::func() gdb::(anonymous namespace)::function(int, int)
(anonymous namespace)::function(int, int) Bn::B::function() gdb::A::func()
A::func() Bn::func() gdb::A::function()
A::function() Bn::function() gdb::func()
B::func() Bn::function(int, int) gdb::function()
B::function() Bn::function(long) gdb::function(int, int)
B::function() const func() gdb::function(long)
B::function_const() const function()
(gdb) b function
Breakpoint 1 at 0x4005ce: function. (26 locations)
(gdb) b B::function<tab>
(anonymous namespace)::B::function() B::function() const Bn::B::function()
(anonymous namespace)::B::function() const B::function_const() const
B::function() Bn::(anonymous namespace)::B::function()
(gdb) b B::function
Breakpoint 1 at 0x40072c: B::function. (6 locations)
To get back the original behavior of interpreting the function name as
a fully-qualified name, you can use the new "-qualified" (or "-q")
option/flag (added by this commit). For example:
(gdb) b B::function
(anonymous namespace)::B::function() B::function() const Bn::B::function()
(anonymous namespace)::B::function() const B::function_const() const
B::function() Bn::(anonymous namespace)::B::function()
vs:
(gdb) b -qualified B::function
B::function() B::function() const B::function_const() const
I've chosen "-qualified" / "-q" because "-f" (for "full" or
"fully-qualified") is already taken for "-function".
Note: the "-qualified" option works with both linespecs and explicit
locations. I.e., these are equivalent:
(gdb) b -q func
(gdb) b -q -f func
and so are these:
(gdb) b -q filename.cc:func
(gdb) b -q -s filename.cc -f func
(gdb) b -s filename.cc -q -f func
(gdb) b -s filename.cc -f func -q
To better understand why I consider wild matching the better default,
consider what happens when we get to the point when _all_ of GDB is
wrapped under "namespace gdb {}". I have a patch series that does
that, and when I started debugging that GDB, I immediately became
frustrated. You'd have to write "b gdb::internal_error", "b
gdb::foo", "b gdb::bar", etc. etc., which gets annoying pretty
quickly. OTOH, consider how this makes it very easy to set
breakpoints in classes wrapped in anonymous namespaces. You just
don't think of them, GDB finds the symbols for you automatically.
(At the Cauldron a couple months ago, several people told me that they
run into a similar issue when debugging other C++ projects. One
example was when debugging LLVM, which puts all its code under the
"llvm" namespace.)
Implementation-wise, what the patch does is:
- makes C++ symbol name hashing only consider the last component of
a symbol name. (so that we can look up symbol names by
last-component name only).
- adds a C++ symbol name matcher for symbol_name_match_type::WILD,
which ignores missing leading specifiers / components.
- adjusts a few preexisting testsuite tests to use "-qualified" when
they mean it.
- adds new testsuite tests.
- adds unit tests.
Grows the gdb.linespec/ tests like this:
-# of expected passes 7823
+# of expected passes 8977
gdb/ChangeLog:
2017-11-29 Pedro Alves <palves@redhat.com>
* NEWS: Mention that breakpoints on C++ functions are now set on
on all namespaces/classes by default, and mention "break
-qualified".
* ax-gdb.c (agent_command_1): Adjust to pass a
symbol_name_match_type to new_linespec_location.
* breakpoint.c (parse_breakpoint_sals): Adjust to
get_linespec_location's return type change.
(strace_marker_create_sals_from_location): Adjust to pass a
symbol_name_match_type to new_linespec_location.
(strace_marker_decode_location): Adjust to get_linespec_location's
return type change.
(strace_command): Adjust to pass a symbol_name_match_type to
new_linespec_location.
(LOCATION_HELP_STRING): Add paragraph about wildmatching, and
mention "-qualified".
* c-lang.c (cplus_language_defn): Install cp_search_name_hash.
* completer.c (explicit_location_match_type::MATCH_QUALIFIED): New
enumerator.
(complete_address_and_linespec_locations): New parameter
'match_type'. Pass it down.
(explicit_options): Add "-qualified".
(collect_explicit_location_matches): Pass the requested match type
to the linespec completers. Handle MATCH_QUALIFIED.
(location_completer): Handle "-qualified" combined with linespecs.
* cp-support.c (cp_search_name_hash): New.
(cp_symbol_name_matches_1): Implement wild matching for C++.
(cp_fq_symbol_name_matches): Reimplement.
(cp_get_symbol_name_matcher): Return different matchers depending
on the lookup name's match type.
(selftests::test_cp_symbol_name_matches): Add wild matching tests.
* cp-support.h (cp_search_name_hash): New declaration.
* dwarf2read.c
(selftests::dw2_expand_symtabs_matching::test_symbols): Add
symbols.
(test_dw2_expand_symtabs_matching_symbol): Add wild matching
tests.
* guile/scm-breakpoint.c (gdbscm_register_breakpoint_x): Adjust to
pass a symbol_name_match_type to new_linespec_location.
* linespec.c (linespec_parse_basic): Lookup function symbols using
the parser's symbol name match type.
(convert_explicit_location_to_linespec): New
symbol_name_match_type parameter. Pass it down to
find_linespec_symbols.
(convert_explicit_location_to_sals): Pass the location's name
match type to convert_explicit_location_to_linespec.
(parse_linespec): New match_type parameter. Save it in the
parser.
(linespec_parser_new): Default to symbol_name_match_type::WILD.
(linespec_complete_function): New symbol_name_match_type
parameter. Use it.
(complete_linespec_component): Pass down the parser's recorded
name match type.
(linespec_complete_label): New symbol_name_match_type parameter.
Use it.
(linespec_complete): New symbol_name_match_type parameter. Save
it in the parser and pass it down. Adjust to
get_linespec_location's prototype change.
(find_function_symbols, find_linespec_symbols): New
symbol_name_match_type parameter. Pass it down instead of
assuming symbol_name_match_type::WILD.
* linespec.h (linespec_complete, linespec_complete_function)
(linespec_complete_label): New symbol_name_match_type parameter.
* location.c (event_location::linespec_location): Now a struct
linespec_location.
(EL_LINESPEC): Adjust.
(initialize_explicit_location): Default to
symbol_name_match_type::WILD.
(new_linespec_location): New symbol_name_match_type parameter.
Record it in the location.
(get_linespec_location): Now returns a struct linespec_location.
(new_explicit_location): Also copy func_name_match_type.
(explicit_to_string_internal)
(string_to_explicit_location): Handle "-qualified".
(copy_event_location): Adjust to LINESPEC_LOCATION type change.
Copy symbol_name_match_type fields.
(event_location_deleter::operator()): Adjust to LINESPEC_LOCATION
type change.
(event_location_to_string): Adjust to LINESPEC_LOCATION type
change. Handle "-qualfied".
(string_to_explicit_location): Handle "-qualified".
(string_to_event_location_basic): New symbol_name_match_type
parameter. Pass it down.
(string_to_event_location): Handle "-qualified".
* location.h (struct linespec_location): New.
(explicit_location::func_name_match_type): New field.
(new_linespec_location): Now returns a const linespec_location *.
(string_to_event_location_basic): New symbol_name_match_type
parameter.
(explicit_completion_info::saw_explicit_location_option): New
field.
* mi/mi-cmd-break.c (mi_cmd_break_insert_1): Adjust to pass a
symbol_name_match_type to new_linespec_location.
* python/py-breakpoint.c (bppy_init): Likewise.
* python/python.c (gdbpy_decode_line): Likewise.
gdb/testsuite/ChangeLog:
2017-11-29 Pedro Alves <palves@redhat.com>
* gdb.base/langs.exp: Use -qualified.
* gdb.cp/meth-typedefs.exp: Use -qualified, and add tests without
it.
* gdb.cp/namespace.exp: Use -qualified.
* gdb.linespec/cpcompletion.exp (overload-2, fqn, fqn-2)
(overload-3, template-overload, template-ret-type, const-overload)
(const-overload-quoted, anon-ns, ambiguous-prefix): New
procedures.
(test_driver): Call them.
* gdb.cp/save-bp-qualified.cc: New.
* gdb.cp/save-bp-qualified.exp: New.
* gdb.linespec/explicit.exp: Test -qualified.
* lib/completion-support.exp (completion::explicit_opts_list): Add
"-qualified".
* lib/gdb.exp (gdb_breakpoint): Handle "qualified".
gdb/doc/ChangeLog:
2017-11-29 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Linespec Locations): Document how "function" is
interpreted in C++ and Ada. Document "-qualified".
(Explicit Locations): Document how "-function" is interpreted in
C++ and Ada. Document "-qualified".
2017-11-30 03:33:23 +08:00
|
|
|
|
Breakpoints in symbols with ABI tags (PR c++/19436)
Trying to set a breakpoint in a function with an ABI tag does not work
currently. E.g., debugging gdb itself, we see this with the
"string_printf" function:
(top-gdb) b string_print [TAB]
(top-gdb) b string_printf[abi:cxx11](char const*, ...) [RET]
No source file named string_printf[abi.
Make breakpoint pending on future shared library load? (y or [n])
Quoting doesn't help:
(top-gdb) b 'string_printf[abi:cxx11]'(char const*, ...)
malformed linespec error: unexpected string, "(char const*, ...)"
(top-gdb) b 'string_printf[abi:cxx11](char const*, ...)'
No source file named string_printf[abi.
Make breakpoint pending on future shared library load? (y or [n]) n
This patch fixes this, and takes it a bit further.
The actual symbol name as demangled by libiberty's demangler is really
string_printf[abi:cxx11](char const*, ...)
however, this patch makes it possible to set the breakpoint with
string_printf(char const*, ...)
too. I.e., ignoring the ABI tag.
And to match, it teaches the completer to complete the symbol name
without the ABI tag, i.e.,
"string_pri<TAB>" -> "string_printf(char const*, ...)"
If however, you really want to break on a symbol with the tag, then
you simply start writing the tag, and GDB will preserve it, like:
"string_printf[a<TAB>" -> "string_printf[abi:cxx11](char const*, ...)"
Grows the gdb.linespec/ tests like this:
-# of expected passes 8977
+# of expected passes 9176
gdb/ChangeLog:
2017-11-29 Pedro Alves <palves@redhat.com>
PR c++/19436
* NEWS: Mention setting breakpoints on functions with C++ ABI
tags.
* completer.h (completion_match_for_lcd) <match,
mark_ignored_range>: New methods.
<finish>: Consider ignored ranges.
<clear>: Clear ignored ranges.
<m_ignored_ranges, m_finished_storage>: New fields.
* cp-support.c (cp_search_name_hash): Ignore ABI tags.
(cp_symbol_name_matches_1, cp_fq_symbol_name_matches): Pass the
completion_match_for_lcd pointer to strncmp_iw_with_mode.
(test_cp_symbol_name_cmp): Add [abi:...] tags unit tests.
* language.c (default_symbol_name_matcher): Pass the
completion_match_for_lcd pointer to strncmp_iw_with_mode.
* linespec.c (linespec_lexer_lex_string): Don't tokenize ABI tags.
* utils.c (skip_abi_tag): New function.
(strncmp_iw_with_mode): Add completion_match_for_lcd parameter.
Handle ABI tags.
* utils.h (strncmp_iw_with_mode): Add completion_match_for_lcd
parameter.
gdb/testsuite/ChangeLog:
2017-11-29 Pedro Alves <palves@redhat.com>
PR c++/19436
* gdb.linespec/cpls-abi-tag.cc: New file.
* gdb.linespec/cpls-abi-tag.exp: New file.
gdb/doc/ChangeLog:
2017-11-29 Pedro Alves <palves@redhat.com>
PR c++/19436
* gdb.texinfo (Debugging C Plus Plus): Document setting
breakpoints in functions with ABI tags.
2017-11-30 03:33:24 +08:00
|
|
|
* Breakpoints on functions marked with C++ ABI tags
|
|
|
|
|
|
|
|
|
|
GDB can now set breakpoints on functions marked with C++ ABI tags
|
|
|
|
|
(e.g., [abi:cxx11]). See here for a description of ABI tags:
|
|
|
|
|
https://developers.redhat.com/blog/2015/02/05/gcc5-and-the-c11-abi/
|
|
|
|
|
|
|
|
|
|
Functions with a C++11 abi tag are demangled/displayed like this:
|
|
|
|
|
|
|
|
|
|
function[abi:cxx11](int)
|
|
|
|
|
^^^^^^^^^^^
|
|
|
|
|
|
|
|
|
|
You can now set a breakpoint on such functions simply as if they had
|
|
|
|
|
no tag, like:
|
|
|
|
|
|
|
|
|
|
(gdb) b function(int)
|
|
|
|
|
|
|
|
|
|
Or if you need to disambiguate between tags, like:
|
|
|
|
|
|
|
|
|
|
(gdb) b function[abi:other_tag](int)
|
|
|
|
|
|
|
|
|
|
Tab completion was adjusted accordingly as well.
|
|
|
|
|
|
Add new_inferior, inferior_deleted, and new_thread events
This adds a few new events to gdb's Python layer: new_inferior,
inferior_deleted, and new_thread. I wanted to be able to add a
combined inferior/thread display window to my GUI, and I needed a few
events to make this work. This is PR python/15622.
ChangeLog
2017-09-11 Tom Tromey <tom@tromey.com>
PR python/15622:
* NEWS: Add entry.
* python/python.c (do_start_initialization): Initialize new event
types.
* python/python-internal.h (gdbpy_initialize_new_inferior_event)
(gdbpy_initialize_inferior_deleted_event)
(gdbpy_initialize_new_thread_event): Declare.
* python/py-threadevent.c (create_thread_event_object): Add option
"thread" parameter.
* python/py-inferior.c (new_thread_event_object_type)
(new_inferior_event_object_type)
(inferior_deleted_event_object_type): Declare.
(python_new_inferior, python_inferior_deleted): New functions.
(add_thread_object): Emit new_thread event.
(gdbpy_initialize_inferior): Attach new functions to corresponding
observers.
(new_thread, new_inferior, inferior_deleted): Define new event
types.
* python/py-evts.c (gdbpy_initialize_py_events): Add new
registries.
* python/py-events.h (events_object) <new_inferior,
inferior_deleted, new_thread>: New fields.
* python/py-event.h (create_thread_event_breakpoint): Add optional
"thread" parameter.
doc/ChangeLog
2017-09-11 Tom Tromey <tom@tromey.com>
* python.texi (Events In Python): Document new events.
testsuite/ChangeLog
2017-09-11 Tom Tromey <tom@tromey.com>
* gdb.python/py-infthread.exp: Add tests for new_thread event.
* gdb.python/py-inferior.exp: Add tests for new inferior events.
2017-09-06 02:07:00 +08:00
|
|
|
* Python Scripting
|
|
|
|
|
|
|
|
|
|
** New events gdb.new_inferior, gdb.inferior_deleted, and
|
|
|
|
|
gdb.new_thread are emitted. See the manual for further
|
|
|
|
|
description of these.
|
|
|
|
|
|
2018-02-09 20:04:38 +08:00
|
|
|
** A new function, "gdb.rbreak" has been added to the Python API.
|
|
|
|
|
This function allows the setting of a large number of breakpoints
|
|
|
|
|
via a regex pattern in Python. See the manual for further details.
|
2017-11-16 22:14:03 +08:00
|
|
|
|
2017-12-08 00:47:33 +08:00
|
|
|
** Python breakpoints can now accept explicit locations. See the
|
|
|
|
|
manual for a further description of this feature.
|
|
|
|
|
|
|
|
|
|
|
2017-08-18 16:20:43 +08:00
|
|
|
* New features in the GDB remote stub, GDBserver
|
|
|
|
|
|
Extend "set cwd" to work on gdbserver
This is the "natural" extension necessary for the "set cwd" command
(and the whole "set the inferior's cwd" logic) to work on gdbserver.
The idea here is to have a new remote packet, QSetWorkingDir (name
adopted from LLDB's extension to the RSP, as can be seen at
<https://raw.githubusercontent.com/llvm-mirror/lldb/master/docs/lldb-gdb-remote.txt>),
which sends an hex-encoded string representing the working directory
that the remote inferior will use. There is a slight difference from
the packet proposed by LLDB: GDB's version will accept empty
arguments, meaning that the user wants to clear the previously set
working directory for the inferior (i.e., "set cwd" without arguments
on GDB).
For UNIX-like targets this feature is already implemented on
nat/fork-inferior.c, and all gdbserver has to do is to basically
implement "set_inferior_cwd" and call it whenever such packet arrives.
For other targets, like Windows, it is possible to use the existing
"get_inferior_cwd" function and do the necessary steps to make sure
that the inferior will use the specified working directory.
Aside from that, the patch consists basically of updates to the
testcase (making it available on remote targets) and the
documentation.
No regressions found.
gdb/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* NEWS (Changes since GDB 8.0): Add entry about new
'set-cwd-on-gdbserver' feature.
(New remote packets): Add entry for QSetWorkingDir.
* common/common-inferior.h (set_inferior_cwd): New prototype.
* infcmd.c (set_inferior_cwd): Remove "static".
(show_cwd_command): Expand text to include remote debugging.
* remote.c: Add PACKET_QSetWorkingDir.
(remote_protocol_features) <QSetWorkingDir>: New entry for
PACKET_QSetWorkingDir.
(extended_remote_set_inferior_cwd): New function.
(extended_remote_create_inferior): Call
"extended_remote_set_inferior_cwd".
(_initialize_remote): Call "add_packet_config_cmd" for
QSetWorkingDir.
gdb/gdbserver/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* inferiors.c (set_inferior_cwd): New function.
* server.c (handle_general_set): Handle QSetWorkingDir packet.
(handle_query): Inform that QSetWorkingDir is supported.
* win32-low.c (create_process): Pass the inferior's cwd to
CreateProcess.
gdb/testsuite/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.base/set-cwd.exp: Make it available on
native-extended-gdbserver.
gdb/doc/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.texinfo (Starting your Program) <The working directory.>:
Mention remote debugging.
(Working Directory) <Your Program's Working Directory>:
Likewise.
(Connecting) <Remote Packet>: Add "set-working-dir"
and "QSetWorkingDir" to the table.
(Remote Protocol) <QSetWorkingDir>: New item, explaining the
packet.
2017-09-21 07:15:40 +08:00
|
|
|
** GDBserver is now able to start inferior processes with a
|
|
|
|
|
specified initial working directory.
|
|
|
|
|
|
|
|
|
|
The user can set the desired working directory to be used from
|
|
|
|
|
GDB using the new "set cwd" command.
|
|
|
|
|
|
2017-08-18 16:20:43 +08:00
|
|
|
** New "--selftest" command line option runs some GDBserver self
|
|
|
|
|
tests. These self tests are disabled in releases.
|
|
|
|
|
|
|
|
|
|
** On Unix systems, GDBserver now does globbing expansion and variable
|
|
|
|
|
substitution in inferior command line arguments.
|
|
|
|
|
|
|
|
|
|
This is done by starting inferiors using a shell, like GDB does.
|
|
|
|
|
See "set startup-with-shell" in the user manual for how to disable
|
|
|
|
|
this from GDB when using "target extended-remote". When using
|
|
|
|
|
"target remote", you can disable the startup with shell by using the
|
|
|
|
|
new "--no-startup-with-shell" GDBserver command line option.
|
2016-12-23 11:14:02 +08:00
|
|
|
|
Implement the ability to set/unset environment variables to GDBserver when starting the inferior
This patch implements the ability to set/unset environment variables
on the remote target, mimicking what GDB already offers to the user.
There are two features present here: user-set and user-unset
environment variables.
User-set environment variables are only the variables that are
explicitly set by the user, using the 'set environment' command. This
means that variables that were already present in the environment when
starting GDB/GDBserver are not transmitted/considered by this feature.
User-unset environment variables are variables that are explicitly
unset by the user, using the 'unset environment' command.
The idea behind this patch is to store user-set and user-unset
environment variables in two separate sets, both part of gdb_environ.
Then, when extended_remote_create_inferior is preparing to start the
inferior, it will iterate over the two sets and set/unset variables
accordingly. Three new packets are introduced:
- QEnvironmentHexEncoded, which is used to set environment variables,
and contains an hex-encoded string in the format "VAR=VALUE" (VALUE
can be empty if the user set a variable with a null value, by doing
'set environment VAR=').
- QEnvironmentUnset, which is used to unset environment variables, and
contains an hex-encoded string in the format "VAR".
- QEnvironmentReset, which is always the first packet to be
transmitted, and is used to reset the environment, i.e., discard any
changes made by the user on previous runs.
The QEnvironmentHexEncoded packet is inspired on LLDB's extensions to
the RSP. Details about it can be seen here:
<https://raw.githubusercontent.com/llvm-mirror/lldb/master/docs/lldb-gdb-remote.txt>
I decided not to implement the QEnvironment packet because it is
considered deprecated by LLDB. This packet, on LLDB, serves the same
purpose of QEnvironmentHexEncoded, but sends the information using a
plain text, non-hex-encoded string.
The other two packets are new.
This patch also includes updates to the documentation, testsuite, and
unit tests, without introducing regressions.
gdb/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* NEWS (Changes since GDB 8.0): Add entry mentioning new support
for setting/unsetting environment variables on the remote target.
(New remote packets): Add entries for QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset.
* common/environ.c (gdb_environ::operator=): Extend method to
handle m_user_set_env_list and m_user_unset_env_list.
(gdb_environ::clear): Likewise.
(match_var_in_string): Change type of first parameter from 'char
*' to 'const char *'.
(gdb_environ::set): Extend method to handle
m_user_set_env_list and m_user_unset_env_list.
(gdb_environ::unset): Likewise.
(gdb_environ::clear_user_set_env): New method.
(gdb_environ::user_set_envp): Likewise.
(gdb_environ::user_unset_envp): Likewise.
* common/environ.h (gdb_environ): Handle m_user_set_env_list and
m_user_unset_env_list on move constructor/assignment.
(unset): Add new default parameter 'update_unset_list = true'.
(clear_user_set_env): New method.
(user_set_envp): Likewise.
(user_unset_envp): Likewise.
(m_user_set_env_list): New std::set.
(m_user_unset_env_list): Likewise.
* common/rsp-low.c (hex2str): New function.
(bin2hex): New overload for bin2hex function.
* common/rsp-low.c (hex2str): New prototype.
(str2hex): New overload prototype.
* remote.c: Include "environ.h". Add QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset.
(remote_protocol_features): Add QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset packets.
(send_environment_packet): New function.
(extended_remote_environment_support): Likewise.
(extended_remote_create_inferior): Call
extended_remote_environment_support.
(_initialize_remote): Add QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset packet configs.
* unittests/environ-selftests.c (gdb_selftest_env_var):
New variable.
(test_vector_initialization): New function.
(test_init_from_host_environ): Likewise.
(test_reinit_from_host_environ): Likewise.
(test_set_A_unset_B_unset_A_cannot_find_A_can_find_B):
Likewise.
(test_unset_set_empty_vector): Likewise.
(test_vector_clear): Likewise.
(test_std_move): Likewise.
(test_move_constructor):
(test_self_move): Likewise.
(test_set_unset_reset): Likewise.
(run_tests): Rewrite in terms of the functions above.
gdb/gdbserver/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* server.c (handle_general_set): Handle QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset packets.
(handle_query): Inform remote that QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset are supported.
gdb/doc/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.texinfo (set environment): Add @anchor. Explain that
environment variables set by the user are sent to GDBserver.
(unset environment): Likewise, but for unsetting variables.
(Connecting) <Remote Packet>: Add "environment-hex-encoded",
"QEnvironmentHexEncoded", "environment-unset", "QEnvironmentUnset",
"environment-reset" and "QEnvironmentReset" to the table.
(Remote Protocol) <QEnvironmentHexEncoded, QEnvironmentUnset,
QEnvironmentReset>: New item, explaining the packet.
gdb/testsuite/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.base/share-env-with-gdbserver.c: New file.
* gdb.base/share-env-with-gdbserver.exp: Likewise.
2017-06-30 03:06:07 +08:00
|
|
|
** On Unix systems, GDBserver now supports receiving environment
|
|
|
|
|
variables that are to be set or unset from GDB. These variables
|
|
|
|
|
will affect the environment to be passed to the inferior.
|
|
|
|
|
|
(Ada) provide the exception message when hitting an exception catchpoint
This patch enhances the debugger to print the exception message, when
available, as part of an exception catchpoint hit notification (both
GDB/CLI and GDB/MI). For instance, with the following code...
procedure A is
begin
raise Constraint_Error with "hello world";
end A;
... instead of printing...
Catchpoint 1, CONSTRAINT_ERROR at 0x000000000040245c in a () at a.adb:3
... it now prints:
Catchpoint 1, CONSTRAINT_ERROR (hello world) at 0x000000000040245c in a ()
^^^^^^^^^^^^^
This enhancement requires runtime support. If not present, the debugger
just behaves as before.
In GDB/MI mode, if the exception message is available, it is provided
as an extra field named "exception-message" in the catchpoint notification:
*stopped,bkptno="1",[...],exception-name="CONSTRAINT_ERROR",
exception-message="hello world",[...]
gdb/ChangeLog:
* ada-lang.c (ada_exception_message_1, ada_exception_message):
New functions.
(print_it_exception): If available, display the exception
message as well.
* NEWS: Document new feature.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI Ada Exception Information): Document
new "exception-message" field.
gdb/testsuite/ChangeLog:
* gdb.ada/catch_ex.exp, gdb.ada/mi_catch_ex.exp,
gdb.ada/mi_ex_cond.exp: Accept optional exception message in
when hitting an exception catchpoint.
2017-11-25 06:09:42 +08:00
|
|
|
* When catching an Ada exception raised with a message, GDB now prints
|
|
|
|
|
the message in the catchpoint hit notification. In GDB/MI mode, that
|
|
|
|
|
information is provided as an extra field named "exception-message"
|
|
|
|
|
in the *stopped notification.
|
|
|
|
|
|
2017-12-02 05:16:33 +08:00
|
|
|
* Trait objects can now be inspected When debugging Rust code. This
|
|
|
|
|
requires compiler support which will appear in Rust 1.24.
|
|
|
|
|
|
2016-12-23 11:14:02 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
Implement the ability to set/unset environment variables to GDBserver when starting the inferior
This patch implements the ability to set/unset environment variables
on the remote target, mimicking what GDB already offers to the user.
There are two features present here: user-set and user-unset
environment variables.
User-set environment variables are only the variables that are
explicitly set by the user, using the 'set environment' command. This
means that variables that were already present in the environment when
starting GDB/GDBserver are not transmitted/considered by this feature.
User-unset environment variables are variables that are explicitly
unset by the user, using the 'unset environment' command.
The idea behind this patch is to store user-set and user-unset
environment variables in two separate sets, both part of gdb_environ.
Then, when extended_remote_create_inferior is preparing to start the
inferior, it will iterate over the two sets and set/unset variables
accordingly. Three new packets are introduced:
- QEnvironmentHexEncoded, which is used to set environment variables,
and contains an hex-encoded string in the format "VAR=VALUE" (VALUE
can be empty if the user set a variable with a null value, by doing
'set environment VAR=').
- QEnvironmentUnset, which is used to unset environment variables, and
contains an hex-encoded string in the format "VAR".
- QEnvironmentReset, which is always the first packet to be
transmitted, and is used to reset the environment, i.e., discard any
changes made by the user on previous runs.
The QEnvironmentHexEncoded packet is inspired on LLDB's extensions to
the RSP. Details about it can be seen here:
<https://raw.githubusercontent.com/llvm-mirror/lldb/master/docs/lldb-gdb-remote.txt>
I decided not to implement the QEnvironment packet because it is
considered deprecated by LLDB. This packet, on LLDB, serves the same
purpose of QEnvironmentHexEncoded, but sends the information using a
plain text, non-hex-encoded string.
The other two packets are new.
This patch also includes updates to the documentation, testsuite, and
unit tests, without introducing regressions.
gdb/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* NEWS (Changes since GDB 8.0): Add entry mentioning new support
for setting/unsetting environment variables on the remote target.
(New remote packets): Add entries for QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset.
* common/environ.c (gdb_environ::operator=): Extend method to
handle m_user_set_env_list and m_user_unset_env_list.
(gdb_environ::clear): Likewise.
(match_var_in_string): Change type of first parameter from 'char
*' to 'const char *'.
(gdb_environ::set): Extend method to handle
m_user_set_env_list and m_user_unset_env_list.
(gdb_environ::unset): Likewise.
(gdb_environ::clear_user_set_env): New method.
(gdb_environ::user_set_envp): Likewise.
(gdb_environ::user_unset_envp): Likewise.
* common/environ.h (gdb_environ): Handle m_user_set_env_list and
m_user_unset_env_list on move constructor/assignment.
(unset): Add new default parameter 'update_unset_list = true'.
(clear_user_set_env): New method.
(user_set_envp): Likewise.
(user_unset_envp): Likewise.
(m_user_set_env_list): New std::set.
(m_user_unset_env_list): Likewise.
* common/rsp-low.c (hex2str): New function.
(bin2hex): New overload for bin2hex function.
* common/rsp-low.c (hex2str): New prototype.
(str2hex): New overload prototype.
* remote.c: Include "environ.h". Add QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset.
(remote_protocol_features): Add QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset packets.
(send_environment_packet): New function.
(extended_remote_environment_support): Likewise.
(extended_remote_create_inferior): Call
extended_remote_environment_support.
(_initialize_remote): Add QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset packet configs.
* unittests/environ-selftests.c (gdb_selftest_env_var):
New variable.
(test_vector_initialization): New function.
(test_init_from_host_environ): Likewise.
(test_reinit_from_host_environ): Likewise.
(test_set_A_unset_B_unset_A_cannot_find_A_can_find_B):
Likewise.
(test_unset_set_empty_vector): Likewise.
(test_vector_clear): Likewise.
(test_std_move): Likewise.
(test_move_constructor):
(test_self_move): Likewise.
(test_set_unset_reset): Likewise.
(run_tests): Rewrite in terms of the functions above.
gdb/gdbserver/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* server.c (handle_general_set): Handle QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset packets.
(handle_query): Inform remote that QEnvironmentHexEncoded,
QEnvironmentUnset and QEnvironmentReset are supported.
gdb/doc/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.texinfo (set environment): Add @anchor. Explain that
environment variables set by the user are sent to GDBserver.
(unset environment): Likewise, but for unsetting variables.
(Connecting) <Remote Packet>: Add "environment-hex-encoded",
"QEnvironmentHexEncoded", "environment-unset", "QEnvironmentUnset",
"environment-reset" and "QEnvironmentReset" to the table.
(Remote Protocol) <QEnvironmentHexEncoded, QEnvironmentUnset,
QEnvironmentReset>: New item, explaining the packet.
gdb/testsuite/ChangeLog:
2017-08-31 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.base/share-env-with-gdbserver.c: New file.
* gdb.base/share-env-with-gdbserver.exp: Likewise.
2017-06-30 03:06:07 +08:00
|
|
|
QEnvironmentHexEncoded
|
|
|
|
|
Inform GDBserver of an environment variable that is to be passed to
|
|
|
|
|
the inferior when starting it.
|
|
|
|
|
|
|
|
|
|
QEnvironmentUnset
|
|
|
|
|
Inform GDBserver of an environment variable that is to be unset
|
|
|
|
|
before starting the remote inferior.
|
|
|
|
|
|
|
|
|
|
QEnvironmentReset
|
|
|
|
|
Inform GDBserver that the environment should be reset (i.e.,
|
|
|
|
|
user-set environment variables should be unset).
|
|
|
|
|
|
2016-12-23 11:14:02 +08:00
|
|
|
QStartupWithShell
|
|
|
|
|
Indicates whether the inferior must be started with a shell or not.
|
|
|
|
|
|
Extend "set cwd" to work on gdbserver
This is the "natural" extension necessary for the "set cwd" command
(and the whole "set the inferior's cwd" logic) to work on gdbserver.
The idea here is to have a new remote packet, QSetWorkingDir (name
adopted from LLDB's extension to the RSP, as can be seen at
<https://raw.githubusercontent.com/llvm-mirror/lldb/master/docs/lldb-gdb-remote.txt>),
which sends an hex-encoded string representing the working directory
that the remote inferior will use. There is a slight difference from
the packet proposed by LLDB: GDB's version will accept empty
arguments, meaning that the user wants to clear the previously set
working directory for the inferior (i.e., "set cwd" without arguments
on GDB).
For UNIX-like targets this feature is already implemented on
nat/fork-inferior.c, and all gdbserver has to do is to basically
implement "set_inferior_cwd" and call it whenever such packet arrives.
For other targets, like Windows, it is possible to use the existing
"get_inferior_cwd" function and do the necessary steps to make sure
that the inferior will use the specified working directory.
Aside from that, the patch consists basically of updates to the
testcase (making it available on remote targets) and the
documentation.
No regressions found.
gdb/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* NEWS (Changes since GDB 8.0): Add entry about new
'set-cwd-on-gdbserver' feature.
(New remote packets): Add entry for QSetWorkingDir.
* common/common-inferior.h (set_inferior_cwd): New prototype.
* infcmd.c (set_inferior_cwd): Remove "static".
(show_cwd_command): Expand text to include remote debugging.
* remote.c: Add PACKET_QSetWorkingDir.
(remote_protocol_features) <QSetWorkingDir>: New entry for
PACKET_QSetWorkingDir.
(extended_remote_set_inferior_cwd): New function.
(extended_remote_create_inferior): Call
"extended_remote_set_inferior_cwd".
(_initialize_remote): Call "add_packet_config_cmd" for
QSetWorkingDir.
gdb/gdbserver/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* inferiors.c (set_inferior_cwd): New function.
* server.c (handle_general_set): Handle QSetWorkingDir packet.
(handle_query): Inform that QSetWorkingDir is supported.
* win32-low.c (create_process): Pass the inferior's cwd to
CreateProcess.
gdb/testsuite/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.base/set-cwd.exp: Make it available on
native-extended-gdbserver.
gdb/doc/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.texinfo (Starting your Program) <The working directory.>:
Mention remote debugging.
(Working Directory) <Your Program's Working Directory>:
Likewise.
(Connecting) <Remote Packet>: Add "set-working-dir"
and "QSetWorkingDir" to the table.
(Remote Protocol) <QSetWorkingDir>: New item, explaining the
packet.
2017-09-21 07:15:40 +08:00
|
|
|
QSetWorkingDir
|
|
|
|
|
Tell GDBserver that the inferior to be started should use a specific
|
|
|
|
|
working directory.
|
|
|
|
|
|
Add optional argument to command "maint prints c-tdesc"
Nowadays, we need two steps to print c files for xml target description,
that is, 1) read xml target description in, update the current tdesc,
2) visit the current tdesc, print the c file. It is unnecessary to
involve in current tdesc, and some validations in each gdbarch are
performed unnecessarily, which will reject some target descriptions if
they are missing some mandatory feature.
This patch adds an optional argument to "maint print c-tdesc", which
is an XML file target description, so that we can combine the two
steps above into one step, and don't have to involve in global current
tdesc.
gdb:
2017-07-26 Yao Qi <yao.qi@linaro.org>
* NEWS: Mention it.
* features/Makefile (%.c: %.xml): Pass the xml file name to
command "maint print c-tdesc".
* target-descriptions.c (maint_print_c_tdesc_cmd): Get file
name from 'arg'.
gdb/doc:
2017-07-26 Yao Qi <yao.qi@linaro.org>
* gdb.texinfo (Maintenance Commands): Document optional
argument of "maint print c-tdesc".
2017-07-26 19:03:47 +08:00
|
|
|
* The "maintenance print c-tdesc" command now takes an optional
|
|
|
|
|
argument which is the file name of XML target description.
|
|
|
|
|
|
Add selftests run filtering
With the growing number of selftests, I think it would be useful to be
able to run only a subset of the tests. This patch associates a name to
each registered selftest. It then allows doing something like:
(gdb) maintenance selftest aarch64
Running self-tests.
Running selftest aarch64-analyze-prologue.
Running selftest aarch64-process-record.
Ran 2 unit tests, 0 failed
or with gdbserver:
./gdbserver --selftest=aarch64
In both cases, only the tests that contain "aarch64" in their name are
ran. To help validate that the tests you want to run were actually ran,
it also prints a message with the test name before running each test.
Right now, all the arch-dependent tests are registered as a single test
of the selftests. To be able to filter those too, I made them
"first-class citizen" selftests. The selftest type is an interface,
with different implementations for "simple selftests" and "arch
selftests". The run_tests function simply iterates on that an invokes
operator() on each test.
I changed the tests data structure from a vector to a map, because
- it allows iterating in a stable (alphabetical) order
- it allows to easily verify if a test with a given name has been
registered, to avoid duplicates
There's also a new command "maintenance info selftests" that lists the
registered selftests.
gdb/ChangeLog:
* common/selftest.h (selftest): New struct/interface.
(register_test): Add name parameter, add new overload.
(run_tests): Add filter parameter.
(for_each_selftest_ftype): New typedef.
(for_each_selftest): New declaration.
* common/selftest.c (tests): Change type to
map<string, unique_ptr<selftest>>.
(simple_selftest): New struct.
(register_test): New function.
(register_test): Add name parameter and use it.
(run_tests): Add filter parameter and use it. Add prints.
Adjust to vector -> map change.
* aarch64-tdep.c (_initialize_aarch64_tdep): Add names when
registering selftests.
* arm-tdep.c (_initialize_arm_tdep): Likewise.
* disasm-selftests.c (_initialize_disasm_selftests): Likewise.
* dwarf2-frame.c (_initialize_dwarf2_frame): Likewise.
* dwarf2loc.c (_initialize_dwarf2loc): Likewise.
* findvar.c (_initialize_findvar): Likewise.
* gdbarch-selftests.c (_initialize_gdbarch_selftests): Likewise.
* maint.c (maintenance_selftest): Update call to run_tests.
(maintenance_info_selftests): New function.
(_initialize_maint_cmds): Register "maintenance info selftests"
command. Update "maintenance selftest" doc.
* regcache.c (_initialize_regcache): Add names when registering
selftests.
* rust-exp.y (_initialize_rust_exp): Likewise.
* selftest-arch.c (gdbarch_selftest): New struct.
(gdbarch_tests): Remove.
(register_test_foreach_arch): Add name parameter. Call
register_test.
(tests_with_arch): Remove, move most content to
gdbarch_selftest::operator().
(_initialize_selftests_foreach_arch): Remove.
* selftest-arch.h (register_test_foreach_arch): Add name
parameter.
(run_tests_with_arch): New declaration.
* utils-selftests.c (_initialize_utils_selftests): Add names
when registering selftests.
* utils.c (_initialize_utils): Likewise.
* unittests/array-view-selftests.c
(_initialize_array_view_selftests): Likewise.
* unittests/environ-selftests.c (_initialize_environ_selftests):
Likewise.
* unittests/function-view-selftests.c
(_initialize_function_view_selftests): Likewise.
* unittests/offset-type-selftests.c
(_initialize_offset_type_selftests): Likewise.
* unittests/optional-selftests.c
(_initialize_optional_selftests): Likewise.
* unittests/scoped_restore-selftests.c
(_initialize_scoped_restore_selftests): Likewise.
* NEWS: Document "maintenance selftest" and "maint info
selftests".
gdb/gdbserver/ChangeLog:
* server.c (captured_main): Accept argument for --selftest.
Update run_tests call.
* linux-x86-tdesc-selftest.c (initialize_low_tdesc): Add names
when registering selftests.
gdb/doc/ChangeLog:
* gdb.texinfo (Maintenance Commands): Document filter parameter
of "maint selftest". Document "maint info selftests" command.
2017-09-16 20:06:03 +08:00
|
|
|
* The "maintenance selftest" command now takes an optional argument to
|
|
|
|
|
filter the tests to be run.
|
|
|
|
|
|
2017-11-07 19:00:31 +08:00
|
|
|
* The "enable", and "disable" commands now accept a range of
|
|
|
|
|
breakpoint locations, e.g. "enable 1.3-5".
|
|
|
|
|
|
2017-06-12 05:16:01 +08:00
|
|
|
* New commands
|
|
|
|
|
|
Implement "set cwd" command on GDB
This commit adds new "set/show cwd" commands, which are used to
set/show the current working directory of the inferior that will be
started.
The idea here is that "set cwd" will become the de facto way of
setting the inferior's cwd. Currently, the user can use "cd" for
that, but there are side effects: with "cd", GDB also switches to
another directory, and that can impact the loading of scripts and
other files. With "set cwd", we separate the logic into a new
command.
To maintain backward compatibility, if the user issues a "cd" command
but doesn't use "set cwd", then the inferior's cwd will still be
changed according to what the user specified. However, "set cwd" has
precedence over "cd", so it can always be used to override it.
"set cwd" works in the following way:
- If the user sets the inferior's cwd by using "set cwd", then this
directory is saved into current_inferior ()->cwd and is used when
the inferior is started (see below).
- If the user doesn't set the inferior's cwd by using "set cwd", but
rather use the "cd" command as before, then this directory is
inherited by the inferior because GDB will have chdir'd into it.
On Unix-like hosts, the way the directory is changed before the
inferior execution is by expanding the user set directory before the
fork, and then "chdir" after the call to fork/vfork on
"fork_inferior", but before the actual execution. On Windows, the
inferior cwd set by the user is passed directly to the CreateProcess
call, which takes care of the actual chdir for us.
This way, we'll make sure that GDB's cwd is not affected by the user
set cwd.
gdb/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* NEWS (New commands): Mention "set/show cwd".
* cli/cli-cmds.c (_initialize_cli_cmds): Mention "set cwd" on
"cd" command's help text.
* common/common-inferior.h (get_inferior_cwd): New prototype.
* infcmd.c (inferior_cwd_scratch): New global variable.
(set_inferior_cwd): New function.
(get_inferior_cwd): Likewise.
(set_cwd_command): Likewise.
(show_cwd_command): Likewise.
(_initialize_infcmd): Add "set/show cwd" commands.
* inferior.h (class inferior) <cwd>: New field.
* nat/fork-inferior.c: Include "gdb_tilde_expand.h".
(fork_inferior): Change inferior's cwd before its execution.
* windows-nat.c (windows_create_inferior): Pass inferior's cwd
to CreateProcess.
gdb/gdbserver/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* inferiors.c (current_inferior_cwd): New global variable.
(get_inferior_cwd): New function.
* inferiors.h (struct process_info) <cwd>: New field.
gdb/doc/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.texinfo (Starting your Program) <The working directory.>:
Mention new "set cwd" command.
(Working Directory) <Your Program's Working Directory>:
Rephrase to explain that "set cwd" exists and is the default
way to change the inferior's cwd.
gdb/testsuite/ChangeLog:
2017-10-04 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.base/set-cwd.c: New file.
* gdb.base/set-cwd.exp: Likewise.
2017-09-11 13:13:50 +08:00
|
|
|
set|show cwd
|
|
|
|
|
Set and show the current working directory for the inferior.
|
|
|
|
|
|
2017-02-22 05:32:56 +08:00
|
|
|
set|show compile-gcc
|
|
|
|
|
Set and show compilation command used for compiling and injecting code
|
|
|
|
|
with the 'compile' commands.
|
|
|
|
|
|
2017-06-12 05:16:01 +08:00
|
|
|
set debug separate-debug-file
|
|
|
|
|
show debug separate-debug-file
|
|
|
|
|
Control the display of debug output about separate debug file search.
|
|
|
|
|
|
2017-12-04 16:17:13 +08:00
|
|
|
set dump-excluded-mappings
|
|
|
|
|
show dump-excluded-mappings
|
|
|
|
|
Control whether mappings marked with the VM_DONTDUMP flag should be
|
|
|
|
|
dumped when generating a core file.
|
|
|
|
|
|
Add selftests run filtering
With the growing number of selftests, I think it would be useful to be
able to run only a subset of the tests. This patch associates a name to
each registered selftest. It then allows doing something like:
(gdb) maintenance selftest aarch64
Running self-tests.
Running selftest aarch64-analyze-prologue.
Running selftest aarch64-process-record.
Ran 2 unit tests, 0 failed
or with gdbserver:
./gdbserver --selftest=aarch64
In both cases, only the tests that contain "aarch64" in their name are
ran. To help validate that the tests you want to run were actually ran,
it also prints a message with the test name before running each test.
Right now, all the arch-dependent tests are registered as a single test
of the selftests. To be able to filter those too, I made them
"first-class citizen" selftests. The selftest type is an interface,
with different implementations for "simple selftests" and "arch
selftests". The run_tests function simply iterates on that an invokes
operator() on each test.
I changed the tests data structure from a vector to a map, because
- it allows iterating in a stable (alphabetical) order
- it allows to easily verify if a test with a given name has been
registered, to avoid duplicates
There's also a new command "maintenance info selftests" that lists the
registered selftests.
gdb/ChangeLog:
* common/selftest.h (selftest): New struct/interface.
(register_test): Add name parameter, add new overload.
(run_tests): Add filter parameter.
(for_each_selftest_ftype): New typedef.
(for_each_selftest): New declaration.
* common/selftest.c (tests): Change type to
map<string, unique_ptr<selftest>>.
(simple_selftest): New struct.
(register_test): New function.
(register_test): Add name parameter and use it.
(run_tests): Add filter parameter and use it. Add prints.
Adjust to vector -> map change.
* aarch64-tdep.c (_initialize_aarch64_tdep): Add names when
registering selftests.
* arm-tdep.c (_initialize_arm_tdep): Likewise.
* disasm-selftests.c (_initialize_disasm_selftests): Likewise.
* dwarf2-frame.c (_initialize_dwarf2_frame): Likewise.
* dwarf2loc.c (_initialize_dwarf2loc): Likewise.
* findvar.c (_initialize_findvar): Likewise.
* gdbarch-selftests.c (_initialize_gdbarch_selftests): Likewise.
* maint.c (maintenance_selftest): Update call to run_tests.
(maintenance_info_selftests): New function.
(_initialize_maint_cmds): Register "maintenance info selftests"
command. Update "maintenance selftest" doc.
* regcache.c (_initialize_regcache): Add names when registering
selftests.
* rust-exp.y (_initialize_rust_exp): Likewise.
* selftest-arch.c (gdbarch_selftest): New struct.
(gdbarch_tests): Remove.
(register_test_foreach_arch): Add name parameter. Call
register_test.
(tests_with_arch): Remove, move most content to
gdbarch_selftest::operator().
(_initialize_selftests_foreach_arch): Remove.
* selftest-arch.h (register_test_foreach_arch): Add name
parameter.
(run_tests_with_arch): New declaration.
* utils-selftests.c (_initialize_utils_selftests): Add names
when registering selftests.
* utils.c (_initialize_utils): Likewise.
* unittests/array-view-selftests.c
(_initialize_array_view_selftests): Likewise.
* unittests/environ-selftests.c (_initialize_environ_selftests):
Likewise.
* unittests/function-view-selftests.c
(_initialize_function_view_selftests): Likewise.
* unittests/offset-type-selftests.c
(_initialize_offset_type_selftests): Likewise.
* unittests/optional-selftests.c
(_initialize_optional_selftests): Likewise.
* unittests/scoped_restore-selftests.c
(_initialize_scoped_restore_selftests): Likewise.
* NEWS: Document "maintenance selftest" and "maint info
selftests".
gdb/gdbserver/ChangeLog:
* server.c (captured_main): Accept argument for --selftest.
Update run_tests call.
* linux-x86-tdesc-selftest.c (initialize_low_tdesc): Add names
when registering selftests.
gdb/doc/ChangeLog:
* gdb.texinfo (Maintenance Commands): Document filter parameter
of "maint selftest". Document "maint info selftests" command.
2017-09-16 20:06:03 +08:00
|
|
|
maint info selftests
|
|
|
|
|
List the registered selftests.
|
|
|
|
|
|
2017-09-12 05:57:37 +08:00
|
|
|
starti
|
|
|
|
|
Start the debugged program stopping at the first instruction.
|
|
|
|
|
|
2017-12-17 06:20:50 +08:00
|
|
|
set|show debug or1k
|
|
|
|
|
Control display of debugging messages related to OpenRISC targets.
|
|
|
|
|
|
Record nested types
GDB currently does not track types defined in classes. Consider:
class A
{
public:
class B
{
public:
class C { };
};
};
(gdb) ptype A
type = class A {
<no data fields>
}
This patch changes this behavior so that GDB records these nested types
and displays them to the user when he has set the (new) "print type"
option "nested-type-limit."
Example:
(gdb) set print type nested-type-limit 1
(gdb) ptype A
type = class A {
<no data fields>
class A::B {
<no data fields>
};
}
(gdb) set print type nested-type-limit 2
type = class A {
<no data fields>
class A::B {
<no data fields>
class A::B::C {
<no data fields>
};
};
}
By default, the code maintains the status quo, that is, it will not print
any nested type definitions at all.
Testing is carried out via cp_ptype_class which required quite a bit of
modification to permit recursive calling (for the nested types). This
was most easily facilitated by turning the ptype command output into a
queue. Upshot: the test suite now has stack and queue data structures that
may be used by test writers.
gdb/ChangeLog
* NEWS (New commands): Mention set/show print type nested-type-limit.
* c-typeprint.c (c_type_print_base): Print out nested types.
* dwarf2read.c (struct typedef_field_list): Rename to ...
(struct decl_field_list): ... this. Change all uses.
(struct field_info) <nested_types_list, nested_types_list_count>:
New fields.
(add_partial_symbol): Look for nested type definitions in C++, too.
(dwarf2_add_typedef): Rename to ...
(dwarf2_add_type_defn): ... this.
(type_can_define_types): New function.
Update assertion to use type_can_define_types.
Permit NULL for a field's name.
(process_structure_scope): Handle child DIEs of types that can
define types.
Copy the list of nested types into the type struct.
* gdbtypes.h (struct typedef_field): Rename to ...
(struct decl_field): ... this. Change all uses.
[is_protected, is_private]: New fields.
(struct cplus_struct_type) <nested_types, nested_types_count>: New
fields.
(TYPE_NESTED_TYPES_ARRAY, TYPE_NESTED_TYPES_FIELD)
(TYPE_NESTED_TYPES_FIELD_NAME, TYPE_NESTED_TYPES_FIELD_TYPE)
(TYPE_NESTED_TYPES_COUNT, TYPE_NESTED_TYPES_FIELD_PROTECTED)
(TYPE_NESTED_TYPES_FIELD_PRIVATE): New macros.
* typeprint.c (type_print_raw_options, default_ptype_flags): Add
default value for print_nested_type_limit.
(print_nested_type_limit): New static variable.
(set_print_type_nested_types, show_print_type_nested_types): New
functions.
(_initialize_typeprint): Register new commands for set/show
`print-nested-type-limit'.
* typeprint.h (struct type_print_options) [print_nested_type_limit]:
New field.
gdb/testsuite/ChangeLog
* gdb.cp/nested-types.cc: New file.
* gdb.cp/nested-types.exp: New file.
* lib/cp-support.exp: Load data-structures.exp library.
(debug_cp_test_ptype_class): New global.
(cp_ptype_class_verbose, next_line): New procedures.
(cp_test_ptype_class): Add and document new parameter `recursive_qid'.
Add and document new return value.
Switch the list of lines to a queue.
Add support for new `type' key for nested type definitions.
Add debugging/troubleshooting messages.
* lib/data-structures.exp: New file.
gdb/doc/ChangeLog
* gdb.texinfo (Symbols): Document "set print type nested-type-limit"
and "show print type nested-type-limit".
2017-12-08 07:01:30 +08:00
|
|
|
set|show print type nested-type-limit
|
|
|
|
|
Set and show the limit of nesting level for nested types that the
|
|
|
|
|
type printer will show.
|
|
|
|
|
|
2017-08-17 13:44:37 +08:00
|
|
|
* TUI Single-Key mode now supports two new shortcut keys: `i' for stepi and
|
|
|
|
|
`o' for nexti.
|
|
|
|
|
|
2017-09-05 03:21:16 +08:00
|
|
|
* Safer/improved support for debugging with no debug info
|
|
|
|
|
|
|
|
|
|
GDB no longer assumes functions with no debug information return
|
|
|
|
|
'int'.
|
|
|
|
|
|
|
|
|
|
This means that GDB now refuses to call such functions unless you
|
|
|
|
|
tell it the function's type, by either casting the call to the
|
|
|
|
|
declared return type, or by casting the function to a function
|
|
|
|
|
pointer of the right type, and calling that:
|
|
|
|
|
|
|
|
|
|
(gdb) p getenv ("PATH")
|
|
|
|
|
'getenv' has unknown return type; cast the call to its declared return type
|
|
|
|
|
(gdb) p (char *) getenv ("PATH")
|
|
|
|
|
$1 = 0x7fffffffe "/usr/local/bin:/"...
|
|
|
|
|
(gdb) p ((char * (*) (const char *)) getenv) ("PATH")
|
|
|
|
|
$2 = 0x7fffffffe "/usr/local/bin:/"...
|
|
|
|
|
|
|
|
|
|
Similarly, GDB no longer assumes that global variables with no debug
|
|
|
|
|
info have type 'int', and refuses to print the variable's value
|
|
|
|
|
unless you tell it the variable's type:
|
|
|
|
|
|
|
|
|
|
(gdb) p var
|
|
|
|
|
'var' has unknown type; cast it to its declared type
|
|
|
|
|
(gdb) p (float) var
|
|
|
|
|
$3 = 3.14
|
|
|
|
|
|
2017-08-11 02:00:42 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
FreeBSD/aarch64 aarch64*-*-freebsd*
|
2017-10-12 02:16:34 +08:00
|
|
|
FreeBSD/arm arm*-*-freebsd*
|
2017-08-11 02:00:42 +08:00
|
|
|
|
2017-08-09 14:25:42 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
FreeBSD/aarch64 aarch64*-*-freebsd*
|
2017-10-12 02:16:34 +08:00
|
|
|
FreeBSD/arm arm*-*-freebsd*
|
2017-12-17 06:20:50 +08:00
|
|
|
OpenRISC ELF or1k*-*-elf
|
2017-08-09 14:25:42 +08:00
|
|
|
|
Remove support for Solaris < 10 (PR gdb/22185)
Given that GCC has obsoleted/removed support for Solaris 9 in GCC 4.9/5 in 2013:
https://gcc.gnu.org/gcc-4.9/changes.html
https://gcc.gnu.org/ml/gcc-patches/2013-05/msg00728.html
and the last gdb version that can be compiled with gcc 4.9 is 7.12.1 only when
configured with --disable-build-with-cxx, it's time to obsolete/remove support
for Solaris < 10.
This patch does this, simplifying configure.nat along the way (only a single
sol2 configuration with variants for i386 and sparc).
Some configure checks for older Solaris versions can go, too, and the check
for libthread_db.so.1 removed:
* Since Solaris 10, dlopen has moved to libc and libdl.so is just a
filter on ld.so.1, so no need to check.
* $RDYNAMIC is already handled above (and is a no-op with Solaris ld
anyway).
Both proc-service.c and sol-thread.c lose support for (Solaris-only)
PROC_SERVICE_IS_OLD.
The attached revised patch has been tested on sparcv9-sun-solaris2.10,
sparcv9-sun-solaris2.11.4, amd64-pc-solaris2.10, amd64-pc-solaris2.11.4,
and x86_64-pc-linux-gnu.
I've also started an i386-pc-solaris2.9 build to check that it really
stops as expected.
PR gdb/22185
* configure.host <*-*-solaris2.[01], *-*-solaris2.[2-9]*>: Mark as
obsolete.
Use gdb_host sol2 for i[34567]86-*-solaris2*, x86_64-*-solaris2*.
Remove i386sol2 support.
* configure.nat <i386sol2>: Remove.
<sol2-64>: Fold into ...
<sol2>: ... this.
Move common settings to default section.
Add sol-thread.o.
* configure.tgt <i[34567]86-*-solaris2.1[0-9]*,
x86_64-*-solaris2.1[0-9]*>: Rename to ...
<i[34567]86-*-solaris2*, x86_64-*-solaris2*>: ... this.
<i[34567]86-*-solaris*>: Remove.
<sparc-*-solaris2.[0-6], sparc-*-solaris2.[0-6].*>: Remove.
* configure.ac: Remove wctype in libw check.
(_MSE_INT_H): Don't define on Solaris 7-9.
<solaris*>: Remove libthread_db.so.1 check.
* configure: Regenerate.
* config.in: Regenerate.
* proc-service.c: Remove PROC_SERVICE_IS_OLD handling.
(gdb_ps_prochandle_t, gdb_ps_read_buf_t, gdb_ps_write_buf_t)
(gdb_ps_size_t): Remove.
Use base types in users.
* sol-thread.c: Likewise, also for gdb_ps_addr_t.
* NEWS (Changes since GDB 8.0): Document Solaris 2.0-9 removal.
2017-09-26 21:19:10 +08:00
|
|
|
* Removed targets and native configurations
|
|
|
|
|
|
|
|
|
|
Solaris 2.0-9 i?86-*-solaris2.[0-9], sparc*-*-solaris2.[0-9]
|
|
|
|
|
|
2017-04-17 22:30:29 +08:00
|
|
|
*** Changes in GDB 8.0
|
Add support for Intel PKRU register to GDB and GDBserver.
This patch adds support for the registers added by the
Memory Protection Keys for Userspace (PKU aka PKEYs) feature.
Native and remote debugging are covered by this patch.
The XSAVE area is extended with a new state containing
the 32-bit wide PKRU register. The new register is added to
amd64-avx-mpx_avx512-* tdesc, thus it is renamed accordingly. Also,
respective xstate mask X86_XSTATE_AVX_MPX_AVX512_MASK is renamed to
X86_XSTATE_AVX_MPX_AVX512_PKU_MASK to reflect the new feature set
it supports.
For more information, please refer to the
Intel(R) 64 and IA-32 Architectures Software Developer's
Manual - Septemper 2015
http://www.intel.com/content/dam/www/public/us/en/documents/
manuals/64-ia-32-architectures-software-developer-manual-325462.pdf
gdb/Changelog:
2015-12-08 Michael Sturm <michael.sturm@intel.com>
* NEWS: Mention addition of PKU feature.
* amd64-linux-nat.c (amd64_linux_gregset32_reg_offset): Add PKRU register.
* amd64-linux-tdep.c (features/i386/amd64-avx-mpx-avx512-linux.c): Rename
to...
(features/i386/amd64-avx-mpx-avx512-pku-linux.c): ...this.
(amd64_linux_gregset_reg_offset): Add PKRU register.
(amd64_linux_core_read_description): Rename
X86_XSTATE_AVX_MPX_AVX512_MASK,
rename tdesc_amd64_avx_mpx_avx512_pku_linux.
(_initialize_amd64_linux_tdep): Rename
initialize_tdesc_amd64_avx_mpx_avx512_linux.
* amd64-linux-tdep.h (AMD64_LINUX_ORIG_RAX_REGNUM): Adjust regnum
calculation.
(tdesc_amd64_avx_mpx_avx512_linux): Rename to...
(tdesc_amd64_avx_mpx_avx512_pku_linux): ...this.
* amd64-tdep.c (features/i386/amd64-avx-mpx-avx512-pku.c): Rename to...
(features/i386/amd64-avx-mpx-avx512-pku.c): ...this.
(amd64_pkeys_names): New register name for raw register PKRU.
(amd64_init_abi): Add code to initialize PKRU tdep variables if feature
is present.
(amd64_target_description): Rename X86_XSTATE_AVX_MPX_AVX512_MASK,
rename tdesc_amd64_avx_mpx_avx512.
(_initialize_amd64_tdep): Rename initialize_tdesc_amd64_avx_mpx_avx512.
* amd64-tdep.h (enum amd64_regnum): Add PKRU register.
(AMD64_NUM_REGS): Adjust regnum calculation.
* i386-linux.nat.c (GETXSTATEREGS_SUPPLIES): Extend range of
registers supplied via XSTATE by PKRU register.
* common/x86-xstate.h (X86_XSTATE_PKRU): New macro.
(X86_XSTATE_AVX_MPX_AVX512_MASK): Add PKRU and renamed mask.
(X86_XSTATE_ALL_MASK): Rename X86_XSTATE_AVX_MPX_AVX512_MASK.
(X86_XSTATE_PKRU_SIZE): New macro.
(X86_XSTATE_MAX_SIZE): Adjust size.
(HAS_PKRU(XCR0)): New macro.
(X86_XSTATE_SIZE): Add checkfor PKRU.
* features/Makefile (WHICH): Rename i386/i386-avx-mpx-avx512,
i386/i386-avx-mpx-avx512-linux, i386/amd64-avx-mpx-avx512,
i386/amd64-avx-mpx-avx512-linux.
(i386/i386-avx-mpx-avx512-expedite): Rename expedite.
(i386/i386-avx-mpx-avx512-linux-expedite): Likewise.
(i386/amd64-avx-mpx-avx512-expedite): Likewise.
(i386/amd64-avx-mpx-avx512-linux-expedite): Likewise.
(XMLTOC): Rename i386/amd64-avx-mpx-avx512-linux.xml,
i386/amd64-avx-mpx-avx512.xml, i386/i386-avx-mpx-avx512-linux.xml,
i386/i386-avx-mpx-avx512.xml.
((outdir)/i386/i386-avx-mpx-avx512.dat): Rename rule, add
i386/32bit-pkeys.xml.
((outdir)/i386/i386-avx-mpx-avx512-pku-linux.dat): Likewise.
((outdir)/i386/amd64-avx-mpx-avx512.dat): Rename rule, add
i386/64bit-pkeys.xml.
((outdir)/i386/amd64-avx-mpx-avx512-linux.dat): Likewise.
* features/i386/32bit-pkeys.xml: New file.
* features/i386/64bit-pkeys.xml: Likewise.
* features/i386/amd64-avx-mpx-avx512-linux-pku.c: Regenerate from
renamed XML file.
* features/i386/amd64-avx-mpx-avx512-linux.xml: Rename to
amd64-avx-mpx-avx512-pku-linux.xml, add 64bit-pkeys.xml
* features/i386/amd64-avx-mpx-avx512.c: Regenerate from
renamed XML file.
* features/i386/amd64-avx-mpx-avx512.xml: Rename to
amd64-avx-mpx-avx512-pku.xml, add 64bit-pkeys.xml.
* features/i386/i386-avx-mpx-avx512-linux.c: Regenerate from
renamed XML file.
* features/i386/i386-avx-mpx-avx512-linux.xml: Rename to
i386-avx-mpx-avx512-pku-linux.xml, add 32bit-pkeys.xml.
* features/i386/i386-avx-mpx-avx512.c: Regenerate from
renamed XML file.
* features/i386/i386-avx-mpx-avx512.xml: Rename to
i386-avx-mpx-avx512-pku.xml, add 32bit-pkeys.xml.
* i386-linux-nat.c (GETXSTATEREGS_SUPPLIES): Change to use
I386_PKEYS_NUM_REGS.
* i386-linux-tdep.c (features/i386/i386-avx-mpx-avx512-linux.c): Rename
include.
(i386_linux_gregset_reg_offset): Add PKRU register.
(i386_linux_core_read_description): Rename xstate mask and returned
tdesc for X86_XSTATE_AVX_MPX_AVX512_PKU_MASK.
(_initialize_i386_linux_tdep): Rename
initialize_tdesc_i386_avx_mpx_avx512_linux.
* i386-linux-tdep.h (I386_LINUX_ORIG_EAX_REGNUM): Adjuste regnum
calculation.
(tdesc_i386_avx_mpx_avx512_linux): Rename prototype.
(/* Format of XSAVE...): Add pkru register.
* i386-tdep.c (i386-avx-mpx-avx512.c): Rename include.
(i386_pkeys_names): New register name for raw register PKRU.
(i386_pkru_regnum_p): Add function to look up register number of
PKRU raw register.
(i386_register_reggroup_p): Add code to exclude PKRU from general
register group.
(i386_validate_tdesc_p): Add code to handle PKRU feature, add PKRU
registers if feature is present in xcr0.
(i386_gdbarch_init): Adjust number of registers in architecture. Add code
to initialize PKRU feature variables in tdep structure.
(i386_target_description): Rename xstate mask and returned
tdesc for X86_XSTATE_AVX_MPX_AVX512_PKU_MASK.
(_initialize_i386_tdep): Rename initialize_tdesc_i386_avx_mpx_avx512.
* i386-tdep.h (struct gdbarch_tdep): Add feature variables to tdep
structure.
(enum i386_regnum): Add PKRU register.
(I386_PKEYS_NUM_REGS): New define for number of registers in PKRU feature.
(i386_pkru_regnum_p): New prototype.
* i387-tdep.c (xsave_pkeys_offset): New table for PKRU offsets in
XSAVE buffer.
(XSAVE_PKEYS_ADDR): New macro.
(i387_supply_xsave): Add code to handle PKRU register.
(i387_collect_xsave): Likewise.
* i387-tdep.h (I387_NUM_PKEYS_REGS): New define for number of registers
in PKRU feature.
(I387_PKRU_REGNUM): New macro.
(I387_PKEYSEND_REGNUM): Likewise.
* regformats/i386/amd64_avx_mpx_avx512_pku_linux.dat: Regenerate from
renamed XML file.
* regformats/i386/amd64_avx_mpx_avx512_pku.dat: Likewise.
* regformats/i386/i386/amd64-avx-mpx-avx512-pku.dat: Likewise.
* regformats/i386/i386_avx_mpx_avx512_pku_linux.dat: Likewise.
testsuite/Changelog:
2016-04-18 Michael Sturm <michael.sturm@intel.com>
* gdb.arch/i386-pkru.c: New file.
* gdb.arch/i386-pkru.exp: Likewise.
gdbserver/Changelog:
2016-04-18 Michael Sturm <michael.sturm@intel.com>
* Makefile.in (clean): Rename i386-avx-mpx-avx512.c,
i386-avx-mpx-avx512-linux.c, amd64-avx-mpx-avx512.c,
amd64-avx-mpx-avx512-linux.c.
(i386-avx-mpx-avx512-linux-ipa.o:): Rename rule and source file.
(amd64-avx-mpx-avx512-linux-ipa.o:): Likewise.
(i386-avx-mpx-avx512.c :): Rename rule, source files and dat files.
(i386-avx-mpx-avx512-linux.c :): Likewise.
(amd64-avx-mpx-avx512.c :): Likewise.
(amd64-avx-mpx-avx512-linux.c :): Likewise.
* configure.srv (srv_i386_regobj): Rename i386-avx-mpx-avx512.o.
(srv_i386_linux_regobj): Rename i386-avx-mpx-avx512-linux.o.
(srv_amd64_regobj): Rename amd64-avx-mpx-avx512.o.
(srv_amd64_linux_regobj): Rename amd64-avx-mpx-avx512-linux.o.
(ipa_i386_linux_regobj): Rename i386-avx-mpx-avx512-linux-ipa.o.
(ipa_amd64_linux_regobj): Rename amd64-avx-mpx-avx512-pku-linux-ipa.o.
(srv_i386_32bit_xmlfiles): Add 32bit-pkeys.xml.
(srv_i386_64bit_xmlfiles): Add 64bit-pkeys.xml.
(srv_i386_xmlfiles): Rename i386/i386-avx-mpx-avx512.xml.
(srv_amd64_xmlfiles): Rename i386/amd64-avx-mpx-avx512.xml.
(srv_i386_linux_xmlfiles): Rename i386/i386-avx-mpx-avx512-linux.xml.
(srv_amd64_linux_xmlfiles): Rename di386/amd64-avx-mpx-avx512-linux.xml.
* i387-fp.c (num_pkeys_registers): New variable.
(struct i387_xsave): Add space for pkru values.
(i387_cache_to_fsave): Add code to handle PKRU register.
(i387_xsave_to_cache): Likewise.
* linux-amd64-ipa.c (get_ipa_tdesc): Rename
tdesc_amd64_avx_mpx_avx512_linux.
(initialize_low_tracepoint): Rename
init_registers_amd64_avx_mpx_avx512_linux.
* linux-i386-ipa.c (get_ipa_desc): Rename
tdesc_i386_avx_mpx_avx512_linux.
(initialize_low_tracepoint): Rename
init_registers_i386_avx_mpx_avx512_linux.
* linux-x86-low.c (x86_64_regmap[]): Add PKRU register.
(x86_linux_read_description): Rename X86_XSTATE_AVX_MPX_AVX512_MASK,
rename tdesc_amd64_avx_mpx_avx512_linux, rename
tdesc_i386_avx_mpx_avx512_linux.
(x86_get_ipa_tdesc_idx): Rename tdesc_amd64_avx_mpx_avx512_linux,
rename tdesc_i386_avx_mpx_avx512_linux.
(initialize_low_arch): Rename init_registers_amd64_avx_mpx_avx512_linux,
rename init_registers_i386_avx_mpx_avx512_linux.
* linux-x86-tdesc.h (init_registers_amd64_avx_mpx_avx512_linux): Renamed
prototype.
(tdesc_amd64_avx_mpx_avx512_linux): Likewise.
(init_registers_i386_avx_mpx_avx512_linux): Likewise.
(tdesc_i386_avx_mpx_avx512_linux): Likewise.
doc/Changelog:
2016-04-18 Michael Sturm <michael.sturm@intel.com>
* gdb.texinfo (i386 Features): Add description of PKRU register.
Change-Id: If75ce5aba7dfd33fdbe3d8b47f04ef3f550c52be
Signed-off-by: Michael Sturm <michael.sturm@intel.com>
2017-02-01 19:22:27 +08:00
|
|
|
|
|
|
|
|
* GDB now supports access to the PKU register on GNU/Linux. The register is
|
|
|
|
|
added by the Memory Protection Keys for Userspace feature which will be
|
|
|
|
|
available in future Intel CPUs.
|
2016-08-01 23:28:26 +08:00
|
|
|
|
2017-03-21 04:47:59 +08:00
|
|
|
* GDB now supports C++11 rvalue references.
|
|
|
|
|
|
2016-11-21 23:39:57 +08:00
|
|
|
* Python Scripting
|
|
|
|
|
|
|
|
|
|
** New functions to start, stop and access a running btrace recording.
|
2017-03-21 04:47:59 +08:00
|
|
|
** Rvalue references are now supported in gdb.Type.
|
2016-11-21 23:39:57 +08:00
|
|
|
|
2017-02-06 17:12:00 +08:00
|
|
|
* GDB now supports recording and replaying rdrand and rdseed Intel 64
|
|
|
|
|
instructions.
|
|
|
|
|
|
2016-10-29 23:30:34 +08:00
|
|
|
* Building GDB and GDBserver now requires a C++11 compiler.
|
2016-10-29 23:14:36 +08:00
|
|
|
|
|
|
|
|
For example, GCC 4.8 or later.
|
2016-09-06 02:10:44 +08:00
|
|
|
|
|
|
|
|
It is no longer possible to build GDB or GDBserver with a C
|
|
|
|
|
compiler. The --disable-build-with-cxx configure option has been
|
|
|
|
|
removed.
|
|
|
|
|
|
2016-11-18 00:59:18 +08:00
|
|
|
* Building GDB and GDBserver now requires GNU make >= 3.81.
|
|
|
|
|
|
|
|
|
|
It is no longer supported to build GDB or GDBserver with another
|
|
|
|
|
implementation of the make program or an earlier version of GNU make.
|
|
|
|
|
|
2016-10-29 23:10:23 +08:00
|
|
|
* Native debugging on MS-Windows supports command-line redirection
|
|
|
|
|
|
|
|
|
|
Command-line arguments used for starting programs on MS-Windows can
|
|
|
|
|
now include redirection symbols supported by native Windows shells,
|
|
|
|
|
such as '<', '>', '>>', '2>&1', etc. This affects GDB commands such
|
|
|
|
|
as "run", "start", and "set args", as well as the corresponding MI
|
|
|
|
|
features.
|
|
|
|
|
|
2016-08-11 02:22:45 +08:00
|
|
|
* Support for thread names on MS-Windows.
|
|
|
|
|
|
|
|
|
|
GDB now catches and handles the special exception that programs
|
|
|
|
|
running on MS-Windows use to assign names to threads in the
|
|
|
|
|
debugger.
|
|
|
|
|
|
Remove Java support
This patch removes the Java support from gdb. gcj has not seen much
development or use for years now, and was recently removed from GCC.
This patch changes gdb to follow; in the unlikely event that there are
still users using gcj, they can continue to use an older gdb to debug.
Or, they can debug in C++ mode.
Built and regtested on x86-64 Fedora 24.
2016-10-06 Tom Tromey <tom@tromey.com>
* MAINTAINERS: Remove Java test maintainer.
* varobj.h (java_varobj_ops): Don't declare.
* valprint.h (struct value_print_options)
<pascal_static_field_print>: Update comment.
* utils.c (producer_is_gcc): Remove java reference.
* symtab.h (struct general_symbol_info): Remove java references.
(SYMBOL_SEARCH_NAME): Likewise.
* objfiles.c (allocate_objfile): Update comment.
* linespec.c (find_linespec_symbols): Remove java references.
* gnu-v3-abi.c (gnuv3_rtti_type, gnuv3_baseclass_offset): Remove
java references.
* gdbtypes.h (struct cplus_struct_type) <is_java>: Remove.
(TYPE_CPLUS_REALLY_JAVA): Remove.
* c-varobj.c (enum vsections): Update comment.
* symtab.c (symbol_set_language, symbol_set_names)
(symbol_natural_name, symbol_demangled_name)
(demangle_for_lookup, symbol_matches_domain)
(default_make_symbol_completion_list_break_on_1): Remove java
references.
(JAVA_PREFIX, JAVA_PREFIX_LEN): Remove.
* psymtab.c (match_partial_symbol, psymtab_search_name)
(lookup_partial_symbol): Remove java references.
* dwarf2read.c (find_slot_in_mapped_hash): Remove java references.
(add_partial_symbol, dwarf2_compute_name, dwarf2_physname)
(dwarf2_add_member_fn, is_vtable_name, read_structure_type)
(process_structure_scope, read_subroutine_type)
(read_subrange_type, load_partial_dies)
(new_symbol_full, determine_prefix, typename_concat)
(dwarf2_name): Remove java references.
(set_cu_language): Treat Java as C++.
* c-typeprint.c (c_type_print_args): Remove java reference.
* defs.h (enum language) <language_java>: Remove.
* Makefile.in (SFILES, HFILES_NO_SRCDIR, COMMON_OBS, YYFILES)
(YYOBJ, local-maintainer-clean): Don't mention java files.
* jv-exp.y, jv-lang.c, jv-lang.h, jv-typeprint.c, jv-valprint.c,
jv-varobj.c: Remove.
2016-10-06 Tom Tromey <tom@tromey.com>
* guile.texi (Types In Guile): Remove Java mentions.
* python.texi (Types In Python): Remove Java mentions.
* gdb.texinfo (Address Locations, Supported Languages)
(Index Section Format): Remove Java mentions.
2016-10-06 Tom Tromey <tom@tromey.com>
* gdb.compile/compile.exp: Change java tests to rust.
* gdb.base/setshow.exp: Change java tests to rust.
* gdb.base/default.exp: Remove java from language list.
* README (Examples): Update language example.
* gdb.python/py-lookup-type.exp (test_lookup_type): Remove java
test.
* lib/gdb.exp (skip_java_tests): Remove.
* lib/java.exp: Remove.
* gdb.java: Remove.
2016-10-05 22:44:34 +08:00
|
|
|
* Support for Java programs compiled with gcj has been removed.
|
|
|
|
|
|
2016-12-03 03:17:14 +08:00
|
|
|
* User commands now accept an unlimited number of arguments.
|
|
|
|
|
Previously, only up to 10 was accepted.
|
|
|
|
|
|
Fix PR 20559 - "eval" command and $arg0...$arg9/$argc substitution
It'd be handy to be able to iterate over command arguments in
user-defined commands, in order to support optional arguments
($arg0..$argN).
I thought I could make it work with "eval", but alas, it doesn't work
currently. E.g., with:
define test
set $i = 0
while $i < $argc
eval "print $arg%d", $i
set $i = $i + 1
end
end
we get:
(gdb) test 1
$1 = void
(gdb) test 1 2 3
$2 = void
$3 = void
$4 = void
(gdb)
The problem is that "eval" doesn't do user-defined command arguments
substitution after expanding its own argument. This patch fixes that,
which makes the example above work:
(gdb) test 1
$1 = 1
(gdb) test 1 2 3
$2 = 1
$3 = 2
$4 = 3
(gdb)
New test included, similar the above, but also exercises expanding
$argc.
I think this is likely to simplify many scripts out there, so I'm
adding an example to the manual and mentioning it in NEWS as well.
gdb/ChangeLog:
2016-12-02 Pedro Alves <palves@redhat.com>
PR cli/20559
* NEWS: Mention "eval" expands user-defined command arguments.
* cli/cli-script.c (execute_control_command): Adjust to rename.
(insert_args): Rename to ...
(insert_user_defined_cmd_args): ... this, and make extern.
* cli/cli-script.h (insert_user_defined_cmd_args): New
declaration.
* printcmd.c: Include "cli/cli-script.h".
(eval_command): Call insert_user_defined_cmd_args.
gdb/doc/ChangeLog:
2016-12-02 Pedro Alves <palves@redhat.com>
PR cli/20559
* gdb.texinfo (Define): Add example of using "eval" to process a
variable number of arguments.
(Output) <eval>: Add anchor.
gdb/testsuite/ChangeLog:
2016-12-02 Pedro Alves <palves@redhat.com>
PR cli/20559
* gdb.base/commands.exp (user_defined_command_args_eval): New
procedure.
(top level): Call it.
2016-12-03 03:17:13 +08:00
|
|
|
* The "eval" command now expands user-defined command arguments.
|
|
|
|
|
|
|
|
|
|
This makes it easier to process a variable number of arguments:
|
|
|
|
|
|
|
|
|
|
define mycommand
|
|
|
|
|
set $i = 0
|
|
|
|
|
while $i < $argc
|
|
|
|
|
eval "print $arg%d", $i
|
|
|
|
|
set $i = $i + 1
|
|
|
|
|
end
|
|
|
|
|
end
|
|
|
|
|
|
2017-02-06 15:44:03 +08:00
|
|
|
* Target descriptions can now describe registers for sparc32 and sparc64.
|
|
|
|
|
|
2017-02-21 03:53:22 +08:00
|
|
|
* GDB now supports DWARF version 5 (debug information format).
|
|
|
|
|
Its .debug_names index is not yet supported.
|
|
|
|
|
|
2017-01-05 01:41:58 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
FreeBSD/mips mips*-*-freebsd
|
|
|
|
|
|
2016-08-13 01:02:20 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Synopsys ARC arc*-*-elf32
|
2017-01-05 01:41:58 +08:00
|
|
|
FreeBSD/mips mips*-*-freebsd
|
2016-08-13 01:02:20 +08:00
|
|
|
|
2017-05-30 17:29:57 +08:00
|
|
|
* Removed targets and native configurations
|
|
|
|
|
|
|
|
|
|
Alpha running FreeBSD alpha*-*-freebsd*
|
|
|
|
|
Alpha running GNU/kFreeBSD alpha*-*-kfreebsd*-gnu
|
|
|
|
|
|
2017-01-20 22:13:03 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
flash-erase
|
|
|
|
|
Erases all the flash memory regions reported by the target.
|
|
|
|
|
|
2017-05-30 17:29:57 +08:00
|
|
|
maint print arc arc-instruction address
|
|
|
|
|
Print internal disassembler information about instruction at a given address.
|
2017-03-21 02:57:51 +08:00
|
|
|
|
2017-05-30 17:29:57 +08:00
|
|
|
* New options
|
2017-03-01 02:32:07 +08:00
|
|
|
|
|
|
|
|
set disassembler-options
|
|
|
|
|
show disassembler-options
|
|
|
|
|
Controls the passing of target specific information to the disassembler.
|
|
|
|
|
If it is necessary to specify more than one disassembler option then
|
|
|
|
|
multiple options can be placed together into a comma separated list.
|
|
|
|
|
The default value is the empty string. Currently, the only supported
|
|
|
|
|
targets are ARM, PowerPC and S/390.
|
|
|
|
|
|
2017-05-30 17:29:57 +08:00
|
|
|
* New MI commands
|
2017-02-10 19:12:06 +08:00
|
|
|
|
2017-05-30 17:29:57 +08:00
|
|
|
-target-flash-erase
|
|
|
|
|
Erases all the flash memory regions reported by the target. This is
|
|
|
|
|
equivalent to the CLI command flash-erase.
|
2017-04-05 05:20:37 +08:00
|
|
|
|
2017-05-30 17:29:57 +08:00
|
|
|
-file-list-shared-libraries
|
|
|
|
|
List the shared libraries in the program. This is
|
|
|
|
|
equivalent to the CLI command "info shared".
|
2017-04-05 05:20:37 +08:00
|
|
|
|
2018-01-26 18:13:11 +08:00
|
|
|
-catch-handlers
|
|
|
|
|
Catchpoints stopping the program when Ada exceptions are
|
|
|
|
|
handled. This is equivalent to the CLI command "catch handlers".
|
|
|
|
|
|
2016-08-01 23:28:26 +08:00
|
|
|
*** Changes in GDB 7.12
|
2016-02-10 11:28:01 +08:00
|
|
|
|
2016-08-06 00:09:31 +08:00
|
|
|
* GDB and GDBserver now build with a C++ compiler by default.
|
|
|
|
|
|
|
|
|
|
The --enable-build-with-cxx configure option is now enabled by
|
|
|
|
|
default. One must now explicitly configure with
|
|
|
|
|
--disable-build-with-cxx in order to build with a C compiler. This
|
|
|
|
|
option will be removed in a future release.
|
|
|
|
|
|
2016-07-25 16:57:06 +08:00
|
|
|
* GDBserver now supports recording btrace without maintaining an active
|
|
|
|
|
GDB connection.
|
|
|
|
|
|
Add negative repeat count to 'x' command
This change adds support for specifying a negative repeat count to
all the formats of the 'x' command to examine memory backward.
A new testcase 'examine-backward' is added to cover this new feature.
Here's the example output from the new feature:
<format 'i'>
(gdb) bt
#0 Func1 (n=42, p=0x40432e "hogehoge") at main.cpp:5
#1 0x00000000004041fa in main (argc=1, argv=0x7fffffffdff8) at main.cpp:19
(gdb) x/-4i 0x4041fa
0x4041e5 <main(int, char**)+11>: mov %rsi,-0x10(%rbp)
0x4041e9 <main(int, char**)+15>: lea 0x13e(%rip),%rsi
0x4041f0 <main(int, char**)+22>: mov $0x2a,%edi
0x4041f5 <main(int, char**)+27>: callq 0x404147
<format 'x'>
(gdb) x/-4xw 0x404200
0x4041f0 <main(int, char**)+22>: 0x00002abf 0xff4de800 0x76e8ffff 0xb8ffffff
(gdb) x/-4
0x4041e0 <main(int, char**)+6>: 0x7d8910ec 0x758948fc 0x358d48f0 0x0000013e
gdb/ChangeLog:
* NEWS: Mention that GDB now supports a negative repeat count in
the 'x' command.
* printcmd.c (decode_format): Allow '-' in the parameter
"string_ptr" to accept a negative repeat count.
(find_instruction_backward): New function.
(read_memory_backward): New function.
(integer_is_zero): New function.
(find_string_backward): New function.
(do_examine): Use new functions to examine memory backward.
(_initialize_printcmd): Mention that 'x' command supports a negative
repeat count.
gdb/doc/ChangeLog:
* gdb.texinfo (Examining Memory): Document negative repeat
count in the 'x' command.
gdb/testsuite/ChangeLog:
* gdb.base/examine-backward.c: New file.
* gdb.base/examine-backward.exp: New file.
2016-06-10 13:47:42 +08:00
|
|
|
* GDB now supports a negative repeat count in the 'x' command to examine
|
|
|
|
|
memory backward from the given address. For example:
|
|
|
|
|
|
|
|
|
|
(gdb) bt
|
|
|
|
|
#0 Func1 (n=42, p=0x40061c "hogehoge") at main.cpp:4
|
|
|
|
|
#1 0x400580 in main (argc=1, argv=0x7fffffffe5c8) at main.cpp:8
|
|
|
|
|
(gdb) x/-5i 0x0000000000400580
|
|
|
|
|
0x40056a <main(int, char**)+8>: mov %edi,-0x4(%rbp)
|
|
|
|
|
0x40056d <main(int, char**)+11>: mov %rsi,-0x10(%rbp)
|
|
|
|
|
0x400571 <main(int, char**)+15>: mov $0x40061c,%esi
|
|
|
|
|
0x400576 <main(int, char**)+20>: mov $0x2a,%edi
|
|
|
|
|
0x40057b <main(int, char**)+25>:
|
|
|
|
|
callq 0x400536 <Func1(int, char const*)>
|
|
|
|
|
|
2016-04-26 22:28:43 +08:00
|
|
|
* Fortran: Support structures with fields of dynamic types and
|
|
|
|
|
arrays of dynamic types.
|
|
|
|
|
|
2016-12-20 00:33:46 +08:00
|
|
|
* The symbol dumping maintenance commands have new syntax.
|
|
|
|
|
maint print symbols [-pc address] [--] [filename]
|
|
|
|
|
maint print symbols [-objfile objfile] [-source source] [--] [filename]
|
|
|
|
|
maint print psymbols [-objfile objfile] [-pc address] [--] [filename]
|
|
|
|
|
maint print psymbols [-objfile objfile] [-source source] [--] [filename]
|
|
|
|
|
maint print msymbols [-objfile objfile] [--] [filename]
|
|
|
|
|
|
2016-03-16 05:37:29 +08:00
|
|
|
* GDB now supports multibit bitfields and enums in target register
|
|
|
|
|
descriptions.
|
|
|
|
|
|
2016-03-11 06:12:30 +08:00
|
|
|
* New Python-based convenience function $_as_string(val), which returns
|
|
|
|
|
the textual representation of a value. This function is especially
|
|
|
|
|
useful to obtain the text label of an enum value.
|
|
|
|
|
|
Intel MPX bound violation handling
With Intel Memory Protection Extensions it was introduced the concept of
boundary violation. A boundary violations is presented to the inferior as
a segmentation fault having SIGCODE 3. This patch adds a
handler for a boundary violation extending the information displayed
when a bound violation is presented to the inferior. In the stop mode
case the debugger will also display the kind of violation: "upper" or
"lower", bounds and the address accessed.
On no stop mode the information will still remain unchanged. Additional
information about bound violations are not meaningful in that case user
does not know the line in which violation occurred as well.
When the segmentation fault handler is stop mode the out puts will be
changed as exemplified below.
The usual output of a segfault is:
Program received signal SIGSEGV, Segmentation fault
0x0000000000400d7c in upper (p=0x603010, a=0x603030, b=0x603050,
c=0x603070, d=0x603090, len=7) at i386-mpx-sigsegv.c:68
68 value = *(p + len);
In case it is a bound violation it will be presented as:
Program received signal SIGSEGV, Segmentation fault
Upper bound violation while accessing address 0x7fffffffc3b3
Bounds: [lower = 0x7fffffffc390, upper = 0x7fffffffc3a3]
0x0000000000400d7c in upper (p=0x603010, a=0x603030, b=0x603050,
c=0x603070, d=0x603090, len=7) at i386-mpx-sigsegv.c:68
68 value = *(p + len);
In mi mode the output of a segfault is:
*stopped,reason="signal-received",signal-name="SIGSEGV",
signal-meaning="Segmentation fault", frame={addr="0x0000000000400d7c",
func="upper",args=[{name="p", value="0x603010"},{name="a",value="0x603030"}
,{name="b",value="0x603050"}, {name="c",value="0x603070"},
{name="d",value="0x603090"},{name="len",value="7"}],
file="i386-mpx-sigsegv.c",fullname="i386-mpx-sigsegv.c",line="68"},
thread-id="1",stopped-threads="all",core="6"
in the case of a bound violation:
*stopped,reason="signal-received",signal-name="SIGSEGV",
signal-meaning="Segmentation fault",
sigcode-meaning="Upper bound violation",
lower-bound="0x603010",upper-bound="0x603023",bound-access="0x60302f",
frame={addr="0x0000000000400d7c",func="upper",args=[{name="p",
value="0x603010"},{name="a",value="0x603030"},{name="b",value="0x603050"},
{name="c",value="0x603070"},{name="d",value="0x603090"},
{name="len",value="7"}],file="i386-mpx-sigsegv.c",
fullname="i386-mpx-sigsegv.c",line="68"},thread-id="1",
stopped-threads="all",core="6"
2016-02-18 Walfred Tedeschi <walfred.tedeschi@intel.com>
gdb/ChangeLog:
* NEWS: Add entry for bound violation.
* amd64-linux-tdep.c (amd64_linux_init_abi_common):
Add handler for segmentation fault.
* gdbarch.sh (handle_segmentation_fault): New.
* gdbarch.c: Regenerate.
* gdbarch.h: Regenerate.
* i386-linux-tdep.c (i386_linux_handle_segmentation_fault): New.
(SIG_CODE_BONDARY_FAULT): New define.
(i386_linux_init_abi): Use i386_mpx_bound_violation_handler.
* i386-linux-tdep.h (i386_linux_handle_segmentation_fault) New.
* i386-tdep.c (i386_mpx_enabled): Add as external.
* i386-tdep.c (i386_mpx_enabled): Add as external.
* infrun.c (handle_segmentation_fault): New function.
(print_signal_received_reason): Use handle_segmentation_fault.
gdb/testsuite/ChangeLog:
* gdb.arch/i386-mpx-sigsegv.c: New file.
* gdb.arch/i386-mpx-sigsegv.exp: New file.
* gdb.arch/i386-mpx-simple_segv.c: New file.
* gdb.arch/i386-mpx-simple_segv.exp: New file.
gdb/doc/ChangeLog:
* gdb.texinfo (Signals): Add bound violation display hints for
a SIGSEGV.
2016-02-19 00:24:59 +08:00
|
|
|
* Intel MPX bound violation handling.
|
|
|
|
|
|
|
|
|
|
Segmentation faults caused by a Intel MPX boundary violation
|
|
|
|
|
now display the kind of violation (upper or lower), the memory
|
|
|
|
|
address accessed and the memory bounds, along with the usual
|
|
|
|
|
signal received and code location.
|
|
|
|
|
|
|
|
|
|
For example:
|
|
|
|
|
|
|
|
|
|
Program received signal SIGSEGV, Segmentation fault
|
|
|
|
|
Upper bound violation while accessing address 0x7fffffffc3b3
|
|
|
|
|
Bounds: [lower = 0x7fffffffc390, upper = 0x7fffffffc3a3]
|
|
|
|
|
0x0000000000400d7c in upper () at i386-mpx-sigsegv.c:68
|
|
|
|
|
|
2016-04-27 09:38:56 +08:00
|
|
|
* Rust language support.
|
|
|
|
|
GDB now supports debugging programs written in the Rust programming
|
|
|
|
|
language. See https://www.rust-lang.org/ for more information about
|
|
|
|
|
Rust.
|
|
|
|
|
|
2016-06-21 08:11:55 +08:00
|
|
|
* Support for running interpreters on specified input/output devices
|
|
|
|
|
|
|
|
|
|
GDB now supports a new mechanism that allows frontends to provide
|
|
|
|
|
fully featured GDB console views, as a better alternative to
|
|
|
|
|
building such views on top of the "-interpreter-exec console"
|
|
|
|
|
command. See the new "new-ui" command below. With that command,
|
|
|
|
|
frontends can now start GDB in the traditional command-line mode
|
|
|
|
|
running in an embedded terminal emulator widget, and create a
|
|
|
|
|
separate MI interpreter running on a specified i/o device. In this
|
|
|
|
|
way, GDB handles line editing, history, tab completion, etc. in the
|
|
|
|
|
console all by itself, and the GUI uses the separate MI interpreter
|
|
|
|
|
for its own control and synchronization, invisible to the command
|
|
|
|
|
line.
|
|
|
|
|
|
2016-07-24 05:38:24 +08:00
|
|
|
* The "catch syscall" command catches groups of related syscalls.
|
|
|
|
|
|
|
|
|
|
The "catch syscall" command now supports catching a group of related
|
|
|
|
|
syscalls using the 'group:' or 'g:' prefix.
|
|
|
|
|
|
2016-02-25 02:19:50 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
skip -file file
|
|
|
|
|
skip -gfile file-glob-pattern
|
|
|
|
|
skip -function function
|
|
|
|
|
skip -rfunction regular-expression
|
|
|
|
|
A generalized form of the skip command, with new support for
|
|
|
|
|
glob-style file names and regular expressions for function names.
|
|
|
|
|
Additionally, a file spec and a function spec may now be combined.
|
|
|
|
|
|
2016-01-21 18:03:32 +08:00
|
|
|
maint info line-table REGEXP
|
2020-06-05 18:24:20 +08:00
|
|
|
Display the contents of GDB's internal line table data structure.
|
2016-01-21 18:03:32 +08:00
|
|
|
|
2016-04-21 00:09:53 +08:00
|
|
|
maint selftest
|
|
|
|
|
Run any GDB unit tests that were compiled in.
|
|
|
|
|
|
2016-06-21 08:11:55 +08:00
|
|
|
new-ui INTERP TTY
|
|
|
|
|
Start a new user interface instance running INTERP as interpreter,
|
|
|
|
|
using the TTY file for input/output.
|
|
|
|
|
|
2016-05-20 05:51:00 +08:00
|
|
|
* Python Scripting
|
|
|
|
|
|
|
|
|
|
** gdb.Breakpoint objects have a new attribute "pending", which
|
|
|
|
|
indicates whether the breakpoint is pending.
|
2016-08-03 06:52:59 +08:00
|
|
|
** Three new breakpoint-related events have been added:
|
|
|
|
|
gdb.breakpoint_created, gdb.breakpoint_modified, and
|
|
|
|
|
gdb.breakpoint_deleted.
|
2016-05-20 05:51:00 +08:00
|
|
|
|
2016-07-23 16:38:03 +08:00
|
|
|
signal-event EVENTID
|
|
|
|
|
Signal ("set") the given MS-Windows event object. This is used in
|
|
|
|
|
conjunction with the Windows JIT debugging (AeDebug) support, where
|
|
|
|
|
the OS suspends a crashing process until a debugger can attach to
|
|
|
|
|
it. Resuming the crashing process, in order to debug it, is done by
|
|
|
|
|
signalling an event.
|
|
|
|
|
|
2016-03-30 05:18:19 +08:00
|
|
|
* Support for tracepoints and fast tracepoints on s390-linux and s390x-linux
|
|
|
|
|
was added in GDBserver, including JIT compiling fast tracepoint's
|
|
|
|
|
conditional expression bytecode into native code.
|
|
|
|
|
|
Remove support for "target m32rsdi" and "target mips/pmon/ddb/rockhopper/lsi"
This removes support for:
| target | source |
|-------------------+-----------------------|
| target m32rsdi | gdb/remote-m32r-sdi.c |
| target mips | gdb/remote-mips.c |
| target pmon | gdb/remote-mips.c |
| target ddb | gdb/remote-mips.c |
| target rockhopper | gdb/remote-mips.c |
| target lsi | gdb/remote-mips.c |
That is:
- Remote M32R debugging over SDI.
- Debugging boards using the MIPS remote debugging protocol
over a serial line, PMON, and a few variants.
These are the last non-"target remote" remote targets in the tree, if
you don't count "target sim".
Refs:
https://sourceware.org/ml/gdb/2016-03/msg00004.html
https://sourceware.org/ml/gdb-patches/2016-03/msg00580.html
gdb/ChangeLog:
2016-03-31 Pedro Alves <palves@redhat.com>
* NEWS: Mention that support for "target m32rsdi", "target mips",
"target pmon", "target ddb", "target rockhopper", and "target lsi"
was removed.
* Makefile.in (ALL_TARGET_OBS): Remove remote-m32r-sdi.o and
remote-mips.o.
(ALLDEPFILES): Remove remote-m32r-sdi.c and remote-mips.c.
* configure.tgt: Remove all references to remote-m32r-sdi.o and
remote-mips.o.
* mips-tdep.c (deprecated_mips_set_processor_regs_hack): Delete
function.
* mips-tdep.h (deprecated_mips_set_processor_regs_hack): Delete
declaration.
* remote-m32r-sdi.c, remote-mips.c: Delete files.
* symfile.c (generic_load, generic_load): Remove comments.
gdb/doc/ChangeLog:
2016-03-31 Pedro Alves <palves@redhat.com>
* gdb.texinfo (M32R/SDI): Delete node.
(MIPS Embedded): Remove references to the MIPS remote debugging
protocol, PMON and variants, and the associated commands.
2016-03-31 20:24:34 +08:00
|
|
|
* Support for various remote target protocols and ROM monitors has
|
|
|
|
|
been removed:
|
|
|
|
|
|
|
|
|
|
target m32rsdi Remote M32R debugging over SDI
|
|
|
|
|
target mips MIPS remote debugging protocol
|
|
|
|
|
target pmon PMON ROM monitor
|
|
|
|
|
target ddb NEC's DDB variant of PMON for Vr4300
|
|
|
|
|
target rockhopper NEC RockHopper variant of PMON
|
|
|
|
|
target lsi LSI variant of PMO
|
|
|
|
|
|
2016-03-31 21:49:25 +08:00
|
|
|
* Support for tracepoints and fast tracepoints on powerpc-linux,
|
|
|
|
|
powerpc64-linux, and powerpc64le-linux was added in GDBserver,
|
|
|
|
|
including JIT compiling fast tracepoint's conditional expression
|
|
|
|
|
bytecode into native code.
|
|
|
|
|
|
Add method/format information to =record-started
Eclipse CDT now supports enabling execution recording using two methods
(full and btrace) and both formats for btrace (bts and pt). In the
event that recording is enabled behind the back of the GUI (by the user
on the command line, or a script), we need to know which method/format
are being used, so it can be correctly reflected in the interface. This
patch adds this information to the =record-started async record.
Before:
=record-started,thread-group="i1"
After:
=record-started,thread-group="i1",method="btrace",format="bts"
=record-started,thread-group="i1",method="btrace",format="pt"
=record-started,thread-group="i1",method="full"
The "format" field is only present when the current method supports
multiple formats (only the btrace method as of now).
gdb/ChangeLog:
* NEWS: Mention the new fields in =record-started.
* common/btrace-common.h (btrace_format_short_string): New function
declaration.
* common/btrace-common.c (btrace_format_short_string): New
function.
* mi/mi-interp.c (mi_record_changed): Output method and format
fields in the =record-started record.
* record-btrace.c (record_btrace_open): Adapt record_changed
notification.
* record-full.c (record_full_open): Likewise.
* record.c (cmd_record_stop): Likewise.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI Async Records): Document method and
format fields in =record-started.
* observer.texi (record_changed): Add method and format
parameters.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-record-changed.exp: Adjust =record-started output
matching.
2016-05-31 05:29:39 +08:00
|
|
|
* MI async record =record-started now includes the method and format used for
|
|
|
|
|
recording. For example:
|
|
|
|
|
|
|
|
|
|
=record-started,thread-group="i1",method="btrace",format="bts"
|
|
|
|
|
|
Emit inferior, thread and frame selection events to all UIs
With this patch, when an inferior, thread or frame is explicitly
selected by the user, notifications will appear on all CLI and MI UIs.
When a GDB console is integrated in a front-end, this allows the
front-end to follow a selection made by the user ont he CLI, and it
informs the user about selection changes made behind the scenes by the
front-end.
This patch addresses PR gdb/20487.
In order to communicate frame changes to the front-end, this patch adds
a new field to the =thread-selected event for the selected frame. The
idea is that since inferior/thread/frame can be seen as a composition,
it makes sense to send them together in the same event. The vision
would be to eventually send the inferior information as well, if we find
that it's needed, although the "=thread-selected" event would be
ill-named for that job.
Front-ends need to handle this new field if they want to follow the
frame selection changes that originate from the console. The format of
the frame attribute is the same as what is found in the *stopped events.
Here's a detailed example for each command and the events they generate:
thread
------
1. CLI command:
thread 1.3
MI event:
=thread-selected,id="3",frame={...}
2. MI command:
-thread-select 3
CLI event:
[Switching to thread 1.3 ...]
3. MI command (CLI-in-MI):
thread 1.3
MI event/reply:
&"thread 1.3\n"
~"#0 child_sub_function () ...
=thread-selected,id="3",frame={level="0",...}
^done
frame
-----
1. CLI command:
frame 1
MI event:
=thread-selected,id="3",frame={level="1",...}
2. MI command:
-stack-select-frame 1
CLI event:
#1 0x00000000004007f0 in child_function...
3. MI command (CLI-in-MI):
frame 1
MI event/reply:
&"frame 1\n"
~"#1 0x00000000004007f9 in ..."
=thread-selected,id="3",frame={level="1"...}
^done
inferior
--------
Inferior selection events only go from the console to MI, since there's
no way to select the inferior in pure MI.
1. CLI command:
inferior 2
MI event:
=thread-selected,id="3"
Note that if the user selects an inferior that is not started or exited,
the MI doesn't receive a notification. Since there is no threads to
select, the =thread-selected event does not apply...
2. MI command (CLI-in-MI):
inferior 2
MI event/reply:
&"inferior 2\n"
~"[Switching to inferior 2 ...]"
=thread-selected,id="4",frame={level="0"...}
^done
Internal implementation detail: this patch makes it possible to suppress
notifications caused by a CLI command, like what is done in mi-interp.c.
This means that it's now possible to use the
add_com_suppress_notification function to register a command with some
event suppressed. It is used to implement the select-frame command in
this patch.
The function command_notifies_uscc_observer was added to extract
the rather complicated logical expression from the if statement. It is
also now clearer what that logic does: if the command used by the user
already notifies the user_selected_context_changed observer, there is
not need to notify it again. It therefore protects again emitting the
event twice.
No regressions, tested on ubuntu 14.04 x86 with target boards unix and
native-extended-gdbserver.
gdb/ChangeLog:
YYYY-MM-DD Antoine Tremblay <antoine.tremblay@ericsson.com>
YYYY-MM-DD Simon Marchi <simon.marchi@ericsson.com>
PR gdb/20487
* NEWS: Mention new frame field of =thread-selected event.
* cli/cli-decode.c (add_cmd): Initialize c->suppress_notification.
(add_com_suppress_notification): New function definition.
(cmd_func): Set and restore the suppress_notification flag.
* cli/cli-deicode.h (struct cmd_list_element)
<suppress_notification>: New field.
* cli/cli-interp.c (cli_suppress_notification): New global variable.
(cli_on_user_selected_context_changed): New function.
(_initialize_cli_interp): Attach to user_selected_context_changed
observer.
* command.h (struct cli_suppress_notification): New structure.
(cli_suppress_notification): New global variable declaration.
(add_com_suppress_notification): New function declaration.
* defs.h (enum user_selected_what_flag): New enum.
(user_selected_what): New enum flag type.
* frame.h (print_stack_frame_to_uiout): New function declaration.
* gdbthread.h (print_selected_thread_frame): New function declaration.
* inferior.c (print_selected_inferior): New function definition.
(inferior_command): Remove printing of inferior/thread/frame switch
notifications, notify user_selected_context_changed observer.
* inferior.h (print_selected_inferior): New function declaration.
* mi/mi-cmds.c (struct mi_cmd): Add user_selected_context
suppression to stack-select-frame and thread-select commands.
* mi/mi-interp.c (struct mi_suppress_notification)
<user_selected_context>: Initialize.
(mi_user_selected_context_changed): New function definition.
(_initialize_mi_interp): Attach to user_selected_context_changed.
* mi/mi-main.c (mi_cmd_thread_select): Print thread selection reply.
(mi_execute_command): Handle notification suppression. Notify
user_selected_context_changed observer on thread change instead of printing
event directly. Don't send it if command already sends the notification.
(command_notifies_uscc_observer): New function.
(mi_cmd_execute): Don't handle notification suppression.
* mi/mi-main.h (struct mi_suppress_notification)
<user_selected_context>: New field.
* stack.c (print_stack_frame_to_uiout): New function definition.
(select_frame_command): Notify user_selected_context_changed
observer.
(frame_command): Call print_selected_thread_frame if there's no frame
change or notify user_selected_context_changed observer if there is.
(up_command): Notify user_selected_context_changed observer.
(down_command): Likewise.
(_initialize_stack): Suppress user_selected_context notification for
command select-frame.
* thread.c (thread_command): Notify
user_selected_context_changed if the thread has changed, print
thread info directly if it hasn't.
(do_captured_thread_select): Do not print thread switch event.
(print_selected_thread_frame): New function definition.
* tui/tui-interp.c (tui_on_user_selected_context_changed):
New function definition.
(_initialize_tui_interp): Attach to user_selected_context_changed
observer.
gdb/doc/ChangeLog:
PR gdb/20487
* gdb.texinfo (Context management): Update mention of frame
change notifications.
(gdb/mi Async Records): Document frame field in
=thread-select event.
* observer.texi (GDB Observers): New user_selected_context_changed
observer.
gdb/testsuite/ChangeLog:
PR gdb/20487
* gdb.mi/mi-pthreads.exp (check_mi_thread_command_set): Adapt
=thread-select-event check.
2016-10-04 04:52:44 +08:00
|
|
|
* MI async record =thread-selected now includes the frame field. For example:
|
|
|
|
|
|
|
|
|
|
=thread-selected,id="3",frame={level="0",addr="0x00000000004007c0"}
|
|
|
|
|
|
2016-06-17 15:25:08 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Andes NDS32 nds32*-*-elf
|
|
|
|
|
|
2016-02-10 11:28:01 +08:00
|
|
|
*** Changes in GDB 7.11
|
2015-07-07 04:02:47 +08:00
|
|
|
|
2015-04-29 23:53:43 +08:00
|
|
|
* GDB now supports debugging kernel-based threads on FreeBSD.
|
|
|
|
|
|
Per-inferior/Inferior-qualified thread IDs
This commit changes GDB to track thread numbers per-inferior. Then,
if you're debugging multiple inferiors, GDB displays
"inferior-num.thread-num" instead of just "thread-num" whenever it
needs to display a thread:
(gdb) info inferiors
Num Description Executable
1 process 6022 /home/pedro/gdb/tests/threads
* 2 process 6037 /home/pedro/gdb/tests/threads
(gdb) info threads
Id Target Id Frame
1.1 Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
1.2 Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
1.3 Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
2.1 Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
2.2 Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
* 2.3 Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)
(gdb)
...
(gdb) thread 1.1
[Switching to thread 1.1 (Thread 0x7ffff7fc2740 (LWP 8155))]
(gdb)
...
etc.
You can still use "thread NUM", in which case GDB infers you're
referring to thread NUM of the current inferior.
The $_thread convenience var and Python's InferiorThread.num attribute
are remapped to the new per-inferior thread number. It's a backward
compatibility break, but since it only matters when debugging multiple
inferiors, I think it's worth doing.
Because MI thread IDs need to be a single integer, we keep giving
threads a global identifier, _in addition_ to the per-inferior number,
and make MI always refer to the global thread IDs. IOW, nothing
changes from a MI frontend's perspective.
Similarly, since Python's Breakpoint.thread and Guile's
breakpoint-thread/set-breakpoint-thread breakpoint methods need to
work with integers, those are adjusted to work with global thread IDs
too. Follow up patches will provide convenient means to access
threads' global IDs.
To avoid potencially confusing users (which also avoids updating much
of the testsuite), if there's only one inferior and its ID is "1",
IOW, the user hasn't done anything multi-process/inferior related,
then the "INF." part of thread IDs is not shown. E.g,.:
(gdb) info inferiors
Num Description Executable
* 1 process 15275 /home/pedro/gdb/tests/threads
(gdb) info threads
Id Target Id Frame
* 1 Thread 0x7ffff7fc1740 (LWP 15275) "threads" main () at threads.c:40
(gdb) add-inferior
Added inferior 2
(gdb) info threads
Id Target Id Frame
* 1.1 Thread 0x7ffff7fc1740 (LWP 15275) "threads" main () at threads.c:40
(gdb)
No regressions on x86_64 Fedora 20.
gdb/ChangeLog:
2016-01-13 Pedro Alves <palves@redhat.com>
* NEWS: Mention that thread IDs are now per inferior and global
thread IDs.
* Makefile.in (SFILES): Add tid-parse.c.
(COMMON_OBS): Add tid-parse.o.
(HFILES_NO_SRCDIR): Add tid-parse.h.
* ada-tasks.c: Adjust to use ptid_to_global_thread_id.
* breakpoint.c (insert_breakpoint_locations)
(remove_threaded_breakpoints, bpstat_check_breakpoint_conditions)
(print_one_breakpoint_location, set_longjmp_breakpoint)
(check_longjmp_breakpoint_for_call_dummy)
(set_momentary_breakpoint): Adjust to use global IDs.
(find_condition_and_thread, watch_command_1): Use parse_thread_id.
(until_break_command, longjmp_bkpt_dtor)
(breakpoint_re_set_thread, insert_single_step_breakpoint): Adjust
to use global IDs.
* dummy-frame.c (pop_dummy_frame_bpt): Adjust to use
ptid_to_global_thread_id.
* elfread.c (elf_gnu_ifunc_resolver_stop): Likewise.
* gdbthread.h (struct thread_info): Rename field 'num' to
'global_num. Add new fields 'per_inf_num' and 'inf'.
(thread_id_to_pid): Rename thread_id_to_pid to
global_thread_id_to_ptid.
(pid_to_thread_id): Rename to ...
(ptid_to_global_thread_id): ... this.
(valid_thread_id): Rename to ...
(valid_global_thread_id): ... this.
(find_thread_id): Rename to ...
(find_thread_global_id): ... this.
(ALL_THREADS, ALL_THREADS_BY_INFERIOR): Declare.
(print_thread_info): Add comment.
* tid-parse.h: New file.
* tid-parse.c: New file.
* infcmd.c (step_command_fsm_prepare)
(step_command_fsm_should_stop): Adjust to use the global thread
ID.
(until_next_command, until_next_command)
(finish_command_fsm_should_stop): Adjust to use the global thread
ID.
(attach_post_wait): Adjust to check the inferior number too.
* inferior.h (struct inferior) <highest_thread_num>: New field.
* infrun.c (handle_signal_stop)
(insert_exception_resume_breakpoint)
(insert_exception_resume_from_probe): Adjust to use the global
thread ID.
* record-btrace.c (record_btrace_open): Use global thread IDs.
* remote.c (process_initial_stop_replies): Also consider the
inferior number.
* target.c (target_pre_inferior): Clear the inferior's highest
thread num.
* thread.c (clear_thread_inferior_resources): Adjust to use the
global thread ID.
(new_thread): New inferior parameter. Adjust to use it. Set both
the thread's global ID and the thread's per-inferior ID.
(add_thread_silent): Adjust.
(find_thread_global_id): New.
(find_thread_id): Make static. Adjust to rename.
(valid_thread_id): Rename to ...
(valid_global_thread_id): ... this.
(pid_to_thread_id): Rename to ...
(ptid_to_global_thread_id): ... this.
(thread_id_to_pid): Rename to ...
(global_thread_id_to_ptid): ... this. Adjust.
(first_thread_of_process): Adjust.
(do_captured_list_thread_ids): Adjust to use global thread IDs.
(should_print_thread): New function.
(print_thread_info): Rename to ...
(print_thread_info_1): ... this, and add new show_global_ids
parameter. Handle it. Iterate over inferiors.
(print_thread_info): Reimplement as wrapper around
print_thread_info_1.
(show_inferior_qualified_tids): New function.
(print_thread_id): Use it.
(tp_array_compar): Compare inferior numbers too.
(thread_apply_command): Use tid_range_parser.
(do_captured_thread_select): Use parse_thread_id.
(thread_id_make_value): Adjust.
(_initialize_thread): Adjust "info threads" help string.
* varobj.c (struct varobj_root): Update comment.
(varobj_create): Adjust to use global thread IDs.
(value_of_root_1): Adjust to use global_thread_id_to_ptid.
* windows-tdep.c (display_tib): No longer accept an argument.
* cli/cli-utils.c (get_number_trailer): Make extern.
* cli/cli-utils.h (get_number_trailer): Declare.
(get_number_const): Adjust documentation.
* mi/mi-cmd-var.c (mi_cmd_var_update_iter): Adjust to use global
thread IDs.
* mi/mi-interp.c (mi_new_thread, mi_thread_exit)
(mi_on_normal_stop, mi_output_running_pid, mi_on_resume):
* mi/mi-main.c (mi_execute_command, mi_cmd_execute): Likewise.
* guile/scm-breakpoint.c (gdbscm_set_breakpoint_thread_x):
Likewise.
* python/py-breakpoint.c (bppy_set_thread): Likewise.
* python/py-finishbreakpoint.c (bpfinishpy_init): Likewise.
* python/py-infthread.c (thpy_get_num): Add comment and return the
per-inferior thread ID.
(thread_object_getset): Update comment of "num".
gdb/testsuite/ChangeLog:
2016-01-07 Pedro Alves <palves@redhat.com>
* gdb.base/break.exp: Adjust to output changes.
* gdb.base/hbreak2.exp: Likewise.
* gdb.base/sepdebug.exp: Likewise.
* gdb.base/watch_thread_num.exp: Likewise.
* gdb.linespec/keywords.exp: Likewise.
* gdb.multi/info-threads.exp: Likewise.
* gdb.threads/thread-find.exp: Likewise.
* gdb.multi/tids.c: New file.
* gdb.multi/tids.exp: New file.
gdb/doc/ChangeLog:
2016-01-07 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Threads): Document per-inferior thread IDs,
qualified thread IDs, global thread IDs and thread ID lists.
(Set Watchpoints, Thread-Specific Breakpoints): Adjust to refer to
thread IDs.
(Convenience Vars): Document the $_thread convenience variable.
(Ada Tasks): Adjust to refer to thread IDs.
(GDB/MI Async Records, GDB/MI Thread Commands, GDB/MI Ada Tasking
Commands, GDB/MI Variable Objects): Update to mention global
thread IDs.
* guile.texi (Breakpoints In Guile)
<breakpoint-thread/set-breakpoint-thread breakpoint>: Mention
global thread IDs instead of thread IDs.
* python.texi (Threads In Python): Adjust documentation of
InferiorThread.num.
(Breakpoint.thread): Mention global thread IDs instead of thread
IDs.
2016-01-13 18:56:07 +08:00
|
|
|
* Per-inferior thread numbers
|
|
|
|
|
|
|
|
|
|
Thread numbers are now per inferior instead of global. If you're
|
|
|
|
|
debugging multiple inferiors, GDB displays thread IDs using a
|
|
|
|
|
qualified INF_NUM.THR_NUM form. For example:
|
|
|
|
|
|
|
|
|
|
(gdb) info threads
|
|
|
|
|
Id Target Id Frame
|
|
|
|
|
1.1 Thread 0x7ffff7fc2740 (LWP 8155) (running)
|
|
|
|
|
1.2 Thread 0x7ffff7fc1700 (LWP 8168) (running)
|
|
|
|
|
* 2.1 Thread 0x7ffff7fc2740 (LWP 8157) (running)
|
|
|
|
|
2.2 Thread 0x7ffff7fc1700 (LWP 8190) (running)
|
|
|
|
|
|
|
|
|
|
As consequence, thread numbers as visible in the $_thread
|
|
|
|
|
convenience variable and in Python's InferiorThread.num attribute
|
|
|
|
|
are no longer unique between inferiors.
|
|
|
|
|
|
|
|
|
|
GDB now maintains a second thread ID per thread, referred to as the
|
|
|
|
|
global thread ID, which is the new equivalent of thread numbers in
|
2016-01-13 18:56:10 +08:00
|
|
|
previous releases. See also $_gthread below.
|
Per-inferior/Inferior-qualified thread IDs
This commit changes GDB to track thread numbers per-inferior. Then,
if you're debugging multiple inferiors, GDB displays
"inferior-num.thread-num" instead of just "thread-num" whenever it
needs to display a thread:
(gdb) info inferiors
Num Description Executable
1 process 6022 /home/pedro/gdb/tests/threads
* 2 process 6037 /home/pedro/gdb/tests/threads
(gdb) info threads
Id Target Id Frame
1.1 Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
1.2 Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
1.3 Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
2.1 Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
2.2 Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
* 2.3 Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)
(gdb)
...
(gdb) thread 1.1
[Switching to thread 1.1 (Thread 0x7ffff7fc2740 (LWP 8155))]
(gdb)
...
etc.
You can still use "thread NUM", in which case GDB infers you're
referring to thread NUM of the current inferior.
The $_thread convenience var and Python's InferiorThread.num attribute
are remapped to the new per-inferior thread number. It's a backward
compatibility break, but since it only matters when debugging multiple
inferiors, I think it's worth doing.
Because MI thread IDs need to be a single integer, we keep giving
threads a global identifier, _in addition_ to the per-inferior number,
and make MI always refer to the global thread IDs. IOW, nothing
changes from a MI frontend's perspective.
Similarly, since Python's Breakpoint.thread and Guile's
breakpoint-thread/set-breakpoint-thread breakpoint methods need to
work with integers, those are adjusted to work with global thread IDs
too. Follow up patches will provide convenient means to access
threads' global IDs.
To avoid potencially confusing users (which also avoids updating much
of the testsuite), if there's only one inferior and its ID is "1",
IOW, the user hasn't done anything multi-process/inferior related,
then the "INF." part of thread IDs is not shown. E.g,.:
(gdb) info inferiors
Num Description Executable
* 1 process 15275 /home/pedro/gdb/tests/threads
(gdb) info threads
Id Target Id Frame
* 1 Thread 0x7ffff7fc1740 (LWP 15275) "threads" main () at threads.c:40
(gdb) add-inferior
Added inferior 2
(gdb) info threads
Id Target Id Frame
* 1.1 Thread 0x7ffff7fc1740 (LWP 15275) "threads" main () at threads.c:40
(gdb)
No regressions on x86_64 Fedora 20.
gdb/ChangeLog:
2016-01-13 Pedro Alves <palves@redhat.com>
* NEWS: Mention that thread IDs are now per inferior and global
thread IDs.
* Makefile.in (SFILES): Add tid-parse.c.
(COMMON_OBS): Add tid-parse.o.
(HFILES_NO_SRCDIR): Add tid-parse.h.
* ada-tasks.c: Adjust to use ptid_to_global_thread_id.
* breakpoint.c (insert_breakpoint_locations)
(remove_threaded_breakpoints, bpstat_check_breakpoint_conditions)
(print_one_breakpoint_location, set_longjmp_breakpoint)
(check_longjmp_breakpoint_for_call_dummy)
(set_momentary_breakpoint): Adjust to use global IDs.
(find_condition_and_thread, watch_command_1): Use parse_thread_id.
(until_break_command, longjmp_bkpt_dtor)
(breakpoint_re_set_thread, insert_single_step_breakpoint): Adjust
to use global IDs.
* dummy-frame.c (pop_dummy_frame_bpt): Adjust to use
ptid_to_global_thread_id.
* elfread.c (elf_gnu_ifunc_resolver_stop): Likewise.
* gdbthread.h (struct thread_info): Rename field 'num' to
'global_num. Add new fields 'per_inf_num' and 'inf'.
(thread_id_to_pid): Rename thread_id_to_pid to
global_thread_id_to_ptid.
(pid_to_thread_id): Rename to ...
(ptid_to_global_thread_id): ... this.
(valid_thread_id): Rename to ...
(valid_global_thread_id): ... this.
(find_thread_id): Rename to ...
(find_thread_global_id): ... this.
(ALL_THREADS, ALL_THREADS_BY_INFERIOR): Declare.
(print_thread_info): Add comment.
* tid-parse.h: New file.
* tid-parse.c: New file.
* infcmd.c (step_command_fsm_prepare)
(step_command_fsm_should_stop): Adjust to use the global thread
ID.
(until_next_command, until_next_command)
(finish_command_fsm_should_stop): Adjust to use the global thread
ID.
(attach_post_wait): Adjust to check the inferior number too.
* inferior.h (struct inferior) <highest_thread_num>: New field.
* infrun.c (handle_signal_stop)
(insert_exception_resume_breakpoint)
(insert_exception_resume_from_probe): Adjust to use the global
thread ID.
* record-btrace.c (record_btrace_open): Use global thread IDs.
* remote.c (process_initial_stop_replies): Also consider the
inferior number.
* target.c (target_pre_inferior): Clear the inferior's highest
thread num.
* thread.c (clear_thread_inferior_resources): Adjust to use the
global thread ID.
(new_thread): New inferior parameter. Adjust to use it. Set both
the thread's global ID and the thread's per-inferior ID.
(add_thread_silent): Adjust.
(find_thread_global_id): New.
(find_thread_id): Make static. Adjust to rename.
(valid_thread_id): Rename to ...
(valid_global_thread_id): ... this.
(pid_to_thread_id): Rename to ...
(ptid_to_global_thread_id): ... this.
(thread_id_to_pid): Rename to ...
(global_thread_id_to_ptid): ... this. Adjust.
(first_thread_of_process): Adjust.
(do_captured_list_thread_ids): Adjust to use global thread IDs.
(should_print_thread): New function.
(print_thread_info): Rename to ...
(print_thread_info_1): ... this, and add new show_global_ids
parameter. Handle it. Iterate over inferiors.
(print_thread_info): Reimplement as wrapper around
print_thread_info_1.
(show_inferior_qualified_tids): New function.
(print_thread_id): Use it.
(tp_array_compar): Compare inferior numbers too.
(thread_apply_command): Use tid_range_parser.
(do_captured_thread_select): Use parse_thread_id.
(thread_id_make_value): Adjust.
(_initialize_thread): Adjust "info threads" help string.
* varobj.c (struct varobj_root): Update comment.
(varobj_create): Adjust to use global thread IDs.
(value_of_root_1): Adjust to use global_thread_id_to_ptid.
* windows-tdep.c (display_tib): No longer accept an argument.
* cli/cli-utils.c (get_number_trailer): Make extern.
* cli/cli-utils.h (get_number_trailer): Declare.
(get_number_const): Adjust documentation.
* mi/mi-cmd-var.c (mi_cmd_var_update_iter): Adjust to use global
thread IDs.
* mi/mi-interp.c (mi_new_thread, mi_thread_exit)
(mi_on_normal_stop, mi_output_running_pid, mi_on_resume):
* mi/mi-main.c (mi_execute_command, mi_cmd_execute): Likewise.
* guile/scm-breakpoint.c (gdbscm_set_breakpoint_thread_x):
Likewise.
* python/py-breakpoint.c (bppy_set_thread): Likewise.
* python/py-finishbreakpoint.c (bpfinishpy_init): Likewise.
* python/py-infthread.c (thpy_get_num): Add comment and return the
per-inferior thread ID.
(thread_object_getset): Update comment of "num".
gdb/testsuite/ChangeLog:
2016-01-07 Pedro Alves <palves@redhat.com>
* gdb.base/break.exp: Adjust to output changes.
* gdb.base/hbreak2.exp: Likewise.
* gdb.base/sepdebug.exp: Likewise.
* gdb.base/watch_thread_num.exp: Likewise.
* gdb.linespec/keywords.exp: Likewise.
* gdb.multi/info-threads.exp: Likewise.
* gdb.threads/thread-find.exp: Likewise.
* gdb.multi/tids.c: New file.
* gdb.multi/tids.exp: New file.
gdb/doc/ChangeLog:
2016-01-07 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Threads): Document per-inferior thread IDs,
qualified thread IDs, global thread IDs and thread ID lists.
(Set Watchpoints, Thread-Specific Breakpoints): Adjust to refer to
thread IDs.
(Convenience Vars): Document the $_thread convenience variable.
(Ada Tasks): Adjust to refer to thread IDs.
(GDB/MI Async Records, GDB/MI Thread Commands, GDB/MI Ada Tasking
Commands, GDB/MI Variable Objects): Update to mention global
thread IDs.
* guile.texi (Breakpoints In Guile)
<breakpoint-thread/set-breakpoint-thread breakpoint>: Mention
global thread IDs instead of thread IDs.
* python.texi (Threads In Python): Adjust documentation of
InferiorThread.num.
(Breakpoint.thread): Mention global thread IDs instead of thread
IDs.
2016-01-13 18:56:07 +08:00
|
|
|
|
|
|
|
|
For backwards compatibility, MI's thread IDs always refer to global
|
|
|
|
|
IDs.
|
|
|
|
|
|
|
|
|
|
* Commands that accept thread IDs now accept the qualified
|
|
|
|
|
INF_NUM.THR_NUM form as well. For example:
|
|
|
|
|
|
|
|
|
|
(gdb) thread 2.1
|
|
|
|
|
[Switching to thread 2.1 (Thread 0x7ffff7fc2740 (LWP 8157))] (running)
|
|
|
|
|
(gdb)
|
|
|
|
|
|
2016-01-16 05:46:23 +08:00
|
|
|
* In commands that accept a list of thread IDs, you can now refer to
|
|
|
|
|
all threads of an inferior using a star wildcard. GDB accepts
|
|
|
|
|
"INF_NUM.*", to refer to all threads of inferior INF_NUM, and "*" to
|
|
|
|
|
refer to all threads of the current inferior. For example, "info
|
|
|
|
|
threads 2.*".
|
|
|
|
|
|
2016-01-13 18:56:09 +08:00
|
|
|
* You can use "info threads -gid" to display the global thread ID of
|
|
|
|
|
all threads.
|
|
|
|
|
|
2016-01-13 18:56:10 +08:00
|
|
|
* The new convenience variable $_gthread holds the global number of
|
|
|
|
|
the current thread.
|
|
|
|
|
|
2016-01-13 18:56:05 +08:00
|
|
|
* The new convenience variable $_inferior holds the number of the
|
|
|
|
|
current inferior.
|
|
|
|
|
|
Fix PR threads/19422 - show which thread caused stop
This commit changes GDB like this:
- Program received signal SIGINT, Interrupt.
+ Thread 1 "main" received signal SIGINT, Interrupt.
- Breakpoint 1 at 0x40087a: file threads.c, line 87.
+ Thread 3 "bar" hit Breakpoint 1 at 0x40087a: file threads.c, line 87.
... once the program goes multi-threaded. Until GDB sees a second
thread spawn, the output is still the same as before, per the
discussion back in 2012:
https://www.sourceware.org/ml/gdb/2012-11/msg00010.html
This helps non-stop mode, where you can't easily tell which thread hit
a breakpoint or received a signal:
(gdb) info threads
Id Target Id Frame
* 1 Thread 0x7ffff7fc1740 (LWP 19362) "main" (running)
2 Thread 0x7ffff7fc0700 (LWP 19366) "foo" (running)
3 Thread 0x7ffff77bf700 (LWP 19367) "bar" (running)
(gdb)
Program received signal SIGUSR1, User defined signal 1.
0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
92 lll_wait_tid (pd->tid);
(gdb) b threads.c:87
Breakpoint 1 at 0x40087a: file threads.c, line 87.
(gdb)
Breakpoint 1, thread_function1 (arg=0x1) at threads.c:87
87 usleep (1); /* Loop increment. */
The best the user can do is run "info threads" and try to figure
things out.
It actually also affects all-stop mode, in case of "handle SIG print
nostop":
...
Program received signal SIGUSR1, User defined signal 1.
Program received signal SIGUSR1, User defined signal 1.
Program received signal SIGUSR1, User defined signal 1.
Program received signal SIGUSR1, User defined signal 1.
...
The above doesn't give any clue that these were different threads
getting the SIGUSR1 signal.
I initially thought of lowercasing "breakpoint" in
"Thread 3 hit Breakpoint 1"
but then after trying it I realized that leaving "Breakpoint"
uppercase helps the eye quickly find the relevant information. It's
also easier to implement not showing anything about threads until the
program goes multi-threaded this way.
Here's a larger example session in non-stop mode:
(gdb) c -a&
Continuing.
(gdb) interrupt -a
(gdb)
Thread 1 "main" stopped.
0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
92 lll_wait_tid (pd->tid);
Thread 2 "foo" stopped.
0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
Thread 3 "bar" stopped.
0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
b threads.c:87
Breakpoint 4 at 0x40087a: file threads.c, line 87.
(gdb) b threads.c:67
Breakpoint 5 at 0x400811: file threads.c, line 67.
(gdb) c -a&
Continuing.
(gdb)
Thread 3 "bar" hit Breakpoint 4, thread_function1 (arg=0x1) at threads.c:87
87 usleep (1); /* Loop increment. */
Thread 2 "foo" hit Breakpoint 5, thread_function0 (arg=0x0) at threads.c:68
68 (*myp) ++;
info threads
Id Target Id Frame
* 1 Thread 0x7ffff7fc1740 (LWP 31957) "main" (running)
2 Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
3 Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
(gdb) shell kill -SIGINT 31957
(gdb)
Thread 1 "main" received signal SIGINT, Interrupt.
0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
92 lll_wait_tid (pd->tid);
info threads
Id Target Id Frame
* 1 Thread 0x7ffff7fc1740 (LWP 31957) "main" 0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
2 Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
3 Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
(gdb) t 2
[Switching to thread 2, Thread 0x7ffff7fc0700 (LWP 31961)]
#0 thread_function0 (arg=0x0) at threads.c:68
68 (*myp) ++;
(gdb) catch syscall
Catchpoint 6 (any syscall)
(gdb) c&
Continuing.
(gdb)
Thread 2 "foo" hit Catchpoint 6 (call to syscall nanosleep), 0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
I'll work on documentation next if this looks agreeable.
This patch applies on top of the star wildcards thread IDs series:
https://sourceware.org/ml/gdb-patches/2016-01/msg00291.html
For convenience, I've pushed this to the
users/palves/show-which-thread-caused-stop branch.
gdb/doc/ChangeLog:
2016-01-18 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Threads): Mention that GDB displays the ID and name
of the thread that hit a breakpoint or received a signal.
gdb/ChangeLog:
2016-01-18 Pedro Alves <palves@redhat.com>
* NEWS: Mention that GDB now displays the ID and name of the
thread that hit a breakpoint or received a signal.
* break-catch-sig.c (signal_catchpoint_print_it): Use
maybe_print_thread_hit_breakpoint.
* break-catch-syscall.c (print_it_catch_syscall): Likewise.
* break-catch-throw.c (print_it_exception_catchpoint): Likewise.
* breakpoint.c (maybe_print_thread_hit_breakpoint): New function.
(print_it_catch_fork, print_it_catch_vfork, print_it_catch_solib)
(print_it_catch_exec, print_it_ranged_breakpoint)
(print_it_watchpoint, print_it_masked_watchpoint, bkpt_print_it):
Use maybe_print_thread_hit_breakpoint.
* breakpoint.h (maybe_print_thread_hit_breakpoint): Declare.
* gdbthread.h (show_thread_that_caused_stop): Declare.
* infrun.c (print_signal_received_reason): Print which thread
received signal.
* thread.c (show_thread_that_caused_stop): New function.
gdb/testsuite/ChangeLog:
2016-01-18 Pedro Alves <palves@redhat.com>
* gdb.base/async-shell.exp: Adjust expected output.
* gdb.base/dprintf-non-stop.exp: Adjust expected output.
* gdb.base/siginfo-thread.exp: Adjust expected output.
* gdb.base/watchpoint-hw-hit-once.exp: Adjust expected output.
* gdb.java/jnpe.exp: Adjust expected output.
* gdb.threads/clone-new-thread-event.exp: Adjust expected output.
* gdb.threads/continue-pending-status.exp: Adjust expected output.
* gdb.threads/leader-exit.exp: Adjust expected output.
* gdb.threads/manythreads.exp: Adjust expected output.
* gdb.threads/pthreads.exp: Adjust expected output.
* gdb.threads/schedlock.exp: Adjust expected output.
* gdb.threads/siginfo-threads.exp: Adjust expected output.
* gdb.threads/signal-command-multiple-signals-pending.exp: Adjust
expected output.
* gdb.threads/signal-delivered-right-thread.exp: Adjust expected
output.
* gdb.threads/sigthread.exp: Adjust expected output.
* gdb.threads/watchpoint-fork.exp: Adjust expected output.
2016-01-18 23:15:18 +08:00
|
|
|
* GDB now displays the ID and name of the thread that hit a breakpoint
|
|
|
|
|
or received a signal, if your program is multi-threaded. For
|
|
|
|
|
example:
|
|
|
|
|
|
|
|
|
|
Thread 3 "bar" hit Breakpoint 1 at 0x40087a: file program.c, line 20.
|
|
|
|
|
Thread 1 "main" received signal SIGINT, Interrupt.
|
|
|
|
|
|
2015-08-26 17:33:07 +08:00
|
|
|
* Record btrace now supports non-stop mode.
|
|
|
|
|
|
2015-07-09 23:35:11 +08:00
|
|
|
* Support for tracepoints on aarch64-linux was added in GDBserver.
|
|
|
|
|
|
2014-03-19 20:49:58 +08:00
|
|
|
* The 'record instruction-history' command now indicates speculative execution
|
2016-01-12 23:03:11 +08:00
|
|
|
when using the Intel Processor Trace recording format.
|
2014-03-19 20:49:58 +08:00
|
|
|
|
2015-08-12 08:09:36 +08:00
|
|
|
* GDB now allows users to specify explicit locations, bypassing
|
|
|
|
|
the linespec parser. This feature is also available to GDB/MI
|
|
|
|
|
clients.
|
|
|
|
|
|
2015-09-04 22:26:21 +08:00
|
|
|
* Multi-architecture debugging is supported on AArch64 GNU/Linux.
|
|
|
|
|
GDB now is able to debug both AArch64 applications and ARM applications
|
|
|
|
|
at the same time.
|
|
|
|
|
|
2015-09-21 22:01:05 +08:00
|
|
|
* Support for fast tracepoints on aarch64-linux was added in GDBserver,
|
|
|
|
|
including JIT compiling fast tracepoint's conditional expression bytecode
|
|
|
|
|
into native code.
|
|
|
|
|
|
2015-10-12 18:28:39 +08:00
|
|
|
* GDB now supports displaced stepping on AArch64 GNU/Linux.
|
|
|
|
|
|
2015-11-25 02:11:23 +08:00
|
|
|
* "info threads", "info inferiors", "info display", "info checkpoints"
|
|
|
|
|
and "maint info program-spaces" now list the corresponding items in
|
|
|
|
|
ascending ID order, for consistency with all other "info" commands.
|
|
|
|
|
|
2015-09-03 23:34:58 +08:00
|
|
|
* In Ada, the overloads selection menu has been enhanced to display the
|
|
|
|
|
parameter types and the return types for the matching overloaded subprograms.
|
|
|
|
|
|
Implement all-stop on top of a target running non-stop mode
This finally implements user-visible all-stop mode running with the
target_ops backend always in non-stop mode. This is a stepping stone
towards finer-grained control of threads, being able to do interesting
things like thread groups, associating groups with breakpoints, etc.
From the user's perspective, all-stop mode is really just a special
case of being able to stop and resume specific sets of threads, so it
makes sense to do this step first.
With this, even in all-stop, the target is no longer in charge of
stopping all threads before reporting an event to the core -- the core
takes care of it when it sees fit. For example, when "next"- or
"step"-ing, we can avoid stopping and resuming all threads at each
internal single-step, and instead only stop all threads when we're
about to present the stop to the user.
The implementation is almost straight forward, as the heavy lifting
has been done already in previous patches. Basically, we replace
checks for "set non-stop on/off" (the non_stop global), with calls to
a new target_is_non_stop_p function. In a few places, if "set
non-stop off", we stop all threads explicitly, and in a few other
places we resume all threads explicitly, making use of existing
methods that were added for teaching non-stop to step over breakpoints
without displaced stepping.
This adds a new "maint set target-non-stop on/off/auto" knob that
allows both disabling the feature if we find problems, and
force-enable it for development (useful when teaching a target about
this. The default is "auto", which means the feature is enabled if a
new target method says it should be enabled. The patch implements the
method in linux-nat.c, just for illustration, because it still returns
false. We'll need a few follow up fixes before turning it on by
default. This is a separate target method from indicating regular
non-stop support, because e.g., while e.g., native linux-nat.c is
close to regression free with all-stop-non-stop (with following
patches will fixing the remaining regressions), remote.c+gdbserver
will still need more fixing, even though it supports "set non-stop
on".
Tested on x86_64 Fedora 20, native, with and without "set displaced
off", and with and without "maint set target-non-stop on"; and also
against gdbserver.
gdb/ChangeLog:
2015-08-07 Pedro Alves <palves@redhat.com>
* NEWS: Mention "maint set/show target-non-stop".
* breakpoint.c (update_global_location_list): Check
target_is_non_stop_p instead of non_stop.
* infcmd.c (attach_command_post_wait, attach_command): Likewise.
* infrun.c (show_can_use_displaced_stepping)
(can_use_displaced_stepping_p, start_step_over_inferior):
Likewise.
(internal_resume_ptid): New function.
(resume): Use it.
(proceed): Check target_is_non_stop_p instead of non_stop. If in
all-stop mode but the target is always in non-stop mode, start all
the other threads that are implicitly resumed too.
(for_each_just_stopped_thread, fetch_inferior_event)
(adjust_pc_after_break, stop_all_threads): Check
target_is_non_stop_p instead of non_stop.
(handle_inferior_event): Likewise. Handle detach-fork in all-stop
with the target always in non-stop mode.
(handle_signal_stop) <random signal>: Check target_is_non_stop_p
instead of non_stop.
(switch_back_to_stepped_thread): Check target_is_non_stop_p
instead of non_stop.
(keep_going_stepped_thread): Use internal_resume_ptid.
(stop_waiting): If in all-stop mode, and the target is in non-stop
mode, stop all threads.
(keep_going_pass): Likewise, when starting a new in-line step-over
sequence.
* linux-nat.c (get_pending_status, select_event_lwp)
(linux_nat_filter_event, linux_nat_wait_1, linux_nat_wait): Check
target_is_non_stop_p instead of non_stop.
(linux_nat_always_non_stop_p): New function.
(linux_nat_stop): Check target_is_non_stop_p instead of non_stop.
(linux_nat_add_target): Install linux_nat_always_non_stop_p.
* target-delegates.c: Regenerate.
* target.c (target_is_non_stop_p): New function.
(target_non_stop_enabled, target_non_stop_enabled_1): New globals.
(maint_set_target_non_stop_command)
(maint_show_target_non_stop_command): New functions.
(_initilize_target): Install "maint set/show target-non-stop"
commands.
* target.h (struct target_ops) <to_always_non_stop_p>: New field.
(target_non_stop_enabled): New declaration.
(target_is_non_stop_p): New declaration.
gdb/doc/ChangeLog:
2015-08-07 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Maintenance Commands): Document "maint set/show
target-non-stop".
2015-08-08 00:24:01 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
maint set target-non-stop (on|off|auto)
|
|
|
|
|
maint show target-non-stop
|
|
|
|
|
Control whether GDB targets always operate in non-stop mode even if
|
|
|
|
|
"set non-stop" is "off". The default is "auto", meaning non-stop
|
|
|
|
|
mode is enabled if supported by the target.
|
|
|
|
|
|
2015-04-13 23:31:21 +08:00
|
|
|
maint set bfd-sharing
|
|
|
|
|
maint show bfd-sharing
|
|
|
|
|
Control the reuse of bfd objects.
|
|
|
|
|
|
2015-04-13 23:56:23 +08:00
|
|
|
set debug bfd-cache
|
|
|
|
|
show debug bfd-cache
|
|
|
|
|
Control display of debugging info regarding bfd caching.
|
|
|
|
|
|
2015-04-29 23:53:43 +08:00
|
|
|
set debug fbsd-lwp
|
|
|
|
|
show debug fbsd-lwp
|
|
|
|
|
Control display of debugging info regarding FreeBSD threads.
|
|
|
|
|
|
2015-08-25 02:58:31 +08:00
|
|
|
set remote multiprocess-extensions-packet
|
|
|
|
|
show remote multiprocess-extensions-packet
|
|
|
|
|
Set/show the use of the remote protocol multiprocess extensions.
|
|
|
|
|
|
Remote thread create/exit events
When testing with "maint set target-non-stop on", a few
threading-related tests expose an issue that requires new RSP packets.
Say there are 3 threads running, 1-3. If GDB tries to stop thread 1,
2 and 3, and then waits for their stops, but meanwhile say, thread 2
exits, GDB hangs forever waiting for a stop for thread 2 that won't
ever happen.
This patch fixes the issue by adding support for thread exit events to
the protocol. However, we don't want these always enabled, as they're
useless most of the time, and would slow down remote debugging. So I
made it so that GDB can enable/disable them, and then made gdb do that
around the cases that need it, which currently is only
infrun.c:stop_all_threads.
In turn, if we have thread exit events, then the extra "thread x
exited" traffic slows down attach-many-short-lived-threads.exp enough
that gdb has trouble keeping up with new threads that are spawned
while gdb tries to stop existing ones. To fix that I added support
for the counterpart thread created events too. Enabling those when we
try to stop threads ensures that new threads never get a chance to
themselves start new threads, killing the race.
gdb/doc/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Remote Configuration): List "set/show remote
thread-events" command in configuration table.
(Stop Reply Packets): Document "T05 create" stop
reason and 'w' stop reply.
(General Query Packets): Document QThreadEvents packet. Document
QThreadEvents qSupported feature.
gdb/gdbserver/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* linux-low.c (handle_extended_wait): Assert that the LWP's
waitstatus is TARGET_WAITKIND_IGNORE. If GDB wants to hear about
thread create events, leave the new child's status pending.
(linux_low_filter_event): If GDB wants to hear about thread exit
events, leave the LWP marked dead and don't delete it.
(linux_wait_for_event_filtered): Don't check for thread exit.
(filter_exit_event): New function.
(linux_wait_1): Use it, when returning an exit event.
(linux_resume_one_lwp_throw): Assert that the LWP's
waitstatus is TARGET_WAITKIND_IGNORE.
* remote-utils.c (prepare_resume_reply): Handle
TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
* server.c (report_thread_events): New global.
(handle_general_set): Handle QThreadEvents.
(handle_query) <qSupported>: Handle and report QThreadEvents+;
(handle_target_event): Handle TARGET_WAITKIND_THREAD_CREATED and
TARGET_WAITKIND_THREAD_EXITED.
* server.h (report_thread_events): Declare.
gdb/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* NEWS (New commands): Mention "set/show remote thread-events"
commands.
(New remote packets): Mention thread created/exited stop reasons
and QThreadEvents packet.
* infrun.c (disable_thread_events): New function.
(stop_all_threads): Disable/enable thread create/exit events.
Handle TARGET_WAITKIND_THREAD_EXITED.
(handle_inferior_event_1): Handle TARGET_WAITKIND_THREAD_CREATED
and TARGET_WAITKIND_THREAD_EXITED.
* remote.c (remove_child_of_pending_fork): Also remove threads of
threads that have TARGET_WAITKIND_THREAD_EXITED events.
(remote_parse_stop_reply): Handle "create" magic register. Handle
'w' stop reply.
(initialize_remote): Install remote_thread_events as
to_thread_events target hook.
(remote_thread_events): New function.
* target-delegates.c: Regenerate.
* target.c (target_thread_events): New function.
* target.h (struct target_ops) <to_thread_events>: New field.
(target_thread_events): Declare.
* target/waitstatus.c (target_waitstatus_to_string): Handle
TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
* target/waitstatus.h (enum target_waitkind)
<TARGET_WAITKIND_THREAD_CREATED, TARGET_WAITKIND_THREAD_EXITED):
New values.
2015-12-01 00:05:21 +08:00
|
|
|
set remote thread-events
|
|
|
|
|
show remote thread-events
|
|
|
|
|
Set/show the use of thread create/exit events.
|
|
|
|
|
|
2015-09-03 23:34:58 +08:00
|
|
|
set ada print-signatures on|off
|
|
|
|
|
show ada print-signatures"
|
|
|
|
|
Control whether parameter types and return types are displayed in overloads
|
2020-06-05 18:24:20 +08:00
|
|
|
selection menus. It is activated (@code{on}) by default.
|
2015-09-03 23:34:58 +08:00
|
|
|
|
2015-12-12 01:37:49 +08:00
|
|
|
set max-value-size
|
|
|
|
|
show max-value-size
|
|
|
|
|
Controls the maximum size of memory, in bytes, that GDB will
|
|
|
|
|
allocate for value contents. Prevents incorrect programs from
|
|
|
|
|
causing GDB to allocate overly large buffers. Default is 64k.
|
|
|
|
|
|
2015-08-15 12:45:54 +08:00
|
|
|
* The "disassemble" command accepts a new modifier: /s.
|
|
|
|
|
It prints mixed source+disassembly like /m with two differences:
|
|
|
|
|
- disassembled instructions are now printed in program order, and
|
|
|
|
|
- and source for all relevant files is now printed.
|
|
|
|
|
The "/m" option is now considered deprecated: its "source-centric"
|
|
|
|
|
output hasn't proved useful in practice.
|
|
|
|
|
|
2015-09-11 16:09:54 +08:00
|
|
|
* The "record instruction-history" command accepts a new modifier: /s.
|
|
|
|
|
It behaves exactly like /m and prints mixed source+disassembly.
|
|
|
|
|
|
2015-09-07 21:41:00 +08:00
|
|
|
* The "set scheduler-locking" command supports a new mode "replay".
|
|
|
|
|
It behaves like "off" in record mode and like "on" in replay mode.
|
|
|
|
|
|
Delete the remaining ROM monitor targets
Ref: https://sourceware.org/ml/gdb/2015-07/msg00011.html
All of these targets use gdb/monitor.c, which has bit rotted
years ago (I'd guess around ~6), and nobody seems to
have noticed:
| target | source |
|----------------+----------------------|
| target dbug | gdb/dbug-rom.c |
| target picobug | gdb/microblaze-rom.c |
| target dink32 | gdb/dink32-rom.c |
| target m32r | gdb/m32r-rom.c |
| target mon2000 | gdb/m32r-rom.c |
| target ppcbug | gdb/ppcbug-rom.c |
This deletes them, along with finally removing monitor.c.
A manual update will be done separately.
gdb/ChangeLog:
2015-08-24 Pedro Alves <palves@redhat.com>
* NEWS: Mention removed support for the various ROM monitors.
* Makefile.in (ALL_TARGET_OBS): Remove dbug-rom.o, dink32-rom.o,
ppcbug-rom.o, m32r-rom.o, dsrec.o and monitor.o from gdb_target_obs.
* configure.tgt (h8300-*-*): Remove monitor.o and m32r-rom.o from
gdb_target_obs.
(m68*-*-*): Remove monitor.o dbug-rom.o and dsrec.o from
gdb_target_obs.
(microblaze*-linux-*): Remove microblaze-rom.o, monitor.o and
dsrec.o from gdb_target_obs.
(microblaze*-*-*): Remove microblaze-rom.o, monitor.o and dsrec.o
from gdb_target_obs.
(powerpc-*-lynx*178): Remove monitor.o and dsrec.o from
gdb_target_obs.
(powerpc*-*-*): Remove monitor.o, dsrec.o, ppcbug-rom.o and
dink32-rom.o from gdb_target_obs.
(sh*-*-linux*): Remove monitor.o and dsrec.o from gdb_target_obs.
(sh*): Remove monitor.o and dsrec.o from gdb_target_obs.
* dbug-rom.c, dink32-rom.c, dsrec.c, m32r-rom.c, microblaze-rom.c,
monitor.c, monitor.h, ppcbug-rom.c, srec.h: Delete files.
2015-08-24 22:40:26 +08:00
|
|
|
* Support for various ROM monitors has been removed:
|
|
|
|
|
|
|
|
|
|
target dbug dBUG ROM monitor for Motorola ColdFire
|
|
|
|
|
target picobug Motorola picobug monitor
|
|
|
|
|
target dink32 DINK32 ROM monitor for PowerPC
|
|
|
|
|
target m32r Renesas M32R/D ROM monitor
|
|
|
|
|
target mon2000 mon2000 ROM monitor
|
|
|
|
|
target ppcbug PPCBUG ROM monitor for PowerPC
|
|
|
|
|
|
2015-08-27 21:30:00 +08:00
|
|
|
* Support for reading/writing memory and extracting values on architectures
|
2015-08-29 03:35:47 +08:00
|
|
|
whose memory is addressable in units of any integral multiple of 8 bits.
|
2015-08-27 21:30:00 +08:00
|
|
|
|
(Ada) New command to stop at start of exception handler.
When using gdb for debugging Ada source code, there are several catchpoint
types you can define in order to stop upon certain conditions. Let's
use this small example:
procedure Foo is
begin
begin
raise Constraint_Error;
exception
when Program_Error =>
null;
when Constraint_Error =>
null;
when others =>
null;
end;
end Foo;
One can stop when the exception is being raised by using the exception
catchpoint like below:
(gdb) catch exception
Catchpoint 1: all Ada exceptions
(gdb)
In that case, when running Foo, gdb will stop at the line where the exception
was raised:
begin
>>> raise Constraint_Error;
exception
This patch introduces new type of catchpoint, when the user wants to stop
at the location of the exception handling.
Imagine we want to stop on any exception handled by the program, we can do:
(gdb) catch handlers
Catchpoint 1: all Ada exceptions handlers
(gdb) r
Starting program: /tmp/foo
By doing so, when running Foo, gdb will stop here:
Catchpoint 1, exception at 0x000000000040255a in foo () at foo.adb:25
25 when Constraint_Error =>
(gdb)
It is also possible to stop when the Constraint_Error exception is being
handled in this program. With this patch, we can use:
(gdb) catch handlers Constraint_Error
Catchpoint 1: `Constraint_Error' Ada exception handlers
(gdb)
Like for other catchpoint, you can set a condition when adding a catchpoint
on exception handlers.
Here the handlers catchpoint checks Global_Var:
(gdb) catch handlers Constraint_Error if Global_Var /= 0
gdb/ChangeLog:
* ada-lang.h (ada_exception_catchpoint_kind) <ada_catch_handlers>:
Add field.
* ada-lang.c (struct exception_support_info) <catch_handlers_sym>:
Add field.
(default_exception_support_info) <catch_handlers_sym>: Add field.
(exception_support_info_fallback) <catch_handlers_sym>: Add field.
(ada_exception_name_addr_1): Add "catch handlers" handling.
(ada_exception_catchpoint_cond_string) <ex>: New parameter.
Update all callers.
(create_excep_cond_exprs) <ex>: Add parameter.
(re_set_exception): Update create_excep_cond_exprs call.
(print_it_exception, print_one_exception, print_mention_exception)
(print_recreate_exception): Add "catch handler" handling.
(allocate_location_catch_handlers, re_set_catch_handlers)
(check_status_catch_handlers, print_it_catch_handlers)
(print_one_catch_handlers, print_mention_catch_handlers)
(print_recreate_catch_handlers): New function.
(catch_handlers_breakpoint_ops): New variable.
(catch_ada_exception_command_split) <is_catch_handlers_cmd>:
Add parameter. Add "catch handler" handling.
(ada_exception_sym_name, ada_exception_breakpoint_ops):
Add "catch handler" handling.
(ada_exception_catchpoint_cond_string): Add "catch handler"
handling.
(create_ada_exception_catchpoint): Update create_excep_cond_exprs
call.
(catch_ada_handlers_command): New function.
(initialize_ada_catchpoint_ops): Initialize "catch handlers"
operations structure.
(_initialize_ada_language): Add "catch handlers" command entry.
* NEWS: Document "catch handlers" feature.
gdb/doc/ChangeLog:
* gdb.texinfo (Set Catchpoints): Add documentation for new
"catch handlers" action.
gdb/testsuite/ChangeLog:
* gdb.ada/excep_handle.exp: New testcase.
* gdb.ada/excep_handle/foo.adb: New file.
* gdb.ada/excep_handle/pck.ads: New file.
Tested on x86_64-linux.
2017-11-22 17:40:39 +08:00
|
|
|
catch handlers
|
|
|
|
|
Allows to break when an Ada exception is handled.
|
|
|
|
|
|
2015-09-12 02:06:03 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
exec stop reason
|
|
|
|
|
Indicates that an exec system call was executed.
|
|
|
|
|
|
|
|
|
|
exec-events feature in qSupported
|
|
|
|
|
The qSupported packet allows GDB to request support for exec
|
|
|
|
|
events using the new 'gdbfeature' exec-event, and the qSupported
|
|
|
|
|
response can contain the corresponding 'stubfeature'. Set and
|
|
|
|
|
show commands can be used to display whether these features are enabled.
|
|
|
|
|
|
2015-12-01 00:05:17 +08:00
|
|
|
vCtrlC
|
|
|
|
|
Equivalent to interrupting with the ^C character, but works in
|
|
|
|
|
non-stop mode.
|
|
|
|
|
|
Remote thread create/exit events
When testing with "maint set target-non-stop on", a few
threading-related tests expose an issue that requires new RSP packets.
Say there are 3 threads running, 1-3. If GDB tries to stop thread 1,
2 and 3, and then waits for their stops, but meanwhile say, thread 2
exits, GDB hangs forever waiting for a stop for thread 2 that won't
ever happen.
This patch fixes the issue by adding support for thread exit events to
the protocol. However, we don't want these always enabled, as they're
useless most of the time, and would slow down remote debugging. So I
made it so that GDB can enable/disable them, and then made gdb do that
around the cases that need it, which currently is only
infrun.c:stop_all_threads.
In turn, if we have thread exit events, then the extra "thread x
exited" traffic slows down attach-many-short-lived-threads.exp enough
that gdb has trouble keeping up with new threads that are spawned
while gdb tries to stop existing ones. To fix that I added support
for the counterpart thread created events too. Enabling those when we
try to stop threads ensures that new threads never get a chance to
themselves start new threads, killing the race.
gdb/doc/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Remote Configuration): List "set/show remote
thread-events" command in configuration table.
(Stop Reply Packets): Document "T05 create" stop
reason and 'w' stop reply.
(General Query Packets): Document QThreadEvents packet. Document
QThreadEvents qSupported feature.
gdb/gdbserver/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* linux-low.c (handle_extended_wait): Assert that the LWP's
waitstatus is TARGET_WAITKIND_IGNORE. If GDB wants to hear about
thread create events, leave the new child's status pending.
(linux_low_filter_event): If GDB wants to hear about thread exit
events, leave the LWP marked dead and don't delete it.
(linux_wait_for_event_filtered): Don't check for thread exit.
(filter_exit_event): New function.
(linux_wait_1): Use it, when returning an exit event.
(linux_resume_one_lwp_throw): Assert that the LWP's
waitstatus is TARGET_WAITKIND_IGNORE.
* remote-utils.c (prepare_resume_reply): Handle
TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
* server.c (report_thread_events): New global.
(handle_general_set): Handle QThreadEvents.
(handle_query) <qSupported>: Handle and report QThreadEvents+;
(handle_target_event): Handle TARGET_WAITKIND_THREAD_CREATED and
TARGET_WAITKIND_THREAD_EXITED.
* server.h (report_thread_events): Declare.
gdb/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* NEWS (New commands): Mention "set/show remote thread-events"
commands.
(New remote packets): Mention thread created/exited stop reasons
and QThreadEvents packet.
* infrun.c (disable_thread_events): New function.
(stop_all_threads): Disable/enable thread create/exit events.
Handle TARGET_WAITKIND_THREAD_EXITED.
(handle_inferior_event_1): Handle TARGET_WAITKIND_THREAD_CREATED
and TARGET_WAITKIND_THREAD_EXITED.
* remote.c (remove_child_of_pending_fork): Also remove threads of
threads that have TARGET_WAITKIND_THREAD_EXITED events.
(remote_parse_stop_reply): Handle "create" magic register. Handle
'w' stop reply.
(initialize_remote): Install remote_thread_events as
to_thread_events target hook.
(remote_thread_events): New function.
* target-delegates.c: Regenerate.
* target.c (target_thread_events): New function.
* target.h (struct target_ops) <to_thread_events>: New field.
(target_thread_events): Declare.
* target/waitstatus.c (target_waitstatus_to_string): Handle
TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
* target/waitstatus.h (enum target_waitkind)
<TARGET_WAITKIND_THREAD_CREATED, TARGET_WAITKIND_THREAD_EXITED):
New values.
2015-12-01 00:05:21 +08:00
|
|
|
thread created stop reason (T05 create:...)
|
|
|
|
|
Indicates that the thread was just created and is stopped at entry.
|
|
|
|
|
|
|
|
|
|
thread exit stop reply (w exitcode;tid)
|
|
|
|
|
Indicates that the thread has terminated.
|
|
|
|
|
|
|
|
|
|
QThreadEvents
|
|
|
|
|
Enables/disables thread create and exit event reporting. For
|
|
|
|
|
example, this is used in non-stop mode when GDB stops a set of
|
|
|
|
|
threads and synchronously waits for the their corresponding stop
|
|
|
|
|
replies. Without exit events, if one of the threads exits, GDB
|
|
|
|
|
would hang forever not knowing that it should no longer expect a
|
|
|
|
|
stop for that same thread.
|
|
|
|
|
|
2015-12-01 00:05:25 +08:00
|
|
|
N stop reply
|
|
|
|
|
Indicates that there are no resumed threads left in the target (all
|
|
|
|
|
threads are stopped). The remote stub reports support for this stop
|
|
|
|
|
reply to GDB's qSupported query.
|
|
|
|
|
|
2016-05-30 02:45:42 +08:00
|
|
|
QCatchSyscalls
|
|
|
|
|
Enables/disables catching syscalls from the inferior process.
|
|
|
|
|
The remote stub reports support for this packet to GDB's qSupported query.
|
2016-01-13 04:27:27 +08:00
|
|
|
|
|
|
|
|
syscall_entry stop reason
|
|
|
|
|
Indicates that a syscall was just called.
|
|
|
|
|
|
|
|
|
|
syscall_return stop reason
|
|
|
|
|
Indicates that a syscall just returned.
|
|
|
|
|
|
2015-09-12 02:06:03 +08:00
|
|
|
* Extended-remote exec events
|
|
|
|
|
|
|
|
|
|
** GDB now has support for exec events on extended-remote Linux targets.
|
|
|
|
|
For such targets with Linux kernels 2.5.46 and later, this enables
|
|
|
|
|
follow-exec-mode and exec catchpoints.
|
|
|
|
|
|
|
|
|
|
set remote exec-event-feature-packet
|
|
|
|
|
show remote exec-event-feature-packet
|
|
|
|
|
Set/show the use of the remote exec event feature.
|
|
|
|
|
|
2015-11-26 22:49:04 +08:00
|
|
|
* Thread names in remote protocol
|
|
|
|
|
|
|
|
|
|
The reply to qXfer:threads:read may now include a name attribute for each
|
|
|
|
|
thread.
|
|
|
|
|
|
2015-12-15 03:18:06 +08:00
|
|
|
* Target remote mode fork and exec events
|
|
|
|
|
|
|
|
|
|
** GDB now has support for fork and exec events on target remote mode
|
|
|
|
|
Linux targets. For such targets with Linux kernels 2.5.46 and later,
|
|
|
|
|
this enables follow-fork-mode, detach-on-fork, follow-exec-mode, and
|
|
|
|
|
fork and exec catchpoints.
|
|
|
|
|
|
2016-01-13 04:27:27 +08:00
|
|
|
* Remote syscall events
|
|
|
|
|
|
|
|
|
|
** GDB now has support for catch syscall on remote Linux targets,
|
|
|
|
|
currently enabled on x86/x86_64 architectures.
|
|
|
|
|
|
|
|
|
|
set remote catch-syscall-packet
|
|
|
|
|
show remote catch-syscall-packet
|
|
|
|
|
Set/show the use of the remote catch syscall feature.
|
|
|
|
|
|
2015-12-09 20:56:27 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** The -var-set-format command now accepts the zero-hexadecimal
|
|
|
|
|
format. It outputs data in hexadecimal format with zero-padding on the
|
|
|
|
|
left.
|
|
|
|
|
|
2016-01-13 18:56:06 +08:00
|
|
|
* Python Scripting
|
|
|
|
|
|
2016-01-13 18:56:08 +08:00
|
|
|
** gdb.InferiorThread objects have a new attribute "global_num",
|
|
|
|
|
which refers to the thread's global thread ID. The existing
|
|
|
|
|
"num" attribute now refers to the thread's per-inferior number.
|
|
|
|
|
See "Per-inferior thread numbers" above.
|
2016-01-13 18:56:06 +08:00
|
|
|
** gdb.InferiorThread objects have a new attribute "inferior", which
|
|
|
|
|
is the Inferior object the thread belongs to.
|
|
|
|
|
|
2015-07-07 04:02:47 +08:00
|
|
|
*** Changes in GDB 7.10
|
Implement support for checking /proc/PID/coredump_filter
This patch, as the subject says, extends GDB so that it is able to use
the contents of the file /proc/PID/coredump_filter when generating a
corefile. This file contains a bit mask that is a representation of
the different types of memory mappings in the Linux kernel; the user
can choose to dump or not dump a certain type of memory mapping by
enabling/disabling the respective bit in the bit mask. Currently,
here is what is supported:
bit 0 Dump anonymous private mappings.
bit 1 Dump anonymous shared mappings.
bit 2 Dump file-backed private mappings.
bit 3 Dump file-backed shared mappings.
bit 4 (since Linux 2.6.24)
Dump ELF headers.
bit 5 (since Linux 2.6.28)
Dump private huge pages.
bit 6 (since Linux 2.6.28)
Dump shared huge pages.
(This table has been taken from core(5), but you can also read about it
on Documentation/filesystems/proc.txt inside the Linux kernel source
tree).
The default value for this file, used by the Linux kernel, is 0x33,
which means that bits 0, 1, 4 and 5 are enabled. This is also the
default for GDB implemented in this patch, FWIW.
Well, reading the file is obviously trivial. The hard part, mind you,
is how to determine the types of the memory mappings. For that, I
extended the code of gdb/linux-tdep.c:linux_find_memory_regions_full and
made it rely *much more* on the information gathered from
/proc/<PID>/smaps. This file contains a "verbose dump" of the
inferior's memory mappings, and we were not using as much information as
we could from it. If you want to read more about this file, take a look
at the proc(5) manpage (I will also write a blog post soon about
everything I had to learn to get this patch done, and when I it is ready
I will post it here).
With Oleg Nesterov's help, we could improve the current algorithm for
determining whether a memory mapping is anonymous/file-backed,
private/shared. GDB now also respects the MADV_DONTDUMP flag and does
not dump the memory mapping marked as so, and will always dump
"[vsyscall]" or "[vdso]" mappings (just like the Linux kernel).
In a nutshell, what the new code is doing is:
- If the mapping is associated to a file whose name ends with
" (deleted)", or if the file is "/dev/zero", or if it is "/SYSV%08x"
(shared memory), or if there is no file associated with it, or if
the AnonHugePages: or the Anonymous: fields in the /proc/PID/smaps
have contents, then GDB considers this mapping to be anonymous.
There is a special case in this, though: if the memory mapping is a
file-backed one, but *also* contains "Anonymous:" or
"AnonHugePages:" pages, then GDB considers this mapping to be *both*
anonymous and file-backed, just like the Linux kernel does. What
that means is simple: this mapping will be dumped if the user
requested anonymous mappings *or* if the user requested file-backed
mappings to be present in the corefile.
It is worth mentioning that, from all those checks described above,
the most fragile is the one to see if the file name ends with
" (deleted)". This does not necessarily mean that the mapping is
anonymous, because the deleted file associated with the mapping may
have been a hard link to another file, for example. The Linux
kernel checks to see if "i_nlink == 0", but GDB cannot easily do
this check (as it has been discussed, GDB would need to run as root,
and would need to check the contents of the /proc/PID/map_files/
directory in order to determine whether the deleted was a hardlink
or not). Therefore, we made a compromise here, and we assume that
if the file name ends with " (deleted)", then the mapping is indeed
anonymous. FWIW, this is something the Linux kernel could do
better: expose this information in a more direct way.
- If we see the flag "sh" in the VmFlags: field (in /proc/PID/smaps),
then certainly the memory mapping is shared (VM_SHARED). If we have
access to the VmFlags, and we don't see the "sh" there, then
certainly the mapping is private. However, older Linux kernels (see
the code for more details) do not have the VmFlags field; in that
case, we use another heuristic: if we see 'p' in the permission
flags, then we assume that the mapping is private, even though the
presence of the 's' flag there would mean VM_MAYSHARE, which means
the mapping could still be private. This should work OK enough,
however.
Finally, it is worth mentioning that I added a new command, 'set
use-coredump-filter on/off'. When it is 'on', it will read the
coredump_filter' file (if it exists) and use its value; otherwise, it
will use the default value mentioned above (0x33) to decide which memory
mappings to dump.
gdb/ChangeLog:
2015-03-31 Sergio Durigan Junior <sergiodj@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Oleg Nesterov <oleg@redhat.com>
PR corefiles/16092
* linux-tdep.c: Include 'gdbcmd.h' and 'gdb_regex.h'.
New enum identifying the various options of the coredump_filter
file.
(struct smaps_vmflags): New struct.
(use_coredump_filter): New variable.
(decode_vmflags): New function.
(mapping_is_anonymous_p): Likewise.
(dump_mapping_p): Likewise.
(linux_find_memory_regions_full): New variables
'coredumpfilter_name', 'coredumpfilterdata', 'pid', 'filterflags'.
Removed variable 'modified'. Read /proc/<PID>/smaps file; improve
parsing of its information. Implement memory mapping filtering
based on its contents.
(show_use_coredump_filter): New function.
(_initialize_linux_tdep): New command 'set use-coredump-filter'.
* NEWS: Mention the possibility of using the
'/proc/PID/coredump_filter' file when generating a corefile.
Mention new command 'set use-coredump-filter'.
gdb/doc/ChangeLog:
2015-03-31 Sergio Durigan Junior <sergiodj@redhat.com>
PR corefiles/16092
* gdb.texinfo (gcore): Mention new command 'set
use-coredump-filter'.
(set use-coredump-filter): Document new command.
gdb/testsuite/ChangeLog:
2015-03-31 Sergio Durigan Junior <sergiodj@redhat.com>
PR corefiles/16092
* gdb.base/coredump-filter.c: New file.
* gdb.base/coredump-filter.exp: Likewise.
2015-04-01 07:32:34 +08:00
|
|
|
|
2015-05-11 19:10:43 +08:00
|
|
|
* Support for process record-replay and reverse debugging on aarch64*-linux*
|
|
|
|
|
targets has been added. GDB now supports recording of A64 instruction set
|
|
|
|
|
including advance SIMD instructions.
|
|
|
|
|
|
2015-06-20 02:34:43 +08:00
|
|
|
* Support for Sun's version of the "stabs" debug file format has been removed.
|
|
|
|
|
|
Implement support for checking /proc/PID/coredump_filter
This patch, as the subject says, extends GDB so that it is able to use
the contents of the file /proc/PID/coredump_filter when generating a
corefile. This file contains a bit mask that is a representation of
the different types of memory mappings in the Linux kernel; the user
can choose to dump or not dump a certain type of memory mapping by
enabling/disabling the respective bit in the bit mask. Currently,
here is what is supported:
bit 0 Dump anonymous private mappings.
bit 1 Dump anonymous shared mappings.
bit 2 Dump file-backed private mappings.
bit 3 Dump file-backed shared mappings.
bit 4 (since Linux 2.6.24)
Dump ELF headers.
bit 5 (since Linux 2.6.28)
Dump private huge pages.
bit 6 (since Linux 2.6.28)
Dump shared huge pages.
(This table has been taken from core(5), but you can also read about it
on Documentation/filesystems/proc.txt inside the Linux kernel source
tree).
The default value for this file, used by the Linux kernel, is 0x33,
which means that bits 0, 1, 4 and 5 are enabled. This is also the
default for GDB implemented in this patch, FWIW.
Well, reading the file is obviously trivial. The hard part, mind you,
is how to determine the types of the memory mappings. For that, I
extended the code of gdb/linux-tdep.c:linux_find_memory_regions_full and
made it rely *much more* on the information gathered from
/proc/<PID>/smaps. This file contains a "verbose dump" of the
inferior's memory mappings, and we were not using as much information as
we could from it. If you want to read more about this file, take a look
at the proc(5) manpage (I will also write a blog post soon about
everything I had to learn to get this patch done, and when I it is ready
I will post it here).
With Oleg Nesterov's help, we could improve the current algorithm for
determining whether a memory mapping is anonymous/file-backed,
private/shared. GDB now also respects the MADV_DONTDUMP flag and does
not dump the memory mapping marked as so, and will always dump
"[vsyscall]" or "[vdso]" mappings (just like the Linux kernel).
In a nutshell, what the new code is doing is:
- If the mapping is associated to a file whose name ends with
" (deleted)", or if the file is "/dev/zero", or if it is "/SYSV%08x"
(shared memory), or if there is no file associated with it, or if
the AnonHugePages: or the Anonymous: fields in the /proc/PID/smaps
have contents, then GDB considers this mapping to be anonymous.
There is a special case in this, though: if the memory mapping is a
file-backed one, but *also* contains "Anonymous:" or
"AnonHugePages:" pages, then GDB considers this mapping to be *both*
anonymous and file-backed, just like the Linux kernel does. What
that means is simple: this mapping will be dumped if the user
requested anonymous mappings *or* if the user requested file-backed
mappings to be present in the corefile.
It is worth mentioning that, from all those checks described above,
the most fragile is the one to see if the file name ends with
" (deleted)". This does not necessarily mean that the mapping is
anonymous, because the deleted file associated with the mapping may
have been a hard link to another file, for example. The Linux
kernel checks to see if "i_nlink == 0", but GDB cannot easily do
this check (as it has been discussed, GDB would need to run as root,
and would need to check the contents of the /proc/PID/map_files/
directory in order to determine whether the deleted was a hardlink
or not). Therefore, we made a compromise here, and we assume that
if the file name ends with " (deleted)", then the mapping is indeed
anonymous. FWIW, this is something the Linux kernel could do
better: expose this information in a more direct way.
- If we see the flag "sh" in the VmFlags: field (in /proc/PID/smaps),
then certainly the memory mapping is shared (VM_SHARED). If we have
access to the VmFlags, and we don't see the "sh" there, then
certainly the mapping is private. However, older Linux kernels (see
the code for more details) do not have the VmFlags field; in that
case, we use another heuristic: if we see 'p' in the permission
flags, then we assume that the mapping is private, even though the
presence of the 's' flag there would mean VM_MAYSHARE, which means
the mapping could still be private. This should work OK enough,
however.
Finally, it is worth mentioning that I added a new command, 'set
use-coredump-filter on/off'. When it is 'on', it will read the
coredump_filter' file (if it exists) and use its value; otherwise, it
will use the default value mentioned above (0x33) to decide which memory
mappings to dump.
gdb/ChangeLog:
2015-03-31 Sergio Durigan Junior <sergiodj@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Oleg Nesterov <oleg@redhat.com>
PR corefiles/16092
* linux-tdep.c: Include 'gdbcmd.h' and 'gdb_regex.h'.
New enum identifying the various options of the coredump_filter
file.
(struct smaps_vmflags): New struct.
(use_coredump_filter): New variable.
(decode_vmflags): New function.
(mapping_is_anonymous_p): Likewise.
(dump_mapping_p): Likewise.
(linux_find_memory_regions_full): New variables
'coredumpfilter_name', 'coredumpfilterdata', 'pid', 'filterflags'.
Removed variable 'modified'. Read /proc/<PID>/smaps file; improve
parsing of its information. Implement memory mapping filtering
based on its contents.
(show_use_coredump_filter): New function.
(_initialize_linux_tdep): New command 'set use-coredump-filter'.
* NEWS: Mention the possibility of using the
'/proc/PID/coredump_filter' file when generating a corefile.
Mention new command 'set use-coredump-filter'.
gdb/doc/ChangeLog:
2015-03-31 Sergio Durigan Junior <sergiodj@redhat.com>
PR corefiles/16092
* gdb.texinfo (gcore): Mention new command 'set
use-coredump-filter'.
(set use-coredump-filter): Document new command.
gdb/testsuite/ChangeLog:
2015-03-31 Sergio Durigan Junior <sergiodj@redhat.com>
PR corefiles/16092
* gdb.base/coredump-filter.c: New file.
* gdb.base/coredump-filter.exp: Likewise.
2015-04-01 07:32:34 +08:00
|
|
|
* GDB now honors the content of the file /proc/PID/coredump_filter
|
|
|
|
|
(PID is the process ID) on GNU/Linux systems. This file can be used
|
|
|
|
|
to specify the types of memory mappings that will be included in a
|
|
|
|
|
corefile. For more information, please refer to the manual page of
|
|
|
|
|
"core(5)". GDB also has a new command: "set use-coredump-filter
|
|
|
|
|
on|off". It allows to set whether GDB will read the content of the
|
|
|
|
|
/proc/PID/coredump_filter file when generating a corefile.
|
2015-01-13 20:24:45 +08:00
|
|
|
|
2015-03-25 23:49:05 +08:00
|
|
|
* The "info os" command on GNU/Linux can now display information on
|
|
|
|
|
cpu information :
|
|
|
|
|
"info os cpus" Listing of all cpus/cores on the system
|
|
|
|
|
|
2015-03-24 05:15:42 +08:00
|
|
|
* GDB has two new commands: "set serial parity odd|even|none" and
|
|
|
|
|
"show serial parity". These allows to set or show parity for the
|
|
|
|
|
remote serial I/O.
|
|
|
|
|
|
2015-01-31 12:49:51 +08:00
|
|
|
* The "info source" command now displays the producer string if it was
|
|
|
|
|
present in the debug info. This typically includes the compiler version
|
|
|
|
|
and may include things like its command line arguments.
|
|
|
|
|
|
2015-05-02 19:46:47 +08:00
|
|
|
* The "info dll", an alias of the "info sharedlibrary" command,
|
|
|
|
|
is now available on all platforms.
|
|
|
|
|
|
2015-04-02 20:38:29 +08:00
|
|
|
* Directory names supplied to the "set sysroot" commands may be
|
|
|
|
|
prefixed with "target:" to tell GDB to access shared libraries from
|
|
|
|
|
the target system, be it local or remote. This replaces the prefix
|
|
|
|
|
"remote:". The default sysroot has been changed from "" to
|
|
|
|
|
"target:". "remote:" is automatically converted to "target:" for
|
|
|
|
|
backward compatibility.
|
|
|
|
|
|
2015-04-17 16:47:30 +08:00
|
|
|
* The system root specified by "set sysroot" will be prepended to the
|
|
|
|
|
filename of the main executable (if reported to GDB as absolute by
|
|
|
|
|
the operating system) when starting processes remotely, and when
|
|
|
|
|
attaching to already-running local or remote processes.
|
|
|
|
|
|
2015-04-17 16:47:30 +08:00
|
|
|
* GDB now supports automatic location and retrieval of executable
|
|
|
|
|
files from remote targets. Remote debugging can now be initiated
|
|
|
|
|
using only a "target remote" or "target extended-remote" command
|
|
|
|
|
(no "set sysroot" or "file" commands are required). See "New remote
|
|
|
|
|
packets" below.
|
|
|
|
|
|
2015-04-23 05:52:36 +08:00
|
|
|
* The "dump" command now supports verilog hex format.
|
|
|
|
|
|
2015-04-27 17:38:47 +08:00
|
|
|
* GDB now supports the vector ABI on S/390 GNU/Linux targets.
|
|
|
|
|
|
2015-06-10 21:28:44 +08:00
|
|
|
* On GNU/Linux, GDB and gdbserver are now able to access executable
|
|
|
|
|
and shared library files without a "set sysroot" command when
|
|
|
|
|
attaching to processes running in different mount namespaces from
|
|
|
|
|
the debugger. This makes it possible to attach to processes in
|
|
|
|
|
containers as simply as "gdb -p PID" or "gdbserver --attach PID".
|
|
|
|
|
See "New remote packets" below.
|
|
|
|
|
|
2015-05-27 06:23:23 +08:00
|
|
|
* The "tui reg" command now provides completion for all of the
|
|
|
|
|
available register groups, including target specific groups.
|
|
|
|
|
|
2015-06-18 01:31:56 +08:00
|
|
|
* The HISTSIZE environment variable is no longer read when determining
|
|
|
|
|
the size of GDB's command history. GDB now instead reads the dedicated
|
2015-05-12 18:50:26 +08:00
|
|
|
GDBHISTSIZE environment variable. Setting GDBHISTSIZE to "-1" or to "" now
|
|
|
|
|
disables truncation of command history. Non-numeric values of GDBHISTSIZE
|
|
|
|
|
are ignored.
|
2015-06-18 01:31:56 +08:00
|
|
|
|
2015-05-17 03:14:26 +08:00
|
|
|
* Guile Scripting
|
|
|
|
|
|
|
|
|
|
** Memory ports can now be unbuffered.
|
|
|
|
|
|
2015-01-28 02:13:52 +08:00
|
|
|
* Python Scripting
|
|
|
|
|
|
|
|
|
|
** gdb.Objfile objects have a new attribute "username",
|
|
|
|
|
which is the name of the objfile as specified by the user,
|
|
|
|
|
without, for example, resolving symlinks.
|
2015-04-02 02:49:12 +08:00
|
|
|
** You can now write frame unwinders in Python.
|
2015-04-29 08:41:09 +08:00
|
|
|
** gdb.Type objects have a new method "optimized_out",
|
|
|
|
|
returning optimized out gdb.Value instance of this type.
|
2015-04-25 22:04:40 +08:00
|
|
|
** gdb.Value objects have new methods "reference_value" and
|
|
|
|
|
"const_value" which return a reference to the value and a
|
|
|
|
|
"const" version of the value respectively.
|
2015-01-28 02:13:52 +08:00
|
|
|
|
Add symbol lookup cache.
gdb/ChangeLog:
Add symbol lookup cache.
* NEWS: Document new options and commands.
* symtab.c (symbol_cache_key): New static global.
(DEFAULT_SYMBOL_CACHE_SIZE, MAX_SYMBOL_CACHE_SIZE): New macros.
(SYMBOL_LOOKUP_FAILED): New macro.
(symbol_cache_slot_state): New enum.
(block_symbol_cache): New struct.
(symbol_cache): New struct.
(new_symbol_cache_size, symbol_cache_size): New static globals.
(hash_symbol_entry, eq_symbol_entry): New functions.
(symbol_cache_byte_size, resize_symbol_cache): New functions.
(make_symbol_cache, free_symbol_cache): New functions.
(get_symbol_cache, symbol_cache_cleanup): New function.
(set_symbol_cache_size, set_symbol_cache_size_handler): New functions.
(symbol_cache_lookup, symbol_cache_clear_slot): New function.
(symbol_cache_mark_found, symbol_cache_mark_not_found): New functions.
(symbol_cache_flush, symbol_cache_dump): New functions.
(maintenance_print_symbol_cache): New function.
(maintenance_flush_symbol_cache): New function.
(symbol_cache_stats): New function.
(maintenance_print_symbol_cache_statistics): New function.
(symtab_new_objfile_observer): New function.
(symtab_free_objfile_observer): New function.
(lookup_static_symbol, lookup_global_symbol): Use symbol cache.
(_initialize_symtab): Init symbol_cache_key. New parameter
maint symbol-cache-size. New maint commands print symbol-cache,
print symbol-cache-statistics, flush-symbol-cache.
Install new_objfile, free_objfile observers.
gdb/doc/ChangeLog:
* gdb.texinfo (Symbols): Document new commands
"maint print symbol-cache", "maint print symbol-cache-statistics",
"maint flush-symbol-cache". Document new option
"maint set symbol-cache-size".
2015-02-01 05:29:33 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
maint print symbol-cache
|
|
|
|
|
Print the contents of the symbol cache.
|
|
|
|
|
|
|
|
|
|
maint print symbol-cache-statistics
|
|
|
|
|
Print statistics of symbol cache usage.
|
|
|
|
|
|
|
|
|
|
maint flush-symbol-cache
|
|
|
|
|
Flush the contents of the symbol cache.
|
|
|
|
|
|
2013-11-28 22:44:13 +08:00
|
|
|
record btrace bts
|
|
|
|
|
record bts
|
|
|
|
|
Start branch trace recording using Branch Trace Store (BTS) format.
|
|
|
|
|
|
2015-05-16 20:20:46 +08:00
|
|
|
compile print
|
|
|
|
|
Evaluate expression by using the compiler and print result.
|
|
|
|
|
|
2015-05-22 16:07:42 +08:00
|
|
|
tui enable
|
|
|
|
|
tui disable
|
|
|
|
|
Explicit commands for enabling and disabling tui mode.
|
|
|
|
|
|
2015-06-09 21:27:02 +08:00
|
|
|
show mpx bound
|
|
|
|
|
set mpx bound on i386 and amd64
|
2016-01-12 23:03:11 +08:00
|
|
|
Support for bound table investigation on Intel MPX enabled applications.
|
2015-06-09 21:27:02 +08:00
|
|
|
|
btrace: support Intel(R) Processor Trace
Adds a new command "record btrace pt" to configure the kernel to use
Intel(R) Processor Trace instead of Branch Trace Strore.
The "record btrace" command chooses the tracing format automatically.
Intel(R) Processor Trace support requires Linux 4.1 and libipt.
gdb/
* NEWS: Announce new commands "record btrace pt" and "record pt".
Announce new options "set|show record btrace pt buffer-size".
* btrace.c: Include "rsp-low.h".
Include "inttypes.h".
(btrace_add_pc): Add forward declaration.
(pt_reclassify_insn, ftrace_add_pt, btrace_pt_readmem_callback)
(pt_translate_cpu_vendor, btrace_finalize_ftrace_pt)
(btrace_compute_ftrace_pt): New.
(btrace_compute_ftrace): Support BTRACE_FORMAT_PT.
(check_xml_btrace_version): Update version check.
(parse_xml_raw, parse_xml_btrace_pt_config_cpu)
(parse_xml_btrace_pt_raw, parse_xml_btrace_pt)
(btrace_pt_config_cpu_attributes, btrace_pt_config_children)
(btrace_pt_children): New.
(btrace_children): Add support for "pt".
(parse_xml_btrace_conf_pt, btrace_conf_pt_attributes): New.
(btrace_conf_children): Add support for "pt".
* btrace.h: Include "intel-pt.h".
(btrace_pt_error): New.
* common/btrace-common.c (btrace_format_string, btrace_data_fini)
(btrace_data_empty): Support BTRACE_FORMAT_PT.
* common/btrace-common.h (btrace_format): Add BTRACE_FORMAT_PT.
(struct btrace_config_pt): New.
(struct btrace_config)<pt>: New.
(struct btrace_data_pt_config, struct btrace_data_pt): New.
(struct btrace_data)<pt>: New.
* features/btrace-conf.dtd (btrace-conf)<pt>: New.
(pt): New.
* features/btrace.dtd (btrace)<pt>: New.
(pt, pt-config, cpu): New.
* nat/linux-btrace.c (perf_event_read, perf_event_read_all)
(perf_event_pt_event_type, kernel_supports_pt)
(linux_supports_pt): New.
(linux_supports_btrace): Support BTRACE_FORMAT_PT.
(linux_enable_bts): Free tinfo on error.
(linux_enable_pt): New.
(linux_enable_btrace): Support BTRACE_FORMAT_PT.
(linux_disable_pt): New.
(linux_disable_btrace): Support BTRACE_FORMAT_PT.
(linux_fill_btrace_pt_config, linux_read_pt): New.
(linux_read_btrace): Support BTRACE_FORMAT_PT.
* nat/linux-btrace.h (struct btrace_tinfo_pt): New.
(struct btrace_target_info)<pt>: New.
* record-btrace.c (set_record_btrace_pt_cmdlist)
(show_record_btrace_pt_cmdlist): New.
(record_btrace_print_pt_conf): New.
(record_btrace_print_conf): Support BTRACE_FORMAT_PT.
(btrace_ui_out_decode_error): Support BTRACE_FORMAT_PT.
(cmd_record_btrace_pt_start): New.
(cmd_record_btrace_start): Support BTRACE_FORMAT_PT.
(cmd_set_record_btrace_pt, cmd_show_record_btrace_pt): New.
(_initialize_record_btrace): Add new commands.
* remote.c (PACKET_Qbtrace_pt, PACKET_Qbtrace_conf_pt_size): New.
(remote_protocol_features): Add "Qbtrace:pt".
Add "Qbtrace-conf:pt:size".
(remote_supports_btrace): Support BTRACE_FORMAT_PT.
(btrace_sync_conf): Support PACKET_Qbtrace_conf_pt_size.
(remote_enable_btrace): Support BTRACE_FORMAT_PT.
(_initialize_remote): Add new commands.
gdbserver/
* linux-low.c: Include "rsp-low.h"
(linux_low_encode_pt_config, linux_low_encode_raw): New.
(linux_low_read_btrace): Support BTRACE_FORMAT_PT.
(linux_low_btrace_conf): Support BTRACE_FORMAT_PT.
(handle_btrace_enable_pt): New.
(handle_btrace_general_set): Support "pt".
(handle_btrace_conf_general_set): Support "pt:size".
doc/
* gdb.texinfo (Process Record and Replay): Spell out that variables
and registers are not available during btrace replay.
Describe the new "record btrace pt" command.
Describe the new "set|show record btrace pt buffer-size" options.
(General Query Packets): Describe the new Qbtrace:pt and
Qbtrace-conf:pt:size packets.
Expand "bts" to "Branch Trace Store".
Update the branch trace DTD.
2014-01-24 20:45:47 +08:00
|
|
|
record btrace pt
|
|
|
|
|
record pt
|
2016-01-12 23:03:11 +08:00
|
|
|
Start branch trace recording using Intel Processor Trace format.
|
btrace: support Intel(R) Processor Trace
Adds a new command "record btrace pt" to configure the kernel to use
Intel(R) Processor Trace instead of Branch Trace Strore.
The "record btrace" command chooses the tracing format automatically.
Intel(R) Processor Trace support requires Linux 4.1 and libipt.
gdb/
* NEWS: Announce new commands "record btrace pt" and "record pt".
Announce new options "set|show record btrace pt buffer-size".
* btrace.c: Include "rsp-low.h".
Include "inttypes.h".
(btrace_add_pc): Add forward declaration.
(pt_reclassify_insn, ftrace_add_pt, btrace_pt_readmem_callback)
(pt_translate_cpu_vendor, btrace_finalize_ftrace_pt)
(btrace_compute_ftrace_pt): New.
(btrace_compute_ftrace): Support BTRACE_FORMAT_PT.
(check_xml_btrace_version): Update version check.
(parse_xml_raw, parse_xml_btrace_pt_config_cpu)
(parse_xml_btrace_pt_raw, parse_xml_btrace_pt)
(btrace_pt_config_cpu_attributes, btrace_pt_config_children)
(btrace_pt_children): New.
(btrace_children): Add support for "pt".
(parse_xml_btrace_conf_pt, btrace_conf_pt_attributes): New.
(btrace_conf_children): Add support for "pt".
* btrace.h: Include "intel-pt.h".
(btrace_pt_error): New.
* common/btrace-common.c (btrace_format_string, btrace_data_fini)
(btrace_data_empty): Support BTRACE_FORMAT_PT.
* common/btrace-common.h (btrace_format): Add BTRACE_FORMAT_PT.
(struct btrace_config_pt): New.
(struct btrace_config)<pt>: New.
(struct btrace_data_pt_config, struct btrace_data_pt): New.
(struct btrace_data)<pt>: New.
* features/btrace-conf.dtd (btrace-conf)<pt>: New.
(pt): New.
* features/btrace.dtd (btrace)<pt>: New.
(pt, pt-config, cpu): New.
* nat/linux-btrace.c (perf_event_read, perf_event_read_all)
(perf_event_pt_event_type, kernel_supports_pt)
(linux_supports_pt): New.
(linux_supports_btrace): Support BTRACE_FORMAT_PT.
(linux_enable_bts): Free tinfo on error.
(linux_enable_pt): New.
(linux_enable_btrace): Support BTRACE_FORMAT_PT.
(linux_disable_pt): New.
(linux_disable_btrace): Support BTRACE_FORMAT_PT.
(linux_fill_btrace_pt_config, linux_read_pt): New.
(linux_read_btrace): Support BTRACE_FORMAT_PT.
* nat/linux-btrace.h (struct btrace_tinfo_pt): New.
(struct btrace_target_info)<pt>: New.
* record-btrace.c (set_record_btrace_pt_cmdlist)
(show_record_btrace_pt_cmdlist): New.
(record_btrace_print_pt_conf): New.
(record_btrace_print_conf): Support BTRACE_FORMAT_PT.
(btrace_ui_out_decode_error): Support BTRACE_FORMAT_PT.
(cmd_record_btrace_pt_start): New.
(cmd_record_btrace_start): Support BTRACE_FORMAT_PT.
(cmd_set_record_btrace_pt, cmd_show_record_btrace_pt): New.
(_initialize_record_btrace): Add new commands.
* remote.c (PACKET_Qbtrace_pt, PACKET_Qbtrace_conf_pt_size): New.
(remote_protocol_features): Add "Qbtrace:pt".
Add "Qbtrace-conf:pt:size".
(remote_supports_btrace): Support BTRACE_FORMAT_PT.
(btrace_sync_conf): Support PACKET_Qbtrace_conf_pt_size.
(remote_enable_btrace): Support BTRACE_FORMAT_PT.
(_initialize_remote): Add new commands.
gdbserver/
* linux-low.c: Include "rsp-low.h"
(linux_low_encode_pt_config, linux_low_encode_raw): New.
(linux_low_read_btrace): Support BTRACE_FORMAT_PT.
(linux_low_btrace_conf): Support BTRACE_FORMAT_PT.
(handle_btrace_enable_pt): New.
(handle_btrace_general_set): Support "pt".
(handle_btrace_conf_general_set): Support "pt:size".
doc/
* gdb.texinfo (Process Record and Replay): Spell out that variables
and registers are not available during btrace replay.
Describe the new "record btrace pt" command.
Describe the new "set|show record btrace pt buffer-size" options.
(General Query Packets): Describe the new Qbtrace:pt and
Qbtrace-conf:pt:size packets.
Expand "bts" to "Branch Trace Store".
Update the branch trace DTD.
2014-01-24 20:45:47 +08:00
|
|
|
|
btrace: maintenance commands
Add maintenance commands that help debugging the btrace record target.
The following new commands are added:
maint info btrace
Print information about branch tracing internals.
maint btrace packet-history
Print the raw branch tracing data.
maint btrace clear-packet-history
Discard the stored raw branch tracing data.
maint btrace clear
Discard all branch tracing data. It will be fetched and processed
anew by the next "record" command.
maint set|show btrace pt skip-pad
Set and show whether PAD packets are skipped when computing the
packet history.
gdb/
* btrace.c: Include gdbcmd.h, cli/cli-utils.h, and ctype.h.
(maint_btrace_cmdlist, maint_btrace_set_cmdlist)
(maint_btrace_show_cmdlist, maint_btrace_pt_set_cmdlist)
(maint_btrace_pt_show_cmdlist, maint_btrace_pt_skip_pad)
(btrace_maint_clear): New.
(btrace_fetch, btrace_clear): Call btrace_maint_clear.
(pt_print_packet, btrace_maint_decode_pt)
(btrace_maint_update_pt_packets, btrace_maint_update_packets)
(btrace_maint_print_packets, get_uint, get_context_size, no_chunk)
(maint_btrace_packet_history_cmd)
(maint_btrace_clear_packet_history_cmd, maint_btrace_clear_cmd)
(maint_btrace_cmd, maint_btrace_set_cmd, maint_btrace_show_cmd)
(maint_btrace_pt_set_cmd, maint_btrace_pt_show_cmd)
(maint_info_btrace_cmd, _initialize_btrace): New.
* btrace.h (btrace_pt_packet, btrace_pt_packet_s)
(btrace_maint_packet_history, btrace_maint_info): New.
(btrace_thread_info) <maint>: New.
* NEWS: Announce it.
doc/
* gdb.texinfo (Maintenance Commands): Document "maint btrace"
commands.
2014-02-03 21:35:28 +08:00
|
|
|
maint info btrace
|
|
|
|
|
Print information about branch tracing internals.
|
|
|
|
|
|
|
|
|
|
maint btrace packet-history
|
|
|
|
|
Print the raw branch tracing data.
|
|
|
|
|
|
|
|
|
|
maint btrace clear-packet-history
|
|
|
|
|
Discard the stored raw branch tracing data.
|
|
|
|
|
|
|
|
|
|
maint btrace clear
|
|
|
|
|
Discard all branch tracing data. It will be fetched and processed
|
|
|
|
|
anew by the next "record" command.
|
|
|
|
|
|
2015-01-23 04:04:53 +08:00
|
|
|
* New options
|
|
|
|
|
|
2015-05-27 07:50:57 +08:00
|
|
|
set debug dwarf-die
|
|
|
|
|
Renamed from "set debug dwarf2-die".
|
|
|
|
|
show debug dwarf-die
|
|
|
|
|
Renamed from "show debug dwarf2-die".
|
|
|
|
|
|
|
|
|
|
set debug dwarf-read
|
|
|
|
|
Renamed from "set debug dwarf2-read".
|
|
|
|
|
show debug dwarf-read
|
|
|
|
|
Renamed from "show debug dwarf2-read".
|
|
|
|
|
|
|
|
|
|
maint set dwarf always-disassemble
|
|
|
|
|
Renamed from "maint set dwarf2 always-disassemble".
|
|
|
|
|
maint show dwarf always-disassemble
|
|
|
|
|
Renamed from "maint show dwarf2 always-disassemble".
|
|
|
|
|
|
|
|
|
|
maint set dwarf max-cache-age
|
|
|
|
|
Renamed from "maint set dwarf2 max-cache-age".
|
|
|
|
|
maint show dwarf max-cache-age
|
|
|
|
|
Renamed from "maint show dwarf2 max-cache-age".
|
|
|
|
|
|
2015-05-28 03:55:19 +08:00
|
|
|
set debug dwarf-line
|
|
|
|
|
show debug dwarf-line
|
|
|
|
|
Control display of debugging info regarding DWARF line processing.
|
|
|
|
|
|
2015-02-01 07:07:22 +08:00
|
|
|
set max-completions
|
|
|
|
|
show max-completions
|
|
|
|
|
Set the maximum number of candidates to be considered during
|
|
|
|
|
completion. The default value is 200. This limit allows GDB
|
|
|
|
|
to avoid generating large completion lists, the computation of
|
|
|
|
|
which can cause the debugger to become temporarily unresponsive.
|
|
|
|
|
|
2015-06-03 10:49:15 +08:00
|
|
|
set history remove-duplicates
|
|
|
|
|
show history remove-duplicates
|
|
|
|
|
Control the removal of duplicate history entries.
|
|
|
|
|
|
Add symbol lookup cache.
gdb/ChangeLog:
Add symbol lookup cache.
* NEWS: Document new options and commands.
* symtab.c (symbol_cache_key): New static global.
(DEFAULT_SYMBOL_CACHE_SIZE, MAX_SYMBOL_CACHE_SIZE): New macros.
(SYMBOL_LOOKUP_FAILED): New macro.
(symbol_cache_slot_state): New enum.
(block_symbol_cache): New struct.
(symbol_cache): New struct.
(new_symbol_cache_size, symbol_cache_size): New static globals.
(hash_symbol_entry, eq_symbol_entry): New functions.
(symbol_cache_byte_size, resize_symbol_cache): New functions.
(make_symbol_cache, free_symbol_cache): New functions.
(get_symbol_cache, symbol_cache_cleanup): New function.
(set_symbol_cache_size, set_symbol_cache_size_handler): New functions.
(symbol_cache_lookup, symbol_cache_clear_slot): New function.
(symbol_cache_mark_found, symbol_cache_mark_not_found): New functions.
(symbol_cache_flush, symbol_cache_dump): New functions.
(maintenance_print_symbol_cache): New function.
(maintenance_flush_symbol_cache): New function.
(symbol_cache_stats): New function.
(maintenance_print_symbol_cache_statistics): New function.
(symtab_new_objfile_observer): New function.
(symtab_free_objfile_observer): New function.
(lookup_static_symbol, lookup_global_symbol): Use symbol cache.
(_initialize_symtab): Init symbol_cache_key. New parameter
maint symbol-cache-size. New maint commands print symbol-cache,
print symbol-cache-statistics, flush-symbol-cache.
Install new_objfile, free_objfile observers.
gdb/doc/ChangeLog:
* gdb.texinfo (Symbols): Document new commands
"maint print symbol-cache", "maint print symbol-cache-statistics",
"maint flush-symbol-cache". Document new option
"maint set symbol-cache-size".
2015-02-01 05:29:33 +08:00
|
|
|
maint set symbol-cache-size
|
|
|
|
|
maint show symbol-cache-size
|
|
|
|
|
Control the size of the symbol cache.
|
|
|
|
|
|
2013-11-28 23:39:12 +08:00
|
|
|
set|show record btrace bts buffer-size
|
|
|
|
|
Set and show the size of the ring buffer used for branch tracing in
|
|
|
|
|
BTS format.
|
|
|
|
|
The obtained size may differ from the requested size. Use "info
|
|
|
|
|
record" to see the obtained buffer size.
|
|
|
|
|
|
2015-06-10 21:28:43 +08:00
|
|
|
set debug linux-namespaces
|
|
|
|
|
show debug linux-namespaces
|
|
|
|
|
Control display of debugging info regarding Linux namespaces.
|
|
|
|
|
|
btrace: support Intel(R) Processor Trace
Adds a new command "record btrace pt" to configure the kernel to use
Intel(R) Processor Trace instead of Branch Trace Strore.
The "record btrace" command chooses the tracing format automatically.
Intel(R) Processor Trace support requires Linux 4.1 and libipt.
gdb/
* NEWS: Announce new commands "record btrace pt" and "record pt".
Announce new options "set|show record btrace pt buffer-size".
* btrace.c: Include "rsp-low.h".
Include "inttypes.h".
(btrace_add_pc): Add forward declaration.
(pt_reclassify_insn, ftrace_add_pt, btrace_pt_readmem_callback)
(pt_translate_cpu_vendor, btrace_finalize_ftrace_pt)
(btrace_compute_ftrace_pt): New.
(btrace_compute_ftrace): Support BTRACE_FORMAT_PT.
(check_xml_btrace_version): Update version check.
(parse_xml_raw, parse_xml_btrace_pt_config_cpu)
(parse_xml_btrace_pt_raw, parse_xml_btrace_pt)
(btrace_pt_config_cpu_attributes, btrace_pt_config_children)
(btrace_pt_children): New.
(btrace_children): Add support for "pt".
(parse_xml_btrace_conf_pt, btrace_conf_pt_attributes): New.
(btrace_conf_children): Add support for "pt".
* btrace.h: Include "intel-pt.h".
(btrace_pt_error): New.
* common/btrace-common.c (btrace_format_string, btrace_data_fini)
(btrace_data_empty): Support BTRACE_FORMAT_PT.
* common/btrace-common.h (btrace_format): Add BTRACE_FORMAT_PT.
(struct btrace_config_pt): New.
(struct btrace_config)<pt>: New.
(struct btrace_data_pt_config, struct btrace_data_pt): New.
(struct btrace_data)<pt>: New.
* features/btrace-conf.dtd (btrace-conf)<pt>: New.
(pt): New.
* features/btrace.dtd (btrace)<pt>: New.
(pt, pt-config, cpu): New.
* nat/linux-btrace.c (perf_event_read, perf_event_read_all)
(perf_event_pt_event_type, kernel_supports_pt)
(linux_supports_pt): New.
(linux_supports_btrace): Support BTRACE_FORMAT_PT.
(linux_enable_bts): Free tinfo on error.
(linux_enable_pt): New.
(linux_enable_btrace): Support BTRACE_FORMAT_PT.
(linux_disable_pt): New.
(linux_disable_btrace): Support BTRACE_FORMAT_PT.
(linux_fill_btrace_pt_config, linux_read_pt): New.
(linux_read_btrace): Support BTRACE_FORMAT_PT.
* nat/linux-btrace.h (struct btrace_tinfo_pt): New.
(struct btrace_target_info)<pt>: New.
* record-btrace.c (set_record_btrace_pt_cmdlist)
(show_record_btrace_pt_cmdlist): New.
(record_btrace_print_pt_conf): New.
(record_btrace_print_conf): Support BTRACE_FORMAT_PT.
(btrace_ui_out_decode_error): Support BTRACE_FORMAT_PT.
(cmd_record_btrace_pt_start): New.
(cmd_record_btrace_start): Support BTRACE_FORMAT_PT.
(cmd_set_record_btrace_pt, cmd_show_record_btrace_pt): New.
(_initialize_record_btrace): Add new commands.
* remote.c (PACKET_Qbtrace_pt, PACKET_Qbtrace_conf_pt_size): New.
(remote_protocol_features): Add "Qbtrace:pt".
Add "Qbtrace-conf:pt:size".
(remote_supports_btrace): Support BTRACE_FORMAT_PT.
(btrace_sync_conf): Support PACKET_Qbtrace_conf_pt_size.
(remote_enable_btrace): Support BTRACE_FORMAT_PT.
(_initialize_remote): Add new commands.
gdbserver/
* linux-low.c: Include "rsp-low.h"
(linux_low_encode_pt_config, linux_low_encode_raw): New.
(linux_low_read_btrace): Support BTRACE_FORMAT_PT.
(linux_low_btrace_conf): Support BTRACE_FORMAT_PT.
(handle_btrace_enable_pt): New.
(handle_btrace_general_set): Support "pt".
(handle_btrace_conf_general_set): Support "pt:size".
doc/
* gdb.texinfo (Process Record and Replay): Spell out that variables
and registers are not available during btrace replay.
Describe the new "record btrace pt" command.
Describe the new "set|show record btrace pt buffer-size" options.
(General Query Packets): Describe the new Qbtrace:pt and
Qbtrace-conf:pt:size packets.
Expand "bts" to "Branch Trace Store".
Update the branch trace DTD.
2014-01-24 20:45:47 +08:00
|
|
|
set|show record btrace pt buffer-size
|
|
|
|
|
Set and show the size of the ring buffer used for branch tracing in
|
2016-01-12 23:03:11 +08:00
|
|
|
Intel Processor Trace format.
|
btrace: support Intel(R) Processor Trace
Adds a new command "record btrace pt" to configure the kernel to use
Intel(R) Processor Trace instead of Branch Trace Strore.
The "record btrace" command chooses the tracing format automatically.
Intel(R) Processor Trace support requires Linux 4.1 and libipt.
gdb/
* NEWS: Announce new commands "record btrace pt" and "record pt".
Announce new options "set|show record btrace pt buffer-size".
* btrace.c: Include "rsp-low.h".
Include "inttypes.h".
(btrace_add_pc): Add forward declaration.
(pt_reclassify_insn, ftrace_add_pt, btrace_pt_readmem_callback)
(pt_translate_cpu_vendor, btrace_finalize_ftrace_pt)
(btrace_compute_ftrace_pt): New.
(btrace_compute_ftrace): Support BTRACE_FORMAT_PT.
(check_xml_btrace_version): Update version check.
(parse_xml_raw, parse_xml_btrace_pt_config_cpu)
(parse_xml_btrace_pt_raw, parse_xml_btrace_pt)
(btrace_pt_config_cpu_attributes, btrace_pt_config_children)
(btrace_pt_children): New.
(btrace_children): Add support for "pt".
(parse_xml_btrace_conf_pt, btrace_conf_pt_attributes): New.
(btrace_conf_children): Add support for "pt".
* btrace.h: Include "intel-pt.h".
(btrace_pt_error): New.
* common/btrace-common.c (btrace_format_string, btrace_data_fini)
(btrace_data_empty): Support BTRACE_FORMAT_PT.
* common/btrace-common.h (btrace_format): Add BTRACE_FORMAT_PT.
(struct btrace_config_pt): New.
(struct btrace_config)<pt>: New.
(struct btrace_data_pt_config, struct btrace_data_pt): New.
(struct btrace_data)<pt>: New.
* features/btrace-conf.dtd (btrace-conf)<pt>: New.
(pt): New.
* features/btrace.dtd (btrace)<pt>: New.
(pt, pt-config, cpu): New.
* nat/linux-btrace.c (perf_event_read, perf_event_read_all)
(perf_event_pt_event_type, kernel_supports_pt)
(linux_supports_pt): New.
(linux_supports_btrace): Support BTRACE_FORMAT_PT.
(linux_enable_bts): Free tinfo on error.
(linux_enable_pt): New.
(linux_enable_btrace): Support BTRACE_FORMAT_PT.
(linux_disable_pt): New.
(linux_disable_btrace): Support BTRACE_FORMAT_PT.
(linux_fill_btrace_pt_config, linux_read_pt): New.
(linux_read_btrace): Support BTRACE_FORMAT_PT.
* nat/linux-btrace.h (struct btrace_tinfo_pt): New.
(struct btrace_target_info)<pt>: New.
* record-btrace.c (set_record_btrace_pt_cmdlist)
(show_record_btrace_pt_cmdlist): New.
(record_btrace_print_pt_conf): New.
(record_btrace_print_conf): Support BTRACE_FORMAT_PT.
(btrace_ui_out_decode_error): Support BTRACE_FORMAT_PT.
(cmd_record_btrace_pt_start): New.
(cmd_record_btrace_start): Support BTRACE_FORMAT_PT.
(cmd_set_record_btrace_pt, cmd_show_record_btrace_pt): New.
(_initialize_record_btrace): Add new commands.
* remote.c (PACKET_Qbtrace_pt, PACKET_Qbtrace_conf_pt_size): New.
(remote_protocol_features): Add "Qbtrace:pt".
Add "Qbtrace-conf:pt:size".
(remote_supports_btrace): Support BTRACE_FORMAT_PT.
(btrace_sync_conf): Support PACKET_Qbtrace_conf_pt_size.
(remote_enable_btrace): Support BTRACE_FORMAT_PT.
(_initialize_remote): Add new commands.
gdbserver/
* linux-low.c: Include "rsp-low.h"
(linux_low_encode_pt_config, linux_low_encode_raw): New.
(linux_low_read_btrace): Support BTRACE_FORMAT_PT.
(linux_low_btrace_conf): Support BTRACE_FORMAT_PT.
(handle_btrace_enable_pt): New.
(handle_btrace_general_set): Support "pt".
(handle_btrace_conf_general_set): Support "pt:size".
doc/
* gdb.texinfo (Process Record and Replay): Spell out that variables
and registers are not available during btrace replay.
Describe the new "record btrace pt" command.
Describe the new "set|show record btrace pt buffer-size" options.
(General Query Packets): Describe the new Qbtrace:pt and
Qbtrace-conf:pt:size packets.
Expand "bts" to "Branch Trace Store".
Update the branch trace DTD.
2014-01-24 20:45:47 +08:00
|
|
|
The obtained size may differ from the requested size. Use "info
|
|
|
|
|
record" to see the obtained buffer size.
|
|
|
|
|
|
btrace: maintenance commands
Add maintenance commands that help debugging the btrace record target.
The following new commands are added:
maint info btrace
Print information about branch tracing internals.
maint btrace packet-history
Print the raw branch tracing data.
maint btrace clear-packet-history
Discard the stored raw branch tracing data.
maint btrace clear
Discard all branch tracing data. It will be fetched and processed
anew by the next "record" command.
maint set|show btrace pt skip-pad
Set and show whether PAD packets are skipped when computing the
packet history.
gdb/
* btrace.c: Include gdbcmd.h, cli/cli-utils.h, and ctype.h.
(maint_btrace_cmdlist, maint_btrace_set_cmdlist)
(maint_btrace_show_cmdlist, maint_btrace_pt_set_cmdlist)
(maint_btrace_pt_show_cmdlist, maint_btrace_pt_skip_pad)
(btrace_maint_clear): New.
(btrace_fetch, btrace_clear): Call btrace_maint_clear.
(pt_print_packet, btrace_maint_decode_pt)
(btrace_maint_update_pt_packets, btrace_maint_update_packets)
(btrace_maint_print_packets, get_uint, get_context_size, no_chunk)
(maint_btrace_packet_history_cmd)
(maint_btrace_clear_packet_history_cmd, maint_btrace_clear_cmd)
(maint_btrace_cmd, maint_btrace_set_cmd, maint_btrace_show_cmd)
(maint_btrace_pt_set_cmd, maint_btrace_pt_show_cmd)
(maint_info_btrace_cmd, _initialize_btrace): New.
* btrace.h (btrace_pt_packet, btrace_pt_packet_s)
(btrace_maint_packet_history, btrace_maint_info): New.
(btrace_thread_info) <maint>: New.
* NEWS: Announce it.
doc/
* gdb.texinfo (Maintenance Commands): Document "maint btrace"
commands.
2014-02-03 21:35:28 +08:00
|
|
|
maint set|show btrace pt skip-pad
|
|
|
|
|
Set and show whether PAD packets are skipped when computing the
|
|
|
|
|
packet history.
|
|
|
|
|
|
2015-01-23 04:04:53 +08:00
|
|
|
* The command 'thread apply all' can now support new option '-ascending'
|
|
|
|
|
to call its specified command for all threads in ascending order.
|
|
|
|
|
|
2015-02-01 04:01:13 +08:00
|
|
|
* Python/Guile scripting
|
|
|
|
|
|
|
|
|
|
** GDB now supports auto-loading of Python/Guile scripts contained in the
|
|
|
|
|
special section named `.debug_gdb_scripts'.
|
|
|
|
|
|
2013-11-28 22:44:13 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
qXfer:btrace-conf:read
|
|
|
|
|
Return the branch trace configuration for the current thread.
|
|
|
|
|
|
2013-11-28 23:39:12 +08:00
|
|
|
Qbtrace-conf:bts:size
|
|
|
|
|
Set the requested ring buffer size for branch tracing in BTS format.
|
|
|
|
|
|
btrace: support Intel(R) Processor Trace
Adds a new command "record btrace pt" to configure the kernel to use
Intel(R) Processor Trace instead of Branch Trace Strore.
The "record btrace" command chooses the tracing format automatically.
Intel(R) Processor Trace support requires Linux 4.1 and libipt.
gdb/
* NEWS: Announce new commands "record btrace pt" and "record pt".
Announce new options "set|show record btrace pt buffer-size".
* btrace.c: Include "rsp-low.h".
Include "inttypes.h".
(btrace_add_pc): Add forward declaration.
(pt_reclassify_insn, ftrace_add_pt, btrace_pt_readmem_callback)
(pt_translate_cpu_vendor, btrace_finalize_ftrace_pt)
(btrace_compute_ftrace_pt): New.
(btrace_compute_ftrace): Support BTRACE_FORMAT_PT.
(check_xml_btrace_version): Update version check.
(parse_xml_raw, parse_xml_btrace_pt_config_cpu)
(parse_xml_btrace_pt_raw, parse_xml_btrace_pt)
(btrace_pt_config_cpu_attributes, btrace_pt_config_children)
(btrace_pt_children): New.
(btrace_children): Add support for "pt".
(parse_xml_btrace_conf_pt, btrace_conf_pt_attributes): New.
(btrace_conf_children): Add support for "pt".
* btrace.h: Include "intel-pt.h".
(btrace_pt_error): New.
* common/btrace-common.c (btrace_format_string, btrace_data_fini)
(btrace_data_empty): Support BTRACE_FORMAT_PT.
* common/btrace-common.h (btrace_format): Add BTRACE_FORMAT_PT.
(struct btrace_config_pt): New.
(struct btrace_config)<pt>: New.
(struct btrace_data_pt_config, struct btrace_data_pt): New.
(struct btrace_data)<pt>: New.
* features/btrace-conf.dtd (btrace-conf)<pt>: New.
(pt): New.
* features/btrace.dtd (btrace)<pt>: New.
(pt, pt-config, cpu): New.
* nat/linux-btrace.c (perf_event_read, perf_event_read_all)
(perf_event_pt_event_type, kernel_supports_pt)
(linux_supports_pt): New.
(linux_supports_btrace): Support BTRACE_FORMAT_PT.
(linux_enable_bts): Free tinfo on error.
(linux_enable_pt): New.
(linux_enable_btrace): Support BTRACE_FORMAT_PT.
(linux_disable_pt): New.
(linux_disable_btrace): Support BTRACE_FORMAT_PT.
(linux_fill_btrace_pt_config, linux_read_pt): New.
(linux_read_btrace): Support BTRACE_FORMAT_PT.
* nat/linux-btrace.h (struct btrace_tinfo_pt): New.
(struct btrace_target_info)<pt>: New.
* record-btrace.c (set_record_btrace_pt_cmdlist)
(show_record_btrace_pt_cmdlist): New.
(record_btrace_print_pt_conf): New.
(record_btrace_print_conf): Support BTRACE_FORMAT_PT.
(btrace_ui_out_decode_error): Support BTRACE_FORMAT_PT.
(cmd_record_btrace_pt_start): New.
(cmd_record_btrace_start): Support BTRACE_FORMAT_PT.
(cmd_set_record_btrace_pt, cmd_show_record_btrace_pt): New.
(_initialize_record_btrace): Add new commands.
* remote.c (PACKET_Qbtrace_pt, PACKET_Qbtrace_conf_pt_size): New.
(remote_protocol_features): Add "Qbtrace:pt".
Add "Qbtrace-conf:pt:size".
(remote_supports_btrace): Support BTRACE_FORMAT_PT.
(btrace_sync_conf): Support PACKET_Qbtrace_conf_pt_size.
(remote_enable_btrace): Support BTRACE_FORMAT_PT.
(_initialize_remote): Add new commands.
gdbserver/
* linux-low.c: Include "rsp-low.h"
(linux_low_encode_pt_config, linux_low_encode_raw): New.
(linux_low_read_btrace): Support BTRACE_FORMAT_PT.
(linux_low_btrace_conf): Support BTRACE_FORMAT_PT.
(handle_btrace_enable_pt): New.
(handle_btrace_general_set): Support "pt".
(handle_btrace_conf_general_set): Support "pt:size".
doc/
* gdb.texinfo (Process Record and Replay): Spell out that variables
and registers are not available during btrace replay.
Describe the new "record btrace pt" command.
Describe the new "set|show record btrace pt buffer-size" options.
(General Query Packets): Describe the new Qbtrace:pt and
Qbtrace-conf:pt:size packets.
Expand "bts" to "Branch Trace Store".
Update the branch trace DTD.
2014-01-24 20:45:47 +08:00
|
|
|
Qbtrace:pt
|
2020-06-05 18:24:20 +08:00
|
|
|
Enable Intel Processor Trace-based branch tracing for the current
|
btrace: support Intel(R) Processor Trace
Adds a new command "record btrace pt" to configure the kernel to use
Intel(R) Processor Trace instead of Branch Trace Strore.
The "record btrace" command chooses the tracing format automatically.
Intel(R) Processor Trace support requires Linux 4.1 and libipt.
gdb/
* NEWS: Announce new commands "record btrace pt" and "record pt".
Announce new options "set|show record btrace pt buffer-size".
* btrace.c: Include "rsp-low.h".
Include "inttypes.h".
(btrace_add_pc): Add forward declaration.
(pt_reclassify_insn, ftrace_add_pt, btrace_pt_readmem_callback)
(pt_translate_cpu_vendor, btrace_finalize_ftrace_pt)
(btrace_compute_ftrace_pt): New.
(btrace_compute_ftrace): Support BTRACE_FORMAT_PT.
(check_xml_btrace_version): Update version check.
(parse_xml_raw, parse_xml_btrace_pt_config_cpu)
(parse_xml_btrace_pt_raw, parse_xml_btrace_pt)
(btrace_pt_config_cpu_attributes, btrace_pt_config_children)
(btrace_pt_children): New.
(btrace_children): Add support for "pt".
(parse_xml_btrace_conf_pt, btrace_conf_pt_attributes): New.
(btrace_conf_children): Add support for "pt".
* btrace.h: Include "intel-pt.h".
(btrace_pt_error): New.
* common/btrace-common.c (btrace_format_string, btrace_data_fini)
(btrace_data_empty): Support BTRACE_FORMAT_PT.
* common/btrace-common.h (btrace_format): Add BTRACE_FORMAT_PT.
(struct btrace_config_pt): New.
(struct btrace_config)<pt>: New.
(struct btrace_data_pt_config, struct btrace_data_pt): New.
(struct btrace_data)<pt>: New.
* features/btrace-conf.dtd (btrace-conf)<pt>: New.
(pt): New.
* features/btrace.dtd (btrace)<pt>: New.
(pt, pt-config, cpu): New.
* nat/linux-btrace.c (perf_event_read, perf_event_read_all)
(perf_event_pt_event_type, kernel_supports_pt)
(linux_supports_pt): New.
(linux_supports_btrace): Support BTRACE_FORMAT_PT.
(linux_enable_bts): Free tinfo on error.
(linux_enable_pt): New.
(linux_enable_btrace): Support BTRACE_FORMAT_PT.
(linux_disable_pt): New.
(linux_disable_btrace): Support BTRACE_FORMAT_PT.
(linux_fill_btrace_pt_config, linux_read_pt): New.
(linux_read_btrace): Support BTRACE_FORMAT_PT.
* nat/linux-btrace.h (struct btrace_tinfo_pt): New.
(struct btrace_target_info)<pt>: New.
* record-btrace.c (set_record_btrace_pt_cmdlist)
(show_record_btrace_pt_cmdlist): New.
(record_btrace_print_pt_conf): New.
(record_btrace_print_conf): Support BTRACE_FORMAT_PT.
(btrace_ui_out_decode_error): Support BTRACE_FORMAT_PT.
(cmd_record_btrace_pt_start): New.
(cmd_record_btrace_start): Support BTRACE_FORMAT_PT.
(cmd_set_record_btrace_pt, cmd_show_record_btrace_pt): New.
(_initialize_record_btrace): Add new commands.
* remote.c (PACKET_Qbtrace_pt, PACKET_Qbtrace_conf_pt_size): New.
(remote_protocol_features): Add "Qbtrace:pt".
Add "Qbtrace-conf:pt:size".
(remote_supports_btrace): Support BTRACE_FORMAT_PT.
(btrace_sync_conf): Support PACKET_Qbtrace_conf_pt_size.
(remote_enable_btrace): Support BTRACE_FORMAT_PT.
(_initialize_remote): Add new commands.
gdbserver/
* linux-low.c: Include "rsp-low.h"
(linux_low_encode_pt_config, linux_low_encode_raw): New.
(linux_low_read_btrace): Support BTRACE_FORMAT_PT.
(linux_low_btrace_conf): Support BTRACE_FORMAT_PT.
(handle_btrace_enable_pt): New.
(handle_btrace_general_set): Support "pt".
(handle_btrace_conf_general_set): Support "pt:size".
doc/
* gdb.texinfo (Process Record and Replay): Spell out that variables
and registers are not available during btrace replay.
Describe the new "record btrace pt" command.
Describe the new "set|show record btrace pt buffer-size" options.
(General Query Packets): Describe the new Qbtrace:pt and
Qbtrace-conf:pt:size packets.
Expand "bts" to "Branch Trace Store".
Update the branch trace DTD.
2014-01-24 20:45:47 +08:00
|
|
|
process. The remote stub reports support for this packet to GDB's
|
|
|
|
|
qSupported query.
|
|
|
|
|
|
|
|
|
|
Qbtrace-conf:pt:size
|
2016-01-12 23:03:11 +08:00
|
|
|
Set the requested ring buffer size for branch tracing in Intel Processor
|
btrace: support Intel(R) Processor Trace
Adds a new command "record btrace pt" to configure the kernel to use
Intel(R) Processor Trace instead of Branch Trace Strore.
The "record btrace" command chooses the tracing format automatically.
Intel(R) Processor Trace support requires Linux 4.1 and libipt.
gdb/
* NEWS: Announce new commands "record btrace pt" and "record pt".
Announce new options "set|show record btrace pt buffer-size".
* btrace.c: Include "rsp-low.h".
Include "inttypes.h".
(btrace_add_pc): Add forward declaration.
(pt_reclassify_insn, ftrace_add_pt, btrace_pt_readmem_callback)
(pt_translate_cpu_vendor, btrace_finalize_ftrace_pt)
(btrace_compute_ftrace_pt): New.
(btrace_compute_ftrace): Support BTRACE_FORMAT_PT.
(check_xml_btrace_version): Update version check.
(parse_xml_raw, parse_xml_btrace_pt_config_cpu)
(parse_xml_btrace_pt_raw, parse_xml_btrace_pt)
(btrace_pt_config_cpu_attributes, btrace_pt_config_children)
(btrace_pt_children): New.
(btrace_children): Add support for "pt".
(parse_xml_btrace_conf_pt, btrace_conf_pt_attributes): New.
(btrace_conf_children): Add support for "pt".
* btrace.h: Include "intel-pt.h".
(btrace_pt_error): New.
* common/btrace-common.c (btrace_format_string, btrace_data_fini)
(btrace_data_empty): Support BTRACE_FORMAT_PT.
* common/btrace-common.h (btrace_format): Add BTRACE_FORMAT_PT.
(struct btrace_config_pt): New.
(struct btrace_config)<pt>: New.
(struct btrace_data_pt_config, struct btrace_data_pt): New.
(struct btrace_data)<pt>: New.
* features/btrace-conf.dtd (btrace-conf)<pt>: New.
(pt): New.
* features/btrace.dtd (btrace)<pt>: New.
(pt, pt-config, cpu): New.
* nat/linux-btrace.c (perf_event_read, perf_event_read_all)
(perf_event_pt_event_type, kernel_supports_pt)
(linux_supports_pt): New.
(linux_supports_btrace): Support BTRACE_FORMAT_PT.
(linux_enable_bts): Free tinfo on error.
(linux_enable_pt): New.
(linux_enable_btrace): Support BTRACE_FORMAT_PT.
(linux_disable_pt): New.
(linux_disable_btrace): Support BTRACE_FORMAT_PT.
(linux_fill_btrace_pt_config, linux_read_pt): New.
(linux_read_btrace): Support BTRACE_FORMAT_PT.
* nat/linux-btrace.h (struct btrace_tinfo_pt): New.
(struct btrace_target_info)<pt>: New.
* record-btrace.c (set_record_btrace_pt_cmdlist)
(show_record_btrace_pt_cmdlist): New.
(record_btrace_print_pt_conf): New.
(record_btrace_print_conf): Support BTRACE_FORMAT_PT.
(btrace_ui_out_decode_error): Support BTRACE_FORMAT_PT.
(cmd_record_btrace_pt_start): New.
(cmd_record_btrace_start): Support BTRACE_FORMAT_PT.
(cmd_set_record_btrace_pt, cmd_show_record_btrace_pt): New.
(_initialize_record_btrace): Add new commands.
* remote.c (PACKET_Qbtrace_pt, PACKET_Qbtrace_conf_pt_size): New.
(remote_protocol_features): Add "Qbtrace:pt".
Add "Qbtrace-conf:pt:size".
(remote_supports_btrace): Support BTRACE_FORMAT_PT.
(btrace_sync_conf): Support PACKET_Qbtrace_conf_pt_size.
(remote_enable_btrace): Support BTRACE_FORMAT_PT.
(_initialize_remote): Add new commands.
gdbserver/
* linux-low.c: Include "rsp-low.h"
(linux_low_encode_pt_config, linux_low_encode_raw): New.
(linux_low_read_btrace): Support BTRACE_FORMAT_PT.
(linux_low_btrace_conf): Support BTRACE_FORMAT_PT.
(handle_btrace_enable_pt): New.
(handle_btrace_general_set): Support "pt".
(handle_btrace_conf_general_set): Support "pt:size".
doc/
* gdb.texinfo (Process Record and Replay): Spell out that variables
and registers are not available during btrace replay.
Describe the new "record btrace pt" command.
Describe the new "set|show record btrace pt buffer-size" options.
(General Query Packets): Describe the new Qbtrace:pt and
Qbtrace-conf:pt:size packets.
Expand "bts" to "Branch Trace Store".
Update the branch trace DTD.
2014-01-24 20:45:47 +08:00
|
|
|
Trace format.
|
|
|
|
|
|
remote+docs: software/hardware breakpoint traps
This adjusts target remote to tell the core whether a trap was caused
by a breakpoint.
To that end, the patch teaches GDB about new RSP stop reasons "T05
swbreak" and "T05 hwbreak", that remote targets report back to GDB,
similarly to how "T05 watch" indicates a stop caused by a watchpoint.
Because targets that can report these events are expected to
themselves adjust the PC after a software breakpoint, these new stop
reasons must only be reported if the stub is talking to a GDB that
understands them. Because of that, the use of the new stop reasons
needs to be handshaked on initial connection, using the qSupported
mechanism. GDB simply sends "swbreak+" in its qSupports query, and
the stub reports back "swbreak+" too.
Because these new stop reasons are required to fix a fundamental
non-stop mode problem, this commit extends the remote non-stop intro
section in the manual, documenting the events as required.
To be clear, GDB will still cope with remote targets that don't
support these new stop reasons; it will behave just like today.
Tested on x86-64 Fedora 20, native and gdbserver.
gdb/ChangeLog:
2015-03-04 Pedro Alves <palves@redhat.com>
* NEWS: Mention the new "swbreak" and "hwbreak" stop reasons.
* remote.c (struct remote_state) <remote_stopped_by_watchpoint_p>:
Delete field.
<stop_reason>: New field.
(PACKET_swbreak_feature, PACKET_hwbreak_feature): New enum values.
(packet_set_cmd_state): New function.
(remote_protocol_features): Register the "swbreak" and "hwbreak"
features.
(remote_query_supported): If not disabled with the corresponding
"set remote foo-packet" command, report support for the swbreak
and hwbreak features.
(struct stop_reply) <remote_stopped_by_watchpoint_p>: Delete
field.
<stop_reason>: New field.
(remote_parse_stop_reply): Handle "swbreak" and "hwbreak".
(remote_wait_as): Adjust.
(remote_stopped_by_sw_breakpoint)
(remote_supports_stopped_by_sw_breakpoint)
(remote_stopped_by_hw_breakpoint)
(remote_supports_stopped_by_hw_breakpoint): New functions.
(remote_stopped_by_watchpoint): New function.
(init_remote_ops): Install them.
(_initialize_remote): Register new "set/show remote
swbreak-feature-packet" and "set/show remote
swbreak-feature-packet" commands.
gdb/doc/ChangeLog:
2015-03-04 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Remote Configuration): Document the "set/show
remote swbreak-feature-packet" and "set/show remote
hwbreak-feature-packet" commands.
(Packets) <Z0>: Add cross link to the "swbreak" stop reason's
decription.
(Stop Reply Packets): Document the swbreak and hwbreak stop
reasons.
(General Query Packets): Document the swbreak and hwbreak
qSupported features.
(Remote Non-Stop): Explain that swbreak and hwbreak are required.
2015-03-05 04:41:16 +08:00
|
|
|
swbreak stop reason
|
|
|
|
|
Indicates a memory breakpoint instruction was executed, irrespective
|
|
|
|
|
of whether it was GDB that planted the breakpoint or the breakpoint
|
|
|
|
|
is hardcoded in the program. This is required for correct non-stop
|
|
|
|
|
mode operation.
|
|
|
|
|
|
|
|
|
|
hwbreak stop reason
|
|
|
|
|
Indicates the target stopped for a hardware breakpoint. This is
|
|
|
|
|
required for correct non-stop mode operation.
|
|
|
|
|
|
2015-03-12 01:53:57 +08:00
|
|
|
vFile:fstat:
|
|
|
|
|
Return information about files on the remote system.
|
|
|
|
|
|
2015-04-17 16:47:30 +08:00
|
|
|
qXfer:exec-file:read
|
|
|
|
|
Return the full absolute name of the file that was executed to
|
|
|
|
|
create a process running on the remote system.
|
|
|
|
|
|
2015-06-10 21:28:44 +08:00
|
|
|
vFile:setfs:
|
|
|
|
|
Select the filesystem on which vFile: operations with filename
|
|
|
|
|
arguments will operate. This is required for GDB to be able to
|
|
|
|
|
access files on remote targets where the remote stub does not
|
|
|
|
|
share a common filesystem with the inferior(s).
|
|
|
|
|
|
2015-05-13 00:52:47 +08:00
|
|
|
fork stop reason
|
|
|
|
|
Indicates that a fork system call was executed.
|
|
|
|
|
|
|
|
|
|
vfork stop reason
|
|
|
|
|
Indicates that a vfork system call was executed.
|
|
|
|
|
|
|
|
|
|
vforkdone stop reason
|
|
|
|
|
Indicates that a vfork child of the specified process has executed
|
|
|
|
|
an exec or exit, allowing the vfork parent to resume execution.
|
|
|
|
|
|
|
|
|
|
fork-events and vfork-events features in qSupported
|
|
|
|
|
The qSupported packet allows GDB to request support for fork and
|
|
|
|
|
vfork events using new 'gdbfeatures' fork-events and vfork-events,
|
|
|
|
|
and the qSupported response can contain the corresponding
|
|
|
|
|
'stubfeatures'. Set and show commands can be used to display
|
|
|
|
|
whether these features are enabled.
|
|
|
|
|
|
|
|
|
|
* Extended-remote fork events
|
|
|
|
|
|
|
|
|
|
** GDB now has support for fork events on extended-remote Linux
|
|
|
|
|
targets. For targets with Linux kernels 2.5.60 and later, this
|
|
|
|
|
enables follow-fork-mode and detach-on-fork for both fork and
|
|
|
|
|
vfork, as well as fork and vfork catchpoints.
|
|
|
|
|
|
2013-11-28 23:39:12 +08:00
|
|
|
* The info record command now shows the recording format and the
|
|
|
|
|
branch tracing configuration for the current thread when using
|
|
|
|
|
the btrace record target.
|
|
|
|
|
For the BTS format, it shows the ring buffer size.
|
|
|
|
|
|
2015-02-17 23:43:48 +08:00
|
|
|
* GDB now has support for DTrace USDT (Userland Static Defined
|
|
|
|
|
Tracing) probes. The supported targets are x86_64-*-linux-gnu.
|
|
|
|
|
|
S390: Add vector register support to gdb
Recognize S/390 targets with the new vector feature and present their
vector registers appropriately: as 32 new 128-bit wide registers
v0-v31, where the first 16 embed the floating point registers f0-f15.
Each of the full registers v0-v15 is modelled as a pseudo register.
gdb/ChangeLog:
* s390-linux-nat.c (have_regset_vxrs): New static variable.
(s390_linux_fetch_inferior_registers): Handle vector registers, if
present.
(s390_linux_store_inferior_registers): Likewise.
(s390_get_hwcap): Remove function. Embed its logic...
(s390_read_description): ...here. Yield a target description with
vector registers if applicable.
* s390-linux-tdep.c: Include "features/s390-vx-linux64.c",
"features/s390-tevx-linux64.c", "features/s390x-vx-linux64.c", and
"features/s390x-tevx-linux64.c".
(struct gdbarch_tdep) <v0_full_regnum>: New field.
(s390_dwarf_regmap): Add vector registers. Remove bogus entries
for "GNU/Linux-specific registers".
(s390_dwarf_reg_r0l): New enum value.
(s390_dwarf_reg_to_regnum): Support vector registers.
(s390_adjust_frame_regnum): Adjust pseudo DWARF register numbers
of GPR lower halves.
(regnum_is_vxr_full): New function.
(s390_register_name): New function.
(s390_pseudo_register_name): Handle v0-v15, which are composed of
f0-f15 and v0l-v15l.
(s390_pseudo_register_type): Likewise.
(s390_pseudo_register_read): Likewise.
(s390_pseudo_register_write): Likewise.
(s390_value_from_register): Account for the fact that values are
placed left-justified in vector registers.
(s390_pseudo_register_reggroup_p): Add pseudo registers v0-v15 to
the vector reggroup and omit them from the general reggroup.
(s390_regmap_vxrs_low, s390_regmap_vxrs_high): New register maps.
(s390_vxrs_low_regset, s390_vxrs_high_regset): New regsets.
(s390_iterate_over_regset_sections): Add iterations for the two
new vector regsets.
(s390_core_read_description): Yield a target description with
vector registers if applicable.
(s390_gdbarch_init): Handle target descriptions with vector
registers. Add "register_name" gdbarch method.
(_initialize_s390_tdep): Call new tdesc initialization functions.
* s390-linux-tdep.h (HWCAP_S390_VX): New macro.
(S390_V0_LOWER_REGNUM, S390_V1_LOWER_REGNUM, S390_V2_LOWER_REGNUM)
(S390_V3_LOWER_REGNUM, S390_V4_LOWER_REGNUM, S390_V5_LOWER_REGNUM)
(S390_V6_LOWER_REGNUM, S390_V7_LOWER_REGNUM, S390_V8_LOWER_REGNUM)
(S390_V9_LOWER_REGNUM, S390_V10_LOWER_REGNUM)
(S390_V11_LOWER_REGNUM, S390_V12_LOWER_REGNUM)
(S390_V13_LOWER_REGNUM, S390_V14_LOWER_REGNUM)
(S390_V15_LOWER_REGNUM, S390_V16_REGNUM, S390_V17_REGNUM)
(S390_V18_REGNUM, S390_V19_REGNUM, S390_V20_REGNUM)
(S390_V21_REGNUM, S390_V22_REGNUM, S390_V23_REGNUM)
(S390_V24_REGNUM, S390_V25_REGNUM, S390_V26_REGNUM)
(S390_V27_REGNUM, S390_V28_REGNUM, S390_V29_REGNUM)
(S390_V30_REGNUM, S390_V31_REGNUM): New macros.
(S390_NUM_REGS): Adjust value.
(s390_vxrs_low_regset, s390_vxrs_high_regset): Declare.
(tdesc_s390_vx_linux64, tdesc_s390_tevx_linux64)
(tdesc_s390x_vx_linux64, tdesc_s390x_tevx_linux64): Likewise.
* NEWS: Announce S/390 vector register support.
2015-03-02 17:57:39 +08:00
|
|
|
* GDB now supports access to vector registers on S/390 GNU/Linux
|
|
|
|
|
targets.
|
|
|
|
|
|
Remove --xdb
Pedro Alves:
The commands that enables aren't even documented in the manual.
Judging from that, I assume that only wdb users would ever really
be using the --xdb switch.
I think it's time to drop "support" for the --xdb switch too. I
looked through the commands that that exposes, the only that looked
potentially interesting was "go", but then it's just an alias
for "tbreak+jump", which can easily be done with "define go...end".
I'd rather free up the "go" name for something potentially
more interesting (either run control, or maybe even unrelated,
e.g., for golang).
gdb/ChangeLog
2015-04-11 Jan Kratochvil <jan.kratochvil@redhat.com>
* NEWS (Changes since GDB 7.9): Add removed -xdb.
* breakpoint.c (command_line_is_silent): Remove xdb_commands
conditional.
(_initialize_breakpoint): Remove xdb_commands for bc, ab, sb, db, ba
and lb.
* cli/cli-cmds.c (_initialize_cli_cmds): Remove xdb_commands for v and
va.
* cli/cli-decode.c (find_command_name_length): Remove xdb_commands
conditional.
* defs.h (xdb_commands): Remove declaration.
* f-valprint.c (_initialize_f_valprint): Remove xdb_commands for lc.
* guile/scm-cmd.c (command_classes): Remove xdb from comment.
* infcmd.c (run_no_args_command, go_command): Remove.
(_initialize_infcmd): Remove xdb_commands for S, go, g, R and lr.
* infrun.c (xdb_handle_command): Remove.
(_initialize_infrun): Remove xdb_commands for lz and z.
* main.c (xdb_commands): Remove variable.
(captured_main): Remove "xdb" from long_options.
(print_gdb_help): Remove --xdb from help.
* python/py-cmd.c (gdbpy_initialize_commands): Remove xdb from comment.
* source.c (_initialize_source): Remove xdb_commands for D, ld, / and ?.
* stack.c (backtrace_full_command, args_plus_locals_info)
(current_frame_command): Remove.
(_initialize_stack): Remove xdb_commands for t, T and l.
* symtab.c (_initialize_symtab): Remove xdb_commands for lf and lg.
* thread.c (_initialize_thread): Remove xdb_commands condition.
* tui/tui-layout.c (tui_toggle_layout_command)
(tui_toggle_split_layout_command, tui_handle_xdb_layout): Remove.
(_initialize_tui_layout): Remove xdb_commands for td and ts.
* tui/tui-regs.c (tui_scroll_regs_forward_command)
(tui_scroll_regs_backward_command): Remove.
(_initialize_tui_regs): Remove xdb_commands for fr, gr, sr, +r and -r.
* tui/tui-win.c (tui_xdb_set_win_height_command): Remove.
(_initialize_tui_win): Remove xdb_commands for U and w.
* utils.c (pagination_on_command, pagination_off_command): Remove.
(initialize_utils): Remove xdb_commands for am and sm.
gdb/doc/ChangeLog
2015-04-11 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.texinfo (Mode Options): Remove -xdb.
2015-04-12 01:49:03 +08:00
|
|
|
* Removed command line options
|
|
|
|
|
|
|
|
|
|
-xdb HP-UX XDB compatibility mode.
|
|
|
|
|
|
2015-03-14 18:01:17 +08:00
|
|
|
* Removed targets and native configurations
|
|
|
|
|
|
|
|
|
|
HP/PA running HP-UX hppa*-*-hpux*
|
|
|
|
|
Itanium running HP-UX ia64-*-hpux*
|
|
|
|
|
|
2013-11-12 23:58:45 +08:00
|
|
|
* New configure options
|
|
|
|
|
|
|
|
|
|
--with-intel-pt
|
|
|
|
|
This configure option allows the user to build GDB with support for
|
2016-01-12 23:03:11 +08:00
|
|
|
Intel Processor Trace (default: auto). This requires libipt.
|
2013-11-12 23:58:45 +08:00
|
|
|
|
|
|
|
|
--with-libipt-prefix=PATH
|
|
|
|
|
Specify the path to the version of libipt that GDB should use.
|
|
|
|
|
$PATH/include should contain the intel-pt.h header and
|
|
|
|
|
$PATH/lib should contain the libipt.so library.
|
|
|
|
|
|
2015-05-14 01:31:00 +08:00
|
|
|
*** Changes in GDB 7.9.1
|
|
|
|
|
|
|
|
|
|
* Python Scripting
|
|
|
|
|
|
|
|
|
|
** Xmethods can now specify a result type.
|
|
|
|
|
|
2015-01-13 20:24:45 +08:00
|
|
|
*** Changes in GDB 7.9
|
2014-06-12 00:52:29 +08:00
|
|
|
|
2014-09-13 02:29:11 +08:00
|
|
|
* GDB now supports hardware watchpoints on x86 GNU Hurd.
|
|
|
|
|
|
2014-09-04 07:34:47 +08:00
|
|
|
* Python Scripting
|
2014-09-19 01:09:12 +08:00
|
|
|
|
|
|
|
|
** You can now access frame registers from Python scripts.
|
|
|
|
|
** New attribute 'producer' for gdb.Symtab objects.
|
2014-10-18 01:57:26 +08:00
|
|
|
** gdb.Objfile objects have a new attribute "progspace",
|
|
|
|
|
which is the gdb.Progspace object of the containing program space.
|
2014-12-09 00:50:48 +08:00
|
|
|
** gdb.Objfile objects have a new attribute "owner".
|
2014-12-05 03:32:24 +08:00
|
|
|
** gdb.Objfile objects have a new attribute "build_id",
|
|
|
|
|
which is the build ID generated when the file was built.
|
2014-12-05 04:01:22 +08:00
|
|
|
** gdb.Objfile objects have a new method "add_separate_debug_file".
|
2014-10-18 02:12:17 +08:00
|
|
|
** A new event "gdb.clear_objfiles" has been added, triggered when
|
|
|
|
|
selecting a new file to debug.
|
2014-10-31 08:05:17 +08:00
|
|
|
** You can now add attributes to gdb.Objfile and gdb.Progspace objects.
|
2014-12-13 01:48:13 +08:00
|
|
|
** New function gdb.lookup_objfile.
|
2014-09-04 07:34:47 +08:00
|
|
|
|
2014-12-15 16:29:21 +08:00
|
|
|
New events which are triggered when GDB modifies the state of the
|
|
|
|
|
inferior.
|
|
|
|
|
|
|
|
|
|
** gdb.events.inferior_call_pre: Function call is about to be made.
|
|
|
|
|
** gdb.events.inferior_call_post: Function call has just been made.
|
|
|
|
|
** gdb.events.memory_changed: A memory location has been altered.
|
|
|
|
|
** gdb.events.register_changed: A register has been altered.
|
|
|
|
|
|
2014-09-07 00:15:44 +08:00
|
|
|
* New Python-based convenience functions:
|
|
|
|
|
|
|
|
|
|
** $_caller_is(name [, number_of_frames])
|
|
|
|
|
** $_caller_matches(regexp [, number_of_frames])
|
|
|
|
|
** $_any_caller_is(name [, number_of_frames])
|
|
|
|
|
** $_any_caller_matches(regexp [, number_of_frames])
|
|
|
|
|
|
the "compile" command
This final patch adds the new "compile" command and subcommands, and
all the machinery needed to make it work.
A shared library supplied by gcc is used for all communications with
gcc. Types and most aspects of symbols are provided directly by gdb
to the compiler using this library.
gdb provides some information about the user's code using plain text.
Macros are emitted this way, and DWARF location expressions (and
bounds for VLA) are compiled to C code.
This hybrid approach was taken because, on the one hand, it is better
to provide global declarations and such on demand; but on the other
hand, for local variables, translating DWARF location expressions to C
was much simpler than exporting a full compiler API to gdb -- the same
result, only easier to implement, understand, and debug.
In the ordinary mode, the user's expression is wrapped in a dummy
function. After compilation, gdb inserts the resulting object code
into the inferior, then calls this function.
Access to local variables is provided by noting which registers are
used by location expressions, and passing a structure of register
values into the function. Writes to registers are supported by
copying out these values after the function returns.
This approach was taken so that we could eventually implement other
more interesting features based on this same infrastructure; for
example, we're planning to investigate inferior-side breakpoint
conditions.
gdb/ChangeLog
2014-12-12 Phil Muldoon <pmuldoon@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Tom Tromey <tromey@redhat.com>
* NEWS: Update.
* symtab.h (struct symbol_computed_ops) <generate_c_location>: New
field.
* p-lang.c (pascal_language_defn): Update.
* opencl-lang.c (opencl_language_defn): Update.
* objc-lang.c (objc_language_defn): Update.
* m2-lang.c (m2_language_defn): Update.
* language.h (struct language_defn) <la_get_compile_instance,
la_compute_program>: New fields.
* language.c (unknown_language_defn, auto_language_defn)
(local_language_defn): Update.
* jv-lang.c (java_language_defn): Update.
* go-lang.c (go_language_defn): Update.
* f-lang.c (f_language_defn): Update.
* dwarf2loc.h (dwarf2_compile_property_to_c): Declare.
* dwarf2loc.c (dwarf2_compile_property_to_c)
(locexpr_generate_c_location, loclist_generate_c_location): New
functions.
(dwarf2_locexpr_funcs, dwarf2_loclist_funcs): Update.
* defs.h (enum compile_i_scope_types): New.
(enum command_control_type) <compile_control>: New constant.
(struct command_line) <control_u>: New field.
* d-lang.c (d_language_defn): Update.
* compile/compile.c: New file.
* compile/compile-c-support.c: New file.
* compile/compile-c-symbols.c: New file.
* compile/compile-c-types.c: New file.
* compile/compile.h: New file.
* compile/compile-internal.h: New file.
* compile/compile-loc2c.c: New file.
* compile/compile-object-load.c: New file.
* compile/compile-object-load.h: New file.
* compile/compile-object-run.c: New file.
* compile/compile-object-run.h: New file.
* cli/cli-script.c (multi_line_command_p, print_command_lines)
(execute_control_command, process_next_line)
(recurse_read_control_structure): Handle compile_control.
* c-lang.h (c_get_compile_context, c_compute_program): Declare.
* c-lang.c (c_language_defn, cplus_language_defn)
(asm_language_defn, minimal_language_defn): Update.
* ada-lang.c (ada_language_defn): Update.
* Makefile.in (SUBDIR_GCC_COMPILE_OBS, SUBDIR_GCC_COMPILE_SRCS):
New variables.
(SFILES): Add SUBDIR_GCC_COMPILE_SRCS.
(HFILES_NO_SRCDIR): Add compile.h.
(COMMON_OBS): Add SUBDIR_GCC_COMPILE_OBS.
(INIT_FILES): Add SUBDIR_GCC_COMPILE_SRCS.
(compile.o, compile-c-types.o, compile-c-symbols.o)
(compile-object-load.o, compile-object-run.o, compile-loc2c.o)
(compile-c-support.o): New targets.
gdb/doc/ChangeLog
2014-12-12 Phil Muldoon <pmuldoon@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.texinfo (Altering): Update.
(Compiling and Injecting Code): New node.
gdb/testsuite/ChangeLog
2014-12-12 Phil Muldoon <pmuldoon@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Tom Tromey <tromey@redhat.com>
* configure.ac: Add gdb.compile/.
* configure: Regenerate.
* gdb.compile/Makefile.in: New file.
* gdb.compile/compile-ops.exp: New file.
* gdb.compile/compile-ops.c: New file.
* gdb.compile/compile-tls.c: New file.
* gdb.compile/compile-tls.exp: New file.
* gdb.compile/compile-constvar.S: New file.
* gdb.compile/compile-constvar.c: New file.
* gdb.compile/compile-mod.c: New file.
* gdb.compile/compile-nodebug.c: New file.
* gdb.compile/compile-setjmp-mod.c: New file.
* gdb.compile/compile-setjmp.c: New file.
* gdb.compile/compile-setjmp.exp: New file.
* gdb.compile/compile-shlib.c: New file.
* gdb.compile/compile.c: New file.
* gdb.compile/compile.exp: New file.
* lib/gdb.exp (skip_compile_feature_tests): New proc.
2014-05-15 04:35:45 +08:00
|
|
|
* GDB now supports the compilation and injection of source code into
|
|
|
|
|
the inferior. GDB will use GCC 5.0 or higher built with libcc1.so
|
|
|
|
|
to compile the source code to object code, and if successful, inject
|
|
|
|
|
and execute that code within the current context of the inferior.
|
|
|
|
|
Currently the C language is supported. The commands used to
|
|
|
|
|
interface with this new feature are:
|
|
|
|
|
|
|
|
|
|
compile code [-raw|-r] [--] [source code]
|
|
|
|
|
compile file [-raw|-r] filename
|
|
|
|
|
|
2014-09-14 12:44:00 +08:00
|
|
|
* New commands
|
|
|
|
|
|
2015-01-12 06:06:34 +08:00
|
|
|
demangle [-l language] [--] name
|
|
|
|
|
Demangle "name" in the specified language, or the current language
|
|
|
|
|
if elided. This command is renamed from the "maint demangle" command.
|
|
|
|
|
The latter is kept as a no-op to avoid "maint demangle" being interpreted
|
|
|
|
|
as "maint demangler-warning".
|
|
|
|
|
|
2014-09-14 12:44:00 +08:00
|
|
|
queue-signal signal-name-or-number
|
|
|
|
|
Queue a signal to be delivered to the thread when it is resumed.
|
|
|
|
|
|
2014-12-01 03:25:48 +08:00
|
|
|
add-auto-load-scripts-directory directory
|
|
|
|
|
Add entries to the list of directories from which to load auto-loaded
|
|
|
|
|
scripts.
|
|
|
|
|
|
2014-12-13 00:11:22 +08:00
|
|
|
maint print user-registers
|
|
|
|
|
List all currently available "user" registers.
|
|
|
|
|
|
the "compile" command
This final patch adds the new "compile" command and subcommands, and
all the machinery needed to make it work.
A shared library supplied by gcc is used for all communications with
gcc. Types and most aspects of symbols are provided directly by gdb
to the compiler using this library.
gdb provides some information about the user's code using plain text.
Macros are emitted this way, and DWARF location expressions (and
bounds for VLA) are compiled to C code.
This hybrid approach was taken because, on the one hand, it is better
to provide global declarations and such on demand; but on the other
hand, for local variables, translating DWARF location expressions to C
was much simpler than exporting a full compiler API to gdb -- the same
result, only easier to implement, understand, and debug.
In the ordinary mode, the user's expression is wrapped in a dummy
function. After compilation, gdb inserts the resulting object code
into the inferior, then calls this function.
Access to local variables is provided by noting which registers are
used by location expressions, and passing a structure of register
values into the function. Writes to registers are supported by
copying out these values after the function returns.
This approach was taken so that we could eventually implement other
more interesting features based on this same infrastructure; for
example, we're planning to investigate inferior-side breakpoint
conditions.
gdb/ChangeLog
2014-12-12 Phil Muldoon <pmuldoon@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Tom Tromey <tromey@redhat.com>
* NEWS: Update.
* symtab.h (struct symbol_computed_ops) <generate_c_location>: New
field.
* p-lang.c (pascal_language_defn): Update.
* opencl-lang.c (opencl_language_defn): Update.
* objc-lang.c (objc_language_defn): Update.
* m2-lang.c (m2_language_defn): Update.
* language.h (struct language_defn) <la_get_compile_instance,
la_compute_program>: New fields.
* language.c (unknown_language_defn, auto_language_defn)
(local_language_defn): Update.
* jv-lang.c (java_language_defn): Update.
* go-lang.c (go_language_defn): Update.
* f-lang.c (f_language_defn): Update.
* dwarf2loc.h (dwarf2_compile_property_to_c): Declare.
* dwarf2loc.c (dwarf2_compile_property_to_c)
(locexpr_generate_c_location, loclist_generate_c_location): New
functions.
(dwarf2_locexpr_funcs, dwarf2_loclist_funcs): Update.
* defs.h (enum compile_i_scope_types): New.
(enum command_control_type) <compile_control>: New constant.
(struct command_line) <control_u>: New field.
* d-lang.c (d_language_defn): Update.
* compile/compile.c: New file.
* compile/compile-c-support.c: New file.
* compile/compile-c-symbols.c: New file.
* compile/compile-c-types.c: New file.
* compile/compile.h: New file.
* compile/compile-internal.h: New file.
* compile/compile-loc2c.c: New file.
* compile/compile-object-load.c: New file.
* compile/compile-object-load.h: New file.
* compile/compile-object-run.c: New file.
* compile/compile-object-run.h: New file.
* cli/cli-script.c (multi_line_command_p, print_command_lines)
(execute_control_command, process_next_line)
(recurse_read_control_structure): Handle compile_control.
* c-lang.h (c_get_compile_context, c_compute_program): Declare.
* c-lang.c (c_language_defn, cplus_language_defn)
(asm_language_defn, minimal_language_defn): Update.
* ada-lang.c (ada_language_defn): Update.
* Makefile.in (SUBDIR_GCC_COMPILE_OBS, SUBDIR_GCC_COMPILE_SRCS):
New variables.
(SFILES): Add SUBDIR_GCC_COMPILE_SRCS.
(HFILES_NO_SRCDIR): Add compile.h.
(COMMON_OBS): Add SUBDIR_GCC_COMPILE_OBS.
(INIT_FILES): Add SUBDIR_GCC_COMPILE_SRCS.
(compile.o, compile-c-types.o, compile-c-symbols.o)
(compile-object-load.o, compile-object-run.o, compile-loc2c.o)
(compile-c-support.o): New targets.
gdb/doc/ChangeLog
2014-12-12 Phil Muldoon <pmuldoon@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.texinfo (Altering): Update.
(Compiling and Injecting Code): New node.
gdb/testsuite/ChangeLog
2014-12-12 Phil Muldoon <pmuldoon@redhat.com>
Jan Kratochvil <jan.kratochvil@redhat.com>
Tom Tromey <tromey@redhat.com>
* configure.ac: Add gdb.compile/.
* configure: Regenerate.
* gdb.compile/Makefile.in: New file.
* gdb.compile/compile-ops.exp: New file.
* gdb.compile/compile-ops.c: New file.
* gdb.compile/compile-tls.c: New file.
* gdb.compile/compile-tls.exp: New file.
* gdb.compile/compile-constvar.S: New file.
* gdb.compile/compile-constvar.c: New file.
* gdb.compile/compile-mod.c: New file.
* gdb.compile/compile-nodebug.c: New file.
* gdb.compile/compile-setjmp-mod.c: New file.
* gdb.compile/compile-setjmp.c: New file.
* gdb.compile/compile-setjmp.exp: New file.
* gdb.compile/compile-shlib.c: New file.
* gdb.compile/compile.c: New file.
* gdb.compile/compile.exp: New file.
* lib/gdb.exp (skip_compile_feature_tests): New proc.
2014-05-15 04:35:45 +08:00
|
|
|
compile code [-r|-raw] [--] [source code]
|
|
|
|
|
Compile, inject, and execute in the inferior the executable object
|
|
|
|
|
code produced by compiling the provided source code.
|
|
|
|
|
|
|
|
|
|
compile file [-r|-raw] filename
|
|
|
|
|
Compile and inject into the inferior the executable object code
|
|
|
|
|
produced by compiling the source code stored in the filename
|
|
|
|
|
provided.
|
|
|
|
|
|
Always pass signals to the right thread
Currently, GDB can pass a signal to the wrong thread in several
different but related scenarios.
E.g., if thread 1 stops for signal SIGFOO, the user switches to thread
2, and then issues "continue", SIGFOO is actually delivered to thread
2, not thread 1. This obviously messes up programs that use
pthread_kill to send signals to specific threads.
This has been a known issue for a long while. Back in 2008 when I
made stop_signal be per-thread (2020b7ab), I kept the behavior -- see
code in 'proceed' being removed -- wanting to come back to it later.
The time has finally come now.
The patch fixes this -- on resumption, intercepted signals are always
delivered to the thread that had intercepted them.
Another example: if thread 1 stops for a breakpoint, the user switches
to thread 2, and then issues "signal SIGFOO", SIGFOO is actually
delivered to thread 1, not thread 2, because 'proceed' first switches
to thread 1 to step over its breakpoint... If the user deletes the
breakpoint before issuing "signal FOO", then the signal is delivered
to thread 2 (the current thread).
"signal SIGFOO" can be used for two things: inject a signal in the
program while the program/thread had stopped for none, bypassing
"handle nopass"; or changing/suppressing a signal the program had
stopped for. These scenarios are really two faces of the same coin,
and GDB can't really guess what the user is trying to do. GDB might
have intercepted signals in more than one thread even (see the new
signal-command-multiple-signals-pending.exp test). At least in the
inject case, it's obviously clear to me that the user means to deliver
the signal to the currently selected thread, so best is to make the
command's behavior consistent and easy to explain.
Then, if the user is trying to suppress/change a signal the program
had stopped for instead of injecting a new signal, but, the user had
changed threads meanwhile, then she will be surprised that with:
(gdb) continue
Thread 1 stopped for signal SIGFOO.
(gdb) thread 2
(gdb) signal SIGBAR
... GDB actually delivers SIGFOO to thread 1, and SIGBAR to thread 2
(with scheduler-locking off, which is the default, because then
"signal" or any other resumption command resumes all threads).
So the patch makes GDB detect that, and ask for confirmation:
(gdb) thread 1
[Switching to thread 1 (Thread 10979)]
(gdb) signal SIGUSR2
Note:
Thread 3 previously stopped with signal SIGUSR2, User defined signal 2.
Thread 2 previously stopped with signal SIGUSR1, User defined signal 1.
Continuing thread 1 (the current thread) with specified signal will
still deliver the signals noted above to their respective threads.
Continue anyway? (y or n)
All these scenarios are covered by the new tests.
Tested on x86_64 Fedora 20, native and gdbserver.
gdb/
2014-07-25 Pedro Alves <palves@redhat.com>
* NEWS: Mention signal passing and "signal" command changes.
* gdbthread.h (struct thread_suspend_state) <stop_signal>: Extend
comment.
* breakpoint.c (until_break_command): Adjust clear_proceed_status
call.
* infcall.c (run_inferior_call): Adjust clear_proceed_status call.
* infcmd.c (proceed_thread_callback, continue_1, step_once)
(jump_command): Adjust clear_proceed_status call.
(signal_command): Warn if other thread that are resumed have
signals that will be delivered. Adjust clear_proceed_status call.
(until_next_command, finish_command)
(proceed_after_attach_callback, attach_command_post_wait)
(attach_command): Adjust clear_proceed_status call.
* infrun.c (proceed_after_vfork_done): Likewise.
(proceed_after_attach_callback): Adjust comment.
(clear_proceed_status_thread): Clear stop_signal if not in pass
state.
(clear_proceed_status_callback): Delete.
(clear_proceed_status): New 'step' parameter. Only clear the
proceed status of threads the command being prepared is about to
resume.
(proceed): If passed in an explicit signal, override stop_signal
with it. Don't pass the last stop signal to the thread we're
resuming.
(init_wait_for_inferior): Adjust clear_proceed_status call.
(switch_back_to_stepped_thread): Clear the signal if it should not
be passed.
* infrun.h (clear_proceed_status): New 'step' parameter.
(user_visible_resume_ptid): Add comment.
* linux-nat.c (linux_nat_resume_callback): Don't check whether the
signal is in pass state.
* remote.c (append_pending_thread_resumptions): Likewise.
* mi/mi-main.c (proceed_thread): Adjust clear_proceed_status call.
gdb/doc/
2014-07-25 Pedro Alves <palves@redhat.com>
Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Signaling) <signal command>: Explain what happens
with multi-threaded programs.
gdb/testsuite/
2014-07-25 Pedro Alves <palves@redhat.com>
* gdb.threads/signal-command-handle-nopass.c: New file.
* gdb.threads/signal-command-handle-nopass.exp: New file.
* gdb.threads/signal-command-multiple-signals-pending.c: New file.
* gdb.threads/signal-command-multiple-signals-pending.exp: New file.
* gdb.threads/signal-delivered-right-thread.c: New file.
* gdb.threads/signal-delivered-right-thread.exp: New file.
2014-07-25 23:57:31 +08:00
|
|
|
* On resume, GDB now always passes the signal the program had stopped
|
|
|
|
|
for to the thread the signal was sent to, even if the user changed
|
|
|
|
|
threads before resuming. Previously GDB would often (but not
|
|
|
|
|
always) deliver the signal to the thread that happens to be current
|
|
|
|
|
at resume time.
|
|
|
|
|
|
|
|
|
|
* Conversely, the "signal" command now consistently delivers the
|
|
|
|
|
requested signal to the current thread. GDB now asks for
|
|
|
|
|
confirmation if the program had stopped for a signal and the user
|
|
|
|
|
switched threads meanwhile.
|
|
|
|
|
|
Fix "breakpoint always-inserted off"; remove "breakpoint always-inserted auto"
By default, GDB removes all breakpoints from the target when the
target stops and the prompt is given back to the user. This is useful
in case GDB crashes while the user is interacting, as otherwise,
there's a higher chance breakpoints would be left planted on the
target.
But, as long as any thread is running free, we need to make sure to
keep breakpoints inserted, lest a thread misses a breakpoint. With
that in mind, in preparation for non-stop mode, we added a "breakpoint
always-inserted on" mode. This traded off the extra crash protection
for never having threads miss breakpoints, and in addition is more
efficient if there's a ton of breakpoints to remove/insert at each
user command (e.g., at each "step").
When we added non-stop mode, and for a period, we required users to
manually set "always-inserted on" when they enabled non-stop mode, as
otherwise GDB removes all breakpoints from the target as soon as any
thread stops, which means the other threads still running will miss
breakpoints. The test added by this patch exercises this.
That soon revealed a nuisance, and so later we added an extra
"breakpoint always-inserted auto" mode, that made GDB behave like
"always-inserted on" when non-stop was enabled, and "always-inserted
off" when non-stop was disabled. "auto" was made the default at the
same time.
In hindsight, this "auto" setting was unnecessary, and not the ideal
solution. Non-stop mode does depends on breakpoints always-inserted
mode, but only as long as any thread is running. If no thread is
running, no breakpoint can be missed. The same is true for all-stop
too. E.g., if, in all-stop mode, and the user does:
(gdb) c&
(gdb) b foo
That breakpoint at "foo" should be inserted immediately, but it
currently isn't -- currently it'll end up inserted only if the target
happens to trip on some event, and is re-resumed, e.g., an internal
breakpoint triggers that doesn't cause a user-visible stop, and so we
end up in keep_going calling insert_breakpoints. The test added by
this patch also covers this.
IOW, no matter whether in non-stop or all-stop, if the target fully
stops, we can remove breakpoints. And no matter whether in all-stop
or non-stop, if any thread is running in the target, then we need
breakpoints to be immediately inserted. And then, if the target has
global breakpoints, we need to keep breakpoints even when the target
is stopped.
So with that in mind, and aiming at reducing all-stop vs non-stop
differences for all-stop-on-stop-of-non-stop, this patch fixes
"breakpoint always-inserted off" to not remove breakpoints from the
target until it fully stops, and then removes the "auto" setting as
unnecessary. I propose removing it straight away rather than keeping
it as an alias, unless someone complains they have scripts that need
it and that can't adjust.
Tested on x86_64 Fedora 20.
gdb/
2014-09-22 Pedro Alves <palves@redhat.com>
* NEWS: Mention merge of "breakpoint always-inserted" modes "off"
and "auto" merged.
* breakpoint.c (enum ugll_insert_mode): New enum.
(always_inserted_mode): Now a plain boolean.
(show_always_inserted_mode): No longer handle AUTO_BOOLEAN_AUTO.
(breakpoints_always_inserted_mode): Delete.
(breakpoints_should_be_inserted_now): New function.
(insert_breakpoints): Pass UGLL_INSERT to
update_global_location_list instead of calling
insert_breakpoint_locations manually.
(create_solib_event_breakpoint_1): New, factored out from ...
(create_solib_event_breakpoint): ... this.
(create_and_insert_solib_event_breakpoint): Use
create_solib_event_breakpoint_1 instead of calling
insert_breakpoint_locations manually.
(update_global_location_list): Change parameter type from boolean
to enum ugll_insert_mode. All callers adjusted. Adjust to use
breakpoints_should_be_inserted_now and handle UGLL_INSERT.
(update_global_location_list_nothrow): Change parameter type from
boolean to enum ugll_insert_mode.
(_initialize_breakpoint): "breakpoint always-inserted" option is
now a boolean command. Update help text.
* breakpoint.h (breakpoints_always_inserted_mode): Delete declaration.
(breakpoints_should_be_inserted_now): New declaration.
* infrun.c (handle_inferior_event) <TARGET_WAITKIND_LOADED>:
Remove breakpoints_always_inserted_mode check.
(normal_stop): Adjust to use breakpoints_should_be_inserted_now.
* remote.c (remote_start_remote): Likewise.
gdb/doc/
2014-09-22 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Set Breaks): Document that "set breakpoint
always-inserted off" is the default mode now. Delete
documentation of "set breakpoint always-inserted auto".
gdb/testsuite/
2014-09-22 Pedro Alves <palves@redhat.com>
* gdb.threads/break-while-running.exp: New file.
* gdb.threads/break-while-running.c: New file.
2014-09-22 16:56:55 +08:00
|
|
|
* "breakpoint always-inserted" modes "off" and "auto" merged.
|
|
|
|
|
|
|
|
|
|
Now, when 'breakpoint always-inserted mode' is set to "off", GDB
|
|
|
|
|
won't remove breakpoints from the target until all threads stop,
|
|
|
|
|
even in non-stop mode. The "auto" mode has been removed, and "off"
|
|
|
|
|
is now the default mode.
|
|
|
|
|
|
2014-12-17 16:17:27 +08:00
|
|
|
* New options
|
|
|
|
|
|
|
|
|
|
set debug symbol-lookup
|
|
|
|
|
show debug symbol-lookup
|
|
|
|
|
Control display of debugging info regarding symbol lookup.
|
|
|
|
|
|
2014-09-30 05:33:09 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** The -list-thread-groups command outputs an exit-code field for
|
|
|
|
|
inferiors that have exited.
|
|
|
|
|
|
2014-12-19 13:13:07 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
MIPS SDE mips*-sde*-elf*
|
|
|
|
|
|
Delete IRIX support
This does most of the mechanical removal. IOW, the easy part.
This doesn't touch procfs.c as that'd be a harder excision,
potentially affecting Solaris.
mips-tdep.c is left alone. E.g., I didn't delete the GDB_OSABI_IRIX
enum value, nor references to it in mips-tdep.c. Some comments
mentioning IRIX ABIs may still be relevant and I wouldn't know what to
do with them. in That can always be done on a separate pass,
preferably by someone who can test on MIPS.
I didn't remove a reference to IRIX in testsuite/lib/future.exp, as I
believe that code is imported from DejaGNU.
Built and tested on x86_64 Fedora 20, with --enable-targets=all.
Tested that building for --target=mips-sgi-irix6 on x86_64 Fedora 20
fails with:
checking for default auto-load directory... $debugdir:$datadir/auto-load
checking for default auto-load safe-path... $debugdir:$datadir/auto-load
*** Configuration mips-sgi-irix6 is obsolete.
*** Support has been REMOVED.
make[1]: *** [configure-gdb] Error 1
make[1]: Leaving directory `/home/pedro/gdb/mygit/build-irix'
make: *** [all] Error 2
gdb/
2014-10-10 Pedro Alves <palves@redhat.com>
* Makefile.in (ALL_TARGET_OBS): Remove mips-irix-tdep.o and solib-irix.o.
(ALLDEPFILES): Remove mips-irix-tdep.c and solib-irix.c.
(HFILES_NO_SRCDIR): Remove solib-irix.h.
* NEWS: Mention that support for mips-sgi-irix5* mips-sgi-irix6*
and been removed.
* config/mips/irix5.mh, config/mips/irix6.mh: Delete files.
* configure.ac: Remove references to IRIX.
* configure.host: Add *-*-irix* to the obsolete hosts section.
Remove all other references to irix.
* irix5-nat.c, mips-irix-tdep.c, solib-irix.c, solib-irix.h:
Delete files.
gdb/testsuite/
2014-10-10 Pedro Alves <palves@redhat.com>
* gdb.base/bigcore.exp: Remove references to IRIX.
* gdb.base/funcargs.exp: Likewise.
* gdb.base/interrupt.exp: Likewise.
* gdb.base/mips_pro.exp: Likewise.
* gdb.base/nodebug.exp: Likewise.
* gdb.base/setvar.exp: Likewise.
* lib/gdb.exp (gdb_compile_shlib): Remove mips-sgi-irix* case.
2014-10-11 01:18:52 +08:00
|
|
|
* Removed targets
|
|
|
|
|
|
|
|
|
|
Support for these obsolete configurations has been removed.
|
|
|
|
|
|
2014-10-25 00:56:29 +08:00
|
|
|
Alpha running OSF/1 (or Tru64) alpha*-*-osf*
|
|
|
|
|
SGI Irix-5.x mips-*-irix5*
|
|
|
|
|
SGI Irix-6.x mips-*-irix6*
|
2014-10-17 21:49:04 +08:00
|
|
|
VAX running (4.2 - 4.3 Reno) BSD vax-*-bsd*
|
|
|
|
|
VAX running Ultrix vax-*-ultrix*
|
Delete IRIX support
This does most of the mechanical removal. IOW, the easy part.
This doesn't touch procfs.c as that'd be a harder excision,
potentially affecting Solaris.
mips-tdep.c is left alone. E.g., I didn't delete the GDB_OSABI_IRIX
enum value, nor references to it in mips-tdep.c. Some comments
mentioning IRIX ABIs may still be relevant and I wouldn't know what to
do with them. in That can always be done on a separate pass,
preferably by someone who can test on MIPS.
I didn't remove a reference to IRIX in testsuite/lib/future.exp, as I
believe that code is imported from DejaGNU.
Built and tested on x86_64 Fedora 20, with --enable-targets=all.
Tested that building for --target=mips-sgi-irix6 on x86_64 Fedora 20
fails with:
checking for default auto-load directory... $debugdir:$datadir/auto-load
checking for default auto-load safe-path... $debugdir:$datadir/auto-load
*** Configuration mips-sgi-irix6 is obsolete.
*** Support has been REMOVED.
make[1]: *** [configure-gdb] Error 1
make[1]: Leaving directory `/home/pedro/gdb/mygit/build-irix'
make: *** [all] Error 2
gdb/
2014-10-10 Pedro Alves <palves@redhat.com>
* Makefile.in (ALL_TARGET_OBS): Remove mips-irix-tdep.o and solib-irix.o.
(ALLDEPFILES): Remove mips-irix-tdep.c and solib-irix.c.
(HFILES_NO_SRCDIR): Remove solib-irix.h.
* NEWS: Mention that support for mips-sgi-irix5* mips-sgi-irix6*
and been removed.
* config/mips/irix5.mh, config/mips/irix6.mh: Delete files.
* configure.ac: Remove references to IRIX.
* configure.host: Add *-*-irix* to the obsolete hosts section.
Remove all other references to irix.
* irix5-nat.c, mips-irix-tdep.c, solib-irix.c, solib-irix.h:
Delete files.
gdb/testsuite/
2014-10-10 Pedro Alves <palves@redhat.com>
* gdb.base/bigcore.exp: Remove references to IRIX.
* gdb.base/funcargs.exp: Likewise.
* gdb.base/interrupt.exp: Likewise.
* gdb.base/mips_pro.exp: Likewise.
* gdb.base/nodebug.exp: Likewise.
* gdb.base/setvar.exp: Likewise.
* lib/gdb.exp (gdb_compile_shlib): Remove mips-sgi-irix* case.
2014-10-11 01:18:52 +08:00
|
|
|
|
2014-12-30 15:36:53 +08:00
|
|
|
* The "dll-symbols" command, and its two aliases ("add-shared-symbol-files"
|
|
|
|
|
and "assf"), have been removed. Use the "sharedlibrary" command, or
|
|
|
|
|
its alias "share", instead.
|
|
|
|
|
|
2014-06-12 00:52:29 +08:00
|
|
|
*** Changes in GDB 7.8
|
2014-04-22 22:26:33 +08:00
|
|
|
|
2014-05-17 03:15:10 +08:00
|
|
|
* New command line options
|
|
|
|
|
|
|
|
|
|
-D data-directory
|
|
|
|
|
This is an alias for the --data-directory option.
|
|
|
|
|
|
2014-04-22 22:26:33 +08:00
|
|
|
* GDB supports printing and modifying of variable length automatic arrays
|
|
|
|
|
as specified in ISO C99.
|
|
|
|
|
|
2014-04-22 18:23:05 +08:00
|
|
|
* The ARM simulator now supports instruction level tracing
|
|
|
|
|
with or without disassembly.
|
2014-01-08 17:41:03 +08:00
|
|
|
|
Add Guile as an extension language.
* NEWS: Mention Guile scripting.
* Makefile.in (SUBDIR_GUILE_OBS): New variable.
(SUBDIR_GUILE_SRCS, SUBDIR_GUILE_DEPS): New variables
(SUBDIR_GUILE_LDFLAGS, SUBDIR_GUILE_CFLAGS): New variables.
(INTERNAL_CPPFLAGS): Add GUILE_CPPFLAGS.
(CLIBS): Add GUILE_LIBS.
(install-guile): New rule.
(guile.o): New rule.
(scm-arch.o, scm-auto-load.o, scm-block.o): New rules.
(scm-breakpoint.o, scm-disasm.o, scm-exception.o): New rules.
(scm-frame.o, scm-iterator.o, scm-lazy-string.o): New rules.
(scm-math.o, scm-objfile.o, scm-ports.o): New rules.
(scm-pretty-print.o, scm-safe-call.o, scm-gsmob.o): New rules.
(scm-string.o, scm-symbol.o, scm-symtab.o): New rules.
(scm-type.o, scm-utils.o, scm-value.o): New rules.
* configure.ac: New option --with-guile.
* configure: Regenerate.
* config.in: Regenerate.
* auto-load.c: Remove #include "python/python.h". Add #include
"gdb/section-scripts.h".
(source_section_scripts): Handle Guile scripts.
(_initialize_auto_load): Add name of Guile objfile script to
scripts-directory help text.
* breakpoint.c (condition_command): Tweak comment to include Scheme.
* breakpoint.h (gdbscm_breakpoint_object): Add forward decl.
(struct breakpoint): New member scm_bp_object.
* defs.h (enum command_control_type): New value guile_control.
* cli/cli-cmds.c: Remove #include "python/python.h". Add #include
"extension.h".
(show_user): Update comment.
(_initialize_cli_cmds): Update help text for "show user". Update help
text for max-user-call-depth.
* cli/cli-script.c: Remove #include "python/python.h". Add #include
"extension.h".
(multi_line_command_p): Add guile_control.
(print_command_lines): Handle guile_control.
(execute_control_command, recurse_read_control_structure): Ditto.
(process_next_line): Recognize "guile" commands.
* disasm.c (gdb_disassemble_info): Make non-static.
* disasm.h: #include "dis-asm.h".
(struct gdbarch): Add forward decl.
(gdb_disassemble_info): Declare.
* extension.c: #include "guile/guile.h".
(extension_languages): Add guile.
(get_ext_lang_defn): Handle EXT_LANG_GDB.
* extension.h (enum extension_language): New value EXT_LANG_GUILE.
* gdbtypes.c (get_unsigned_type_max): New function.
(get_signed_type_minmax): New function.
* gdbtypes.h (get_unsigned_type_max): Declare.
(get_signed_type_minmax): Declare.
* guile/README: New file.
* guile/guile-internal.h: New file.
* guile/guile.c: New file.
* guile/guile.h: New file.
* guile/scm-arch.c: New file.
* guile/scm-auto-load.c: New file.
* guile/scm-block.c: New file.
* guile/scm-breakpoint.c: New file.
* guile/scm-disasm.c: New file.
* guile/scm-exception.c: New file.
* guile/scm-frame.c: New file.
* guile/scm-gsmob.c: New file.
* guile/scm-iterator.c: New file.
* guile/scm-lazy-string.c: New file.
* guile/scm-math.c: New file.
* guile/scm-objfile.c: New file.
* guile/scm-ports.c: New file.
* guile/scm-pretty-print.c: New file.
* guile/scm-safe-call.c: New file.
* guile/scm-string.c: New file.
* guile/scm-symbol.c: New file.
* guile/scm-symtab.c: New file.
* guile/scm-type.c: New file.
* guile/scm-utils.c: New file.
* guile/scm-value.c: New file.
* guile/lib/gdb.scm: New file.
* guile/lib/gdb/boot.scm: New file.
* guile/lib/gdb/experimental.scm: New file.
* guile/lib/gdb/init.scm: New file.
* guile/lib/gdb/iterator.scm: New file.
* guile/lib/gdb/printing.scm: New file.
* guile/lib/gdb/types.scm: New file.
* data-directory/Makefile.in (GUILE_SRCDIR): New variable.
(VPATH): Add $(GUILE_SRCDIR).
(GUILE_DIR): New variable.
(GUILE_INSTALL_DIR, GUILE_FILES): New variables.
(all): Add stamp-guile dependency.
(stamp-guile): New rule.
(clean-guile, install-guile, uninstall-guile): New rules.
(install-only): Add install-guile dependency.
(uninstall): Add uninstall-guile dependency.
(clean): Add clean-guile dependency.
doc/
* Makefile.in (GDB_DOC_FILES): Add guile.texi.
* gdb.texinfo (Auto-loading): Add set/show auto-load guile-scripts.
(Extending GDB): New menu entries Guile, Multiple Extension Languages.
(Guile docs): Include guile.texi.
(objfile-gdbdotext file): Add objfile-gdb.scm.
(dotdebug_gdb_scripts section): Mention Guile scripts.
(Multiple Extension Languages): New node.
* guile.texi: New file.
testsuite/
* configure.ac (AC_OUTPUT): Add gdb.guile.
* configure: Regenerate.
* lib/gdb-guile.exp: New file.
* lib/gdb.exp (get_target_charset): New function.
* gdb.base/help.exp: Update expected output from "apropos apropos".
* gdb.guile/Makefile.in: New file.
* gdb.guile/guile.exp: New file.
* gdb.guile/scm-arch.c: New file.
* gdb.guile/scm-arch.exp: New file.
* gdb.guile/scm-block.c: New file.
* gdb.guile/scm-block.exp: New file.
* gdb.guile/scm-breakpoint.c: New file.
* gdb.guile/scm-breakpoint.exp: New file.
* gdb.guile/scm-disasm.c: New file.
* gdb.guile/scm-disasm.exp: New file.
* gdb.guile/scm-equal.c: New file.
* gdb.guile/scm-equal.exp: New file.
* gdb.guile/scm-error.exp: New file.
* gdb.guile/scm-error.scm: New file.
* gdb.guile/scm-frame-args.c: New file.
* gdb.guile/scm-frame-args.exp: New file.
* gdb.guile/scm-frame-args.scm: New file.
* gdb.guile/scm-frame-inline.c: New file.
* gdb.guile/scm-frame-inline.exp: New file.
* gdb.guile/scm-frame.c: New file.
* gdb.guile/scm-frame.exp: New file.
* gdb.guile/scm-generics.exp: New file.
* gdb.guile/scm-gsmob.exp: New file.
* gdb.guile/scm-iterator.c: New file.
* gdb.guile/scm-iterator.exp: New file.
* gdb.guile/scm-math.c: New file.
* gdb.guile/scm-math.exp: New file.
* gdb.guile/scm-objfile-script-gdb.in: New file.
* gdb.guile/scm-objfile-script.c: New file.
* gdb.guile/scm-objfile-script.exp: New file.
* gdb.guile/scm-objfile.c: New file.
* gdb.guile/scm-objfile.exp: New file.
* gdb.guile/scm-ports.exp: New file.
* gdb.guile/scm-pretty-print.c: New file.
* gdb.guile/scm-pretty-print.exp: New file.
* gdb.guile/scm-pretty-print.scm: New file.
* gdb.guile/scm-section-script.c: New file.
* gdb.guile/scm-section-script.exp: New file.
* gdb.guile/scm-section-script.scm: New file.
* gdb.guile/scm-symbol.c: New file.
* gdb.guile/scm-symbol.exp: New file.
* gdb.guile/scm-symtab-2.c: New file.
* gdb.guile/scm-symtab.c: New file.
* gdb.guile/scm-symtab.exp: New file.
* gdb.guile/scm-type.c: New file.
* gdb.guile/scm-type.exp: New file.
* gdb.guile/scm-value-cc.cc: New file.
* gdb.guile/scm-value-cc.exp: New file.
* gdb.guile/scm-value.c: New file.
* gdb.guile/scm-value.exp: New file.
* gdb.guile/source2.scm: New file.
* gdb.guile/types-module.cc: New file.
* gdb.guile/types-module.exp: New file.
2014-02-10 11:40:01 +08:00
|
|
|
* Guile scripting
|
|
|
|
|
|
|
|
|
|
GDB now has support for scripting using Guile. Whether this is
|
|
|
|
|
available is determined at configure time.
|
|
|
|
|
Guile version 2.0 or greater is required.
|
|
|
|
|
Guile version 2.0.9 is well tested, earlier 2.0 versions are not.
|
|
|
|
|
|
|
|
|
|
* New commands (for set/show, see "New options" below)
|
|
|
|
|
|
|
|
|
|
guile [code]
|
|
|
|
|
gu [code]
|
|
|
|
|
Invoke CODE by passing it to the Guile interpreter.
|
|
|
|
|
|
|
|
|
|
guile-repl
|
|
|
|
|
gr
|
|
|
|
|
Start a Guile interactive prompt (or "repl" for "read-eval-print loop").
|
|
|
|
|
|
|
|
|
|
info auto-load guile-scripts [regexp]
|
|
|
|
|
Print the list of automatically loaded Guile scripts.
|
|
|
|
|
|
|
|
|
|
* The source command is now capable of sourcing Guile scripts.
|
|
|
|
|
This feature is dependent on the debugger being built with Guile support.
|
|
|
|
|
|
New Ada maintenance command to ignore descriptive types (DWARF).
Currently, Ada debugging requires the use of certain GNAT-specific
encodings, which are generated by the compiler. These encodings
were created a long time ago to work around the fairly limited
capabilities of the stabs debugging format. With DWARF, the vast
majority of the encodings could be abandoned in favor of a pure
DWARF approach.
In order to make it easier to evaluate the quality of the DWARF
debugging information generated by the compiler, and how the debugger
handles it, we are introducing a small Ada-specific maintenance
setting which changes the debugger's behavior to ignore descriptive
types. Descriptive types are artificial types generated by the
compiler purely to give the debugger hints as to how to properly
decode certain properties of a type. For instance, for array
types, it generates a parallel type whose name is the name of
the array suffixed with ___XA, whose contents tells us what
the array's index type is, and possibly its bounds. See GCC's
gcc/ada/exp_dbug.ads for the full description of all encodings.
This is only a first step, as this setting does not deactivate
all encodings; More settings dedicated to each type of encoding
will likely be implemented in the future, as we make progress.
gdb/ChangeLog:
* ada-lang.c (maint_set_ada_cmdlist, maint_show_ada_cmdlist):
New static globals.
(maint_set_ada_cmd, maint_show_ada_cmd): New functions.
(ada_ignore_descriptive_types_p): New static global.
(find_parallel_type_by_descriptive_type): Return immediately
if ada_ignore_descriptive_types_p is set.
(_initialize_ada_language): Register new commands "maintenance
set ada", "maintenance show ada", "maintenance set ada
ignore-descriptive-types" and "maintenance show ada
ignore-descriptive-types".
* NEWS: Add entry for new "maint ada set/show
ignore-descriptive-types" commands.
gdb/doc/ChangeLog:
* gdb.texinfo (Ada Glitches): Document the new "maint ada set/show
ignore-descriptive-types". commands.
2014-01-16 19:08:16 +08:00
|
|
|
* New options
|
|
|
|
|
|
2014-04-01 03:07:48 +08:00
|
|
|
set print symbol-loading (off|brief|full)
|
|
|
|
|
show print symbol-loading
|
|
|
|
|
Control whether to print informational messages when loading symbol
|
|
|
|
|
information for a file. The default is "full", but when debugging
|
|
|
|
|
programs with large numbers of shared libraries the amount of output
|
|
|
|
|
becomes less useful.
|
|
|
|
|
|
Add Guile as an extension language.
* NEWS: Mention Guile scripting.
* Makefile.in (SUBDIR_GUILE_OBS): New variable.
(SUBDIR_GUILE_SRCS, SUBDIR_GUILE_DEPS): New variables
(SUBDIR_GUILE_LDFLAGS, SUBDIR_GUILE_CFLAGS): New variables.
(INTERNAL_CPPFLAGS): Add GUILE_CPPFLAGS.
(CLIBS): Add GUILE_LIBS.
(install-guile): New rule.
(guile.o): New rule.
(scm-arch.o, scm-auto-load.o, scm-block.o): New rules.
(scm-breakpoint.o, scm-disasm.o, scm-exception.o): New rules.
(scm-frame.o, scm-iterator.o, scm-lazy-string.o): New rules.
(scm-math.o, scm-objfile.o, scm-ports.o): New rules.
(scm-pretty-print.o, scm-safe-call.o, scm-gsmob.o): New rules.
(scm-string.o, scm-symbol.o, scm-symtab.o): New rules.
(scm-type.o, scm-utils.o, scm-value.o): New rules.
* configure.ac: New option --with-guile.
* configure: Regenerate.
* config.in: Regenerate.
* auto-load.c: Remove #include "python/python.h". Add #include
"gdb/section-scripts.h".
(source_section_scripts): Handle Guile scripts.
(_initialize_auto_load): Add name of Guile objfile script to
scripts-directory help text.
* breakpoint.c (condition_command): Tweak comment to include Scheme.
* breakpoint.h (gdbscm_breakpoint_object): Add forward decl.
(struct breakpoint): New member scm_bp_object.
* defs.h (enum command_control_type): New value guile_control.
* cli/cli-cmds.c: Remove #include "python/python.h". Add #include
"extension.h".
(show_user): Update comment.
(_initialize_cli_cmds): Update help text for "show user". Update help
text for max-user-call-depth.
* cli/cli-script.c: Remove #include "python/python.h". Add #include
"extension.h".
(multi_line_command_p): Add guile_control.
(print_command_lines): Handle guile_control.
(execute_control_command, recurse_read_control_structure): Ditto.
(process_next_line): Recognize "guile" commands.
* disasm.c (gdb_disassemble_info): Make non-static.
* disasm.h: #include "dis-asm.h".
(struct gdbarch): Add forward decl.
(gdb_disassemble_info): Declare.
* extension.c: #include "guile/guile.h".
(extension_languages): Add guile.
(get_ext_lang_defn): Handle EXT_LANG_GDB.
* extension.h (enum extension_language): New value EXT_LANG_GUILE.
* gdbtypes.c (get_unsigned_type_max): New function.
(get_signed_type_minmax): New function.
* gdbtypes.h (get_unsigned_type_max): Declare.
(get_signed_type_minmax): Declare.
* guile/README: New file.
* guile/guile-internal.h: New file.
* guile/guile.c: New file.
* guile/guile.h: New file.
* guile/scm-arch.c: New file.
* guile/scm-auto-load.c: New file.
* guile/scm-block.c: New file.
* guile/scm-breakpoint.c: New file.
* guile/scm-disasm.c: New file.
* guile/scm-exception.c: New file.
* guile/scm-frame.c: New file.
* guile/scm-gsmob.c: New file.
* guile/scm-iterator.c: New file.
* guile/scm-lazy-string.c: New file.
* guile/scm-math.c: New file.
* guile/scm-objfile.c: New file.
* guile/scm-ports.c: New file.
* guile/scm-pretty-print.c: New file.
* guile/scm-safe-call.c: New file.
* guile/scm-string.c: New file.
* guile/scm-symbol.c: New file.
* guile/scm-symtab.c: New file.
* guile/scm-type.c: New file.
* guile/scm-utils.c: New file.
* guile/scm-value.c: New file.
* guile/lib/gdb.scm: New file.
* guile/lib/gdb/boot.scm: New file.
* guile/lib/gdb/experimental.scm: New file.
* guile/lib/gdb/init.scm: New file.
* guile/lib/gdb/iterator.scm: New file.
* guile/lib/gdb/printing.scm: New file.
* guile/lib/gdb/types.scm: New file.
* data-directory/Makefile.in (GUILE_SRCDIR): New variable.
(VPATH): Add $(GUILE_SRCDIR).
(GUILE_DIR): New variable.
(GUILE_INSTALL_DIR, GUILE_FILES): New variables.
(all): Add stamp-guile dependency.
(stamp-guile): New rule.
(clean-guile, install-guile, uninstall-guile): New rules.
(install-only): Add install-guile dependency.
(uninstall): Add uninstall-guile dependency.
(clean): Add clean-guile dependency.
doc/
* Makefile.in (GDB_DOC_FILES): Add guile.texi.
* gdb.texinfo (Auto-loading): Add set/show auto-load guile-scripts.
(Extending GDB): New menu entries Guile, Multiple Extension Languages.
(Guile docs): Include guile.texi.
(objfile-gdbdotext file): Add objfile-gdb.scm.
(dotdebug_gdb_scripts section): Mention Guile scripts.
(Multiple Extension Languages): New node.
* guile.texi: New file.
testsuite/
* configure.ac (AC_OUTPUT): Add gdb.guile.
* configure: Regenerate.
* lib/gdb-guile.exp: New file.
* lib/gdb.exp (get_target_charset): New function.
* gdb.base/help.exp: Update expected output from "apropos apropos".
* gdb.guile/Makefile.in: New file.
* gdb.guile/guile.exp: New file.
* gdb.guile/scm-arch.c: New file.
* gdb.guile/scm-arch.exp: New file.
* gdb.guile/scm-block.c: New file.
* gdb.guile/scm-block.exp: New file.
* gdb.guile/scm-breakpoint.c: New file.
* gdb.guile/scm-breakpoint.exp: New file.
* gdb.guile/scm-disasm.c: New file.
* gdb.guile/scm-disasm.exp: New file.
* gdb.guile/scm-equal.c: New file.
* gdb.guile/scm-equal.exp: New file.
* gdb.guile/scm-error.exp: New file.
* gdb.guile/scm-error.scm: New file.
* gdb.guile/scm-frame-args.c: New file.
* gdb.guile/scm-frame-args.exp: New file.
* gdb.guile/scm-frame-args.scm: New file.
* gdb.guile/scm-frame-inline.c: New file.
* gdb.guile/scm-frame-inline.exp: New file.
* gdb.guile/scm-frame.c: New file.
* gdb.guile/scm-frame.exp: New file.
* gdb.guile/scm-generics.exp: New file.
* gdb.guile/scm-gsmob.exp: New file.
* gdb.guile/scm-iterator.c: New file.
* gdb.guile/scm-iterator.exp: New file.
* gdb.guile/scm-math.c: New file.
* gdb.guile/scm-math.exp: New file.
* gdb.guile/scm-objfile-script-gdb.in: New file.
* gdb.guile/scm-objfile-script.c: New file.
* gdb.guile/scm-objfile-script.exp: New file.
* gdb.guile/scm-objfile.c: New file.
* gdb.guile/scm-objfile.exp: New file.
* gdb.guile/scm-ports.exp: New file.
* gdb.guile/scm-pretty-print.c: New file.
* gdb.guile/scm-pretty-print.exp: New file.
* gdb.guile/scm-pretty-print.scm: New file.
* gdb.guile/scm-section-script.c: New file.
* gdb.guile/scm-section-script.exp: New file.
* gdb.guile/scm-section-script.scm: New file.
* gdb.guile/scm-symbol.c: New file.
* gdb.guile/scm-symbol.exp: New file.
* gdb.guile/scm-symtab-2.c: New file.
* gdb.guile/scm-symtab.c: New file.
* gdb.guile/scm-symtab.exp: New file.
* gdb.guile/scm-type.c: New file.
* gdb.guile/scm-type.exp: New file.
* gdb.guile/scm-value-cc.cc: New file.
* gdb.guile/scm-value-cc.exp: New file.
* gdb.guile/scm-value.c: New file.
* gdb.guile/scm-value.exp: New file.
* gdb.guile/source2.scm: New file.
* gdb.guile/types-module.cc: New file.
* gdb.guile/types-module.exp: New file.
2014-02-10 11:40:01 +08:00
|
|
|
set guile print-stack (none|message|full)
|
|
|
|
|
show guile print-stack
|
|
|
|
|
Show a stack trace when an error is encountered in a Guile script.
|
|
|
|
|
|
|
|
|
|
set auto-load guile-scripts (on|off)
|
|
|
|
|
show auto-load guile-scripts
|
|
|
|
|
Control auto-loading of Guile script files.
|
|
|
|
|
|
New Ada maintenance command to ignore descriptive types (DWARF).
Currently, Ada debugging requires the use of certain GNAT-specific
encodings, which are generated by the compiler. These encodings
were created a long time ago to work around the fairly limited
capabilities of the stabs debugging format. With DWARF, the vast
majority of the encodings could be abandoned in favor of a pure
DWARF approach.
In order to make it easier to evaluate the quality of the DWARF
debugging information generated by the compiler, and how the debugger
handles it, we are introducing a small Ada-specific maintenance
setting which changes the debugger's behavior to ignore descriptive
types. Descriptive types are artificial types generated by the
compiler purely to give the debugger hints as to how to properly
decode certain properties of a type. For instance, for array
types, it generates a parallel type whose name is the name of
the array suffixed with ___XA, whose contents tells us what
the array's index type is, and possibly its bounds. See GCC's
gcc/ada/exp_dbug.ads for the full description of all encodings.
This is only a first step, as this setting does not deactivate
all encodings; More settings dedicated to each type of encoding
will likely be implemented in the future, as we make progress.
gdb/ChangeLog:
* ada-lang.c (maint_set_ada_cmdlist, maint_show_ada_cmdlist):
New static globals.
(maint_set_ada_cmd, maint_show_ada_cmd): New functions.
(ada_ignore_descriptive_types_p): New static global.
(find_parallel_type_by_descriptive_type): Return immediately
if ada_ignore_descriptive_types_p is set.
(_initialize_ada_language): Register new commands "maintenance
set ada", "maintenance show ada", "maintenance set ada
ignore-descriptive-types" and "maintenance show ada
ignore-descriptive-types".
* NEWS: Add entry for new "maint ada set/show
ignore-descriptive-types" commands.
gdb/doc/ChangeLog:
* gdb.texinfo (Ada Glitches): Document the new "maint ada set/show
ignore-descriptive-types". commands.
2014-01-16 19:08:16 +08:00
|
|
|
maint ada set ignore-descriptive-types (on|off)
|
|
|
|
|
maint ada show ignore-descriptive-types
|
|
|
|
|
Control whether the debugger should ignore descriptive types in Ada
|
|
|
|
|
programs. The default is not to ignore the descriptive types. See
|
|
|
|
|
the user manual for more details on descriptive types and the intended
|
|
|
|
|
usage of this option.
|
|
|
|
|
|
Allow making GDB not automatically connect to the native target.
Sometimes it's useful to be able to disable the automatic connection
to the native target. E.g., sometimes GDB disconnects from the
extended-remote target I was debugging, without me noticing it, and
then I do "run". That starts the program locally, and only after a
little head scratch session do I figure out the program is running
locally instead of remotely as intended. Same thing with "attach",
"info os", etc.
With the patch, we now can have this instead:
(gdb) set auto-connect-native-target off
(gdb) target extended-remote :9999
...
*gdb disconnects*
(gdb) run
Don't know how to run. Try "help target".
To still be able to connect to the native target with
auto-connect-native-target set to off, I've made "target native" work
instead of erroring out as today.
Before:
(gdb) target native
Use the "run" command to start a native process.
After:
(gdb) target native
Done. Use the "run" command to start a process.
(gdb) maint print target-stack
The current target stack is:
- native (Native process)
- exec (Local exec file)
- None (None)
(gdb) run
Starting program: ./a.out
...
I've also wanted this for the testsuite, when running against the
native-extended-gdbserver.exp board (runs against gdbserver in
extended-remote mode). With a non-native-target board, it's always a
bug to launch a program with the native target. Turns out we still
have one such case this patch catches:
(gdb) break main
Breakpoint 1 at 0x4009e5: file ../../../src/gdb/testsuite/gdb.base/coremaker.c, line 138.
(gdb) run
Don't know how to run. Try "help target".
(gdb) FAIL: gdb.base/corefile.exp: run: with core
On the patch itself, probably the least obvious bit is the need to go
through all targets, and move the unpush_target call to after the
generic_mourn_inferior call instead of before. This is what
inf-ptrace.c does too, ever since multi-process support was added.
The reason inf-ptrace.c does things in that order is that in the
current multi-process/single-target model, we shouldn't unpush the
target if there are still other live inferiors being debugged. The
check for that is "have_inferiors ()" (a misnomer nowadays...), which
does:
have_inferiors (void)
{
for (inf = inferior_list; inf; inf = inf->next)
if (inf->pid != 0)
return 1;
It's generic_mourn_inferior that ends up clearing inf->pid, so we need
to call it before the have_inferiors check. To make all native
targets behave the same WRT to explicit "target native", I've added an
inf_child_maybe_unpush_target function that targets call instead of
calling unpush_target directly, and as that includes the
have_inferiors check, I needed to adjust the targets.
Tested on x86_64 Fedora 20, native, and also with the
extended-gdbserver board.
Confirmed a cross build of djgpp gdb still builds.
Smoke tested a cross build of Windows gdb under Wine.
Untested otherwise.
gdb/
2014-05-21 Pedro Alves <palves@redhat.com>
* inf-child.c (inf_child_ops, inf_child_explicitly_opened): New
globals.
(inf_child_open_target): New function.
(inf_child_open): Use inf_child_open_target to push the target
instead of erroring out.
(inf_child_disconnect, inf_child_close)
(inf_child_maybe_unpush_target): New functions.
(inf_child_target): Install inf_child_disconnect and
inf_child_close. Store a pointer to the returned object.
* inf-child.h (inf_child_open_target, inf_child_maybe_unpush): New
declarations.
* target.c (auto_connect_native_target): New global.
(show_default_run_target): New function.
(find_default_run_target): Return NULL if automatically connecting
to the native target is disabled.
(_initialize_target): Install set/show auto-connect-native-target.
* NEWS: Mention "set auto-connect-native-target", and "target
native".
* linux-nat.c (super_close): New global.
(linux_nat_close): Call super_close.
(linux_nat_add_target): Store a pointer to the base class's
to_close method.
* inf-ptrace.c (inf_ptrace_mourn_inferior, inf_ptrace_detach): Use
inf_child_maybe_unpush.
* inf-ttrace.c (inf_ttrace_him): Don't push the target if it is
already pushed.
(inf_ttrace_mourn_inferior): Only unpush the target after mourning
the inferior. Use inf_child_maybe_unpush_target.
(inf_ttrace_attach): Don't push the target if it is already
pushed.
(inf_ttrace_detach): Use inf_child_maybe_unpush_target.
* darwin-nat.c (darwin_mourn_inferior): Only unpush the target
after mourning the inferior. Use inf_child_maybe_unpush_target.
(darwin_attach_pid): Don't push the target if it is already
pushed.
* gnu-nat.c (gnu_mourn_inferior): Only unpush the target after
mourning the inferior. Use inf_child_maybe_unpush_target.
(gnu_detach): Use inf_child_maybe_unpush_target.
* go32-nat.c (go32_create_inferior): Don't push the target if it
is already pushed.
(go32_mourn_inferior): Use inf_child_maybe_unpush_target.
* nto-procfs.c (procfs_is_nto_target): Adjust comment.
(procfs_open): Rename to ...
(procfs_open_1): ... this. Add target_ops parameter. Adjust
comments. Can target_preopen before changing node. Call
inf_child_open_target to push the target explicitly.
(procfs_attach): Don't push the target if it is already pushed.
(procfs_detach): Use inf_child_maybe_unpush_target.
(procfs_create_inferior): Don't push the target if it is already
pushed.
(nto_native_ops): New global.
(procfs_open): Reimplement.
(procfs_native_open): New function.
(init_procfs_targets): Install procfs_native_open as to_open of
"target native". Store a pointer to the "native" target in
nto_native_ops.
* procfs.c (procfs_attach): Don't push the target if it is already
pushed.
(procfs_detach): Use inf_child_maybe_unpush_target.
(procfs_mourn_inferior): Only unpush the target after mourning the
inferior. Use inf_child_maybe_unpush_target.
(procfs_init_inferior): Don't push the target if it is already
pushed.
* windows-nat.c (do_initial_windows_stuff): Don't push the target
if it is already pushed.
(windows_detach): Use inf_child_maybe_unpush_target.
(windows_mourn_inferior): Only unpush the target after mourning
the inferior. Use inf_child_maybe_unpush_target.
gdb/doc/
2014-05-21 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Starting): Document "set/show
auto-connect-native-target".
(Target Commands): Document "target native".
gdb/testsuite/
2014-05-21 Pedro Alves <palves@redhat.com>
* boards/gdbserver-base.exp (GDBFLAGS): Set to "set
auto-connect-native-target off".
* gdb.base/auto-connect-native-target.c: New file.
* gdb.base/auto-connect-native-target.exp: New file.
2014-05-22 01:30:47 +08:00
|
|
|
set auto-connect-native-target
|
|
|
|
|
|
|
|
|
|
Control whether GDB is allowed to automatically connect to the
|
|
|
|
|
native target for the run, attach, etc. commands when not connected
|
|
|
|
|
to any target yet. See also "target native" below.
|
|
|
|
|
|
2014-03-05 22:38:11 +08:00
|
|
|
set record btrace replay-memory-access (read-only|read-write)
|
|
|
|
|
show record btrace replay-memory-access
|
|
|
|
|
Control what memory accesses are allowed during replay.
|
|
|
|
|
|
enable target async by default; separate MI and target notions of async
This finally makes background execution commands possible by default.
However, in order to do that, there's one last thing we need to do --
we need to separate the MI and target notions of "async". Unlike the
CLI, where the user explicitly requests foreground vs background
execution in the execution command itself (c vs c&), MI chose to treat
"set target-async" specially -- setting it changes the default
behavior of execution commands.
So, we can't simply "set target-async" default to on, as that would
affect MI frontends. Instead we have to make the setting MI-specific,
and teach MI about sync commands on top of an async target.
Because the "target" word in "set target-async" ends up as a potential
source of confusion, the patch adds a "set mi-async" option, and makes
"set target-async" a deprecated alias.
Rather than make the targets always async, this patch introduces a new
"maint set target-async" option so that the GDB developer can control
whether the target is async. This makes it simpler to debug issues
arising only in the synchronous mode; important because sync mode
seems unlikely to go away.
Unlike in previous revisions, "set target-async" does not affect this
new maint parameter. The rationale for this is that then one can
easily run the test suite in the "maint set target-async off" mode and
have tests that enable mi-async fail just like they fail on
non-async-capable targets. This emulation is exactly the point of the
maint option.
I had asked Tom in a previous iteration to split the actual change of
the target async default to a separate patch, but it turns out that
that is quite awkward in this version of the patch, because with MI
async and target async decoupled (unlike in previous versions), if we
don't flip the default at the same time, then just "set target-async
on" alone never actually manages to do anything. It's best to not
have that transitory state in the tree.
Given "set target-async on" now only has effect for MI, the patch goes
through the testsuite removing it from non-MI tests. MI tests are
adjusted to use the new and less confusing "mi-async" spelling.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* NEWS: Mention "maint set target-async", "set mi-async", and that
background execution commands are now always available.
* target.h (target_async_permitted): Update comment.
* target.c (target_async_permitted, target_async_permitted_1):
Default to 1.
(set_target_async_command): Rename to ...
(maint_set_target_async_command): ... this.
(show_target_async_command): Rename to ...
(maint_show_target_async_command): ... this.
(_initialize_target): Adjust.
* infcmd.c (prepare_execution_command): Make extern.
* inferior.h (prepare_execution_command): Declare.
* infrun.c (set_observer_mode): Leave target async alone.
* mi/mi-interp.c (mi_interpreter_init): Install
mi_on_sync_execution_done as sync_execution_done observer.
(mi_on_sync_execution_done): New function.
(mi_execute_command_input_handler): Don't print the prompt if we
just started a synchronous command with an async target.
(mi_on_resume): Check sync_execution before printing prompt.
* mi/mi-main.h (mi_async_p): Declare.
* mi/mi-main.c: Include gdbcmd.h.
(mi_async_p): New function.
(mi_async, mi_async_1): New globals.
(set_mi_async_command, show_mi_async_command, mi_async): New
functions.
(exec_continue): Call prepare_execution_command.
(run_one_inferior, mi_cmd_exec_run, mi_cmd_list_target_features)
(mi_execute_async_cli_command): Use mi_async_p.
(_initialize_mi_main): Install "set mi-async". Make
"target-async" a deprecated alias.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Non-Stop Mode): Remove "set target-async 1"
from example.
(Asynchronous and non-stop modes): Document '-gdb-set mi-async'.
Mention that target-async is now deprecated.
(Maintenance Commands): Document maint set/show target-async.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* gdb.base/async-shell.exp: Don't enable target-async.
* gdb.base/async.exp
* gdb.base/corefile.exp (corefile_test_attach): Remove 'async'
parameter. Adjust.
(top level): Don't test with "target-async".
* gdb.base/dprintf-non-stop.exp: Don't enable target-async.
* gdb.base/gdb-sigterm.exp: Don't test with "target-async".
* gdb.base/inferior-died.exp: Don't enable target-async.
* gdb.base/interrupt-noterm.exp: Likewise.
* gdb.mi/mi-async.exp: Use "mi-async" instead of "target-async".
* gdb.mi/mi-nonstop-exit.exp: Likewise.
* gdb.mi/mi-nonstop.exp: Likewise.
* gdb.mi/mi-ns-stale-regcache.exp: Likewise.
* gdb.mi/mi-nsintrall.exp: Likewise.
* gdb.mi/mi-nsmoribund.exp: Likewise.
* gdb.mi/mi-nsthrexec.exp: Likewise.
* gdb.mi/mi-watch-nonstop.exp: Likewise.
* gdb.multi/watchpoint-multi.exp: Adjust comment.
* gdb.python/py-evsignal.exp: Don't enable target-async.
* gdb.python/py-evthreads.exp: Likewise.
* gdb.python/py-prompt.exp: Likewise.
* gdb.reverse/break-precsave.exp: Don't test with "target-async".
* gdb.server/solib-list.exp: Don't enable target-async.
* gdb.threads/thread-specific-bp.exp: Likewise.
* lib/mi-support.exp: Adjust to use mi-async.
2014-05-30 02:58:57 +08:00
|
|
|
maint set target-async (on|off)
|
|
|
|
|
maint show target-async
|
2014-11-14 01:56:48 +08:00
|
|
|
This controls whether GDB targets operate in synchronous or
|
|
|
|
|
asynchronous mode. Normally the default is asynchronous, if it is
|
enable target async by default; separate MI and target notions of async
This finally makes background execution commands possible by default.
However, in order to do that, there's one last thing we need to do --
we need to separate the MI and target notions of "async". Unlike the
CLI, where the user explicitly requests foreground vs background
execution in the execution command itself (c vs c&), MI chose to treat
"set target-async" specially -- setting it changes the default
behavior of execution commands.
So, we can't simply "set target-async" default to on, as that would
affect MI frontends. Instead we have to make the setting MI-specific,
and teach MI about sync commands on top of an async target.
Because the "target" word in "set target-async" ends up as a potential
source of confusion, the patch adds a "set mi-async" option, and makes
"set target-async" a deprecated alias.
Rather than make the targets always async, this patch introduces a new
"maint set target-async" option so that the GDB developer can control
whether the target is async. This makes it simpler to debug issues
arising only in the synchronous mode; important because sync mode
seems unlikely to go away.
Unlike in previous revisions, "set target-async" does not affect this
new maint parameter. The rationale for this is that then one can
easily run the test suite in the "maint set target-async off" mode and
have tests that enable mi-async fail just like they fail on
non-async-capable targets. This emulation is exactly the point of the
maint option.
I had asked Tom in a previous iteration to split the actual change of
the target async default to a separate patch, but it turns out that
that is quite awkward in this version of the patch, because with MI
async and target async decoupled (unlike in previous versions), if we
don't flip the default at the same time, then just "set target-async
on" alone never actually manages to do anything. It's best to not
have that transitory state in the tree.
Given "set target-async on" now only has effect for MI, the patch goes
through the testsuite removing it from non-MI tests. MI tests are
adjusted to use the new and less confusing "mi-async" spelling.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* NEWS: Mention "maint set target-async", "set mi-async", and that
background execution commands are now always available.
* target.h (target_async_permitted): Update comment.
* target.c (target_async_permitted, target_async_permitted_1):
Default to 1.
(set_target_async_command): Rename to ...
(maint_set_target_async_command): ... this.
(show_target_async_command): Rename to ...
(maint_show_target_async_command): ... this.
(_initialize_target): Adjust.
* infcmd.c (prepare_execution_command): Make extern.
* inferior.h (prepare_execution_command): Declare.
* infrun.c (set_observer_mode): Leave target async alone.
* mi/mi-interp.c (mi_interpreter_init): Install
mi_on_sync_execution_done as sync_execution_done observer.
(mi_on_sync_execution_done): New function.
(mi_execute_command_input_handler): Don't print the prompt if we
just started a synchronous command with an async target.
(mi_on_resume): Check sync_execution before printing prompt.
* mi/mi-main.h (mi_async_p): Declare.
* mi/mi-main.c: Include gdbcmd.h.
(mi_async_p): New function.
(mi_async, mi_async_1): New globals.
(set_mi_async_command, show_mi_async_command, mi_async): New
functions.
(exec_continue): Call prepare_execution_command.
(run_one_inferior, mi_cmd_exec_run, mi_cmd_list_target_features)
(mi_execute_async_cli_command): Use mi_async_p.
(_initialize_mi_main): Install "set mi-async". Make
"target-async" a deprecated alias.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Non-Stop Mode): Remove "set target-async 1"
from example.
(Asynchronous and non-stop modes): Document '-gdb-set mi-async'.
Mention that target-async is now deprecated.
(Maintenance Commands): Document maint set/show target-async.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* gdb.base/async-shell.exp: Don't enable target-async.
* gdb.base/async.exp
* gdb.base/corefile.exp (corefile_test_attach): Remove 'async'
parameter. Adjust.
(top level): Don't test with "target-async".
* gdb.base/dprintf-non-stop.exp: Don't enable target-async.
* gdb.base/gdb-sigterm.exp: Don't test with "target-async".
* gdb.base/inferior-died.exp: Don't enable target-async.
* gdb.base/interrupt-noterm.exp: Likewise.
* gdb.mi/mi-async.exp: Use "mi-async" instead of "target-async".
* gdb.mi/mi-nonstop-exit.exp: Likewise.
* gdb.mi/mi-nonstop.exp: Likewise.
* gdb.mi/mi-ns-stale-regcache.exp: Likewise.
* gdb.mi/mi-nsintrall.exp: Likewise.
* gdb.mi/mi-nsmoribund.exp: Likewise.
* gdb.mi/mi-nsthrexec.exp: Likewise.
* gdb.mi/mi-watch-nonstop.exp: Likewise.
* gdb.multi/watchpoint-multi.exp: Adjust comment.
* gdb.python/py-evsignal.exp: Don't enable target-async.
* gdb.python/py-evthreads.exp: Likewise.
* gdb.python/py-prompt.exp: Likewise.
* gdb.reverse/break-precsave.exp: Don't test with "target-async".
* gdb.server/solib-list.exp: Don't enable target-async.
* gdb.threads/thread-specific-bp.exp: Likewise.
* lib/mi-support.exp: Adjust to use mi-async.
2014-05-30 02:58:57 +08:00
|
|
|
available; but this can be changed to more easily debug problems
|
2014-11-14 01:56:48 +08:00
|
|
|
occurring only in synchronous mode.
|
enable target async by default; separate MI and target notions of async
This finally makes background execution commands possible by default.
However, in order to do that, there's one last thing we need to do --
we need to separate the MI and target notions of "async". Unlike the
CLI, where the user explicitly requests foreground vs background
execution in the execution command itself (c vs c&), MI chose to treat
"set target-async" specially -- setting it changes the default
behavior of execution commands.
So, we can't simply "set target-async" default to on, as that would
affect MI frontends. Instead we have to make the setting MI-specific,
and teach MI about sync commands on top of an async target.
Because the "target" word in "set target-async" ends up as a potential
source of confusion, the patch adds a "set mi-async" option, and makes
"set target-async" a deprecated alias.
Rather than make the targets always async, this patch introduces a new
"maint set target-async" option so that the GDB developer can control
whether the target is async. This makes it simpler to debug issues
arising only in the synchronous mode; important because sync mode
seems unlikely to go away.
Unlike in previous revisions, "set target-async" does not affect this
new maint parameter. The rationale for this is that then one can
easily run the test suite in the "maint set target-async off" mode and
have tests that enable mi-async fail just like they fail on
non-async-capable targets. This emulation is exactly the point of the
maint option.
I had asked Tom in a previous iteration to split the actual change of
the target async default to a separate patch, but it turns out that
that is quite awkward in this version of the patch, because with MI
async and target async decoupled (unlike in previous versions), if we
don't flip the default at the same time, then just "set target-async
on" alone never actually manages to do anything. It's best to not
have that transitory state in the tree.
Given "set target-async on" now only has effect for MI, the patch goes
through the testsuite removing it from non-MI tests. MI tests are
adjusted to use the new and less confusing "mi-async" spelling.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* NEWS: Mention "maint set target-async", "set mi-async", and that
background execution commands are now always available.
* target.h (target_async_permitted): Update comment.
* target.c (target_async_permitted, target_async_permitted_1):
Default to 1.
(set_target_async_command): Rename to ...
(maint_set_target_async_command): ... this.
(show_target_async_command): Rename to ...
(maint_show_target_async_command): ... this.
(_initialize_target): Adjust.
* infcmd.c (prepare_execution_command): Make extern.
* inferior.h (prepare_execution_command): Declare.
* infrun.c (set_observer_mode): Leave target async alone.
* mi/mi-interp.c (mi_interpreter_init): Install
mi_on_sync_execution_done as sync_execution_done observer.
(mi_on_sync_execution_done): New function.
(mi_execute_command_input_handler): Don't print the prompt if we
just started a synchronous command with an async target.
(mi_on_resume): Check sync_execution before printing prompt.
* mi/mi-main.h (mi_async_p): Declare.
* mi/mi-main.c: Include gdbcmd.h.
(mi_async_p): New function.
(mi_async, mi_async_1): New globals.
(set_mi_async_command, show_mi_async_command, mi_async): New
functions.
(exec_continue): Call prepare_execution_command.
(run_one_inferior, mi_cmd_exec_run, mi_cmd_list_target_features)
(mi_execute_async_cli_command): Use mi_async_p.
(_initialize_mi_main): Install "set mi-async". Make
"target-async" a deprecated alias.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Non-Stop Mode): Remove "set target-async 1"
from example.
(Asynchronous and non-stop modes): Document '-gdb-set mi-async'.
Mention that target-async is now deprecated.
(Maintenance Commands): Document maint set/show target-async.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* gdb.base/async-shell.exp: Don't enable target-async.
* gdb.base/async.exp
* gdb.base/corefile.exp (corefile_test_attach): Remove 'async'
parameter. Adjust.
(top level): Don't test with "target-async".
* gdb.base/dprintf-non-stop.exp: Don't enable target-async.
* gdb.base/gdb-sigterm.exp: Don't test with "target-async".
* gdb.base/inferior-died.exp: Don't enable target-async.
* gdb.base/interrupt-noterm.exp: Likewise.
* gdb.mi/mi-async.exp: Use "mi-async" instead of "target-async".
* gdb.mi/mi-nonstop-exit.exp: Likewise.
* gdb.mi/mi-nonstop.exp: Likewise.
* gdb.mi/mi-ns-stale-regcache.exp: Likewise.
* gdb.mi/mi-nsintrall.exp: Likewise.
* gdb.mi/mi-nsmoribund.exp: Likewise.
* gdb.mi/mi-nsthrexec.exp: Likewise.
* gdb.mi/mi-watch-nonstop.exp: Likewise.
* gdb.multi/watchpoint-multi.exp: Adjust comment.
* gdb.python/py-evsignal.exp: Don't enable target-async.
* gdb.python/py-evthreads.exp: Likewise.
* gdb.python/py-prompt.exp: Likewise.
* gdb.reverse/break-precsave.exp: Don't test with "target-async".
* gdb.server/solib-list.exp: Don't enable target-async.
* gdb.threads/thread-specific-bp.exp: Likewise.
* lib/mi-support.exp: Adjust to use mi-async.
2014-05-30 02:58:57 +08:00
|
|
|
|
|
|
|
|
set mi-async (on|off)
|
|
|
|
|
show mi-async
|
|
|
|
|
Control whether MI asynchronous mode is preferred. This supersedes
|
|
|
|
|
"set target-async" of previous GDB versions.
|
|
|
|
|
|
|
|
|
|
* "set target-async" is deprecated as a CLI option and is now an alias
|
|
|
|
|
for "set mi-async" (only puts MI into async mode).
|
|
|
|
|
|
|
|
|
|
* Background execution commands (e.g., "c&", "s&", etc.) are now
|
|
|
|
|
possible ``out of the box'' if the target supports them. Previously
|
|
|
|
|
the user would need to explicitly enable the possibility with the
|
|
|
|
|
"set target-async on" command.
|
|
|
|
|
|
2014-01-23 06:17:39 +08:00
|
|
|
* New features in the GDB remote stub, GDBserver
|
|
|
|
|
|
|
|
|
|
** New option --debug-format=option1[,option2,...] allows one to add
|
|
|
|
|
additional text to each output. At present only timestamps
|
|
|
|
|
are supported: --debug-format=timestamps.
|
|
|
|
|
Timestamps can also be turned on with the
|
|
|
|
|
"monitor set debug-format timestamps" command from GDB.
|
|
|
|
|
|
2013-05-13 20:57:42 +08:00
|
|
|
* The 'record instruction-history' command now starts counting instructions
|
|
|
|
|
at one. This also affects the instruction ranges reported by the
|
|
|
|
|
'record function-call-history' command when given the /i modifier.
|
|
|
|
|
|
2013-04-18 16:58:05 +08:00
|
|
|
* The command 'record function-call-history' supports a new modifier '/c' to
|
|
|
|
|
indent the function names based on their call stack depth.
|
|
|
|
|
The fields for the '/i' and '/l' modifier have been reordered.
|
|
|
|
|
The source line range is now prefixed with 'at'.
|
|
|
|
|
The instruction range is now prefixed with 'inst'.
|
|
|
|
|
Both ranges are now printed as '<from>, <to>' to allow copy&paste to the
|
|
|
|
|
"record instruction-history" and "list" commands.
|
|
|
|
|
|
2013-04-17 15:39:43 +08:00
|
|
|
* The ranges given as arguments to the 'record function-call-history' and
|
|
|
|
|
'record instruction-history' commands are now inclusive.
|
|
|
|
|
|
2013-03-25 23:01:33 +08:00
|
|
|
* The btrace record target now supports the 'record goto' command.
|
2013-03-27 16:49:47 +08:00
|
|
|
For locations inside the execution trace, the back trace is computed
|
|
|
|
|
based on the information stored in the execution trace.
|
2013-03-25 23:01:33 +08:00
|
|
|
|
2013-05-06 22:04:46 +08:00
|
|
|
* The btrace record target supports limited reverse execution and replay.
|
|
|
|
|
The target does not record data and therefore does not allow reading
|
|
|
|
|
memory or registers.
|
|
|
|
|
|
2014-01-23 01:54:43 +08:00
|
|
|
* The "catch syscall" command now works on s390*-linux* targets.
|
|
|
|
|
|
Make compare-sections work against all targets; add compare-sections [-r] tests.
This does two things:
1. Adds a test.
Recently compare-sections got a new "-r" switch, but given no test
existed for compare-sections, the patch was allowed in with no
testsuite addition. This now adds a test for both compare-sections
and compare-sections -r.
2. Makes the compare-sections command work against all targets.
Currently, compare-sections only works with remote targets, and only
those that support the qCRC packet. The patch makes it so that if the
target doesn't support accelerating memory verification, then GDB
falls back to comparing memory itself. This is of course slower, but
it's better than nothing, IMO. While testing against extended-remote
GDBserver I noticed that we send the qCRC request to the target if
we're connected, but not yet running a program. That can't work of
course -- the patch fixes that. This all also goes in the direction
of bridging the local/remote parity gap.
I didn't decouple 1. from 2., because that would mean that the test
would need to handle the case of the target not supporting the
command.
Tested on x86_64 Fedora 17, native, remote GDBserver, and
extended-remote GDBserver. I also hack-disabled qCRC support to make
sure the fallback paths in remote.c work.
gdb/doc/
2014-05-20 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Memory) <compare-sections>: Generalize comments to
not be remote specific. Add cross reference to the qCRC packet.
(Separate Debug Files): Update cross reference to the qCRC packet.
(General Query Packets) <qCRC packet>: Add anchor.
gdb/
2014-05-20 Pedro Alves <palves@redhat.com>
* NEWS: Mention that compare-sections now works with all targets.
* remote.c (PACKET_qCRC): New enum value.
(remote_verify_memory): Don't send qCRC if the target has no
execution. Use packet_support/packet_ok. If the target doesn't
support the qCRC packet, fallback to a deep memory copy.
(compare_sections_command): Say "target image" instead of "remote
executable".
(_initialize_remote): Add PACKET_qCRC to the list of config
packets that have no associated command. Extend comment.
* target.c (simple_verify_memory, default_verify_memory): New
function.
* target.h (struct target_ops) <to_verify_memory>: Default to
default_verify_memory.
(simple_verify_memory): New declaration.
* target-delegates.c: Regenerate.
gdb/testsuite/
2014-05-20 Pedro Alves <palves@redhat.com>
* gdb.base/compare-sections.c: New file.
* gdb.base/compare-sections.exp: New file.
2014-05-21 02:11:39 +08:00
|
|
|
* The "compare-sections" command is no longer specific to target
|
|
|
|
|
remote. It now works with all targets.
|
|
|
|
|
|
2014-05-22 01:30:46 +08:00
|
|
|
* All native targets are now consistently called "native".
|
|
|
|
|
Consequently, the "target child", "target GNU", "target djgpp",
|
|
|
|
|
"target procfs" (Solaris/Irix/OSF/AIX) and "target darwin-child"
|
|
|
|
|
commands have been replaced with "target native". The QNX/NTO port
|
|
|
|
|
leaves the "procfs" target in place and adds a "native" target for
|
|
|
|
|
consistency with other ports. The impact on users should be minimal
|
|
|
|
|
as these commands previously either throwed an error, or were
|
|
|
|
|
no-ops. The target's name is visible in the output of the following
|
|
|
|
|
commands: "help target", "info target", "info files", "maint print
|
|
|
|
|
target-stack".
|
|
|
|
|
|
Allow making GDB not automatically connect to the native target.
Sometimes it's useful to be able to disable the automatic connection
to the native target. E.g., sometimes GDB disconnects from the
extended-remote target I was debugging, without me noticing it, and
then I do "run". That starts the program locally, and only after a
little head scratch session do I figure out the program is running
locally instead of remotely as intended. Same thing with "attach",
"info os", etc.
With the patch, we now can have this instead:
(gdb) set auto-connect-native-target off
(gdb) target extended-remote :9999
...
*gdb disconnects*
(gdb) run
Don't know how to run. Try "help target".
To still be able to connect to the native target with
auto-connect-native-target set to off, I've made "target native" work
instead of erroring out as today.
Before:
(gdb) target native
Use the "run" command to start a native process.
After:
(gdb) target native
Done. Use the "run" command to start a process.
(gdb) maint print target-stack
The current target stack is:
- native (Native process)
- exec (Local exec file)
- None (None)
(gdb) run
Starting program: ./a.out
...
I've also wanted this for the testsuite, when running against the
native-extended-gdbserver.exp board (runs against gdbserver in
extended-remote mode). With a non-native-target board, it's always a
bug to launch a program with the native target. Turns out we still
have one such case this patch catches:
(gdb) break main
Breakpoint 1 at 0x4009e5: file ../../../src/gdb/testsuite/gdb.base/coremaker.c, line 138.
(gdb) run
Don't know how to run. Try "help target".
(gdb) FAIL: gdb.base/corefile.exp: run: with core
On the patch itself, probably the least obvious bit is the need to go
through all targets, and move the unpush_target call to after the
generic_mourn_inferior call instead of before. This is what
inf-ptrace.c does too, ever since multi-process support was added.
The reason inf-ptrace.c does things in that order is that in the
current multi-process/single-target model, we shouldn't unpush the
target if there are still other live inferiors being debugged. The
check for that is "have_inferiors ()" (a misnomer nowadays...), which
does:
have_inferiors (void)
{
for (inf = inferior_list; inf; inf = inf->next)
if (inf->pid != 0)
return 1;
It's generic_mourn_inferior that ends up clearing inf->pid, so we need
to call it before the have_inferiors check. To make all native
targets behave the same WRT to explicit "target native", I've added an
inf_child_maybe_unpush_target function that targets call instead of
calling unpush_target directly, and as that includes the
have_inferiors check, I needed to adjust the targets.
Tested on x86_64 Fedora 20, native, and also with the
extended-gdbserver board.
Confirmed a cross build of djgpp gdb still builds.
Smoke tested a cross build of Windows gdb under Wine.
Untested otherwise.
gdb/
2014-05-21 Pedro Alves <palves@redhat.com>
* inf-child.c (inf_child_ops, inf_child_explicitly_opened): New
globals.
(inf_child_open_target): New function.
(inf_child_open): Use inf_child_open_target to push the target
instead of erroring out.
(inf_child_disconnect, inf_child_close)
(inf_child_maybe_unpush_target): New functions.
(inf_child_target): Install inf_child_disconnect and
inf_child_close. Store a pointer to the returned object.
* inf-child.h (inf_child_open_target, inf_child_maybe_unpush): New
declarations.
* target.c (auto_connect_native_target): New global.
(show_default_run_target): New function.
(find_default_run_target): Return NULL if automatically connecting
to the native target is disabled.
(_initialize_target): Install set/show auto-connect-native-target.
* NEWS: Mention "set auto-connect-native-target", and "target
native".
* linux-nat.c (super_close): New global.
(linux_nat_close): Call super_close.
(linux_nat_add_target): Store a pointer to the base class's
to_close method.
* inf-ptrace.c (inf_ptrace_mourn_inferior, inf_ptrace_detach): Use
inf_child_maybe_unpush.
* inf-ttrace.c (inf_ttrace_him): Don't push the target if it is
already pushed.
(inf_ttrace_mourn_inferior): Only unpush the target after mourning
the inferior. Use inf_child_maybe_unpush_target.
(inf_ttrace_attach): Don't push the target if it is already
pushed.
(inf_ttrace_detach): Use inf_child_maybe_unpush_target.
* darwin-nat.c (darwin_mourn_inferior): Only unpush the target
after mourning the inferior. Use inf_child_maybe_unpush_target.
(darwin_attach_pid): Don't push the target if it is already
pushed.
* gnu-nat.c (gnu_mourn_inferior): Only unpush the target after
mourning the inferior. Use inf_child_maybe_unpush_target.
(gnu_detach): Use inf_child_maybe_unpush_target.
* go32-nat.c (go32_create_inferior): Don't push the target if it
is already pushed.
(go32_mourn_inferior): Use inf_child_maybe_unpush_target.
* nto-procfs.c (procfs_is_nto_target): Adjust comment.
(procfs_open): Rename to ...
(procfs_open_1): ... this. Add target_ops parameter. Adjust
comments. Can target_preopen before changing node. Call
inf_child_open_target to push the target explicitly.
(procfs_attach): Don't push the target if it is already pushed.
(procfs_detach): Use inf_child_maybe_unpush_target.
(procfs_create_inferior): Don't push the target if it is already
pushed.
(nto_native_ops): New global.
(procfs_open): Reimplement.
(procfs_native_open): New function.
(init_procfs_targets): Install procfs_native_open as to_open of
"target native". Store a pointer to the "native" target in
nto_native_ops.
* procfs.c (procfs_attach): Don't push the target if it is already
pushed.
(procfs_detach): Use inf_child_maybe_unpush_target.
(procfs_mourn_inferior): Only unpush the target after mourning the
inferior. Use inf_child_maybe_unpush_target.
(procfs_init_inferior): Don't push the target if it is already
pushed.
* windows-nat.c (do_initial_windows_stuff): Don't push the target
if it is already pushed.
(windows_detach): Use inf_child_maybe_unpush_target.
(windows_mourn_inferior): Only unpush the target after mourning
the inferior. Use inf_child_maybe_unpush_target.
gdb/doc/
2014-05-21 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Starting): Document "set/show
auto-connect-native-target".
(Target Commands): Document "target native".
gdb/testsuite/
2014-05-21 Pedro Alves <palves@redhat.com>
* boards/gdbserver-base.exp (GDBFLAGS): Set to "set
auto-connect-native-target off".
* gdb.base/auto-connect-native-target.c: New file.
* gdb.base/auto-connect-native-target.exp: New file.
2014-05-22 01:30:47 +08:00
|
|
|
* The "target native" command now connects to the native target. This
|
|
|
|
|
can be used to launch native programs even when "set
|
|
|
|
|
auto-connect-native-target" is set to off.
|
|
|
|
|
|
2016-01-12 23:03:11 +08:00
|
|
|
* GDB now supports access to Intel MPX registers on GNU/Linux.
|
2014-08-05 03:32:06 +08:00
|
|
|
|
2016-01-12 23:03:11 +08:00
|
|
|
* Support for Intel AVX-512 registers on GNU/Linux.
|
|
|
|
|
Support displaying and modifying Intel AVX-512 registers
|
2014-08-05 03:32:06 +08:00
|
|
|
$zmm0 - $zmm31 and $k0 - $k7 on GNU/Linux.
|
|
|
|
|
|
2013-06-03 21:39:35 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
qXfer:btrace:read's annex
|
|
|
|
|
The qXfer:btrace:read packet supports a new annex 'delta' to read
|
|
|
|
|
branch trace incrementally.
|
|
|
|
|
|
2013-12-02 22:45:09 +08:00
|
|
|
* Python Scripting
|
|
|
|
|
|
|
|
|
|
** Valid Python operations on gdb.Value objects representing
|
|
|
|
|
structs/classes invoke the corresponding overloaded operators if
|
|
|
|
|
available.
|
2014-03-31 07:24:50 +08:00
|
|
|
** New `Xmethods' feature in the Python API. Xmethods are
|
|
|
|
|
additional methods or replacements for existing methods of a C++
|
|
|
|
|
class. This feature is useful for those cases where a method
|
|
|
|
|
defined in C++ source code could be inlined or optimized out by
|
|
|
|
|
the compiler, making it unavailable to GDB.
|
2013-12-02 22:45:09 +08:00
|
|
|
|
2014-02-05 01:19:51 +08:00
|
|
|
* New targets
|
|
|
|
|
PowerPC64 GNU/Linux little-endian powerpc64le-*-linux*
|
|
|
|
|
|
Deprecate windows-specific dll-symbols command and aliases
The "dll-symbols" command, specific to native Windows platforms,
gives the impression that the symbols were not loaded, first
because it completes silently, and second because the "info shared"
output does not get updated after the command completes:
(gdb) dll-symbols C:\WINDOWS\syswow64\rpcrt4.dll
(gdb) info shared
From To Syms Read Shared Object Library
[...]
0x77e51000 0x77ee2554 No C:\WINDOWS\system32\rpcrt4.dll
(we exected the "Syms Read" column to read "Yes").
As far as I can tell, the symbols actually do get loaded, but completely
independently from the solib framework, which explains the silent
loading and the fact that the "Syms Read" column does not get updated.
See windows-nat.c::safe_symbol_file_add_stub, which calls symbol_file_add
instead of calling solib_add.
But, aside from the fact that the "Syms Read" status does not get
updated, I also noticed that it does not take into account the DLL's
actual load address when loading its symbols. As a result, I believe
that we get it wrong if the DLL does not get loaded at the prefered
address.
Rather than trying to fix this command, there does not seem to be
a reason other than historical for having Windows-specific commands
which essentially re-implements the "sharedlibrary" command. The
command interface is slightly different (the latter takes a regexp
rather than a plain filename), but it should be just as easy to use
the "sharedlibrary" command, or its "share" alias, as usisng the
"dll-symbols" command. For instance:
(gdb) share rpcrt4.dll
Reading symbols from C:\WINDOWS\system32\rpcrt4.dll...(no debugging symbols found)...done.
Loaded symbols for C:\WINDOWS\system32\rpcrt4.dll
(gdb) info shared
From To Syms Read Shared Object Library
[...]
0x77e51000 0x77ee2554 Yes (*) C:\WINDOWS\system32\rpcrt4.dll
This patch therefore deprecates the "dll-symbols" command, as well
as its two aliases "add-shared-symbol-files" and "assf", with a view
of deleting them as soon as the 7.8 branch gets cut.
gdb/ChangeLog:
* windows-nat.c (_initialize_windows_nat): Deprecate the
"dll-symbols" command. Turn the "add-shared-symbol-files"
and "assf" aliases into commands, and deprecate them as well.
* NEWS: Add entry explaining that "dll-symbols" and its two
aliases are now deprecated.
gdb/doc/ChangeLog:
* gdb.texinfo (Files): Document "add-shared-symbol-files"
and "assf" as being deprecated.
(Cygwin Native): Likewise for "dll-symbols".
(Non-debug DLL Symbols): Remove reference to "dll-symbols"
as a way to force the loading of symbols from a DLL.
2014-01-31 17:22:53 +08:00
|
|
|
* The "dll-symbols" command, and its two aliases ("add-shared-symbol-files"
|
|
|
|
|
and "assf"), have been deprecated. Use the "sharedlibrary" command, or
|
|
|
|
|
its alias "share", instead.
|
|
|
|
|
|
2014-05-20 02:46:19 +08:00
|
|
|
* The commands "set remotebaud" and "show remotebaud" are no longer
|
|
|
|
|
supported. Use "set serial baud" and "show serial baud" (respectively)
|
|
|
|
|
instead.
|
|
|
|
|
|
enable target async by default; separate MI and target notions of async
This finally makes background execution commands possible by default.
However, in order to do that, there's one last thing we need to do --
we need to separate the MI and target notions of "async". Unlike the
CLI, where the user explicitly requests foreground vs background
execution in the execution command itself (c vs c&), MI chose to treat
"set target-async" specially -- setting it changes the default
behavior of execution commands.
So, we can't simply "set target-async" default to on, as that would
affect MI frontends. Instead we have to make the setting MI-specific,
and teach MI about sync commands on top of an async target.
Because the "target" word in "set target-async" ends up as a potential
source of confusion, the patch adds a "set mi-async" option, and makes
"set target-async" a deprecated alias.
Rather than make the targets always async, this patch introduces a new
"maint set target-async" option so that the GDB developer can control
whether the target is async. This makes it simpler to debug issues
arising only in the synchronous mode; important because sync mode
seems unlikely to go away.
Unlike in previous revisions, "set target-async" does not affect this
new maint parameter. The rationale for this is that then one can
easily run the test suite in the "maint set target-async off" mode and
have tests that enable mi-async fail just like they fail on
non-async-capable targets. This emulation is exactly the point of the
maint option.
I had asked Tom in a previous iteration to split the actual change of
the target async default to a separate patch, but it turns out that
that is quite awkward in this version of the patch, because with MI
async and target async decoupled (unlike in previous versions), if we
don't flip the default at the same time, then just "set target-async
on" alone never actually manages to do anything. It's best to not
have that transitory state in the tree.
Given "set target-async on" now only has effect for MI, the patch goes
through the testsuite removing it from non-MI tests. MI tests are
adjusted to use the new and less confusing "mi-async" spelling.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* NEWS: Mention "maint set target-async", "set mi-async", and that
background execution commands are now always available.
* target.h (target_async_permitted): Update comment.
* target.c (target_async_permitted, target_async_permitted_1):
Default to 1.
(set_target_async_command): Rename to ...
(maint_set_target_async_command): ... this.
(show_target_async_command): Rename to ...
(maint_show_target_async_command): ... this.
(_initialize_target): Adjust.
* infcmd.c (prepare_execution_command): Make extern.
* inferior.h (prepare_execution_command): Declare.
* infrun.c (set_observer_mode): Leave target async alone.
* mi/mi-interp.c (mi_interpreter_init): Install
mi_on_sync_execution_done as sync_execution_done observer.
(mi_on_sync_execution_done): New function.
(mi_execute_command_input_handler): Don't print the prompt if we
just started a synchronous command with an async target.
(mi_on_resume): Check sync_execution before printing prompt.
* mi/mi-main.h (mi_async_p): Declare.
* mi/mi-main.c: Include gdbcmd.h.
(mi_async_p): New function.
(mi_async, mi_async_1): New globals.
(set_mi_async_command, show_mi_async_command, mi_async): New
functions.
(exec_continue): Call prepare_execution_command.
(run_one_inferior, mi_cmd_exec_run, mi_cmd_list_target_features)
(mi_execute_async_cli_command): Use mi_async_p.
(_initialize_mi_main): Install "set mi-async". Make
"target-async" a deprecated alias.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Non-Stop Mode): Remove "set target-async 1"
from example.
(Asynchronous and non-stop modes): Document '-gdb-set mi-async'.
Mention that target-async is now deprecated.
(Maintenance Commands): Document maint set/show target-async.
2014-05-29 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@redhat.com>
* gdb.base/async-shell.exp: Don't enable target-async.
* gdb.base/async.exp
* gdb.base/corefile.exp (corefile_test_attach): Remove 'async'
parameter. Adjust.
(top level): Don't test with "target-async".
* gdb.base/dprintf-non-stop.exp: Don't enable target-async.
* gdb.base/gdb-sigterm.exp: Don't test with "target-async".
* gdb.base/inferior-died.exp: Don't enable target-async.
* gdb.base/interrupt-noterm.exp: Likewise.
* gdb.mi/mi-async.exp: Use "mi-async" instead of "target-async".
* gdb.mi/mi-nonstop-exit.exp: Likewise.
* gdb.mi/mi-nonstop.exp: Likewise.
* gdb.mi/mi-ns-stale-regcache.exp: Likewise.
* gdb.mi/mi-nsintrall.exp: Likewise.
* gdb.mi/mi-nsmoribund.exp: Likewise.
* gdb.mi/mi-nsthrexec.exp: Likewise.
* gdb.mi/mi-watch-nonstop.exp: Likewise.
* gdb.multi/watchpoint-multi.exp: Adjust comment.
* gdb.python/py-evsignal.exp: Don't enable target-async.
* gdb.python/py-evthreads.exp: Likewise.
* gdb.python/py-prompt.exp: Likewise.
* gdb.reverse/break-precsave.exp: Don't test with "target-async".
* gdb.server/solib-list.exp: Don't enable target-async.
* gdb.threads/thread-specific-bp.exp: Likewise.
* lib/mi-support.exp: Adjust to use mi-async.
2014-05-30 02:58:57 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** A new option "-gdb-set mi-async" replaces "-gdb-set
|
|
|
|
|
target-async". The latter is left as a deprecated alias of the
|
|
|
|
|
former for backward compatibility. If the target supports it,
|
|
|
|
|
CLI background execution commands are now always possible by
|
|
|
|
|
default, independently of whether the frontend stated a
|
|
|
|
|
preference for asynchronous execution with "-gdb-set mi-async".
|
|
|
|
|
Previously "-gdb-set target-async off" affected both MI execution
|
|
|
|
|
commands and CLI execution commands.
|
|
|
|
|
|
2014-01-08 17:41:03 +08:00
|
|
|
*** Changes in GDB 7.7
|
2013-03-13 06:36:27 +08:00
|
|
|
|
2014-01-04 03:15:36 +08:00
|
|
|
* Improved support for process record-replay and reverse debugging on
|
|
|
|
|
arm*-linux* targets. Support for thumb32 and syscall instruction
|
|
|
|
|
recording has been added.
|
|
|
|
|
|
2013-12-29 00:14:11 +08:00
|
|
|
* GDB now supports SystemTap SDT probes on AArch64 GNU/Linux.
|
|
|
|
|
|
Add support for DWP file format version 2.
* NEWS: Mention support for DWP file format version 2.
* dwarf2read.c (dwarf2_section_info): Convert asection field to a
union of asection, containing_section. New fields virtual_offset
and is_virtual. Change type of readin filed from int to char.
(dwo_sections, dwo_file): Tweak comments.
(dwp_v2_section_ids): New enum.
(dwp_sections): New fields abbrev, info, line, loc, macinfo, macro,
str_offsets, types.
(virtual_v1_dwo_sections): Renamed from virtual_dwo_sections.
All uses updated.
(virtual_v2_dwo_sections): New struct.
(dwp_hash_table): New fields version, nr_columns. Change type of
section_pool field to a union.
(dwp_file): New field version.
(dwarf2_has_info): Check for virtual sections.
(get_containing_section): New function.
(get_section_bfd_owner, get_section_bfd_section): Call it.
(dwarf2_locate_sections): Update.
(dwarf2_section_empty_p): Update.
(dwarf2_read_section): Handle virtual sections.
(locate_dwz_sections): Update.
(create_dwp_hash_table): Document and handle V2 format.
(locate_v1_virtual_dwo_sections): Renamed from
locate_virtual_dwo_sections and update. All callers updated.
(create_dwo_unit_in_dwp_v1): Renamed from create_dwo_in_dwp.
Delete arg htab. Rename arg section_index to unit_index.
All callers updated.
(MAX_NR_V1_DWO_SECTIONS): Renamed from MAX_NR_DWO_SECTIONS.
All uses updated.
(create_dwp_v2_section, create_dwo_unit_in_dwp_v2): New functions.
(lookup_dwo_unit_in_dwp): Add V2 support.
(dwarf2_locate_dwo_sections): Update.
(dwarf2_locate_common_dwp_sections): Renamed from
dwarf2_locate_dwp_sections and update. All callers updated.
(dwarf2_locate_v2_dwp_sections): New function.
(open_and_init_dwp_file): Add V2 support.
(read_str_index): New locals str_section, str_offsets_section.
2013-10-05 09:44:17 +08:00
|
|
|
* GDB now supports Fission DWP file format version 2.
|
|
|
|
|
http://gcc.gnu.org/wiki/DebugFission
|
|
|
|
|
|
Based on the discussion at:
<https://sourceware.org/ml/gdb-patches/2013-09/msg00301.html>
<https://sourceware.org/ml/gdb-patches/2013-09/msg00383.html>
This patch adds a new convenience function called $_isvoid, whose
only purpose is to check whether an expression is void or not.
This became necessary because the new convenience variable
$_exitsignal (not yet approved) has a mutual exclusive behavior
with $_exitcode, i.e., when one is "defined" (i.e., non-void),
the other is cleared (i.e., becomes void). Doug wanted a way to
identify which variable to use, and checking for voidness is the
obvious solution.
It is worth mentioning that my first attempt, after a conversation with
Doug, was to actually implement a new $_isdefined() convenience
function. I would do that (for convenience variables) by calling
lookup_only_internalvar. However, I found a few problems:
- Whenever I called $_isdefined ($variable), $variable became defined
(with a void value), and $_isdefined always returned true.
- Then, I tried to implement $_isdefined ("variable"), and do the "$" +
"variable" inside GDB, thus making it impossible for GDB to create the
convenience variable. However, it was hard to extract the string
without having to mess with values and their idiossincrasies.
Therefore, I decided to abandon this attempt (specially because I
didn't want to spend too much time struggling with it).
Anyway, after talking to Doug again we decided that it would be easier
to implement $_isvoid, and this will probably help in cases like
<http://stackoverflow.com/questions/3744554/testing-if-a-gdb-convenience-variable-is-defined>.
I wrote a NEWS entry for it, and some new lines on the documentation.
gdb/
2013-09-16 Sergio Durigan Junior <sergiodj@redhat.com>
* NEWS: Mention new convenience function $_isvoid.
* value.c (isvoid_internal_fn): New function.
(_initialize_values): Add new convenience function $_isvoid.
gdb/doc/
2013-09-16 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.texinfo (Convenience Functions): Mention new convenience
function $_isvoid.
gdb/testsuite/
2013-09-16 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.base/gdbvars.c (foo_void): New function.
(foo_int): Likewise.
* gdb.base/gdbvars.exp (test_convenience_functions): New
function. Call it.
2013-09-17 01:47:30 +08:00
|
|
|
* New convenience function "$_isvoid", to check whether an expression
|
|
|
|
|
is void. A void expression is an expression where the type of the
|
|
|
|
|
result is "void". For example, some convenience variables may be
|
|
|
|
|
"void" when evaluated (e.g., "$_exitcode" before the execution of
|
|
|
|
|
the program being debugged; or an undefined convenience variable).
|
|
|
|
|
Another example, when calling a function whose return type is
|
|
|
|
|
"void".
|
|
|
|
|
|
2013-08-27 02:41:31 +08:00
|
|
|
* The "maintenance print objfiles" command now takes an optional regexp.
|
|
|
|
|
|
2013-08-23 04:32:54 +08:00
|
|
|
* The "catch syscall" command now works on arm*-linux* targets.
|
|
|
|
|
|
Print registers not saved in the frame as "<not saved>" instead of "<optimized out>".
Currently, in some scenarios, GDB prints <optimized out> when printing
outer frame registers. An <optimized out> register is a confusing
concept. What this really means is that the register is
call-clobbered, or IOW, not saved by the callee. This patch makes GDB
say that instead.
Before patch:
(gdb) p/x $rax $1 = <optimized out>
(gdb) info registers rax
rax <optimized out>
After patch:
(gdb) p/x $rax
$1 = <not saved>
(gdb) info registers rax
rax <not saved>
However, if for some reason the debug info describes a variable as
being in such a register (**), we still want to print <optimized out>
when printing the variable. IOW, <not saved> is reserved for
inspecting registers at the machine level. The patch uses
lval_register+optimized_out to encode the not saved registers, and
makes it so that optimized out variables always end up in
!lval_register values.
** See <https://sourceware.org/ml/gdb-patches/2012-08/msg00787.html>.
Current/recent enough GCC doesn't mark variables/arguments as being in
call-clobbered registers in the ranges corresponding to function
calls, while older GCCs did. Newer GCCs will just not say where the
variable is, so GDB will end up realizing the variable is optimized
out.
frame_unwind_got_optimized creates not_lval optimized out registers,
so by default, in most cases, we'll see <optimized out>.
value_of_register is the function eval.c uses for evaluating
OP_REGISTER (again, $pc, etc.), and related bits. It isn't used for
anything else. This function makes sure to return lval_register
values. The patch makes "info registers" and the MI equivalent use it
too. I think it just makes a lot of sense, as this makes it so that
when printing machine registers ($pc, etc.), we go through a central
function.
We're likely to need a different encoding at some point, if/when we
support partially saved registers. Even then, I think
value_of_register will still be the spot to tag the intention to print
machine register values differently.
value_from_register however may also return optimized out
lval_register values, so at a couple places where we're computing a
variable's location from a dwarf expression, we convert the resulting
value away from lval_register to a regular optimized out value.
Tested on x86_64 Fedora 17
gdb/
2013-10-02 Pedro Alves <palves@redhat.com>
* cp-valprint.c (cp_print_value_fields): Adjust calls to
val_print_optimized_out.
* jv-valprint.c (java_print_value_fields): Likewise.
* p-valprint.c (pascal_object_print_value_fields): Likewise.
* dwarf2loc.c (dwarf2_evaluate_loc_desc_full)
<DWARF_VALUE_REGISTER>: If the register was not saved, return a
new optimized out value.
* findvar.c (address_from_register): Likewise.
* frame.c (put_frame_register): Tweak error string to say the
register was not saved, rather than optimized out.
* infcmd.c (default_print_one_register_info): Adjust call to
val_print_optimized_out. Use value_of_register instead of
get_frame_register_value.
* mi/mi-main.c (output_register): Use value_of_register instead of
get_frame_register_value.
* valprint.c (valprint_check_validity): Likewise.
(val_print_optimized_out): New value parameter. If the value is
lval_register, print <not saved> instead.
(value_check_printable, val_print_scalar_formatted): Adjust calls
to val_print_optimized_out.
* valprint.h (val_print_optimized_out): New value parameter.
* value.c (struct value) <optimized_out>: Extend comment.
(error_value_optimized_out): New function.
(require_not_optimized_out): Use it. Use a different string for
lval_register values.
* value.h (error_value_optimized_out): New declaration.
* NEWS: Mention <not saved>.
gdb/testsuite/
2013-10-02 Pedro Alves <palves@redhat.com>
* gdb.dwarf2/dw2-reg-undefined.exp <pattern_rax_rbx_rcx_print,
pattern_rax_rbx_rcx_info>: Set to "<not saved>".
* gdb.mi/mi-reg-undefined.exp (opt_out_pattern): Delete.
(not_saved_pattern): New.
Replace use of the former with the latter.
gdb/doc/
2013-10-02 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Registers): Expand description of saved registers
in frames. Explain <not saved>.
2013-10-03 00:15:46 +08:00
|
|
|
* GDB now consistently shows "<not saved>" when printing values of
|
|
|
|
|
registers the debug info indicates have not been saved in the frame
|
|
|
|
|
and there's nowhere to retrieve them from
|
|
|
|
|
(callee-saved/call-clobbered registers):
|
|
|
|
|
|
|
|
|
|
(gdb) p $rax
|
|
|
|
|
$1 = <not saved>
|
|
|
|
|
|
|
|
|
|
(gdb) info registers rax
|
|
|
|
|
rax <not saved>
|
|
|
|
|
|
|
|
|
|
Before, the former would print "<optimized out>", and the latter
|
|
|
|
|
"*value not available*".
|
|
|
|
|
|
2013-11-16 05:09:33 +08:00
|
|
|
* New script contrib/gdb-add-index.sh for adding .gdb_index sections
|
|
|
|
|
to binaries.
|
|
|
|
|
|
2013-05-10 Phil Muldoon <pmuldoon@redhat.com>
* stack.c (backtrace_command_1): Add "no-filters", and Python frame
filter logic.
(backtrace_command): Add "no-filters" option parsing.
(_initialize_stack): Alter help to reflect "no-filters" option.
* Makefile.in (SUBDIR_PYTHON_OBS): Add py-framefilter.o
(SUBDIR_PYTHON_SRCS): Add py-framefilter.c
(py-frame.o): Add target
* data-directory/Makefile.in (PYTHON_DIR): Add Python frame
filter files.
* python/python.h: Add new frame filter constants, and flag enum.
(apply_frame_filter): Add definition.
* python/python.c (apply_frame_filter): New non-Python
enabled function.
* python/py-utils.c (py_xdecref): New function.
(make_cleanup_py_xdecref): Ditto.
* python/py-objfile.c: Declare frame_filters dictionary.
(objfpy_dealloc): Add frame_filters dealloc.
(objfpy_new): Initialize frame_filters attribute.
(objfile_to_objfile_object): Ditto.
(objfpy_get_frame_filters): New function.
(objfpy_set_frame_filters): New function.
* python/py-progspace.c: Declare frame_filters dictionary.
(pspy_dealloc): Add frame_filters dealloc.
(pspy_new): Initialize frame_filters attribute.
(pspacee_to_pspace_object): Ditto.
(pspy_get_frame_filters): New function.
(pspy_set_frame_filters): New function.
* python/py-framefilter.c: New file.
* python/lib/gdb/command/frame_filters.py: New file.
* python/lib/gdb/frames.py: New file.
* python/lib/gdb/__init__.py: Initialize global frame_filters
dictionary
* python/lib/gdb/FrameDecorator.py: New file.
* python/lib/gdb/FrameIterator.py: New file.
* mi/mi-cmds.c (mi_cmds): Add frame filters command.
* mi/mi-cmds.h: Declare.
* mi/mi-cmd-stack.c (mi_cmd_stack_list_frames): Add
--no-frame-filter logic, and Python frame filter logic.
(stack_enable_frame_filters): New function.
(parse_no_frame_option): Ditto.
(mi_cmd_stack_list_frames): Add --no-frame-filter and Python frame
filter logic.
(mi_cmd_stack_list_locals): Ditto.
(mi_cmd_stack_list_args): Ditto.
(mi_cmd_stack_list_variables): Ditto.
* NEWS: Add frame filter note.
2013-05-10 Phil Muldoon <pmuldoon@redhat.com>
* gdb.python/py-framefilter.py: New File.
* gdb.python/py-framefilter-mi.exp: Ditto.
* gdb.python/py-framefilter.c: Ditto.
* gdb.python/py-framefilter-mi.exp: Ditto.
* gdb.python/py-framefilter-mi.c: Ditto,
* gdb.python/py-framefilter-gdb.py.in: Ditto.
2013-05-10 Phil Muldoon <pmuldoon@redhat.com>
* gdb.texinfo (Backtrace): Add "no-filter" argument.
(Python API): Add Frame Filters API, Frame Wrapper API,
Writing a Frame Filter/Wrapper, Managing Management of Frame
Filters chapter entries.
(Frame Filters API): New Node.
(Frame Wrapper API): New Node.
(Writing a Frame Filter): New Node.
(Managing Frame Filters): New Node.
(Progspaces In Python): Add note about frame_filters attribute.
(Objfiles in Python): Ditto.
(GDB/MI Stack Manipulation): Add -enable-frame-filters command,
@anchors and --no-frame-filters option to -stack-list-variables,
-stack-list-frames, -stack-list-locals and -stack-list-arguments
commands.
2013-05-10 18:26:03 +08:00
|
|
|
* Python scripting
|
|
|
|
|
|
|
|
|
|
** Frame filters and frame decorators have been added.
|
2013-11-07 20:04:45 +08:00
|
|
|
** Temporary breakpoints are now supported.
|
2013-11-12 03:49:45 +08:00
|
|
|
** Line tables representation has been added.
|
2013-12-13 07:18:27 +08:00
|
|
|
** New attribute 'parent_type' for gdb.Field objects.
|
|
|
|
|
** gdb.Field objects can be used as subscripts on gdb.Value objects.
|
2013-12-23 11:18:51 +08:00
|
|
|
** New attribute 'name' for gdb.Type objects.
|
2013-05-10 Phil Muldoon <pmuldoon@redhat.com>
* stack.c (backtrace_command_1): Add "no-filters", and Python frame
filter logic.
(backtrace_command): Add "no-filters" option parsing.
(_initialize_stack): Alter help to reflect "no-filters" option.
* Makefile.in (SUBDIR_PYTHON_OBS): Add py-framefilter.o
(SUBDIR_PYTHON_SRCS): Add py-framefilter.c
(py-frame.o): Add target
* data-directory/Makefile.in (PYTHON_DIR): Add Python frame
filter files.
* python/python.h: Add new frame filter constants, and flag enum.
(apply_frame_filter): Add definition.
* python/python.c (apply_frame_filter): New non-Python
enabled function.
* python/py-utils.c (py_xdecref): New function.
(make_cleanup_py_xdecref): Ditto.
* python/py-objfile.c: Declare frame_filters dictionary.
(objfpy_dealloc): Add frame_filters dealloc.
(objfpy_new): Initialize frame_filters attribute.
(objfile_to_objfile_object): Ditto.
(objfpy_get_frame_filters): New function.
(objfpy_set_frame_filters): New function.
* python/py-progspace.c: Declare frame_filters dictionary.
(pspy_dealloc): Add frame_filters dealloc.
(pspy_new): Initialize frame_filters attribute.
(pspacee_to_pspace_object): Ditto.
(pspy_get_frame_filters): New function.
(pspy_set_frame_filters): New function.
* python/py-framefilter.c: New file.
* python/lib/gdb/command/frame_filters.py: New file.
* python/lib/gdb/frames.py: New file.
* python/lib/gdb/__init__.py: Initialize global frame_filters
dictionary
* python/lib/gdb/FrameDecorator.py: New file.
* python/lib/gdb/FrameIterator.py: New file.
* mi/mi-cmds.c (mi_cmds): Add frame filters command.
* mi/mi-cmds.h: Declare.
* mi/mi-cmd-stack.c (mi_cmd_stack_list_frames): Add
--no-frame-filter logic, and Python frame filter logic.
(stack_enable_frame_filters): New function.
(parse_no_frame_option): Ditto.
(mi_cmd_stack_list_frames): Add --no-frame-filter and Python frame
filter logic.
(mi_cmd_stack_list_locals): Ditto.
(mi_cmd_stack_list_args): Ditto.
(mi_cmd_stack_list_variables): Ditto.
* NEWS: Add frame filter note.
2013-05-10 Phil Muldoon <pmuldoon@redhat.com>
* gdb.python/py-framefilter.py: New File.
* gdb.python/py-framefilter-mi.exp: Ditto.
* gdb.python/py-framefilter.c: Ditto.
* gdb.python/py-framefilter-mi.exp: Ditto.
* gdb.python/py-framefilter-mi.c: Ditto,
* gdb.python/py-framefilter-gdb.py.in: Ditto.
2013-05-10 Phil Muldoon <pmuldoon@redhat.com>
* gdb.texinfo (Backtrace): Add "no-filter" argument.
(Python API): Add Frame Filters API, Frame Wrapper API,
Writing a Frame Filter/Wrapper, Managing Management of Frame
Filters chapter entries.
(Frame Filters API): New Node.
(Frame Wrapper API): New Node.
(Writing a Frame Filter): New Node.
(Managing Frame Filters): New Node.
(Progspaces In Python): Add note about frame_filters attribute.
(Objfiles in Python): Ditto.
(GDB/MI Stack Manipulation): Add -enable-frame-filters command,
@anchors and --no-frame-filters option to -stack-list-variables,
-stack-list-frames, -stack-list-locals and -stack-list-arguments
commands.
2013-05-10 18:26:03 +08:00
|
|
|
|
2013-05-07 09:09:29 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Nios II ELF nios2*-*-elf
|
|
|
|
|
Nios II GNU/Linux nios2*-*-linux
|
2013-06-25 23:55:12 +08:00
|
|
|
Texas Instruments MSP430 msp430*-*-elf
|
2013-05-07 09:09:29 +08:00
|
|
|
|
2013-09-24 21:48:44 +08:00
|
|
|
* Removed native configurations
|
|
|
|
|
|
|
|
|
|
Support for these a.out NetBSD and OpenBSD obsolete configurations has
|
|
|
|
|
been removed. ELF variants of these configurations are kept supported.
|
|
|
|
|
|
|
|
|
|
arm*-*-netbsd* but arm*-*-netbsdelf* is kept supported.
|
|
|
|
|
i[34567]86-*-netbsd* but i[34567]86-*-netbsdelf* is kept supported.
|
|
|
|
|
i[34567]86-*-openbsd[0-2].* but i[34567]86-*-openbsd* is kept supported.
|
|
|
|
|
i[34567]86-*-openbsd3.[0-3]
|
|
|
|
|
m68*-*-netbsd* but m68*-*-netbsdelf* is kept supported.
|
|
|
|
|
sparc-*-netbsd* but sparc-*-netbsdelf* is kept supported.
|
|
|
|
|
vax-*-netbsd* but vax-*-netbsdelf* is kept supported.
|
|
|
|
|
|
New commands "mt set per-command {space,time,symtab} {on,off}".
* NEWS: Add entry.
* event-top.c: #include "maint.h".
* main.c: #include "maint.h".
* maint.c: #include <sys/time.h>, <time.h>, block.h, top.h,
timeval-utils.h, maint.h, cli/cli-setshow.h.
(per_command_time, per_command_space): New static globals.
(per_command_symtab): New static global.
(per_command_setlist, per_command_showlist): New static globals.
(struct cmd_stats): Move here from utils.c.
(set_per_command_time): Renamed from set_display_time in utils.c
and moved here. All callers updated.
(set_per_command_space): Renamed from set_display_space in utils.c
and moved here. All callers updated.
(count_symtabs_and_blocks): New function.
(report_command_stats): Moved here from utils.c. Add support for
printing symtab stats. Only print data if enabled before command
executed.
(make_command_stats_cleanup): Ditto.
(sert_per_command_cmd, show_per_command_cmd): New functions.
(_initialize_maint_cmds): Add new commands
mt set per-command {space,time,symtab} {on,off}.
* maint.h: New file.
* top.c: #include "maint.h".
* utils.c (reset_prompt_for_continue_wait_time): New function.
(get_prompt_for_continue_wait_time): New function.
* utils.h (reset_prompt_for_continue_wait_time): Declare
(get_prompt_for_continue_wait_time): Declare.
(make_command_stats_cleanup): Moved to maint.h.
(set_display_time, set_display_space): Moved to maint.h and renamed
to set_per_command_time, set_per_command_space.
* cli/cli-setshow.c (parse_cli_boolean_value): Renamed from
parse_binary_operation and made non-static. Don't call error,
just return an error marker. All callers updated.
* cli/cli-setshow.h (parse_cli_boolean_value): Declare.
doc/
* gdb.texinfo (Maintenance Commands): Add docs for
"mt set per-command {space,time,symtab} {on,off}".
testsuite/
* gdb.base/maint.exp: Update tests for per-command stats.
2013-03-22 01:37:30 +08:00
|
|
|
* New commands:
|
2013-04-16 02:24:48 +08:00
|
|
|
catch rethrow
|
|
|
|
|
Like "catch throw", but catches a re-thrown exception.
|
2013-05-18 02:09:06 +08:00
|
|
|
maint check-psymtabs
|
|
|
|
|
Renamed from old "maint check-symtabs".
|
|
|
|
|
maint check-symtabs
|
|
|
|
|
Perform consistency checks on symtabs.
|
|
|
|
|
maint expand-symtabs
|
|
|
|
|
Expand symtabs matching an optional regexp.
|
2013-04-16 02:24:48 +08:00
|
|
|
|
2013-04-12 16:57:43 +08:00
|
|
|
show configuration
|
|
|
|
|
Display the details of GDB configure-time options.
|
|
|
|
|
|
New commands "mt set per-command {space,time,symtab} {on,off}".
* NEWS: Add entry.
* event-top.c: #include "maint.h".
* main.c: #include "maint.h".
* maint.c: #include <sys/time.h>, <time.h>, block.h, top.h,
timeval-utils.h, maint.h, cli/cli-setshow.h.
(per_command_time, per_command_space): New static globals.
(per_command_symtab): New static global.
(per_command_setlist, per_command_showlist): New static globals.
(struct cmd_stats): Move here from utils.c.
(set_per_command_time): Renamed from set_display_time in utils.c
and moved here. All callers updated.
(set_per_command_space): Renamed from set_display_space in utils.c
and moved here. All callers updated.
(count_symtabs_and_blocks): New function.
(report_command_stats): Moved here from utils.c. Add support for
printing symtab stats. Only print data if enabled before command
executed.
(make_command_stats_cleanup): Ditto.
(sert_per_command_cmd, show_per_command_cmd): New functions.
(_initialize_maint_cmds): Add new commands
mt set per-command {space,time,symtab} {on,off}.
* maint.h: New file.
* top.c: #include "maint.h".
* utils.c (reset_prompt_for_continue_wait_time): New function.
(get_prompt_for_continue_wait_time): New function.
* utils.h (reset_prompt_for_continue_wait_time): Declare
(get_prompt_for_continue_wait_time): Declare.
(make_command_stats_cleanup): Moved to maint.h.
(set_display_time, set_display_space): Moved to maint.h and renamed
to set_per_command_time, set_per_command_space.
* cli/cli-setshow.c (parse_cli_boolean_value): Renamed from
parse_binary_operation and made non-static. Don't call error,
just return an error marker. All callers updated.
* cli/cli-setshow.h (parse_cli_boolean_value): Declare.
doc/
* gdb.texinfo (Maintenance Commands): Add docs for
"mt set per-command {space,time,symtab} {on,off}".
testsuite/
* gdb.base/maint.exp: Update tests for per-command stats.
2013-03-22 01:37:30 +08:00
|
|
|
maint set|show per-command
|
|
|
|
|
maint set|show per-command space
|
|
|
|
|
maint set|show per-command time
|
|
|
|
|
maint set|show per-command symtab
|
|
|
|
|
Enable display of per-command gdb resource usage.
|
|
|
|
|
|
2013-04-05 15:15:56 +08:00
|
|
|
remove-symbol-file FILENAME
|
|
|
|
|
remove-symbol-file -a ADDRESS
|
|
|
|
|
Remove a symbol file added via add-symbol-file. The file to remove
|
|
|
|
|
can be identified by its filename or by an address that lies within
|
|
|
|
|
the boundaries of this symbol file in memory.
|
|
|
|
|
|
2013-11-08 18:21:14 +08:00
|
|
|
info exceptions
|
|
|
|
|
info exceptions REGEXP
|
|
|
|
|
Display the list of Ada exceptions defined in the program being
|
|
|
|
|
debugged. If provided, only the exceptions whose names match REGEXP
|
|
|
|
|
are listed.
|
|
|
|
|
|
2013-03-29 05:58:03 +08:00
|
|
|
* New options
|
|
|
|
|
|
2013-09-26 07:17:12 +08:00
|
|
|
set debug symfile off|on
|
|
|
|
|
show debug symfile
|
|
|
|
|
Control display of debugging info regarding reading symbol files and
|
|
|
|
|
symbol tables within those files
|
|
|
|
|
|
2013-07-18 04:35:11 +08:00
|
|
|
set print raw frame-arguments
|
|
|
|
|
show print raw frame-arguments
|
|
|
|
|
Set/show whether to print frame arguments in raw mode,
|
|
|
|
|
disregarding any defined pretty-printers.
|
|
|
|
|
|
2013-03-29 05:58:03 +08:00
|
|
|
set remote trace-status-packet
|
|
|
|
|
show remote trace-status-packet
|
|
|
|
|
Set/show the use of remote protocol qTStatus packet.
|
|
|
|
|
|
2013-05-07 09:09:29 +08:00
|
|
|
set debug nios2
|
|
|
|
|
show debug nios2
|
|
|
|
|
Control display of debugging messages related to Nios II targets.
|
|
|
|
|
|
range stepping: gdb
This patch teaches GDB to take advantage of target-assisted range
stepping. It adds a new 'r ADDR1,ADDR2' action to vCont (vCont;r),
meaning, "step once, and keep stepping as long as the thread is in the
[ADDR1,ADDR2) range".
Rationale:
When user issues the "step" command on the following line of source,
a = b + c + d * e - a;
GDB single-steps every single instruction until the program reaches a
new different line. E.g., on x86_64, that line compiles to:
0x08048434 <+65>: mov 0x1c(%esp),%eax
0x08048438 <+69>: mov 0x30(%esp),%edx
0x0804843c <+73>: add %eax,%edx
0x0804843e <+75>: mov 0x18(%esp),%eax
0x08048442 <+79>: imul 0x2c(%esp),%eax
0x08048447 <+84>: add %edx,%eax
0x08048449 <+86>: sub 0x34(%esp),%eax
0x0804844d <+90>: mov %eax,0x34(%esp)
0x08048451 <+94>: mov 0x1c(%esp),%eax
and the following is the RSP traffic between GDB and GDBserver:
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:3c840408;thread:p2e13.2e13;core:1;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:3e840408;thread:p2e13.2e13;core:2;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:42840408;thread:p2e13.2e13;core:2;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:47840408;thread:p2e13.2e13;core:0;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:49840408;thread:p2e13.2e13;core:0;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:4d840408;thread:p2e13.2e13;core:0;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:51840408;thread:p2e13.2e13;core:0;
IOW, a lot of roundtrips between GDB and GDBserver.
If we add a new command to the RSP, meaning "keep stepping and don't
report a stop until the program goes out of the [0x08048434,
0x08048451) address range", then the RSP traffic can be reduced down
to:
--> vCont;r8048434,8048451:p2db0.2db0;c
<-- T0505:68efffbf;04:30efffbf;08:51840408;thread:p2db0.2db0;core:1;
As number of packets is reduced dramatically, the performance of
stepping source lines is much improved.
In case something is wrong with range stepping on the stub side, the
debug info or even gdb, this adds a "set/show range-stepping" command
to be able to turn range stepping off.
gdb/
2013-05-23 Yao Qi <yao@codesourcery.com>
Pedro Alves <palves@redhat.com>
* gdbthread.h (struct thread_control_state) <may_range_step>: New
field.
* infcmd.c (step_once, until_next_command): Enable range stepping.
* infrun.c (displaced_step_prepare): Disable range stepping.
(resume): Disable range stepping if stepping over a breakpoint or
we have software watchpoints. If range stepping is enabled,
assert the thread is in the stepping range.
(clear_proceed_status_thread): Clear may_range_step.
(handle_inferior_event): Disable range stepping as soon as we know
the thread that hit the event. Re-enable it whenever we're going
to step with a step range.
* remote.c (struct vCont_action_support) <r>: New field.
(use_range_stepping): New global.
(remote_vcont_probe): Handle 'r' action.
(append_resumption): Append an 'r' action if the thread may range
step.
(show_range_stepping): New function.
(set_range_stepping): New function.
(_initialize_remote): Call add_setshow_boolean_cmd to register the
'set range-stepping' and 'show range-stepping' commands.
* NEWS: Mention range stepping, the new vCont;r action, and the
new "set/show range-stepping" commands.
gdb/doc/
2013-05-23 Yao Qi <yao@codesourcery.com>
Pedro Alves <palves@redhat.com>
* gdb.texinfo (Packets): Document 'vCont;r'.
(Continuing and Stepping): Document target-assisted range
stepping, and the 'set range-stepping' and 'show range-stepping'
commands.
2013-05-24 01:15:35 +08:00
|
|
|
set range-stepping
|
|
|
|
|
show range-stepping
|
|
|
|
|
Control whether target-assisted range stepping is enabled.
|
|
|
|
|
|
2013-10-24 23:10:05 +08:00
|
|
|
set startup-with-shell
|
|
|
|
|
show startup-with-shell
|
|
|
|
|
Specifies whether Unix child processes are started via a shell or
|
|
|
|
|
directly.
|
|
|
|
|
|
2013-11-01 12:26:10 +08:00
|
|
|
set code-cache
|
|
|
|
|
show code-cache
|
|
|
|
|
Use the target memory cache for accesses to the code segment. This
|
|
|
|
|
improves performance of remote debugging (particularly disassembly).
|
|
|
|
|
|
2013-04-16 22:36:53 +08:00
|
|
|
* You can now use a literal value 'unlimited' for options that
|
|
|
|
|
interpret 0 or -1 as meaning "unlimited". E.g., "set
|
|
|
|
|
trace-buffer-size unlimited" is now an alias for "set
|
|
|
|
|
trace-buffer-size -1" and "set height unlimited" is now an alias for
|
|
|
|
|
"set height 0".
|
|
|
|
|
|
2013-11-09 02:43:23 +08:00
|
|
|
* The "set debug symtab-create" debugging option of GDB has been changed to
|
|
|
|
|
accept a verbosity level. 0 means "off", 1 provides basic debugging
|
|
|
|
|
output, and values of 2 or greater provides more verbose output.
|
|
|
|
|
|
2013-04-12 16:57:43 +08:00
|
|
|
* New command-line options
|
|
|
|
|
--configuration
|
|
|
|
|
Display the details of GDB configure-time options.
|
|
|
|
|
|
2013-03-14 17:02:30 +08:00
|
|
|
* The command 'tsave' can now support new option '-ctf' to save trace
|
|
|
|
|
buffer in Common Trace Format.
|
|
|
|
|
|
gdb/
* Makefile.in (HAVE_NATIVE_GCORE_TARGET): New.
(generated_files): Add gcore.
(install-only, uninstall): Add gcore if HAVE_NATIVE_GCORE_TARGET or
HAVE_NATIVE_GCORE_HOST.
(gcore): New.
* NEWS (Changes since GDB 7.6): Mention newly installed gcore.
* config/alpha/alpha-osf3.mh, config/i386/fbsd.mh,
config/i386/fbsd64.mh, config/i386/i386gnu.mh, config/i386/i386sol2.mh,
config/i386/sol2-64.mh, config/mips/irix5.mh, config/mips/irix6.mh,
config/powerpc/fbsd.mh, config/sparc/fbsd.mh, config/sparc/sol2.mh:
Add HAVE_NATIVE_GCORE_HOST.
* configure: Regenerate.
* configure.ac (HAVE_NATIVE_GCORE_TARGET): New, set it, AC_SUBST it.
New AC_SUBST fir GDB_TRANSFORM_NAME and GCORE_TRANSFORM_NAME. New
AC_CONFIG_FILES for gcore.
* configure.tgt: Add gdb_have_gcore to the initial comment. Set
gdb_have_gcore.
* gdb_gcore.sh: Rename to ...
* gcore.in: ... here. Remove gcore.sh comment. Use GDB_TRANSFORM_NAME
and GCORE_TRANSFORM_NAME substitutions.
gdb/doc/
* Makefile.in (MAN1S): Add gcore.1.
Remove "Host, target, and site specific Makefile fragments" comment.
(@host_makefile_frag@, HAVE_NATIVE_GCORE_TARGET): New.
(install-man1, uninstall-man1): Conditionalize gcore.1.
(gcore.1): New.
* gdb.texinfo (Man Pages): Add gcore man.
(gcore man): New node.
2013-04-11 22:13:44 +08:00
|
|
|
* Newly installed $prefix/bin/gcore acts as a shell interface for the
|
|
|
|
|
GDB command gcore.
|
|
|
|
|
|
2020-03-06 22:22:23 +08:00
|
|
|
* GDB now implements the C++ 'typeid' operator.
|
2013-04-16 01:36:14 +08:00
|
|
|
|
2013-04-16 02:24:48 +08:00
|
|
|
* The new convenience variable $_exception holds the exception being
|
|
|
|
|
thrown or caught at an exception-related catchpoint.
|
|
|
|
|
|
|
|
|
|
* The exception-related catchpoints, like "catch throw", now accept a
|
|
|
|
|
regular expression which can be used to filter exceptions by type.
|
|
|
|
|
|
2013-10-07 13:34:11 +08:00
|
|
|
* The new convenience variable $_exitsignal is automatically set to
|
|
|
|
|
the terminating signal number when the program being debugged dies
|
|
|
|
|
due to an uncaught signal.
|
|
|
|
|
|
2013-03-14 17:02:30 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
GDB/MI: Add new "--language LANG" command option.
Frontend sometimes need to evaluate expressions that are
language-specific. For instance, Eclipse uses the following
expression to determine the size of an address on the target:
-data-evaluate-expression "sizeof (void*)"
Unfortunately, if the main of the program being debugged is not C,
this may not work. For instance, if the main is in Ada, you get...
-data-evaluate-expression "sizeof (void*)"
^error,msg="No definition of \"sizeof\" in current context."
... and apparently decides to stop the debugging session as a result.
The recommendation sent was to specifically set the language to C
before trying to evaluate the expression. Something such as:
1. save current language
2. set language c
3. -data-evaluate-expression "sizeof (void*)"
4. Restore language
This has the same disadvantages as the ones outlined in the "Context
Management" section of the GDB/MI documentation regarding setting
the current thread or the current frame, thus recommending the use of
general command-line switches such as --frame, or --thread instead.
This patch follows the same steps for the language, adding a similar
new command option: --language LANG. Example of use:
-data-evaluate-expression --language c "sizeof (void*)"
^done,value="4"
gdb/ChangeLog:
* mi/mi-parse.h (struct mi_parse) <language>: New field.
* mi/mi-main.c (mi_cmd_execute): Temporarily set language to
PARSE->LANGUAGE during command execution, if set.
* mi/mi-parse.c: Add "language.h" #include.
(mi_parse): Add parsing of "--language" command option.
* NEWS: Add entry mentioning the new "--language" command option.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-language.exp: New file.
gdb/doc/ChangeLog:
* gdb.texinfo (Show): Add xref anchor for "show language" command.
(Context management): Place current subsection text into its own
subsubsection. Add new subsubsection describing the "--language"
command option.
2013-11-11 13:21:44 +08:00
|
|
|
** All MI commands now accept an optional "--language" option.
|
2013-12-03 12:58:47 +08:00
|
|
|
Support for this feature can be verified by using the "-list-features"
|
|
|
|
|
command, which should contain "language-option".
|
GDB/MI: Add new "--language LANG" command option.
Frontend sometimes need to evaluate expressions that are
language-specific. For instance, Eclipse uses the following
expression to determine the size of an address on the target:
-data-evaluate-expression "sizeof (void*)"
Unfortunately, if the main of the program being debugged is not C,
this may not work. For instance, if the main is in Ada, you get...
-data-evaluate-expression "sizeof (void*)"
^error,msg="No definition of \"sizeof\" in current context."
... and apparently decides to stop the debugging session as a result.
The recommendation sent was to specifically set the language to C
before trying to evaluate the expression. Something such as:
1. save current language
2. set language c
3. -data-evaluate-expression "sizeof (void*)"
4. Restore language
This has the same disadvantages as the ones outlined in the "Context
Management" section of the GDB/MI documentation regarding setting
the current thread or the current frame, thus recommending the use of
general command-line switches such as --frame, or --thread instead.
This patch follows the same steps for the language, adding a similar
new command option: --language LANG. Example of use:
-data-evaluate-expression --language c "sizeof (void*)"
^done,value="4"
gdb/ChangeLog:
* mi/mi-parse.h (struct mi_parse) <language>: New field.
* mi/mi-main.c (mi_cmd_execute): Temporarily set language to
PARSE->LANGUAGE during command execution, if set.
* mi/mi-parse.c: Add "language.h" #include.
(mi_parse): Add parsing of "--language" command option.
* NEWS: Add entry mentioning the new "--language" command option.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-language.exp: New file.
gdb/doc/ChangeLog:
* gdb.texinfo (Show): Add xref anchor for "show language" command.
(Context management): Place current subsection text into its own
subsubsection. Add new subsubsection describing the "--language"
command option.
2013-11-11 13:21:44 +08:00
|
|
|
|
New GDB/MI command "-info-gdb-mi-command"
This patch adds a new GDB/MI command meant for graphical frontends
trying to determine whether a given GDB/MI command exists or not.
Examples:
-info-gdb-mi-command unsupported-command
^done,command={exists="false"}
(gdb)
-info-gdb-mi-command symbol-list-lines
^done,command={exists="true"}
(gdb)
At the moment, this is the only piece of information that this
command returns.
Eventually, and if needed, we can extend it to provide
command-specific pieces of information, such as updates to
the command's syntax since inception. This could become,
for instance:
-info-gdb-mi-command symbol-list-lines
^done,command={exists="true",features=[]}
(gdb)
-info-gdb-mi-command catch-assert
^done,command={exists="true",features=["conditions"]}
In the first case, it would mean that no extra features,
while in the second, it announces that the -catch-assert
command in this version of the debugger supports a feature
called "condition" - exact semantics to be documented with
combined with the rest of the queried command's documentation.
But for now, we start small, and only worry about existance.
And to bootstrap the process, I have added an entry in the
output of the -list-features command as well ("info-gdb-mi-command"),
allowing the graphical frontends to go through the following process:
1. Send -list-features, collect info from there as before;
2. Check if the output contains "info-gdb-mi-command".
If it does, then support for various commands can be
queried though -info-gdb-mi-command. Newer commands
will be expected to always be checked via this new
-info-gdb-mi-command.
gdb/ChangeLog:
* mi/mi-cmds.h (mi_cmd_info_gdb_mi_command): Declare.
* mi/mi-cmd-info.c (mi_cmd_info_gdb_mi_command): New function.
* mi/mi-cmds.c (mi_cmds): Add -info-gdb-mi-command command.
* mi/mi-main.c (mi_cmd_list_features): Add "info-gdb-mi-command"
field to output of "-list-features".
* NEWS: Add entry for new -info-gdb-mi-command.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI Miscellaneous Commands): Document
the new -info-gdb-mi-command GDB/MI command. Document
the meaning of "-info-gdb-mi-command" in the output of
-list-features.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-i-cmd.exp: New file.
2013-11-12 18:51:30 +08:00
|
|
|
** The new command -info-gdb-mi-command allows the user to determine
|
|
|
|
|
whether a GDB/MI command is supported or not.
|
|
|
|
|
|
2013-11-18 20:55:16 +08:00
|
|
|
** The "^error" result record returned when trying to execute an undefined
|
|
|
|
|
GDB/MI command now provides a variable named "code" whose content is the
|
|
|
|
|
"undefined-command" error code. Support for this feature can be verified
|
|
|
|
|
by using the "-list-features" command, which should contain
|
|
|
|
|
"undefined-command-error-code".
|
|
|
|
|
|
2013-03-14 17:02:30 +08:00
|
|
|
** The -trace-save MI command can optionally save trace buffer in Common
|
|
|
|
|
Trace Format now.
|
|
|
|
|
|
2013-05-21 12:18:55 +08:00
|
|
|
** The new command -dprintf-insert sets a dynamic printf breakpoint.
|
|
|
|
|
|
2013-06-20 08:39:11 +08:00
|
|
|
** The command -data-list-register-values now accepts an optional
|
|
|
|
|
"--skip-unavailable" option. When used, only the available registers
|
|
|
|
|
are displayed.
|
|
|
|
|
|
2013-06-26 16:17:27 +08:00
|
|
|
** The new command -trace-frame-collected dumps collected variables,
|
|
|
|
|
computed expressions, tvars, memory and registers in a traceframe.
|
|
|
|
|
|
Add options to skip unavailable locals
This is the patch to add new option '--skip-unavailable' to MI
commands '-stack-list-{locals, arguments, variables}'. This patch
extends list_args_or_locals to add a new parameter 'skip_unavailable',
and don't list locals or arguments if values are unavailable and
'skip_unavailable' is true.
This is inspecting a trace frame (tfind mode), where only a few
locals have been collected.
-stack-list-locals, no switch vs new switch:
-stack-list-locals --simple-values
^done,locals=[{name="array",type="unsigned char [2]"},{name="i",type="int",value="<unavailable>"}]
-stack-list-locals --skip-unavailable --simple-values
^done,locals=[{name="array",type="unsigned char [2]"}]
-stack-list-arguments, no switch vs new switch:
-stack-list-arguments --simple-values
^done,stack-args=[frame={level="0",args=[{name="j",type="int",value="4"},{name="s",type="char *",value="<unavailable>"}]},frame={level="1",args=[]}]
-stack-list-arguments --skip-unavailable --simple-values
^done,stack-args=[frame={level="0",args=[{name="j",type="int",value="4"}]},frame={level="1",args=[]}]
-stack-list-variables, no switch vs new switch:
-stack-list-variables --simple-values
^done,variables=[{name="j",arg="1",type="int",value="4"},{name="s",arg="1",type="char *",value="<unavailable>"},{name="array",type="unsigned char [2]"},{name="i",type="int",value="<unavailable>"}]
-stack-list-variables --skip-unavailable --simple-values
^done,variables=[{name="j",arg="1",type="int",value="4"},{name="array",type="unsigned char [2]"}]
tests are added to test these new options.
gdb:
2013-08-27 Pedro Alves <pedro@codesourcery.com>
Yao Qi <yao@codesourcery.com>
* mi/mi-cmd-stack.c (list_args_or_locals): Adjust prototype.
(parse_no_frames_option): Remove.
(mi_cmd_stack_list_locals): Handle --skip-unavailable.
(mi_cmd_stack_list_args): Adjust.
(mi_cmd_stack_list_variables): Handle --skip-unavailable.
(list_arg_or_local): Add new parameter 'skip_unavailable'. Return
early if SKIP_UNAVAILABLE is true and ARG->val is unavailable.
Caller update.
(list_args_or_locals): New parameter 'skip_unavailable'.
Handle it.
* valprint.c (scalar_type_p): Rename to ...
(val_print_scalar_type_p): ... this. Make extern.
(val_print, value_check_printable): Adjust.
* valprint.h (val_print_scalar_type_p): Declare.
* value.c (value_entirely_unavailable): New function.
* value.h (value_entirely_unavailable): Declare.
* NEWS: Mention the new option "--skip-unavailable" to MI
commands '-stack-list-locals', '-stack-list-arguments' and
'-stack-list-variables'.
gdb/doc:
2013-08-27 Pedro Alves <pedro@codesourcery.com>
Yao Qi <yao@codesourcery.com>
* gdb.texinfo (GDB/MI Stack Manipulation) <-stack-list-locals>:
Document new --skip-unavailable option.
<-stack-list-variables>: Document new --skip-unavailable option.
gdb/testsuite:
2013-08-27 Yao Qi <yao@codesourcery.com>
* gdb.trace/entry-values.exp: Test unavailable entry value is
not shown when option '--skip-unavailable' is specified.
* gdb.trace/mi-trace-unavailable.exp (test_trace_unavailable):
Add tests for new option '--skip-unavailable'.
2013-08-27 13:20:57 +08:00
|
|
|
** The commands -stack-list-locals, -stack-list-arguments and
|
|
|
|
|
-stack-list-variables now accept an option "--skip-unavailable".
|
|
|
|
|
When used, only the available locals or arguments are displayed.
|
|
|
|
|
|
2013-10-04 16:35:31 +08:00
|
|
|
** The -exec-run command now accepts an optional "--start" option.
|
|
|
|
|
When used, the command follows the same semantics as the "start"
|
|
|
|
|
command, stopping the program's execution at the start of its
|
2013-12-03 14:04:32 +08:00
|
|
|
main subprogram. Support for this feature can be verified using
|
|
|
|
|
the "-list-features" command, which should contain
|
|
|
|
|
"exec-run-start-option".
|
2013-10-04 16:35:31 +08:00
|
|
|
|
2013-10-11 21:51:27 +08:00
|
|
|
** The new commands -catch-assert and -catch-exceptions insert
|
|
|
|
|
catchpoints stopping the program when Ada exceptions are raised.
|
|
|
|
|
|
2013-11-08 18:21:14 +08:00
|
|
|
** The new command -info-ada-exceptions provides the equivalent of
|
|
|
|
|
the new "info exceptions" command.
|
|
|
|
|
|
2013-05-23 14:00:53 +08:00
|
|
|
* New system-wide configuration scripts
|
|
|
|
|
A GDB installation now provides scripts suitable for use as system-wide
|
|
|
|
|
configuration scripts for the following systems:
|
|
|
|
|
** ElinOS
|
|
|
|
|
** Wind River Linux
|
|
|
|
|
|
range stepping: gdb
This patch teaches GDB to take advantage of target-assisted range
stepping. It adds a new 'r ADDR1,ADDR2' action to vCont (vCont;r),
meaning, "step once, and keep stepping as long as the thread is in the
[ADDR1,ADDR2) range".
Rationale:
When user issues the "step" command on the following line of source,
a = b + c + d * e - a;
GDB single-steps every single instruction until the program reaches a
new different line. E.g., on x86_64, that line compiles to:
0x08048434 <+65>: mov 0x1c(%esp),%eax
0x08048438 <+69>: mov 0x30(%esp),%edx
0x0804843c <+73>: add %eax,%edx
0x0804843e <+75>: mov 0x18(%esp),%eax
0x08048442 <+79>: imul 0x2c(%esp),%eax
0x08048447 <+84>: add %edx,%eax
0x08048449 <+86>: sub 0x34(%esp),%eax
0x0804844d <+90>: mov %eax,0x34(%esp)
0x08048451 <+94>: mov 0x1c(%esp),%eax
and the following is the RSP traffic between GDB and GDBserver:
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:3c840408;thread:p2e13.2e13;core:1;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:3e840408;thread:p2e13.2e13;core:2;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:42840408;thread:p2e13.2e13;core:2;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:47840408;thread:p2e13.2e13;core:0;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:49840408;thread:p2e13.2e13;core:0;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:4d840408;thread:p2e13.2e13;core:0;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:51840408;thread:p2e13.2e13;core:0;
IOW, a lot of roundtrips between GDB and GDBserver.
If we add a new command to the RSP, meaning "keep stepping and don't
report a stop until the program goes out of the [0x08048434,
0x08048451) address range", then the RSP traffic can be reduced down
to:
--> vCont;r8048434,8048451:p2db0.2db0;c
<-- T0505:68efffbf;04:30efffbf;08:51840408;thread:p2db0.2db0;core:1;
As number of packets is reduced dramatically, the performance of
stepping source lines is much improved.
In case something is wrong with range stepping on the stub side, the
debug info or even gdb, this adds a "set/show range-stepping" command
to be able to turn range stepping off.
gdb/
2013-05-23 Yao Qi <yao@codesourcery.com>
Pedro Alves <palves@redhat.com>
* gdbthread.h (struct thread_control_state) <may_range_step>: New
field.
* infcmd.c (step_once, until_next_command): Enable range stepping.
* infrun.c (displaced_step_prepare): Disable range stepping.
(resume): Disable range stepping if stepping over a breakpoint or
we have software watchpoints. If range stepping is enabled,
assert the thread is in the stepping range.
(clear_proceed_status_thread): Clear may_range_step.
(handle_inferior_event): Disable range stepping as soon as we know
the thread that hit the event. Re-enable it whenever we're going
to step with a step range.
* remote.c (struct vCont_action_support) <r>: New field.
(use_range_stepping): New global.
(remote_vcont_probe): Handle 'r' action.
(append_resumption): Append an 'r' action if the thread may range
step.
(show_range_stepping): New function.
(set_range_stepping): New function.
(_initialize_remote): Call add_setshow_boolean_cmd to register the
'set range-stepping' and 'show range-stepping' commands.
* NEWS: Mention range stepping, the new vCont;r action, and the
new "set/show range-stepping" commands.
gdb/doc/
2013-05-23 Yao Qi <yao@codesourcery.com>
Pedro Alves <palves@redhat.com>
* gdb.texinfo (Packets): Document 'vCont;r'.
(Continuing and Stepping): Document target-assisted range
stepping, and the 'set range-stepping' and 'show range-stepping'
commands.
2013-05-24 01:15:35 +08:00
|
|
|
* GDB now supports target-assigned range stepping with remote targets.
|
|
|
|
|
This improves the performance of stepping source lines by reducing
|
|
|
|
|
the number of control packets from/to GDB. See "New remote packets"
|
|
|
|
|
below.
|
|
|
|
|
|
2013-06-26 16:01:57 +08:00
|
|
|
* GDB now understands the element 'tvar' in the XML traceframe info.
|
|
|
|
|
It has the id of the collected trace state variables.
|
|
|
|
|
|
2013-09-13 22:17:31 +08:00
|
|
|
* On S/390 targets that provide the transactional-execution feature,
|
|
|
|
|
the program interruption transaction diagnostic block (TDB) is now
|
|
|
|
|
represented as a number of additional "registers" in GDB.
|
|
|
|
|
|
range stepping: gdb
This patch teaches GDB to take advantage of target-assisted range
stepping. It adds a new 'r ADDR1,ADDR2' action to vCont (vCont;r),
meaning, "step once, and keep stepping as long as the thread is in the
[ADDR1,ADDR2) range".
Rationale:
When user issues the "step" command on the following line of source,
a = b + c + d * e - a;
GDB single-steps every single instruction until the program reaches a
new different line. E.g., on x86_64, that line compiles to:
0x08048434 <+65>: mov 0x1c(%esp),%eax
0x08048438 <+69>: mov 0x30(%esp),%edx
0x0804843c <+73>: add %eax,%edx
0x0804843e <+75>: mov 0x18(%esp),%eax
0x08048442 <+79>: imul 0x2c(%esp),%eax
0x08048447 <+84>: add %edx,%eax
0x08048449 <+86>: sub 0x34(%esp),%eax
0x0804844d <+90>: mov %eax,0x34(%esp)
0x08048451 <+94>: mov 0x1c(%esp),%eax
and the following is the RSP traffic between GDB and GDBserver:
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:3c840408;thread:p2e13.2e13;core:1;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:3e840408;thread:p2e13.2e13;core:2;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:42840408;thread:p2e13.2e13;core:2;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:47840408;thread:p2e13.2e13;core:0;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:49840408;thread:p2e13.2e13;core:0;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:4d840408;thread:p2e13.2e13;core:0;
--> vCont;s:p2e13.2e13;c
<-- T0505:68efffbf;04:30efffbf;08:51840408;thread:p2e13.2e13;core:0;
IOW, a lot of roundtrips between GDB and GDBserver.
If we add a new command to the RSP, meaning "keep stepping and don't
report a stop until the program goes out of the [0x08048434,
0x08048451) address range", then the RSP traffic can be reduced down
to:
--> vCont;r8048434,8048451:p2db0.2db0;c
<-- T0505:68efffbf;04:30efffbf;08:51840408;thread:p2db0.2db0;core:1;
As number of packets is reduced dramatically, the performance of
stepping source lines is much improved.
In case something is wrong with range stepping on the stub side, the
debug info or even gdb, this adds a "set/show range-stepping" command
to be able to turn range stepping off.
gdb/
2013-05-23 Yao Qi <yao@codesourcery.com>
Pedro Alves <palves@redhat.com>
* gdbthread.h (struct thread_control_state) <may_range_step>: New
field.
* infcmd.c (step_once, until_next_command): Enable range stepping.
* infrun.c (displaced_step_prepare): Disable range stepping.
(resume): Disable range stepping if stepping over a breakpoint or
we have software watchpoints. If range stepping is enabled,
assert the thread is in the stepping range.
(clear_proceed_status_thread): Clear may_range_step.
(handle_inferior_event): Disable range stepping as soon as we know
the thread that hit the event. Re-enable it whenever we're going
to step with a step range.
* remote.c (struct vCont_action_support) <r>: New field.
(use_range_stepping): New global.
(remote_vcont_probe): Handle 'r' action.
(append_resumption): Append an 'r' action if the thread may range
step.
(show_range_stepping): New function.
(set_range_stepping): New function.
(_initialize_remote): Call add_setshow_boolean_cmd to register the
'set range-stepping' and 'show range-stepping' commands.
* NEWS: Mention range stepping, the new vCont;r action, and the
new "set/show range-stepping" commands.
gdb/doc/
2013-05-23 Yao Qi <yao@codesourcery.com>
Pedro Alves <palves@redhat.com>
* gdb.texinfo (Packets): Document 'vCont;r'.
(Continuing and Stepping): Document target-assisted range
stepping, and the 'set range-stepping' and 'show range-stepping'
commands.
2013-05-24 01:15:35 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
vCont;r
|
|
|
|
|
|
|
|
|
|
The vCont packet supports a new 'r' action, that tells the remote
|
|
|
|
|
stub to step through an address range itself, without GDB
|
|
|
|
|
involvemement at each single-step.
|
|
|
|
|
|
2013-06-04 21:02:15 +08:00
|
|
|
qXfer:libraries-svr4:read's annex
|
|
|
|
|
The previously unused annex of the qXfer:libraries-svr4:read packet
|
|
|
|
|
is now used to support passing an argument list. The remote stub
|
|
|
|
|
reports support for this argument list to GDB's qSupported query.
|
|
|
|
|
The defined arguments are "start" and "prev", used to reduce work
|
|
|
|
|
necessary for library list updating, resulting in significant
|
|
|
|
|
speedup.
|
|
|
|
|
|
2013-05-24 01:17:50 +08:00
|
|
|
* New features in the GDB remote stub, GDBserver
|
|
|
|
|
|
|
|
|
|
** GDBserver now supports target-assisted range stepping. Currently
|
|
|
|
|
enabled on x86/x86_64 GNU/Linux targets.
|
|
|
|
|
|
2013-06-26 16:01:57 +08:00
|
|
|
** GDBserver now adds element 'tvar' in the XML in the reply to
|
|
|
|
|
'qXfer:traceframe-info:read'. It has the id of the collected
|
|
|
|
|
trace state variables.
|
|
|
|
|
|
2013-07-27 15:59:49 +08:00
|
|
|
** GDBserver now supports hardware watchpoints on the MIPS GNU/Linux
|
|
|
|
|
target.
|
|
|
|
|
|
2013-07-25 18:16:08 +08:00
|
|
|
* New 'z' formatter for printing and examining memory, this displays the
|
|
|
|
|
value as hexadecimal zero padded on the left to the size of the type.
|
|
|
|
|
|
2013-09-02 17:28:02 +08:00
|
|
|
* GDB can now use Windows x64 unwinding data.
|
|
|
|
|
|
2013-10-10 13:50:20 +08:00
|
|
|
* The "set remotebaud" command has been replaced by "set serial baud".
|
|
|
|
|
Similarly, "show remotebaud" has been replaced by "show serial baud".
|
|
|
|
|
The "set remotebaud" and "show remotebaud" commands are still available
|
|
|
|
|
to provide backward compatibility with older versions of GDB.
|
|
|
|
|
|
2013-03-13 06:36:27 +08:00
|
|
|
*** Changes in GDB 7.6
|
2012-07-18 12:02:10 +08:00
|
|
|
|
2013-03-11 16:55:36 +08:00
|
|
|
* Target record has been renamed to record-full.
|
|
|
|
|
Record/replay is now enabled with the "record full" command.
|
|
|
|
|
This also affects settings that are associated with full record/replay
|
|
|
|
|
that have been moved from "set/show record" to "set/show record full":
|
|
|
|
|
|
|
|
|
|
set|show record full insn-number-max
|
|
|
|
|
set|show record full stop-at-limit
|
|
|
|
|
set|show record full memory-query
|
|
|
|
|
|
|
|
|
|
* A new record target "record-btrace" has been added. The new target
|
|
|
|
|
uses hardware support to record the control-flow of a process. It
|
|
|
|
|
does not support replaying the execution, but it implements the
|
|
|
|
|
below new commands for investigating the recorded execution log.
|
|
|
|
|
This new recording method can be enabled using:
|
|
|
|
|
|
|
|
|
|
record btrace
|
|
|
|
|
|
|
|
|
|
The "record-btrace" target is only available on Intel Atom processors
|
|
|
|
|
and requires a Linux kernel 2.6.32 or later.
|
|
|
|
|
|
|
|
|
|
* Two new commands have been added for record/replay to give information
|
|
|
|
|
about the recorded execution without having to replay the execution.
|
|
|
|
|
The commands are only supported by "record btrace".
|
|
|
|
|
|
|
|
|
|
record instruction-history prints the execution history at
|
|
|
|
|
instruction granularity
|
|
|
|
|
|
|
|
|
|
record function-call-history prints the execution history at
|
|
|
|
|
function granularity
|
|
|
|
|
|
2013-02-05 13:59:55 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
2013-02-08 19:11:47 +08:00
|
|
|
ARM AArch64 GNU/Linux aarch64*-*-linux-gnu
|
2013-02-05 13:59:55 +08:00
|
|
|
FreeBSD/powerpc powerpc*-*-freebsd
|
2013-04-04 02:04:33 +08:00
|
|
|
x86_64/Cygwin x86_64-*-cygwin*
|
2013-04-02 10:49:55 +08:00
|
|
|
Tilera TILE-Gx GNU/Linux tilegx*-*-linux-gnu
|
2013-02-05 13:59:55 +08:00
|
|
|
|
2012-12-19 12:28:53 +08:00
|
|
|
* New targets
|
|
|
|
|
|
2013-02-08 19:11:47 +08:00
|
|
|
ARM AArch64 aarch64*-*-elf
|
|
|
|
|
ARM AArch64 GNU/Linux aarch64*-*-linux
|
2012-12-19 12:28:53 +08:00
|
|
|
Lynx 178 PowerPC powerpc-*-lynx*178
|
2013-03-05 21:39:00 +08:00
|
|
|
x86_64/Cygwin x86_64-*-cygwin*
|
2013-04-02 10:49:55 +08:00
|
|
|
Tilera TILE-Gx GNU/Linux tilegx*-*-linux
|
2012-12-19 12:28:53 +08:00
|
|
|
|
2012-11-17 03:43:39 +08:00
|
|
|
* If the configured location of system.gdbinit file (as given by the
|
|
|
|
|
--with-system-gdbinit option at configure time) is in the
|
|
|
|
|
data-directory (as specified by --with-gdb-datadir at configure
|
|
|
|
|
time) or in one of its subdirectories, then GDB will look for the
|
|
|
|
|
system-wide init file in the directory specified by the
|
|
|
|
|
--data-directory command-line option.
|
|
|
|
|
|
2012-10-16 05:45:04 +08:00
|
|
|
* New command line options:
|
|
|
|
|
|
|
|
|
|
-nh Disables auto-loading of ~/.gdbinit, but still executes all the
|
|
|
|
|
other initialization files, unlike -nx which disables all of them.
|
|
|
|
|
|
2013-01-08 00:40:39 +08:00
|
|
|
* Removed command line options
|
|
|
|
|
|
|
|
|
|
-epoch This was used by the gdb mode in Epoch, an ancient fork of
|
|
|
|
|
Emacs.
|
|
|
|
|
|
* NEWS: Update.
* c-typeprint.c (c_type_print_base): Handle print_method and
print_typedefs flags.
* gdbcmd.h (setprinttypelist, showprinttypelist): Declare.
* python/py-type.c (typy_str): Use LA_PRINT_TYPE and raw
options.
* typeprint.c (type_print_raw_options, default_ptype_flags):
Update for new field.s
(whatis_exp): Parse flags. Use LA_PRINT_TYPE.
(setprinttypelist, showprinttypelist, print_methods,
print_typedefs): New globals.
(set_print_type, show_print_type, set_print_type_methods,
show_print_type_methods, set_print_type_typedefs,
show_print_type_typedefs): New functions.
(_initialize_typeprint): Update documentation. Add "print
type methods" and "print type typedefs" parameters.
* typeprint.h (struct type_print_options) <print_methods,
print_typedefs>: New fields.
doc
* gdb.texinfo (Symbols): Document "set print type methods",
"set print type typedefs", and flags to ptype and whatis.
2012-11-13 01:26:21 +08:00
|
|
|
* The 'ptype' and 'whatis' commands now accept an argument to control
|
|
|
|
|
type formatting.
|
|
|
|
|
|
2012-12-14 23:30:38 +08:00
|
|
|
* 'info proc' now works on some core files.
|
|
|
|
|
|
2012-08-11 04:26:00 +08:00
|
|
|
* Python scripting
|
|
|
|
|
|
|
|
|
|
** Vectors can be created with gdb.Type.vector.
|
|
|
|
|
|
2012-09-21 04:54:11 +08:00
|
|
|
** Python's atexit.register now works in GDB.
|
|
|
|
|
|
* NEWS: Update.
* data-directory/Makefile.in (PYTHON_FILES): Add
type_printers.py.
* python/lib/gdb/command/type_printers.py: New file.
* python/lib/gdb/command/types.py (TypePrinter): New class.
(_get_some_type_recognizers, get_type_recognizers,
apply_type_recognizers, register_type_printer): New
functions.
* python/py-objfile.c (objfile_object) <type_printers>: New
field.
(objfpy_dealloc): Decref new field.
(objfpy_new): Set new field.
(objfpy_get_type_printers, objfpy_set_type_printers): New
functions.
(objfile_to_objfile_object): Set new field.
(objfile_getset): Add "type_printers".
* python/py-progspace.c (pspace_object) <type_printers>: New
field.
(pspy_dealloc): Decref new field.
(pspy_new): Set new field.
(pspy_get_type_printers, pspy_set_type_printers): New functions.
(pspace_to_pspace_object): Set new field.
(pspace_getset): Add "type_printers".
* python/python.c (start_type_printers, apply_type_printers,
free_type_printers): New functions.
(_initialize_python): Set gdb.type_printers.
* python/python.h (start_type_printers, apply_type_printers,
free_type_printers): Declare.
* typeprint.c (type_print_raw_options, default_ptype_flags):
Update for new fields.
(do_free_global_table, create_global_typedef_table,
find_global_typedef): New functions.
(find_typedef_in_hash): Use find_global_typedef.
(whatis_exp): Use create_global_typedef_table. Change cleanup
handling.
* typeprint.h (struct type_print_options) <global_typedefs,
global_printers>: New fields.
doc
* gdb.texinfo (Symbols): Document "info type-printers",
"enable type-printer" and "disable type-printer".
(Python API): Add new node to menu.
(Type Printing API): New node.
(Progspaces In Python): Document type_printers field.
(Objfiles In Python): Likewise.
(gdb.types) <get_type_recognizers, apply_type_recognizers,
register_type_printer, TypePrinter>: Document.
testsuite
* gdb.base/completion.exp: Update for "info type-printers".
* gdb.python/py-typeprint.cc: New file.
* gdb.python/py-typeprint.exp: New file.
* gdb.python/py-typeprint.py: New file.
2012-11-13 01:41:59 +08:00
|
|
|
** Types can be pretty-printed via a Python API.
|
|
|
|
|
|
2012-12-13 00:47:30 +08:00
|
|
|
** Python 3 is now supported (in addition to Python 2.4 or later)
|
|
|
|
|
|
2013-01-24 03:59:13 +08:00
|
|
|
** New class gdb.Architecture exposes GDB's internal representation
|
|
|
|
|
of architecture in the Python API.
|
|
|
|
|
|
|
|
|
|
** New method Frame.architecture returns the gdb.Architecture object
|
|
|
|
|
corresponding to the frame's architecture.
|
|
|
|
|
|
2012-08-11 04:26:00 +08:00
|
|
|
* New Python-based convenience functions:
|
|
|
|
|
|
|
|
|
|
** $_memeq(buf1, buf2, length)
|
|
|
|
|
** $_streq(str1, str2)
|
|
|
|
|
** $_strlen(str)
|
|
|
|
|
** $_regex(str, regex)
|
|
|
|
|
|
2012-08-07 01:13:27 +08:00
|
|
|
* The 'cd' command now defaults to using '~' (the home directory) if not
|
|
|
|
|
given an argument.
|
|
|
|
|
|
2013-01-22 01:29:39 +08:00
|
|
|
* The C++ ABI now defaults to the GNU v3 ABI. This has been the
|
|
|
|
|
default for GCC since November 2000.
|
|
|
|
|
|
2012-11-09 20:48:11 +08:00
|
|
|
* The command 'forward-search' can now be abbreviated as 'fo'.
|
|
|
|
|
|
2012-12-15 10:19:21 +08:00
|
|
|
* The command 'info tracepoints' can now display 'installed on target'
|
|
|
|
|
or 'not installed on target' for each non-pending location of tracepoint.
|
|
|
|
|
|
2012-07-26 23:28:21 +08:00
|
|
|
* New configure options
|
|
|
|
|
|
|
|
|
|
--enable-libmcheck/--disable-libmcheck
|
|
|
|
|
By default, development versions are built with -lmcheck on hosts
|
|
|
|
|
that support it, in order to help track memory corruption issues.
|
|
|
|
|
Release versions, on the other hand, are built without -lmcheck
|
|
|
|
|
by default. The --enable-libmcheck/--disable-libmcheck configure
|
|
|
|
|
options allow the user to override that default.
|
gdb/
2013-04-10 Hui Zhu <hui@codesourcery.com>
Yao Qi <yao@codesourcery.com>
* configure.ac: Check libbabeltrace is installed.
* config.in: Regenerate.
* configure: Regenerate.
* Makefile.in (LIBBABELTRACE): New.
(CLIBS): Add LIBBABELTRACE.
* ctf.c: Include "exec.h".
(CTF_EVENT_ID_STATUS, CTF_EVENT_ID_TSV_DEF): New macros.
(CTF_EVENT_ID_TP_DEF, ctf_save_write_int32): New macros.
(ctf_save_metadata_header): Define new type aliases in
metadata.
(ctf_write_header): Define event type "tsv_def" and "tp_def"
in metadata. Start a new faked packet for trace status.
(ctf_write_status): Write trace status to CTF.
(ctf_write_uploaded_tsv): Write TSV to CTF.
(ctf_write_uploaded_tp): Write tracepoint definition to CTF.
(ctf_write_definition_end): End the faked packet.
(ctx, ctf_iter, trace_dirname): New.
(start_pos): New variable.
(ctf_destroy, ctf_open_dir, ctf_open): New.
(SET_INT32_FIELD, SET_ARRAY_FIELD, SET_STRING_FIELD): New
macros.
(ctf_read_tsv, ctf_read_tp, ctf_close, ctf_files_info): New.
(ctf_fetch_registers, ctf_xfer_partial): New.
(ctf_get_trace_state_variable_value): New.
(ctf_get_tpnum_from_frame_event): New.
(ctf_get_traceframe_address): New.
(ctf_trace_find, ctf_has_stack): New.
(ctf_has_registers, ctf_traceframe_info, init_ctf_ops): New.
(ctf_get_trace_status, ctf_read_status): New.
(_initialize_ctf): New.
* tracepoint.c (get_tracepoint_number): New
(get_uploaded_tsv): Remove 'static'.
(struct traceframe_info, trace_regblock_size): Move it to ...
* tracepoint.h: ... here.
(get_tracepoint_number): Declare it.
(get_uploaded_tsv): Declare it.
* NEWS: Mention new configure option.
gdb/doc/
2013-04-10 Yao Qi <yao@codesourcery.com>
* gdb.texinfo (Trace Files): Add "target ctf".
gdb/testsuite/
2013-04-10 Yao Qi <yao@codesourcery.com>
* gdb.trace/actions.exp: Save trace data to CTF.
Change to ctf target if GDB supports, read CTF data in ctf
target, and check the actions of tracepoints.
* gdb.trace/while-stepping.exp: Likewise.
* gdb.trace/report.exp: Test GDB saves trace data to CTF
format and read CTF trace file if GDB supports.
* gdb.trace/tstatus.exp: Save trace data to CTF. If ctf
target is supported, change to ctf target, read trace data and
check output of command "tstatus".
* gdb.trace/tsv.exp: Save trace frame to CTF. If GDB supports,
read CTF data by target ctf and call check_tsv.
2013-04-10 17:42:57 +08:00
|
|
|
--with-babeltrace/--with-babeltrace-include/--with-babeltrace-lib
|
|
|
|
|
This configure option allows the user to build GDB with
|
|
|
|
|
libbabeltrace using which GDB can read Common Trace Format data.
|
2012-07-26 23:28:21 +08:00
|
|
|
|
2012-07-25 23:47:09 +08:00
|
|
|
* New commands (for set/show, see "New options" below)
|
|
|
|
|
|
2013-01-17 01:31:40 +08:00
|
|
|
catch signal
|
|
|
|
|
Catch signals. This is similar to "handle", but allows commands and
|
|
|
|
|
conditions to be attached.
|
|
|
|
|
|
2012-07-25 23:47:09 +08:00
|
|
|
maint info bfds
|
|
|
|
|
List the BFDs known to GDB.
|
|
|
|
|
|
2012-08-23 03:15:15 +08:00
|
|
|
python-interactive [command]
|
|
|
|
|
pi [command]
|
|
|
|
|
Start a Python interactive prompt, or evaluate the optional command
|
|
|
|
|
and print the result of expressions.
|
|
|
|
|
|
|
|
|
|
py [command]
|
|
|
|
|
"py" is a new alias for "python".
|
|
|
|
|
|
* NEWS: Update.
* data-directory/Makefile.in (PYTHON_FILES): Add
type_printers.py.
* python/lib/gdb/command/type_printers.py: New file.
* python/lib/gdb/command/types.py (TypePrinter): New class.
(_get_some_type_recognizers, get_type_recognizers,
apply_type_recognizers, register_type_printer): New
functions.
* python/py-objfile.c (objfile_object) <type_printers>: New
field.
(objfpy_dealloc): Decref new field.
(objfpy_new): Set new field.
(objfpy_get_type_printers, objfpy_set_type_printers): New
functions.
(objfile_to_objfile_object): Set new field.
(objfile_getset): Add "type_printers".
* python/py-progspace.c (pspace_object) <type_printers>: New
field.
(pspy_dealloc): Decref new field.
(pspy_new): Set new field.
(pspy_get_type_printers, pspy_set_type_printers): New functions.
(pspace_to_pspace_object): Set new field.
(pspace_getset): Add "type_printers".
* python/python.c (start_type_printers, apply_type_printers,
free_type_printers): New functions.
(_initialize_python): Set gdb.type_printers.
* python/python.h (start_type_printers, apply_type_printers,
free_type_printers): Declare.
* typeprint.c (type_print_raw_options, default_ptype_flags):
Update for new fields.
(do_free_global_table, create_global_typedef_table,
find_global_typedef): New functions.
(find_typedef_in_hash): Use find_global_typedef.
(whatis_exp): Use create_global_typedef_table. Change cleanup
handling.
* typeprint.h (struct type_print_options) <global_typedefs,
global_printers>: New fields.
doc
* gdb.texinfo (Symbols): Document "info type-printers",
"enable type-printer" and "disable type-printer".
(Python API): Add new node to menu.
(Type Printing API): New node.
(Progspaces In Python): Document type_printers field.
(Objfiles In Python): Likewise.
(gdb.types) <get_type_recognizers, apply_type_recognizers,
register_type_printer, TypePrinter>: Document.
testsuite
* gdb.base/completion.exp: Update for "info type-printers".
* gdb.python/py-typeprint.cc: New file.
* gdb.python/py-typeprint.exp: New file.
* gdb.python/py-typeprint.py: New file.
2012-11-13 01:41:59 +08:00
|
|
|
enable type-printer [name]...
|
|
|
|
|
disable type-printer [name]...
|
|
|
|
|
Enable or disable type printers.
|
|
|
|
|
|
2012-09-19 19:07:01 +08:00
|
|
|
* Removed commands
|
|
|
|
|
|
|
|
|
|
** For the Renesas Super-H architecture, the "regs" command has been removed
|
|
|
|
|
(has been deprecated in GDB 7.5), and "info all-registers" should be used
|
|
|
|
|
instead.
|
|
|
|
|
|
* NEWS: Update.
* c-typeprint.c (c_type_print_base): Handle print_method and
print_typedefs flags.
* gdbcmd.h (setprinttypelist, showprinttypelist): Declare.
* python/py-type.c (typy_str): Use LA_PRINT_TYPE and raw
options.
* typeprint.c (type_print_raw_options, default_ptype_flags):
Update for new field.s
(whatis_exp): Parse flags. Use LA_PRINT_TYPE.
(setprinttypelist, showprinttypelist, print_methods,
print_typedefs): New globals.
(set_print_type, show_print_type, set_print_type_methods,
show_print_type_methods, set_print_type_typedefs,
show_print_type_typedefs): New functions.
(_initialize_typeprint): Update documentation. Add "print
type methods" and "print type typedefs" parameters.
* typeprint.h (struct type_print_options) <print_methods,
print_typedefs>: New fields.
doc
* gdb.texinfo (Symbols): Document "set print type methods",
"set print type typedefs", and flags to ptype and whatis.
2012-11-13 01:26:21 +08:00
|
|
|
* New options
|
|
|
|
|
|
|
|
|
|
set print type methods (on|off)
|
|
|
|
|
show print type methods
|
|
|
|
|
Control whether method declarations are displayed by "ptype".
|
|
|
|
|
The default is to show them.
|
|
|
|
|
|
|
|
|
|
set print type typedefs (on|off)
|
|
|
|
|
show print type typedefs
|
|
|
|
|
Control whether typedef definitions are displayed by "ptype".
|
|
|
|
|
The default is to show them.
|
|
|
|
|
|
2013-02-04 00:09:33 +08:00
|
|
|
set filename-display basename|relative|absolute
|
|
|
|
|
show filename-display
|
|
|
|
|
Control the way in which filenames is displayed.
|
|
|
|
|
The default is "relative", which preserves previous behavior.
|
|
|
|
|
|
2013-04-02 23:19:07 +08:00
|
|
|
set trace-buffer-size
|
|
|
|
|
show trace-buffer-size
|
|
|
|
|
Request target to change the size of trace buffer.
|
|
|
|
|
|
2013-04-03 01:48:49 +08:00
|
|
|
set remote trace-buffer-size-packet auto|on|off
|
|
|
|
|
show remote trace-buffer-size-packet
|
|
|
|
|
Control the use of the remote protocol `QTBuffer:size' packet.
|
|
|
|
|
|
2013-04-03 01:52:08 +08:00
|
|
|
set debug aarch64
|
|
|
|
|
show debug aarch64
|
|
|
|
|
Control display of debugging messages related to ARM AArch64.
|
|
|
|
|
The default is off.
|
|
|
|
|
|
|
|
|
|
set debug coff-pe-read
|
|
|
|
|
show debug coff-pe-read
|
|
|
|
|
Control display of debugging messages related to reading of COFF/PE
|
|
|
|
|
exported symbols.
|
|
|
|
|
|
|
|
|
|
set debug mach-o
|
|
|
|
|
show debug mach-o
|
|
|
|
|
Control display of debugging messages related to Mach-O symbols
|
|
|
|
|
processing.
|
|
|
|
|
|
|
|
|
|
set debug notification
|
|
|
|
|
show debug notification
|
|
|
|
|
Control display of debugging info for async remote notification.
|
|
|
|
|
|
2012-08-09 20:53:46 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** Command parameter changes are now notified using new async record
|
|
|
|
|
"=cmd-param-changed".
|
2012-09-18 19:33:43 +08:00
|
|
|
** Trace frame changes caused by command "tfind" are now notified using
|
|
|
|
|
new async record "=traceframe-changed".
|
2013-02-06 22:45:20 +08:00
|
|
|
** The creation, deletion and modification of trace state variables
|
|
|
|
|
are now notified using new async records "=tsv-created",
|
|
|
|
|
"=tsv-deleted" and "=tsv-modified".
|
2012-09-21 09:46:46 +08:00
|
|
|
** The start and stop of process record are now notified using new
|
|
|
|
|
async record "=record-started" and "=record-stopped".
|
2012-10-17 08:53:24 +08:00
|
|
|
** Memory changes are now notified using new async record
|
|
|
|
|
"=memory-changed".
|
2012-11-09 21:23:33 +08:00
|
|
|
** The data-disassemble command response will include a "fullname" field
|
2013-04-04 02:28:49 +08:00
|
|
|
containing the absolute file name when source has been requested.
|
2012-11-14 05:19:11 +08:00
|
|
|
** New optional parameter COUNT added to the "-data-write-memory-bytes"
|
|
|
|
|
command, to allow pattern filling of memory areas.
|
2012-12-13 05:23:29 +08:00
|
|
|
** New commands "-catch-load"/"-catch-unload" added for intercepting
|
|
|
|
|
library load/unload events.
|
2012-12-15 10:19:21 +08:00
|
|
|
** The response to breakpoint commands and breakpoint async records
|
|
|
|
|
includes an "installed" field containing a boolean state about each
|
|
|
|
|
non-pending tracepoint location is whether installed on target or not.
|
2013-02-15 17:47:50 +08:00
|
|
|
** Output of the "-trace-status" command includes a "trace-file" field
|
|
|
|
|
containing the name of the trace file being examined. This field is
|
|
|
|
|
optional, and only present when examining a trace file.
|
2013-04-04 02:28:49 +08:00
|
|
|
** The "fullname" field is now always present along with the "file" field,
|
|
|
|
|
even if the file cannot be found by GDB.
|
2012-08-09 20:53:46 +08:00
|
|
|
|
2012-11-27 03:23:56 +08:00
|
|
|
* GDB now supports the "mini debuginfo" section, .gnu_debugdata.
|
|
|
|
|
You must have the LZMA library available when configuring GDB for this
|
|
|
|
|
feature to be enabled. For more information, see:
|
|
|
|
|
http://fedoraproject.org/wiki/Features/MiniDebugInfo
|
|
|
|
|
|
2013-03-08 23:06:39 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
QTBuffer:size
|
|
|
|
|
Set the size of trace buffer. The remote stub reports support for this
|
|
|
|
|
packet to gdb's qSupported query.
|
|
|
|
|
|
2013-04-09 16:04:32 +08:00
|
|
|
Qbtrace:bts
|
|
|
|
|
Enable Branch Trace Store (BTS)-based branch tracing for the current
|
|
|
|
|
thread. The remote stub reports support for this packet to gdb's
|
|
|
|
|
qSupported query.
|
|
|
|
|
|
|
|
|
|
Qbtrace:off
|
|
|
|
|
Disable branch tracing for the current thread. The remote stub reports
|
|
|
|
|
support for this packet to gdb's qSupported query.
|
|
|
|
|
|
|
|
|
|
qXfer:btrace:read
|
|
|
|
|
Read the traced branches for the current thread. The remote stub
|
|
|
|
|
reports support for this packet to gdb's qSupported query.
|
|
|
|
|
|
2012-07-18 12:02:10 +08:00
|
|
|
*** Changes in GDB 7.5
|
2011-04-04 00:55:15 +08:00
|
|
|
|
2012-07-05 04:49:56 +08:00
|
|
|
* GDB now supports x32 ABI. Visit <http://sites.google.com/site/x32abi/>
|
|
|
|
|
for more x32 ABI info.
|
|
|
|
|
|
2012-05-23 01:12:07 +08:00
|
|
|
* GDB now supports access to MIPS DSP registers on Linux targets.
|
|
|
|
|
|
gdb/
* NEWS: Add microMIPS support and "set mips compression",
"show mips compression" commands.
* mips-tdep.h (mips_isa): New enum.
(gdbarch_tdep): Add mips_isa.
(mips_pc_is_mips16): Update prototype.
(mips_pc_is_mips, mips_pc_is_micromips): New prototypes.
* mips-tdep.c (mips_compression_mips16): New variable.
(mips_compression_micromips): Likewise.
(mips_compression_strings): Likewise.
(mips_compression_string): Likewise.
(is_mips16_isa, is_micromips_isa): New functions.
(is_mips16_addr): Rename to...
(is_compact_addr): ... this.
(unmake_mips16_addr): Likewise to...
(unmake_compact_addr): ... this.
(make_mips16_addr): Likewise to...
(make_compact_addr): ... this.
(is_mips_addr, is_mips16_addr, is_micromips_addr): New
functions.
(mips_elf_make_msymbol_special): Handle microMIPS code.
(msymbol_is_special): Rename to...
(msymbol_is_mips16): ... this.
(mips_make_symbol_special, mips_pc_is_mips16): Update
accordingly.
(msymbol_is_mips, msymbol_is_micromips): New functions.
(mips16_to_32_reg): Rename to...
(mips_reg3_to_reg): ... this.
(mips_pc_is_mips, mips_pc_is_micromips): New functions.
(mips_pc_isa): Likewise.
(mips_read_pc, mips_unwind_pc, mips_write_pc): Handle microMIPS
code.
(mips_fetch_instruction): Pass return status instead of printing
an error message if requested. Handle microMIPS code. Bail out
on an invalid ISA.
(micromips_op): New macro.
(b0s4_imm, b0s5_imm, b0s5_reg, b0s7_imm, b0s10_imm): Likewise.
(b1s9_imm, b2s3_cc, b4s2_regl, b5s5_op, b5s5_reg): Likewise.
(b6s4_op, b7s3_reg): Likewise.
(b0s6_op, b0s11_op, b0s12_imm, b0s16_imm, b0s26_imm): Likewise.
(b6s10_ext, b11s5_reg, b12s4_op): Likewise.
(mips_insn_size): New function.
(mips32_next_pc): Update mips_fetch_instruction call.
(micromips_relative_offset7): New function.
(micromips_relative_offset10): Likewise.
(micromips_relative_offset16): Likewise.
(micromips_pc_insn_size): Likewise.
(micromips_bc1_pc): Likewise.
(micromips_next_pc): Likewise.
(unpack_mips16): Update mips_fetch_instruction call.
(extended_mips16_next_pc): Update according to change to
mips16_to_32_reg.
(mips_next_pc): Update mips_pc_is_mips16 call. Handle microMIPS
code.
(mips16_scan_prologue): Update mips_fetch_instruction call.
Update according to change to mips16_to_32_reg.
(mips_insn16_frame_sniffer): Update mips_pc_is_mips16 call.
(mips_insn16_frame_base_sniffer): Likewise.
(micromips_decode_imm9): New function.
(micromips_scan_prologue): Likewise.
(mips_micro_frame_cache): Likewise.
(mips_micro_frame_this_id): Likewise.
(mips_micro_frame_prev_register): Likewise.
(mips_micro_frame_sniffer): Likewise.
(mips_micro_frame_unwind): New variable.
(mips_micro_frame_base_address): New function.
(mips_micro_frame_base): New variable.
(mips_micro_frame_base_sniffer): New function.
(mips32_scan_prologue): Update mips_fetch_instruction call.
(mips_insn32_frame_sniffer): Check for the standard MIPS ISA
rather than for MIPS16.
(mips_insn32_frame_base_sniffer): Likewise.
(mips_addr_bits_remove): Handle microMIPS code.
(deal_with_atomic_sequence): Rename to...
(mips_deal_with_atomic_sequence): ... this. Update the type
of the variable used to hold an instruction. Remove the ISA bit
check. Update mips_fetch_instruction call.
(micromips_deal_with_atomic_sequence): New function.
(deal_with_atomic_sequence): Likewise.
(mips_about_to_return): Handle microMIPS code. Update
mips_fetch_instruction call.
(heuristic_proc_start): Check for the standard MIPS ISA rather
than for MIPS16. Update mips_pc_is_mips16 and
mips_fetch_instruction calls. Handle microMIPS code.
(mips_push_dummy_code): Handle microMIPS code.
(mips_eabi_push_dummy_call): Likewise.
(mips_o32_return_value): Update mips_pc_is_mips16 call.
(mips_o64_push_dummy_call): Handle microMIPS code.
(mips_o64_return_value): Update mips_pc_is_mips16 call.
(is_delayed): Remove function.
(mips_single_step_through_delay): Replace the call to is_delayed
with mips32_instruction_has_delay_slot. Correct MIPS16 handling.
Handle microMIPS code.
(mips_skip_prologue): Update mips_pc_is_mips16 call. Handle
microMIPS code.
(mips32_in_function_epilogue_p): Update mips_fetch_instruction
call.
(micromips_in_function_epilogue_p): New function.
(mips16_in_function_epilogue_p): Update mips_fetch_instruction
call.
(mips_in_function_epilogue_p): Update mips_pc_is_mips16 call.
Handle microMIPS.
(gdb_print_insn_mips): Likewise.
(mips_breakpoint_from_pc): Likewise.
(mips_remote_breakpoint_from_pc): New function.
(mips32_instruction_has_delay_slot): Simplify making use of the
updated mips_fetch_instruction interface.
(micromips_instruction_has_delay_slot): New function.
(mips16_instruction_has_delay_slot): Simplify making use of the
updated mips_fetch_instruction interface.
(mips_adjust_breakpoint_address): Check for the standard MIPS
ISA rather than for MIPS16 ISA. Update for unmake_compact_addr
calls. Handle microMIPS code.
(mips_get_mips16_fn_stub_pc): Update mips_fetch_instruction call.
(mips_skip_trampoline_code): Handle microMIPS code.
(global_mips_compression): New function.
(mips_gdbarch_init): Handle the compressed ISA setting from ELF
file flags. Register the microMIPS remote breakpoint handler
and heuristic frame unwinder.
(show_mips_compression): New function.
(_initialize_mips_tdep): Add the "set mips compression" and
"show mips compression" commands.
gdb/doc/
* gdb.texinfo (MIPS): Document "set mips compression" and "show
mips compression".
(MIPS Breakpoint Kinds): New subsubsection.
2012-05-19 07:46:40 +08:00
|
|
|
* GDB now supports debugging microMIPS binaries.
|
|
|
|
|
|
2012-05-12 06:24:24 +08:00
|
|
|
* The "info os" command on GNU/Linux can now display information on
|
|
|
|
|
several new classes of objects managed by the operating system:
|
|
|
|
|
"info os procgroups" lists process groups
|
|
|
|
|
"info os files" lists file descriptors
|
|
|
|
|
"info os sockets" lists internet-domain sockets
|
|
|
|
|
"info os shm" lists shared-memory regions
|
|
|
|
|
"info os semaphores" lists semaphores
|
|
|
|
|
"info os msg" lists message queues
|
|
|
|
|
"info os modules" lists loaded kernel modules
|
|
|
|
|
|
2012-04-28 04:47:57 +08:00
|
|
|
* GDB now has support for SDT (Static Defined Tracing) probes. Currently,
|
|
|
|
|
the only implemented backend is for SystemTap probes (<sys/sdt.h>). You
|
|
|
|
|
can set a breakpoint using the new "-probe, "-pstap" or "-probe-stap"
|
|
|
|
|
options and inspect the probe arguments using the new $_probe_arg family
|
|
|
|
|
of convenience variables. You can obtain more information about SystemTap
|
|
|
|
|
in <http://sourceware.org/systemtap/>.
|
|
|
|
|
|
2012-03-27 23:46:33 +08:00
|
|
|
* GDB now supports reversible debugging on ARM, it allows you to
|
|
|
|
|
debug basic ARM and THUMB instructions, and provides
|
|
|
|
|
record/replay support.
|
|
|
|
|
|
2012-03-14 05:02:40 +08:00
|
|
|
* The option "symbol-reloading" has been deleted as it is no longer used.
|
|
|
|
|
|
2012-01-15 02:13:27 +08:00
|
|
|
* Python scripting
|
|
|
|
|
|
2012-03-02 03:30:25 +08:00
|
|
|
** GDB commands implemented in Python can now be put in command class
|
|
|
|
|
"gdb.COMMAND_USER".
|
|
|
|
|
|
2012-01-15 02:13:27 +08:00
|
|
|
** The "maint set python print-stack on|off" is now deleted.
|
|
|
|
|
|
2012-01-20 00:54:03 +08:00
|
|
|
** A new class, gdb.printing.FlagEnumerationPrinter, can be used to
|
|
|
|
|
apply "flag enum"-style pretty-printing to any enum.
|
|
|
|
|
|
2012-02-08 03:42:27 +08:00
|
|
|
** gdb.lookup_symbol can now work when there is no current frame.
|
|
|
|
|
|
|
|
|
|
** gdb.Symbol now has a 'line' attribute, holding the line number in
|
|
|
|
|
the source at which the symbol was defined.
|
|
|
|
|
|
2012-02-08 03:47:16 +08:00
|
|
|
** gdb.Symbol now has the new attribute 'needs_frame' and the new
|
|
|
|
|
method 'value'. The former indicates whether the symbol needs a
|
|
|
|
|
frame in order to compute its value, and the latter computes the
|
|
|
|
|
symbol's value.
|
|
|
|
|
|
2012-03-22 16:10:44 +08:00
|
|
|
** A new method 'referenced_value' on gdb.Value objects which can
|
|
|
|
|
dereference pointer as well as C++ reference values.
|
|
|
|
|
|
2012-05-03 15:07:26 +08:00
|
|
|
** New methods 'global_block' and 'static_block' on gdb.Symtab objects
|
|
|
|
|
which return the global and static blocks (as gdb.Block objects),
|
|
|
|
|
of the underlying symbol table, respectively.
|
|
|
|
|
|
2012-05-13 19:33:44 +08:00
|
|
|
** New function gdb.find_pc_line which returns the gdb.Symtab_and_line
|
|
|
|
|
object associated with a PC value.
|
|
|
|
|
|
2012-06-27 08:21:21 +08:00
|
|
|
** gdb.Symtab_and_line has new attribute 'last' which holds the end
|
|
|
|
|
of the address range occupied by code for the current source line.
|
|
|
|
|
|
2012-04-25 22:07:23 +08:00
|
|
|
* Go language support.
|
|
|
|
|
GDB now supports debugging programs written in the Go programming
|
|
|
|
|
language.
|
|
|
|
|
|
2011-12-17 03:06:38 +08:00
|
|
|
* GDBserver now supports stdio connections.
|
|
|
|
|
E.g. (gdb) target remote | ssh myhost gdbserver - hello
|
|
|
|
|
|
2012-01-02 10:28:59 +08:00
|
|
|
* The binary "gdbtui" can no longer be built or installed.
|
|
|
|
|
Use "gdb -tui" instead.
|
|
|
|
|
|
2012-01-17 03:44:16 +08:00
|
|
|
* GDB will now print "flag" enums specially. A flag enum is one where
|
|
|
|
|
all the enumerator values have no bits in common when pairwise
|
|
|
|
|
"and"ed. When printing a value whose type is a flag enum, GDB will
|
|
|
|
|
show all the constants, e.g., for enum E { ONE = 1, TWO = 2}:
|
|
|
|
|
(gdb) print (enum E) 3
|
|
|
|
|
$1 = (ONE | TWO)
|
|
|
|
|
|
2012-01-17 04:40:53 +08:00
|
|
|
* The filename part of a linespec will now match trailing components
|
|
|
|
|
of a source file name. For example, "break gcc/expr.c:1000" will
|
|
|
|
|
now set a breakpoint in build/gcc/expr.c, but not
|
|
|
|
|
build/libcpp/expr.c.
|
|
|
|
|
|
2012-01-20 18:31:26 +08:00
|
|
|
* The "info proc" and "generate-core-file" commands will now also
|
|
|
|
|
work on remote targets connected to GDBserver on Linux.
|
|
|
|
|
|
2012-01-24 23:13:30 +08:00
|
|
|
* The command "info catch" has been removed. It has been disabled
|
|
|
|
|
since December 2007.
|
|
|
|
|
|
2012-03-02 02:12:43 +08:00
|
|
|
* The "catch exception" and "catch assert" commands now accept
|
|
|
|
|
a condition at the end of the command, much like the "break"
|
|
|
|
|
command does. For instance:
|
|
|
|
|
|
|
|
|
|
(gdb) catch exception Constraint_Error if Barrier = True
|
|
|
|
|
|
|
|
|
|
Previously, it was possible to add a condition to such catchpoints,
|
|
|
|
|
but it had to be done as a second step, after the catchpoint had been
|
|
|
|
|
created, using the "condition" command.
|
|
|
|
|
|
2012-03-03 17:51:29 +08:00
|
|
|
* The "info static-tracepoint-marker" command will now also work on
|
|
|
|
|
native Linux targets with in-process agent.
|
|
|
|
|
|
2012-03-17 00:47:34 +08:00
|
|
|
* GDB can now set breakpoints on inlined functions.
|
|
|
|
|
|
|
|
|
|
* The .gdb_index section has been updated to include symbols for
|
|
|
|
|
inlined functions. GDB will ignore older .gdb_index sections by
|
|
|
|
|
default, which could cause symbol files to be loaded more slowly
|
2012-07-21 01:38:05 +08:00
|
|
|
until their .gdb_index sections can be recreated. The new command
|
|
|
|
|
"set use-deprecated-index-sections on" will cause GDB to use any older
|
|
|
|
|
.gdb_index sections it finds. This will restore performance, but the
|
|
|
|
|
ability to set breakpoints on inlined functions will be lost in symbol
|
|
|
|
|
files with older .gdb_index sections.
|
2012-03-17 00:47:34 +08:00
|
|
|
|
2012-06-24 06:23:47 +08:00
|
|
|
The .gdb_index section has also been updated to record more information
|
|
|
|
|
about each symbol. This speeds up the "info variables", "info functions"
|
|
|
|
|
and "info types" commands when used with programs having the .gdb_index
|
|
|
|
|
section, as well as speeding up debugging with shared libraries using
|
|
|
|
|
the .gdb_index section.
|
|
|
|
|
|
2012-03-29 05:31:56 +08:00
|
|
|
* Ada support for GDB/MI Variable Objects has been added.
|
|
|
|
|
|
2012-04-24 22:33:12 +08:00
|
|
|
* GDB can now support 'breakpoint always-inserted mode' in 'record'
|
|
|
|
|
target.
|
|
|
|
|
|
2012-05-24 08:33:47 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** New command -info-os is the MI equivalent of "info os".
|
|
|
|
|
|
2012-06-29 06:11:23 +08:00
|
|
|
** Output logs ("set logging" and related) now include MI output.
|
|
|
|
|
|
2012-01-25 05:39:18 +08:00
|
|
|
* New commands
|
|
|
|
|
|
2012-07-21 01:38:05 +08:00
|
|
|
** "set use-deprecated-index-sections on|off"
|
|
|
|
|
"show use-deprecated-index-sections on|off"
|
|
|
|
|
Controls the use of deprecated .gdb_index sections.
|
|
|
|
|
|
2012-01-25 05:39:18 +08:00
|
|
|
** "catch load" and "catch unload" can be used to stop when a shared
|
|
|
|
|
library is loaded or unloaded, respectively.
|
|
|
|
|
|
2012-02-15 07:28:15 +08:00
|
|
|
** "enable count" can be used to auto-disable a breakpoint after
|
|
|
|
|
several hits.
|
|
|
|
|
|
2012-03-16 00:32:16 +08:00
|
|
|
** "info vtbl" can be used to show the virtual method tables for
|
2012-03-15 23:43:18 +08:00
|
|
|
C++ and Java objects.
|
|
|
|
|
|
2012-04-11 13:50:44 +08:00
|
|
|
** "explore" and its sub commands "explore value" and "explore type"
|
2013-11-16 02:19:57 +08:00
|
|
|
can be used to recursively explore values and types of
|
2012-04-11 13:50:44 +08:00
|
|
|
expressions. These commands are available only if GDB is
|
|
|
|
|
configured with '--with-python'.
|
|
|
|
|
|
gdb/
auto-load: Implementation.
* NEWS: New descriptions for "info auto-load",
"info auto-load gdb-scripts", "info auto-load python-scripts",
"info auto-load local-gdbinit" and "info auto-load libthread-db".
Deprecate "info auto-load-scripts", "set auto-load-scripts on|off"
and "show auto-load-scripts". New description for "set auto-load",
"show auto-load", "set auto-load gdb-scripts",
"show auto-load gdb-scripts", "set auto-load python-scripts",
"show auto-load python-scripts", "set auto-load local-gdbinit",
"show auto-load local-gdbinit", "set auto-load libthread-db" and
"show auto-load libthread-db".
* auto-load.c: Remove include python/python-internal.h. Add includes
exceptions.h, cli/cli-script.h, gdbcmd.h, cli/cli-decode.h and
cli/cli-setshow.h.
(GDB_AUTO_FILE_NAME, source_gdb_script_for_objfile)
(auto_load_gdb_scripts, show_auto_load_gdb_scripts): New.
(gdbpy_global_auto_load): Rename to ...
(global_auto_load): ... here.
(auto_load_local_gdbinit, auto_load_local_gdbinit_pathname)
(auto_load_local_gdbinit_loaded, show_auto_load_local_gdbinit)
(script_language_gdb, source_gdb_script_for_objfile): New.
(struct loaded_script): New field language.
(hash_loaded_script_entry, eq_loaded_script_entry): Calculate also
LANGUAGE.
(maybe_add_script): Add parameter language. Drop redundant
entry.full_path initialization. Initialize entry.language and
(*slot)->language.
(auto_load_objfile_script): Change parameter suffix to language.
Remove the call of maybe_add_script.
Call language->source_script_for_objfile.
(load_auto_scripts_for_objfile, struct collect_matching_scripts_data):
New.
(collect_matching_scripts): Adjust it for
struct collect_matching_scripts_data.
(auto_load_info_scripts_pattern_nl): New variable.
(info_auto_load_scripts): Rename to ...
(auto_load_info_scripts): ... here, add parameter language. Adjust it
for struct collect_matching_scripts_data.
(info_auto_load_gdb_scripts, info_auto_load_local_gdbinit)
(set_auto_load_cmd, auto_load_set_cmdlist_get, show_auto_load_cmd)
(auto_load_show_cmdlist_get, info_auto_load_cmd)
(auto_load_info_cmdlist_get): New.
(_initialize_auto_load): Move add_info of "auto-load-scripts" to
python/py-auto-load.c. New installment for "set auto-load gdb-scripts",
"info auto-load gdb-scripts", "set auto-load local-gdbinit" and
"info auto-load local-gdbinit".
* auto-load.h (struct script_language): New.
(gdbpy_global_auto_load): Rename to ...
(global_auto_load): ... here.
(auto_load_local_gdbinit, auto_load_local_gdbinit_pathname)
(auto_load_local_gdbinit_loaded): New declarations.
(maybe_add_script): New parameter language.
(auto_load_objfile_script): Change parameter suffix to language.
(load_auto_scripts_for_objfile, auto_load_info_scripts_pattern_nl)
(auto_load_info_scripts, auto_load_set_cmdlist_get)
(auto_load_show_cmdlist_get, auto_load_info_cmdlist_get): New
declarations.
* linux-thread-db.c: Include auto-load.h and ctype.h.
(auto_load_thread_db, show_auto_load_thread_db): New.
(struct thread_db_info): New field filename.
(delete_thread_db_info): Call xfree for FILENAME.
(try_thread_db_load): Initialize FILENAME.
(try_thread_db_load_from_pdir, try_thread_db_load_from_dir): Return
if !AUTO_LOAD_THREAD_DB.
(info_auto_load_libthread_db_compare, info_auto_load_libthread_db): New.
(_initialize_thread_db): Install auto_load_thread_db
as "set auto-load libthread-db" and install info_auto_load_libthread_db
as "info auto-load libthread-db".
* main.c (captured_main): Rename gdbpy_global_auto_load to
global_auto_load. Initialize AUTO_LOAD_LOCAL_GDBINIT_PATHNAME and
AUTO_LOAD_LOCAL_GDBINIT_LOADED.
(print_gdb_help): Extend the help for 'local init file'.
* python/py-auto-load.c: Remove a comment about gdb scripts extension.
(GDBPY_AUTO_SECTION_NAME): Extend the comment it is Python specific.
(auto_load_scripts): Rename to ...
(auto_load_python_scripts): ... here, update the comment.
(gdbpy_load_auto_script_for_objfile): New declaration.
(show_auto_load_python_scripts, script_language_python)
(gdbpy_load_auto_script_for_objfile): New.
(source_section_scripts): Refactor the code.
(load_auto_scripts_for_objfile): Rename to ...
(gdbpy_load_auto_scripts_for_objfile): ... here, update the
auto_load_objfile_script caller, drop GDBPY_GLOBAL_AUTO_LOAD checking.
(info_auto_load_python_scripts): New.
(gdbpy_initialize_auto_load): New variables cmd and cmd_name.
Rename "set auto-load-scripts" to "set auto-load python-scripts".
Register "set auto-load-scripts" as its deprecated alias. Register
"info auto-load python-scripts". Register "info auto-load-scripts" as
its deprecated alias.
(load_auto_scripts_for_objfile): Rename to ...
(gdbpy_load_auto_scripts_for_objfile): ... here.
* python/python.h (load_auto_scripts_for_objfile): Rename to ...
(gdbpy_load_auto_scripts_for_objfile): ... here.
gdb/doc/
auto-load: Implementation.
* gdb.texinfo (Mode Options): New anchor for -nx.
(Startup): New anchors for Option -init-eval-command,
Home Directory Init File
and Init File in the Current Directory during Startup.
Mention set auto-load local-gdbinit with a reference.
Change the sample code to "set auto-load python-scripts".
(Threads): New anchor set libthread-db-search-path.
Provide references to libthread_db.so.1 file.
(Controlling GDB): New menu item for Auto-loading.
(Auto-loading, Init File in the Current Directory)
(libthread_db.so.1 file, objfile-gdb.gdb file): New nodes.
(Python): Rename the menu item Auto-loading to Python Auto-loading.
(Writing a Pretty-Printer, Objfiles In Python): Update the renamed
reference.
(Auto-loading): Rename to ...
(Python Auto-loading): ... here. Change "set auto-load-scripts" to
"set auto-load python-scripts", new anchor for it. Change
"show auto-load-scripts" to "show auto-load python-scripts", new anchor
for it. Change "info auto-load-scripts"
to "info auto-load python-scripts", new anchor for it. Change "scripts"
to "Python scripts".
gdb/testsuite/
auto-load: Implementation.
* gdb.base/help.exp (test set height): Increase the height.
* gdb.python/py-objfile-script.exp (info auto-load-scripts): Change
to ...
(info auto-load python-scripts): ... here.
* gdb.python/py-section-script.exp (info auto-load-scripts *): Change
to ...
(info auto-load python-scripts *): ... here.
2012-04-17 23:51:48 +08:00
|
|
|
** "info auto-load" shows status of all kinds of auto-loaded files,
|
|
|
|
|
"info auto-load gdb-scripts" shows status of auto-loading GDB canned
|
|
|
|
|
sequences of commands files, "info auto-load python-scripts"
|
|
|
|
|
shows status of auto-loading Python script files,
|
|
|
|
|
"info auto-load local-gdbinit" shows status of loading init file
|
|
|
|
|
(.gdbinit) from current directory and "info auto-load libthread-db" shows
|
|
|
|
|
status of inferior specific thread debugging shared library loading.
|
|
|
|
|
|
|
|
|
|
** "info auto-load-scripts", "set auto-load-scripts on|off"
|
|
|
|
|
and "show auto-load-scripts" commands have been deprecated, use their
|
|
|
|
|
"info auto-load python-scripts", "set auto-load python-scripts on|off"
|
|
|
|
|
and "show auto-load python-scripts" counterparts instead.
|
|
|
|
|
|
2012-05-14 23:38:41 +08:00
|
|
|
** "dprintf location,format,args..." creates a dynamic printf, which
|
|
|
|
|
is basically a breakpoint that does a printf and immediately
|
|
|
|
|
resumes your program's execution, so it is like a printf that you
|
|
|
|
|
can insert dynamically at runtime instead of at compiletime.
|
|
|
|
|
|
2012-05-18 23:31:42 +08:00
|
|
|
** "set print symbol"
|
|
|
|
|
"show print symbol"
|
|
|
|
|
Controls whether GDB attempts to display the symbol, if any,
|
|
|
|
|
corresponding to addresses it prints. This defaults to "on", but
|
|
|
|
|
you can set it to "off" to restore GDB's previous behavior.
|
|
|
|
|
|
2012-06-07 02:03:54 +08:00
|
|
|
* Deprecated commands
|
|
|
|
|
|
|
|
|
|
** For the Renesas Super-H architecture, the "regs" command has been
|
|
|
|
|
deprecated, and "info all-registers" should be used instead.
|
|
|
|
|
|
2012-02-16 06:17:02 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Renesas RL78 rl78-*-elf
|
2012-03-05 19:46:35 +08:00
|
|
|
HP OpenVMS ia64 ia64-hp-openvms*
|
2012-02-16 06:17:02 +08:00
|
|
|
|
2012-02-24 23:04:58 +08:00
|
|
|
* GDBserver supports evaluation of breakpoint conditions. When
|
|
|
|
|
support is advertised by GDBserver, GDB may be told to send the
|
|
|
|
|
breakpoint conditions in bytecode form to GDBserver. GDBserver
|
|
|
|
|
will only report the breakpoint trigger to GDB when its condition
|
|
|
|
|
evaluates to true.
|
|
|
|
|
|
|
|
|
|
* New options
|
|
|
|
|
|
gdb/
* NEWS: Add microMIPS support and "set mips compression",
"show mips compression" commands.
* mips-tdep.h (mips_isa): New enum.
(gdbarch_tdep): Add mips_isa.
(mips_pc_is_mips16): Update prototype.
(mips_pc_is_mips, mips_pc_is_micromips): New prototypes.
* mips-tdep.c (mips_compression_mips16): New variable.
(mips_compression_micromips): Likewise.
(mips_compression_strings): Likewise.
(mips_compression_string): Likewise.
(is_mips16_isa, is_micromips_isa): New functions.
(is_mips16_addr): Rename to...
(is_compact_addr): ... this.
(unmake_mips16_addr): Likewise to...
(unmake_compact_addr): ... this.
(make_mips16_addr): Likewise to...
(make_compact_addr): ... this.
(is_mips_addr, is_mips16_addr, is_micromips_addr): New
functions.
(mips_elf_make_msymbol_special): Handle microMIPS code.
(msymbol_is_special): Rename to...
(msymbol_is_mips16): ... this.
(mips_make_symbol_special, mips_pc_is_mips16): Update
accordingly.
(msymbol_is_mips, msymbol_is_micromips): New functions.
(mips16_to_32_reg): Rename to...
(mips_reg3_to_reg): ... this.
(mips_pc_is_mips, mips_pc_is_micromips): New functions.
(mips_pc_isa): Likewise.
(mips_read_pc, mips_unwind_pc, mips_write_pc): Handle microMIPS
code.
(mips_fetch_instruction): Pass return status instead of printing
an error message if requested. Handle microMIPS code. Bail out
on an invalid ISA.
(micromips_op): New macro.
(b0s4_imm, b0s5_imm, b0s5_reg, b0s7_imm, b0s10_imm): Likewise.
(b1s9_imm, b2s3_cc, b4s2_regl, b5s5_op, b5s5_reg): Likewise.
(b6s4_op, b7s3_reg): Likewise.
(b0s6_op, b0s11_op, b0s12_imm, b0s16_imm, b0s26_imm): Likewise.
(b6s10_ext, b11s5_reg, b12s4_op): Likewise.
(mips_insn_size): New function.
(mips32_next_pc): Update mips_fetch_instruction call.
(micromips_relative_offset7): New function.
(micromips_relative_offset10): Likewise.
(micromips_relative_offset16): Likewise.
(micromips_pc_insn_size): Likewise.
(micromips_bc1_pc): Likewise.
(micromips_next_pc): Likewise.
(unpack_mips16): Update mips_fetch_instruction call.
(extended_mips16_next_pc): Update according to change to
mips16_to_32_reg.
(mips_next_pc): Update mips_pc_is_mips16 call. Handle microMIPS
code.
(mips16_scan_prologue): Update mips_fetch_instruction call.
Update according to change to mips16_to_32_reg.
(mips_insn16_frame_sniffer): Update mips_pc_is_mips16 call.
(mips_insn16_frame_base_sniffer): Likewise.
(micromips_decode_imm9): New function.
(micromips_scan_prologue): Likewise.
(mips_micro_frame_cache): Likewise.
(mips_micro_frame_this_id): Likewise.
(mips_micro_frame_prev_register): Likewise.
(mips_micro_frame_sniffer): Likewise.
(mips_micro_frame_unwind): New variable.
(mips_micro_frame_base_address): New function.
(mips_micro_frame_base): New variable.
(mips_micro_frame_base_sniffer): New function.
(mips32_scan_prologue): Update mips_fetch_instruction call.
(mips_insn32_frame_sniffer): Check for the standard MIPS ISA
rather than for MIPS16.
(mips_insn32_frame_base_sniffer): Likewise.
(mips_addr_bits_remove): Handle microMIPS code.
(deal_with_atomic_sequence): Rename to...
(mips_deal_with_atomic_sequence): ... this. Update the type
of the variable used to hold an instruction. Remove the ISA bit
check. Update mips_fetch_instruction call.
(micromips_deal_with_atomic_sequence): New function.
(deal_with_atomic_sequence): Likewise.
(mips_about_to_return): Handle microMIPS code. Update
mips_fetch_instruction call.
(heuristic_proc_start): Check for the standard MIPS ISA rather
than for MIPS16. Update mips_pc_is_mips16 and
mips_fetch_instruction calls. Handle microMIPS code.
(mips_push_dummy_code): Handle microMIPS code.
(mips_eabi_push_dummy_call): Likewise.
(mips_o32_return_value): Update mips_pc_is_mips16 call.
(mips_o64_push_dummy_call): Handle microMIPS code.
(mips_o64_return_value): Update mips_pc_is_mips16 call.
(is_delayed): Remove function.
(mips_single_step_through_delay): Replace the call to is_delayed
with mips32_instruction_has_delay_slot. Correct MIPS16 handling.
Handle microMIPS code.
(mips_skip_prologue): Update mips_pc_is_mips16 call. Handle
microMIPS code.
(mips32_in_function_epilogue_p): Update mips_fetch_instruction
call.
(micromips_in_function_epilogue_p): New function.
(mips16_in_function_epilogue_p): Update mips_fetch_instruction
call.
(mips_in_function_epilogue_p): Update mips_pc_is_mips16 call.
Handle microMIPS.
(gdb_print_insn_mips): Likewise.
(mips_breakpoint_from_pc): Likewise.
(mips_remote_breakpoint_from_pc): New function.
(mips32_instruction_has_delay_slot): Simplify making use of the
updated mips_fetch_instruction interface.
(micromips_instruction_has_delay_slot): New function.
(mips16_instruction_has_delay_slot): Simplify making use of the
updated mips_fetch_instruction interface.
(mips_adjust_breakpoint_address): Check for the standard MIPS
ISA rather than for MIPS16 ISA. Update for unmake_compact_addr
calls. Handle microMIPS code.
(mips_get_mips16_fn_stub_pc): Update mips_fetch_instruction call.
(mips_skip_trampoline_code): Handle microMIPS code.
(global_mips_compression): New function.
(mips_gdbarch_init): Handle the compressed ISA setting from ELF
file flags. Register the microMIPS remote breakpoint handler
and heuristic frame unwinder.
(show_mips_compression): New function.
(_initialize_mips_tdep): Add the "set mips compression" and
"show mips compression" commands.
gdb/doc/
* gdb.texinfo (MIPS): Document "set mips compression" and "show
mips compression".
(MIPS Breakpoint Kinds): New subsubsection.
2012-05-19 07:46:40 +08:00
|
|
|
set mips compression
|
|
|
|
|
show mips compression
|
|
|
|
|
Select the compressed ISA encoding used in functions that have no symbol
|
|
|
|
|
information available. The encoding can be set to either of:
|
|
|
|
|
mips16
|
|
|
|
|
micromips
|
|
|
|
|
and is updated automatically from ELF file flags if available.
|
|
|
|
|
|
2012-02-24 23:04:58 +08:00
|
|
|
set breakpoint condition-evaluation
|
|
|
|
|
show breakpoint condition-evaluation
|
2012-04-02 15:32:31 +08:00
|
|
|
Control whether breakpoint conditions are evaluated by GDB ("host") or by
|
2012-03-25 21:44:01 +08:00
|
|
|
GDBserver ("target"). Default option "auto" chooses the most efficient
|
|
|
|
|
available mode.
|
2012-02-24 23:04:58 +08:00
|
|
|
This option can improve debugger efficiency depending on the speed of the
|
|
|
|
|
target.
|
|
|
|
|
|
gdb/
auto-load: Implementation.
* NEWS: New descriptions for "info auto-load",
"info auto-load gdb-scripts", "info auto-load python-scripts",
"info auto-load local-gdbinit" and "info auto-load libthread-db".
Deprecate "info auto-load-scripts", "set auto-load-scripts on|off"
and "show auto-load-scripts". New description for "set auto-load",
"show auto-load", "set auto-load gdb-scripts",
"show auto-load gdb-scripts", "set auto-load python-scripts",
"show auto-load python-scripts", "set auto-load local-gdbinit",
"show auto-load local-gdbinit", "set auto-load libthread-db" and
"show auto-load libthread-db".
* auto-load.c: Remove include python/python-internal.h. Add includes
exceptions.h, cli/cli-script.h, gdbcmd.h, cli/cli-decode.h and
cli/cli-setshow.h.
(GDB_AUTO_FILE_NAME, source_gdb_script_for_objfile)
(auto_load_gdb_scripts, show_auto_load_gdb_scripts): New.
(gdbpy_global_auto_load): Rename to ...
(global_auto_load): ... here.
(auto_load_local_gdbinit, auto_load_local_gdbinit_pathname)
(auto_load_local_gdbinit_loaded, show_auto_load_local_gdbinit)
(script_language_gdb, source_gdb_script_for_objfile): New.
(struct loaded_script): New field language.
(hash_loaded_script_entry, eq_loaded_script_entry): Calculate also
LANGUAGE.
(maybe_add_script): Add parameter language. Drop redundant
entry.full_path initialization. Initialize entry.language and
(*slot)->language.
(auto_load_objfile_script): Change parameter suffix to language.
Remove the call of maybe_add_script.
Call language->source_script_for_objfile.
(load_auto_scripts_for_objfile, struct collect_matching_scripts_data):
New.
(collect_matching_scripts): Adjust it for
struct collect_matching_scripts_data.
(auto_load_info_scripts_pattern_nl): New variable.
(info_auto_load_scripts): Rename to ...
(auto_load_info_scripts): ... here, add parameter language. Adjust it
for struct collect_matching_scripts_data.
(info_auto_load_gdb_scripts, info_auto_load_local_gdbinit)
(set_auto_load_cmd, auto_load_set_cmdlist_get, show_auto_load_cmd)
(auto_load_show_cmdlist_get, info_auto_load_cmd)
(auto_load_info_cmdlist_get): New.
(_initialize_auto_load): Move add_info of "auto-load-scripts" to
python/py-auto-load.c. New installment for "set auto-load gdb-scripts",
"info auto-load gdb-scripts", "set auto-load local-gdbinit" and
"info auto-load local-gdbinit".
* auto-load.h (struct script_language): New.
(gdbpy_global_auto_load): Rename to ...
(global_auto_load): ... here.
(auto_load_local_gdbinit, auto_load_local_gdbinit_pathname)
(auto_load_local_gdbinit_loaded): New declarations.
(maybe_add_script): New parameter language.
(auto_load_objfile_script): Change parameter suffix to language.
(load_auto_scripts_for_objfile, auto_load_info_scripts_pattern_nl)
(auto_load_info_scripts, auto_load_set_cmdlist_get)
(auto_load_show_cmdlist_get, auto_load_info_cmdlist_get): New
declarations.
* linux-thread-db.c: Include auto-load.h and ctype.h.
(auto_load_thread_db, show_auto_load_thread_db): New.
(struct thread_db_info): New field filename.
(delete_thread_db_info): Call xfree for FILENAME.
(try_thread_db_load): Initialize FILENAME.
(try_thread_db_load_from_pdir, try_thread_db_load_from_dir): Return
if !AUTO_LOAD_THREAD_DB.
(info_auto_load_libthread_db_compare, info_auto_load_libthread_db): New.
(_initialize_thread_db): Install auto_load_thread_db
as "set auto-load libthread-db" and install info_auto_load_libthread_db
as "info auto-load libthread-db".
* main.c (captured_main): Rename gdbpy_global_auto_load to
global_auto_load. Initialize AUTO_LOAD_LOCAL_GDBINIT_PATHNAME and
AUTO_LOAD_LOCAL_GDBINIT_LOADED.
(print_gdb_help): Extend the help for 'local init file'.
* python/py-auto-load.c: Remove a comment about gdb scripts extension.
(GDBPY_AUTO_SECTION_NAME): Extend the comment it is Python specific.
(auto_load_scripts): Rename to ...
(auto_load_python_scripts): ... here, update the comment.
(gdbpy_load_auto_script_for_objfile): New declaration.
(show_auto_load_python_scripts, script_language_python)
(gdbpy_load_auto_script_for_objfile): New.
(source_section_scripts): Refactor the code.
(load_auto_scripts_for_objfile): Rename to ...
(gdbpy_load_auto_scripts_for_objfile): ... here, update the
auto_load_objfile_script caller, drop GDBPY_GLOBAL_AUTO_LOAD checking.
(info_auto_load_python_scripts): New.
(gdbpy_initialize_auto_load): New variables cmd and cmd_name.
Rename "set auto-load-scripts" to "set auto-load python-scripts".
Register "set auto-load-scripts" as its deprecated alias. Register
"info auto-load python-scripts". Register "info auto-load-scripts" as
its deprecated alias.
(load_auto_scripts_for_objfile): Rename to ...
(gdbpy_load_auto_scripts_for_objfile): ... here.
* python/python.h (load_auto_scripts_for_objfile): Rename to ...
(gdbpy_load_auto_scripts_for_objfile): ... here.
gdb/doc/
auto-load: Implementation.
* gdb.texinfo (Mode Options): New anchor for -nx.
(Startup): New anchors for Option -init-eval-command,
Home Directory Init File
and Init File in the Current Directory during Startup.
Mention set auto-load local-gdbinit with a reference.
Change the sample code to "set auto-load python-scripts".
(Threads): New anchor set libthread-db-search-path.
Provide references to libthread_db.so.1 file.
(Controlling GDB): New menu item for Auto-loading.
(Auto-loading, Init File in the Current Directory)
(libthread_db.so.1 file, objfile-gdb.gdb file): New nodes.
(Python): Rename the menu item Auto-loading to Python Auto-loading.
(Writing a Pretty-Printer, Objfiles In Python): Update the renamed
reference.
(Auto-loading): Rename to ...
(Python Auto-loading): ... here. Change "set auto-load-scripts" to
"set auto-load python-scripts", new anchor for it. Change
"show auto-load-scripts" to "show auto-load python-scripts", new anchor
for it. Change "info auto-load-scripts"
to "info auto-load python-scripts", new anchor for it. Change "scripts"
to "Python scripts".
gdb/testsuite/
auto-load: Implementation.
* gdb.base/help.exp (test set height): Increase the height.
* gdb.python/py-objfile-script.exp (info auto-load-scripts): Change
to ...
(info auto-load python-scripts): ... here.
* gdb.python/py-section-script.exp (info auto-load-scripts *): Change
to ...
(info auto-load python-scripts *): ... here.
2012-04-17 23:51:48 +08:00
|
|
|
set auto-load off
|
|
|
|
|
Disable auto-loading globally.
|
|
|
|
|
|
|
|
|
|
show auto-load
|
|
|
|
|
Show auto-loading setting of all kinds of auto-loaded files.
|
|
|
|
|
|
|
|
|
|
set auto-load gdb-scripts on|off
|
|
|
|
|
show auto-load gdb-scripts
|
|
|
|
|
Control auto-loading of GDB canned sequences of commands files.
|
|
|
|
|
|
|
|
|
|
set auto-load python-scripts on|off
|
|
|
|
|
show auto-load python-scripts
|
|
|
|
|
Control auto-loading of Python script files.
|
|
|
|
|
|
|
|
|
|
set auto-load local-gdbinit on|off
|
|
|
|
|
show auto-load local-gdbinit
|
|
|
|
|
Control loading of init file (.gdbinit) from current directory.
|
|
|
|
|
|
|
|
|
|
set auto-load libthread-db on|off
|
|
|
|
|
show auto-load libthread-db
|
|
|
|
|
Control auto-loading of inferior specific thread debugging shared library.
|
|
|
|
|
|
2012-05-12 02:20:26 +08:00
|
|
|
set auto-load scripts-directory <dir1>[:<dir2>...]
|
2012-05-15 12:12:17 +08:00
|
|
|
show auto-load scripts-directory
|
2012-05-12 02:20:26 +08:00
|
|
|
Set a list of directories from which to load auto-loaded scripts.
|
|
|
|
|
Automatically loaded Python scripts and GDB scripts are located in one
|
|
|
|
|
of the directories listed by this option.
|
|
|
|
|
The delimiter (':' above) may differ according to the host platform.
|
|
|
|
|
|
2012-04-17 23:54:35 +08:00
|
|
|
set auto-load safe-path <dir1>[:<dir2>...]
|
|
|
|
|
show auto-load safe-path
|
|
|
|
|
Set a list of directories from which it is safe to auto-load files.
|
|
|
|
|
The delimiter (':' above) may differ according to the host platform.
|
|
|
|
|
|
2012-04-17 23:56:21 +08:00
|
|
|
set debug auto-load on|off
|
|
|
|
|
show debug auto-load
|
|
|
|
|
Control display of debugging info for auto-loading the files above.
|
|
|
|
|
|
2012-07-02 23:29:39 +08:00
|
|
|
set dprintf-style gdb|call|agent
|
2012-05-14 23:38:41 +08:00
|
|
|
show dprintf-style
|
2012-07-02 23:29:39 +08:00
|
|
|
Control the way in which a dynamic printf is performed; "gdb"
|
|
|
|
|
requests a GDB printf command, while "call" causes dprintf to call a
|
|
|
|
|
function in the inferior. "agent" requests that the target agent
|
|
|
|
|
(such as GDBserver) do the printing.
|
2012-05-14 23:38:41 +08:00
|
|
|
|
|
|
|
|
set dprintf-function <expr>
|
|
|
|
|
show dprintf-function
|
|
|
|
|
set dprintf-channel <expr>
|
|
|
|
|
show dprintf-channel
|
|
|
|
|
Set the function and optional first argument to the call when using
|
|
|
|
|
the "call" style of dynamic printf.
|
|
|
|
|
|
2012-07-02 23:29:39 +08:00
|
|
|
set disconnected-dprintf on|off
|
|
|
|
|
show disconnected-dprintf
|
|
|
|
|
Control whether agent-style dynamic printfs continue to be in effect
|
|
|
|
|
after GDB disconnects.
|
|
|
|
|
|
2012-05-12 02:13:26 +08:00
|
|
|
* New configure options
|
|
|
|
|
|
2012-05-12 02:20:26 +08:00
|
|
|
--with-auto-load-dir
|
|
|
|
|
Configure default value for the 'set auto-load scripts-directory'
|
2012-05-21 04:35:19 +08:00
|
|
|
setting above. It defaults to '$debugdir:$datadir/auto-load',
|
|
|
|
|
$debugdir representing global debugging info directories (available
|
|
|
|
|
via 'show debug-file-directory') and $datadir representing GDB's data
|
|
|
|
|
directory (available via 'show data-directory').
|
2012-05-12 02:20:26 +08:00
|
|
|
|
2012-05-12 02:13:26 +08:00
|
|
|
--with-auto-load-safe-path
|
|
|
|
|
Configure default value for the 'set auto-load safe-path' setting
|
2012-05-12 02:20:26 +08:00
|
|
|
above. It defaults to the --with-auto-load-dir setting.
|
2012-05-12 02:13:26 +08:00
|
|
|
|
|
|
|
|
--without-auto-load-safe-path
|
|
|
|
|
Set 'set auto-load safe-path' to '/', effectively disabling this
|
|
|
|
|
security feature.
|
|
|
|
|
|
2012-02-24 23:04:58 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
2012-03-08 03:17:36 +08:00
|
|
|
z0/z1 conditional breakpoints extension
|
|
|
|
|
|
2012-02-24 23:04:58 +08:00
|
|
|
The z0/z1 breakpoint insertion packets have been extended to carry
|
|
|
|
|
a list of conditional expressions over to the remote stub depending on the
|
|
|
|
|
condition evaluation mode. The use of this extension can be controlled
|
|
|
|
|
via the "set remote conditional-breakpoints-packet" command.
|
|
|
|
|
|
2012-03-08 03:25:39 +08:00
|
|
|
QProgramSignals:
|
|
|
|
|
|
|
|
|
|
Specify the signals which the remote stub may pass to the debugged
|
|
|
|
|
program without GDB involvement.
|
|
|
|
|
|
2012-03-20 02:19:26 +08:00
|
|
|
* New command line options
|
|
|
|
|
|
|
|
|
|
--init-command=FILE, -ix Like --command, -x but execute it
|
|
|
|
|
before loading inferior.
|
|
|
|
|
--init-eval-command=COMMAND, -iex Like --eval-command=COMMAND, -ex but
|
|
|
|
|
execute it before loading inferior.
|
|
|
|
|
|
2011-12-13 21:36:38 +08:00
|
|
|
*** Changes in GDB 7.4
|
|
|
|
|
|
the "ambiguous linespec" series
gdb
2011-12-06 Joel Brobecker <brobecker@acacore.com>
* language.h (struct language_defn): Add new component
la_symbol_name_compare.
* symfile.h (struct quick_symbol_functions): Update the profile
of parameter "name_matcher" for the expand_symtabs_matching
method. Update the documentation accordingly.
* ada-lang.h (ada_name_for_lookup): Add declaration.
* ada-lang.c (ada_name_for_lookup): New function, extracted out
from ada_iterate_over_symbols.
(ada_iterate_over_symbols): Do not encode symbol name anymore.
(ada_expand_partial_symbol_name): Adjust profile.
(ada_language_defn): Add value for la_symbol_name_compare field.
* linespec.c: #include "ada-lang.h".
(iterate_name_matcher): Add language parameter. Replace call
to strcmp_iw by call to language->la_symbol_name_compare.
(decode_variable): Encode COPY if current language is Ada.
* dwarf2read.c (dw2_expand_symtabs_matching): Adjust profile
of name_matcher parameter. Adjust call to name_matcher.
* psymtab.c (expand_symtabs_matching_via_partial): Likewise.
(expand_partial_symbol_names): Update profile of parameter "fun".
* psymtab.h (expand_partial_symbol_names): Update profile of
parameter "fun".
* symtab.c (demangle_for_lookup): Update function documentation.
(search_symbols_name_matches): Add language parameter.
(expand_partial_symbol_name): Likewise.
* c-lang.c (c_language_defn, cplus_language_defn)
(asm_language_defn, minimal_language_defn): Add value for
la_symbol_name_compare field.
* d-lang.c (d_language_defn): Likewise.
* f-lang.c (f_language_defn): Ditto.
* jv-lang.c (java_language_defn): Ditto.
* m2-lang.c (m2_language_defn): Ditto.
* objc-lang.c (objc_language_defn): Ditto.
* opencl-lang.c (opencl_language_defn): Ditto.
* p-lang.c (pascal_language_defn): Ditto.
* language.c (unknown_language_defn, auto_language_defn)
(local_language_defn): Ditto.
2011-12-06 Tom Tromey <tromey@redhat.com>
* linespec.c (iterate_over_all_matching_symtabs): Use
LA_ITERATE_OVER_SYMBOLS.
(lookup_prefix_sym, add_matching_symbols_to_info): Likewise.
(find_function_symbols, decode_variable): Remove Ada special
case.
* language.h (struct language_defn) <la_iterate_over_symbols>: New
field.
(LA_ITERATE_OVER_SYMBOLS): New macro.
* language.c (unknown_language_defn, auto_language_defn)
(local_language_defn): Update.
* c-lang.c (c_language_defn, cplus_language_defn)
(asm_language_defn, minimal_language_defn): Update.
* d-lang.c (d_language_defn): Update.
* f-lang.c (f_language_defn): Update.
* jv-lang.c (java_language_defn): Update.
* m2-lang.c (m2_language_defn): Update.
* objc-lang.c (objc_language_defn): Update.
* opencl-lang.c (opencl_language_defn): Update.
* p-lang.c (pascal_language_defn): Update.
* ada-lang.c (ada_iterate_over_symbols): New function.
(ada_language_defn): Update.
2011-12-06 Tom Tromey <tromey@redhat.com>
Joel Brobecker <brobecker@acacore.com>
PR breakpoints/13105, PR objc/8341, PR objc/8343, PR objc/8366,
PR objc/8535, PR breakpoints/11657, PR breakpoints/11970,
PR breakpoints/12023, PR breakpoints/12334, PR breakpoints/12856,
PR shlibs/8929, PR shlibs/7393:
* python/py-type.c (compare_maybe_null_strings): Rename from
compare_strings.
(check_types_equal): Update.
* utils.c (compare_strings): New function.
* tui/tui-winsource.c (tui_update_breakpoint_info): Update for
location changes.
* tracepoint.c (scope_info): Update.
(trace_find_line_command): Use DECODE_LINE_FUNFIRSTLINE.
* symtab.h (iterate_over_minimal_symbols)
(iterate_over_some_symtabs, iterate_over_symtabs)
(find_pcs_for_symtab_line, iterate_over_symbols)
(demangle_for_lookup): Declare.
(expand_line_sal): Remove.
* symtab.c (iterate_over_some_symtabs, iterate_over_symtabs)
(lookup_symtab_callback): New functions.
(lookup_symtab): Rewrite.
(demangle_for_lookup): New function, extract from
lookup_symbol_in_language.
(lookup_symbol_in_language): Use it.
(iterate_over_symbols): New function.
(find_line_symtab): Update.
(find_pcs_for_symtab_line): New functions.
(find_line_common): Add 'start' argument.
(decode_line_spec): Update. Change argument to 'flags', change
interpretation.
(append_expanded_sal): Remove.
(append_exact_match_to_sals): Remove.
(expand_line_sal): Remove.
* symfile.h (struct quick_symbol_functions) <lookup_symtab>:
Remove.
<map_symtabs_matching_filename>: New field.
* stack.c (func_command): Only look in the current program space.
Use DECODE_LINE_FUNFIRSTLINE.
* source.c (line_info): Set pspace on sal. Check program space in
the loop. Use DECODE_LINE_LIST_MODE.
(select_source_symtab): Use DECODE_LINE_FUNFIRSTLINE.
* solib-target.c: Remove DEF_VEC_I(CORE_ADDR).
* python/python.c (gdbpy_decode_line): Update.
* psymtab.c (partial_map_expand_apply): New function.
(partial_map_symtabs_matching_filename): Rename from
lookup_partial_symbol. Update arguments.
(lookup_symtab_via_partial_symtab): Remove.
(psym_functions): Update.
* objc-lang.h (parse_selector, parse_method): Don't declare.
(find_imps): Update.
* objc-lang.c (parse_selector, parse_method): Now static.
(find_methods): Change arguments. Fill in a vector of symbol
names.
(uniquify_strings): New function.
(find_imps): Change arguments.
* minsyms.c (iterate_over_minimal_symbols): New function.
* linespec.h (enum decode_line_flags): New.
(struct linespec_sals): New.
(struct linespec_result) <canonical>: Remove.
<pre_expanded, addr_string, sals>: New fields.
(destroy_linespec_result, make_cleanup_destroy_linespec_result)
(decode_line_full): Declare.
(decode_line_1): Update.
* linespec.c (struct address_entry, struct linespec_state, struct
collect_info): New types.
(add_sal_to_sals_basic, add_sal_to_sals, hash_address_entry)
(eq_address_entry, maybe_add_address): New functions.
(total_number_of_methods): Remove.
(iterate_name_matcher, iterate_over_all_matching_symtabs): New
functions.
(find_methods): Change arguments. Don't canonicalize input.
Simplify logic.
(add_matching_methods, add_constructors)
(build_canonical_line_spec): Remove.
(filter_results, convert_results_to_lsals): New functions.
(decode_line_2): Change arguments. Rewrite for new data
structures.
(decode_line_internal): Rename from decode_line_1. Change
arguments. Add cleanups. Update for new data structures.
(linespec_state_constructor, linespec_state_destructor)
(decode_line_full, decode_line_1): New functions.
(decode_indirect): Change arguments. Update.
(locate_first_half): Use skip_spaces.
(decode_objc): Change arguments. Update for new data structures.
Simplify logic.
(decode_compound): Change arguments. Add cleanups. Remove
fallback code, replace with error.
(struct decode_compound_collector): New type.
(collect_one_symbol): New function.
(lookup_prefix_sym): Change arguments. Update.
(compare_symbol_name, add_all_symbol_names_from_pspace)
(find_superclass_methods ): New functions.
(find_method): Rewrite.
(struct symtab_collector): New type.
(add_symtabs_to_list, collect_symtabs_from_filename): New
functions.
(symtabs_from_filename): Change API. Rename from
symtab_from_filename.
(collect_function_symbols): New function.
(find_function_symbols): Change API. Rename from
find_function_symbol. Rewrite.
(decode_all_digits): Change arguments. Rewrite.
(decode_dollar): Change arguments. Use decode_variable.
(decode_label): Change arguments. Rewrite.
(collect_symbols): New function.
(minsym_found): Change arguments. Rewrite.
(check_minsym, search_minsyms_for_name)
(add_matching_symbols_to_info): New function.
(decode_variable): Change arguments. Iterate over all symbols.
(symbol_found): Remove.
(symbol_to_sal): New function.
(init_linespec_result, destroy_linespec_result)
(cleanup_linespec_result, make_cleanup_destroy_linespec_result):
New functions.
(decode_digits_list_mode, decode_digits_ordinary): New functions.
* dwarf2read.c (dw2_map_expand_apply): New function.
(dw2_map_symtabs_matching_filename): Rename from
dw2_lookup_symtab. Change arguments.
(dwarf2_gdb_index_functions): Update.
* dwarf2loc.c: Remove DEF_VEC_I(CORE_ADDR).
* defs.h (compare_strings): Declare.
* cli/cli-cmds.c (compare_strings): Move to utils.c.
(edit_command, list_command): Use DECODE_LINE_LIST_MODE. Call
filter_sals.
(compare_symtabs, filter_sals): New functions.
* breakpoint.h (struct bp_location) <line_number, source_file>:
New fields.
(struct breakpoint) <line_number, source_file>: Remove.
<filter>: New field.
* breakpoint.c (print_breakpoint_location, init_raw_breakpoint)
(momentary_breakpoint_from_master, add_location_to_breakpoint):
Update for changes to locations.
(init_breakpoint_sal): Add 'filter' argument. Set 'filter' on
breakpoint.
(create_breakpoint_sal): Add 'filter' argument.
(remove_sal, expand_line_sal_maybe): Remove.
(create_breakpoints_sal): Remove 'sals' argument. Handle
pre-expanded sals and the filter.
(parse_breakpoint_sals): Use decode_line_full.
(check_fast_tracepoint_sals): Use get_sal_arch.
(create_breakpoint): Create a linespec_sals. Update.
(break_range_command): Use decode_line_full. Update.
(until_break_command): Update.
(clear_command): Update match conditions for linespec.c changes.
Use DECODE_LINE_LIST_MODE.
(say_where): Update for changes to locations.
(bp_location_dtor): Free 'source_file'.
(base_breakpoint_dtor): Free 'filter'. Don't free 'source_file'.
(update_static_tracepoint): Update for changes to locations.
(update_breakpoint_locations): Disable ranged breakpoint if too
many locations match. Update.
(addr_string_to_sals): Use decode_line_full. Resolve all sal
PCs.
(breakpoint_re_set_default): Don't call expand_line_sal_maybe.
(decode_line_spec_1): Update. Change argument name to 'flags',
change interpretation.
* block.h (block_containing_function): Declare.
* block.c (block_containing_function): New function.
* skip.c (skip_function_command): Update.
(skip_re_set): Update.
* infcmd.c (jump_command): Use DECODE_LINE_FUNFIRSTLINE.
* mi/mi-main.c (mi_cmd_trace_find): Use DECODE_LINE_FUNFIRSTLINE.
* NEWS: Add entry.
2011-12-06 Tom Tromey <tromey@redhat.com>
* elfread.c (elf_gnu_ifunc_resolver_return_stop): Allow
breakpoint's pspace to be NULL.
* breakpoint.h (struct breakpoint) <pspace>: Update comment.
* breakpoint.c (init_raw_breakpoint): Conditionally set
breakpoint's pspace.
(init_breakpoint_sal): Don't set breakpoint's pspace.
(prepare_re_set_context): Conditionally switch program space.
(addr_string_to_sals): Check executing_startup on location's
program space.
2011-12-06 Tom Tromey <tromey@redhat.com>
* breakpoint.h (enum enable_state) <bp_startup_disabled>: Remove.
* breakpoint.c (should_be_inserted): Explicitly check if program
space is executing startup.
(describe_other_breakpoints): Update.
(disable_breakpoints_before_startup): Change executing_startup
earlier. Remove loop.
(enable_breakpoints_after_startup): Likewise.
(init_breakpoint_sal): Don't use bp_startup_disabled.
(create_breakpoint): Don't use bp_startup_disabled.
(update_global_location_list): Use should_be_inserted.
(bkpt_re_set): Update.
gdb/testsuite
2011-12-06 Joel Brobecker <brobecker@acacore.com>
* gdb.ada/fullname_bp.exp: Add tests for other valid linespecs
involving a fully qualified function name.
2011-12-06 Tom Tromey <tromey@redhat.com>
* gdb.ada/homonym.exp: Add three breakpoint tests.
2011-12-06 Tom Tromey <tromey@redhat.com>
* gdb.base/solib-weak.exp (do_test): Remove kfail.
* gdb.trace/tracecmd.exp: Disable pending breakpoints earlier.
* gdb.objc/objcdecode.exp: Update for output changes.
* gdb.linespec/linespec.exp: New file.
* gdb.linespec/lspec.cc: New file.
* gdb.linespec/lspec.h: New file.
* gdb.linespec/body.h: New file.
* gdb.linespec/base/two/thefile.cc: New file.
* gdb.linespec/base/one/thefile.cc: New file.
* gdb.linespec/Makefile.in: New file.
* gdb.cp/templates.exp (test_template_breakpoints): Update for
output changes.
* gdb.cp/re-set-overloaded.exp: Remove kfail.
* gdb.cp/ovldbreak.exp: Update for output changes. "all" test now
makes one breakpoint.
* gdb.cp/method2.exp (test_break): Update for output changes.
* gdb.cp/mb-templates.exp: Update for output changes.
* gdb.cp/mb-inline.exp: Update for output changes.
* gdb.cp/mb-ctor.exp: Update for output changes.
* gdb.cp/ovsrch.exp: Use fully-qualified names.
* gdb.base/solib-symbol.exp: Run to main later. Breakpoint now
has multiple matches.
* gdb.base/sepdebug.exp: Disable pending breakpoints. Update for
error message change.
* gdb.base/list.exp (test_list_filename_and_number): Update for
error message change.
* gdb.base/break.exp: Disable pending breakpoints. Update for
output changes.
* configure.ac: Add gdb.linespec.
* configure: Rebuild.
* Makefile.in (ALL_SUBDIRS): Add gdb.linespec.
gdb/doc
2011-12-06 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Set Breaks): Update for new behavior.
2011-12-07 02:54:43 +08:00
|
|
|
* GDB now handles ambiguous linespecs more consistently; the existing
|
|
|
|
|
FILE:LINE support has been expanded to other types of linespecs. A
|
|
|
|
|
breakpoint will now be set on all matching locations in all
|
|
|
|
|
inferiors, and locations will be added or removed according to
|
|
|
|
|
inferior changes.
|
|
|
|
|
|
2011-10-06 Justin Lebar <justin.lebar@gmail.com>
* Makefile.in: (SFILES): Add skip.c.
(HFILES_NO_SRCDIR): Add skip.h.
(COMMON_OBS): Add skip.o.
* skip.h, skip.c: New.
* breakpoint.h (set_default_breakpoint): Remove.
(get_sal_arch): Declare.
* breakpoint.c: Remove default_breakpoint_valid,
default_breakpoint_address, default_breakpoint_symtab,
default_breakpoint_line, default_breakpoint_pspace variables.
(get_sal_arch): Make public.
(set_default_breakpoint): Remove.
(parse_breakpoint_sals, create_breakpoint, clear_command,
decode_line_spec_1): Remove uses of default_breakpoint variables;
replaced with function calls into stack.c.
* cli/cli-cmds.h: Add cmd_list_element *skiplist.
* cli/cli-cmds.c: Add skiplist.
(init_cmd_lists): Initialize skiplist.
(init_cli_cmds): Fix comment (classes of commands appear in
alphabetical order).
* infrun.c (handle_inferior_event): Add check that we don't step into
a function whose pc is marked for skip.
* stack.c: Declare last_displayed_sal_valid, last_displayed_pspace,
last_displayed_addr, last_displayed_symtab, last_displayed_line
variables.
(set_last_displayed_sal): New static function.
(print_frame_info): Switch call to set_default_breakpoint to call to
set_last_displayed_sal.
(clear_last_displayed_sal, last_displayed_sal_is_valid,
get_last_displayed_pspace, get_last_displayed_addr,
get_last_displayed_symtab, get_last_displayed_line,
get_last_displayed_sal): New public functions.
* stack.h (clear_last_displayed_sal, last_displayed_sal_is_valid,
get_last_displayed_pspace, get_last_displayed_addr,
get_last_displayed_symtab, get_last_displayed_line,
get_last_displayed_sal): Declare.
2011-10-06 Justin Lebar <justin.lebar@gmail.com>
Add tests for skip command.
* testsuite/gdb.base/skip-solib-lib.c: New
* testsuite/gdb.base/skip-solib-main.c: New
* testsuite/gdb.base/skip-solib.exp: New
* testsuite/gdb.base/skip.c: New
* testsuite/gdb.base/skip.exp: New
* testsuite/gdb.base/skip1.c: New
* testsuite/gdb.base/Makefile.in: Adding new files.
2011-11-01 22:51:25 +08:00
|
|
|
* GDB now allows you to skip uninteresting functions and files when
|
|
|
|
|
stepping with the "skip function" and "skip file" commands.
|
|
|
|
|
|
2011-07-27 04:57:54 +08:00
|
|
|
* GDB has two new commands: "set remote hardware-watchpoint-length-limit"
|
|
|
|
|
and "show remote hardware-watchpoint-length-limit". These allows to
|
|
|
|
|
set or show the maximum length limit (in bytes) of a remote
|
|
|
|
|
target hardware watchpoint.
|
|
|
|
|
|
|
|
|
|
This allows e.g. to use "unlimited" hardware watchpoints with the
|
|
|
|
|
gdbserver integrated in Valgrind version >= 3.7.0. Such Valgrind
|
|
|
|
|
watchpoints are slower than real hardware watchpoints but are
|
|
|
|
|
significantly faster than gdb software watchpoints.
|
|
|
|
|
|
2011-07-21 23:58:52 +08:00
|
|
|
* Python scripting
|
|
|
|
|
|
2011-10-17 03:40:37 +08:00
|
|
|
** The register_pretty_printer function in module gdb.printing now takes
|
2011-10-17 03:54:33 +08:00
|
|
|
an optional `replace' argument. If True, the new printer replaces any
|
2011-10-17 03:40:37 +08:00
|
|
|
existing one.
|
|
|
|
|
|
2011-07-21 23:58:52 +08:00
|
|
|
** The "maint set python print-stack on|off" command has been
|
2012-01-15 02:13:27 +08:00
|
|
|
deprecated and will be deleted in GDB 7.5.
|
|
|
|
|
A new command: "set python print-stack none|full|message" has
|
|
|
|
|
replaced it. Additionally, the default for "print-stack" is
|
|
|
|
|
now "message", which just prints the error message without
|
|
|
|
|
the stack trace.
|
2011-07-21 23:58:52 +08:00
|
|
|
|
2011-10-24 19:49:26 +08:00
|
|
|
** A prompt substitution hook (prompt_hook) is now available to the
|
2011-07-21 23:58:52 +08:00
|
|
|
Python API.
|
2011-07-11 21:07:38 +08:00
|
|
|
|
2011-08-17 18:41:22 +08:00
|
|
|
** A new Python module, gdb.prompt has been added to the GDB Python
|
|
|
|
|
modules library. This module provides functionality for
|
2011-10-24 19:49:26 +08:00
|
|
|
escape sequences in prompts (used by set/show
|
2011-08-17 18:41:22 +08:00
|
|
|
extended-prompt). These escape sequences are replaced by their
|
|
|
|
|
corresponding value.
|
|
|
|
|
|
2011-08-09 20:45:40 +08:00
|
|
|
** Python commands and convenience-functions located in
|
|
|
|
|
'data-directory'/python/gdb/command and
|
|
|
|
|
'data-directory'/python/gdb/function are now automatically loaded
|
|
|
|
|
on GDB start-up.
|
|
|
|
|
|
2011-10-20 20:31:30 +08:00
|
|
|
** Blocks now provide four new attributes. global_block and
|
|
|
|
|
static_block will return the global and static blocks
|
|
|
|
|
respectively. is_static and is_global are boolean attributes
|
|
|
|
|
that indicate if the block is one of those two types.
|
|
|
|
|
|
2011-08-13 06:21:57 +08:00
|
|
|
** Symbols now provide the "type" attribute, the type of the symbol.
|
|
|
|
|
|
2011-09-15 20:27:20 +08:00
|
|
|
** The "gdb.breakpoint" function has been deprecated in favor of
|
|
|
|
|
"gdb.breakpoints".
|
|
|
|
|
|
2011-12-24 01:06:16 +08:00
|
|
|
** A new class "gdb.FinishBreakpoint" is provided to catch the return
|
|
|
|
|
of a function. This class is based on the "finish" command
|
|
|
|
|
available in the CLI.
|
|
|
|
|
|
2011-10-04 23:55:39 +08:00
|
|
|
** Type objects for struct and union types now allow access to
|
|
|
|
|
the fields using standard Python dictionary (mapping) methods.
|
|
|
|
|
For example, "some_type['myfield']" now works, as does
|
|
|
|
|
"some_type.items()".
|
|
|
|
|
|
2011-10-07 15:38:30 +08:00
|
|
|
** A new event "gdb.new_objfile" has been added, triggered by loading a
|
|
|
|
|
new object file.
|
|
|
|
|
|
2011-10-28 22:48:38 +08:00
|
|
|
** A new function, "deep_items" has been added to the gdb.types
|
|
|
|
|
module in the GDB Python modules library. This function returns
|
|
|
|
|
an iterator over the fields of a struct or union type. Unlike
|
|
|
|
|
the standard Python "iteritems" method, it will recursively traverse
|
|
|
|
|
any anonymous fields.
|
|
|
|
|
|
2011-12-06 22:27:39 +08:00
|
|
|
* MI changes
|
|
|
|
|
|
|
|
|
|
** "*stopped" events can report several new "reason"s, such as
|
|
|
|
|
"solib-event".
|
|
|
|
|
|
|
|
|
|
** Breakpoint changes are now notified using new async records, like
|
|
|
|
|
"=breakpoint-modified".
|
|
|
|
|
|
|
|
|
|
** New command -ada-task-info.
|
|
|
|
|
|
2011-05-14 06:36:07 +08:00
|
|
|
* libthread-db-search-path now supports two special values: $sdir and $pdir.
|
|
|
|
|
$sdir specifies the default system locations of shared libraries.
|
|
|
|
|
$pdir specifies the directory where the libpthread used by the application
|
|
|
|
|
lives.
|
|
|
|
|
|
|
|
|
|
GDB no longer looks in $sdir and $pdir after it has searched the directories
|
|
|
|
|
mentioned in libthread-db-search-path. If you want to search those
|
|
|
|
|
directories, they must be specified in libthread-db-search-path.
|
|
|
|
|
The default value of libthread-db-search-path on GNU/Linux and Solaris
|
|
|
|
|
systems is now "$sdir:$pdir".
|
|
|
|
|
|
|
|
|
|
$pdir is not supported by gdbserver, it is currently ignored.
|
|
|
|
|
$sdir is supported by gdbserver.
|
|
|
|
|
|
2011-05-10 05:49:57 +08:00
|
|
|
* New configure option --with-iconv-bin.
|
|
|
|
|
When using the internationalization support like the one in the GNU C
|
|
|
|
|
library, GDB will invoke the "iconv" program to get a list of supported
|
|
|
|
|
character sets. If this program lives in a non-standard location, one can
|
|
|
|
|
use this option to specify where to find it.
|
|
|
|
|
|
2011-05-06 Sergio Durigan Junior <sergiodj@linux.vnet.ibm.com>
Thiago Jung Bauermann <bauerman@br.ibm.com>
Implement support for PowerPC BookE masked watchpoints.
gdb/
* NEWS: Mention masked watchpoint support. Create "Changed commands"
section.
* breakpoint.h (struct breakpoint_ops) <works_in_software_mode>: New
method. Initialize to NULL in all existing breakpoint_ops instances.
(struct breakpoint) <hw_wp_mask>: New field.
* breakpoint.c (is_masked_watchpoint): Add prototype.
(update_watchpoint): Don't set b->val for masked watchpoints. Call
breakpoint's breakpoint_ops.works_in_software_mode if available.
(watchpoints_triggered): Handle the case of a hardware masked
watchpoint trigger.
(watchpoint_check): Likewise.
(works_in_software_mode_watchpoint): New function.
(insert_masked_watchpoint, remove_masked_watchpoint)
(resources_needed_masked_watchpoint)
(works_in_software_mode_masked_watchpoint, print_it_masked_watchpoint)
(print_one_detail_masked_watchpoint, print_mention_masked_watchpoint)
(print_recreate_masked_watchpoint, is_masked_watchpoint): New
functions.
(masked_watchpoint_breakpoint_ops): New structure.
(watch_command_1): Check for the existence of the `mask' parameter.
Set b->ops according to the type of hardware watchpoint being created.
* ppc-linux-nat.c (ppc_linux_insert_mask_watchpoint)
(ppc_linux_remove_mask_watchpoint)
(ppc_linux_masked_watch_num_registers): New functions.
(_initialize_ppc_linux_nat): Initialize to_insert_mask_watchpoint,
to_remove_mask_watchpoint and to_masked_watch_num_registers.
* target.c (update_current_target): Mention to_insert_mask_watchpoint,
to_remove_mask_watchpoint, and to_masked_watch_num_registers.
(target_insert_mask_watchpoint, target_remove_mask_watchpoint)
(target_masked_watch_num_registers): New functions.
* target.h (struct target_ops) <to_insert_mask_watchpoint>,
<to_remove_mask_watchpoint>, <to_masked_watch_num_registers>: New
methods.
(target_insert_mask_watchpoint, target_remove_mask_watchpoint)
(target_masked_watch_num_registers): Add prototypes.
gdb/doc/
* gdb.texinfo (Set Watchpoints): Document mask parameter.
(PowerPC Embedded): Mention support of masked watchpoints.
2011-05-07 02:46:33 +08:00
|
|
|
* When natively debugging programs on PowerPC BookE processors running
|
|
|
|
|
a Linux kernel version 2.6.34 or later, GDB supports masked hardware
|
|
|
|
|
watchpoints, which specify a mask in addition to an address to watch.
|
|
|
|
|
The mask specifies that some bits of an address (the bits which are
|
|
|
|
|
reset in the mask) should be ignored when matching the address accessed
|
|
|
|
|
by the inferior against the watchpoint address. See the "PowerPC Embedded"
|
|
|
|
|
section in the user manual for more details.
|
|
|
|
|
|
2011-04-24 16:02:21 +08:00
|
|
|
* The new option --once causes GDBserver to stop listening for connections once
|
|
|
|
|
the first connection is made. The listening port used by GDBserver will
|
|
|
|
|
become available after that.
|
|
|
|
|
|
2011-11-13 01:01:12 +08:00
|
|
|
* New commands "info macros" and "alias" have been added.
|
2011-07-22 01:23:55 +08:00
|
|
|
|
2011-10-10 03:46:05 +08:00
|
|
|
* New function parameters suffix @entry specifies value of function parameter
|
|
|
|
|
at the time the function got called. Entry values are available only since
|
|
|
|
|
gcc version 4.7.
|
|
|
|
|
|
2011-11-15 13:06:35 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
!SHELL COMMAND
|
|
|
|
|
"!" is now an alias of the "shell" command.
|
|
|
|
|
Note that no space is needed between "!" and SHELL COMMAND.
|
|
|
|
|
|
2011-05-06 Sergio Durigan Junior <sergiodj@linux.vnet.ibm.com>
Thiago Jung Bauermann <bauerman@br.ibm.com>
Implement support for PowerPC BookE masked watchpoints.
gdb/
* NEWS: Mention masked watchpoint support. Create "Changed commands"
section.
* breakpoint.h (struct breakpoint_ops) <works_in_software_mode>: New
method. Initialize to NULL in all existing breakpoint_ops instances.
(struct breakpoint) <hw_wp_mask>: New field.
* breakpoint.c (is_masked_watchpoint): Add prototype.
(update_watchpoint): Don't set b->val for masked watchpoints. Call
breakpoint's breakpoint_ops.works_in_software_mode if available.
(watchpoints_triggered): Handle the case of a hardware masked
watchpoint trigger.
(watchpoint_check): Likewise.
(works_in_software_mode_watchpoint): New function.
(insert_masked_watchpoint, remove_masked_watchpoint)
(resources_needed_masked_watchpoint)
(works_in_software_mode_masked_watchpoint, print_it_masked_watchpoint)
(print_one_detail_masked_watchpoint, print_mention_masked_watchpoint)
(print_recreate_masked_watchpoint, is_masked_watchpoint): New
functions.
(masked_watchpoint_breakpoint_ops): New structure.
(watch_command_1): Check for the existence of the `mask' parameter.
Set b->ops according to the type of hardware watchpoint being created.
* ppc-linux-nat.c (ppc_linux_insert_mask_watchpoint)
(ppc_linux_remove_mask_watchpoint)
(ppc_linux_masked_watch_num_registers): New functions.
(_initialize_ppc_linux_nat): Initialize to_insert_mask_watchpoint,
to_remove_mask_watchpoint and to_masked_watch_num_registers.
* target.c (update_current_target): Mention to_insert_mask_watchpoint,
to_remove_mask_watchpoint, and to_masked_watch_num_registers.
(target_insert_mask_watchpoint, target_remove_mask_watchpoint)
(target_masked_watch_num_registers): New functions.
* target.h (struct target_ops) <to_insert_mask_watchpoint>,
<to_remove_mask_watchpoint>, <to_masked_watch_num_registers>: New
methods.
(target_insert_mask_watchpoint, target_remove_mask_watchpoint)
(target_masked_watch_num_registers): Add prototypes.
gdb/doc/
* gdb.texinfo (Set Watchpoints): Document mask parameter.
(PowerPC Embedded): Mention support of masked watchpoints.
2011-05-07 02:46:33 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
|
|
|
|
watch EXPRESSION mask MASK_VALUE
|
|
|
|
|
The watch command now supports the mask argument which allows creation
|
|
|
|
|
of masked watchpoints, if the current architecture supports this feature.
|
|
|
|
|
|
2011-05-14 06:11:47 +08:00
|
|
|
info auto-load-scripts [REGEXP]
|
|
|
|
|
This command was formerly named "maintenance print section-scripts".
|
|
|
|
|
It is now generally useful and is no longer a maintenance-only command.
|
|
|
|
|
|
2011-11-13 01:01:12 +08:00
|
|
|
info macro [-all] [--] MACRO
|
|
|
|
|
The info macro command has new options `-all' and `--'. The first for
|
|
|
|
|
printing all definitions of a macro. The second for explicitly specifying
|
|
|
|
|
the end of arguments and the beginning of the macro name in case the macro
|
|
|
|
|
name starts with a hyphen.
|
|
|
|
|
|
2011-11-03 07:44:21 +08:00
|
|
|
collect[/s] EXPRESSIONS
|
|
|
|
|
The tracepoint collect command now takes an optional modifier "/s"
|
|
|
|
|
that directs it to dereference pointer-to-character types and
|
|
|
|
|
collect the bytes of memory up to a zero byte. The behavior is
|
|
|
|
|
similar to what you see when you use the regular print command on a
|
|
|
|
|
string. An optional integer following the "/s" sets a bound on the
|
|
|
|
|
number of bytes that will be collected.
|
|
|
|
|
|
2011-11-21 07:59:49 +08:00
|
|
|
tstart [NOTES]
|
|
|
|
|
The trace start command now interprets any supplied arguments as a
|
|
|
|
|
note to be recorded with the trace run, with an effect similar to
|
|
|
|
|
setting the variable trace-notes.
|
|
|
|
|
|
|
|
|
|
tstop [NOTES]
|
|
|
|
|
The trace stop command now interprets any arguments as a note to be
|
|
|
|
|
mentioned along with the tstatus report that the trace was stopped
|
|
|
|
|
with a command. The effect is similar to setting the variable
|
|
|
|
|
trace-stop-notes.
|
|
|
|
|
|
2011-05-12 20:09:17 +08:00
|
|
|
* Tracepoints can now be enabled and disabled at any time after a trace
|
|
|
|
|
experiment has been started using the standard "enable" and "disable"
|
|
|
|
|
commands. It is now possible to start a trace experiment with no enabled
|
|
|
|
|
tracepoints; GDB will display a warning, but will allow the experiment to
|
|
|
|
|
begin, assuming that tracepoints will be enabled as needed while the trace
|
|
|
|
|
is running.
|
|
|
|
|
|
2011-11-15 04:07:25 +08:00
|
|
|
* Fast tracepoints on 32-bit x86-architectures can now be placed at
|
|
|
|
|
locations with 4-byte instructions, when they were previously
|
|
|
|
|
limited to locations with instructions of 5 bytes or longer.
|
|
|
|
|
|
2011-10-10 03:46:05 +08:00
|
|
|
* New options
|
|
|
|
|
|
2012-06-27 04:14:03 +08:00
|
|
|
set debug dwarf2-read
|
|
|
|
|
show debug dwarf2-read
|
|
|
|
|
Turns on or off display of debugging messages related to reading
|
|
|
|
|
DWARF debug info. The default is off.
|
|
|
|
|
|
|
|
|
|
set debug symtab-create
|
|
|
|
|
show debug symtab-create
|
|
|
|
|
Turns on or off display of debugging messages related to symbol table
|
|
|
|
|
creation. The default is off.
|
|
|
|
|
|
2011-10-24 19:49:26 +08:00
|
|
|
set extended-prompt
|
|
|
|
|
show extended-prompt
|
|
|
|
|
Set the GDB prompt, and allow escape sequences to be inserted to
|
|
|
|
|
display miscellaneous information (see 'help set extended-prompt'
|
|
|
|
|
for the list of sequences). This prompt (and any information
|
|
|
|
|
accessed through the escape sequences) is updated every time the
|
|
|
|
|
prompt is displayed.
|
|
|
|
|
|
2011-10-10 03:46:05 +08:00
|
|
|
set print entry-values (both|compact|default|if-needed|no|only|preferred)
|
|
|
|
|
show print entry-values
|
|
|
|
|
Set printing of frame argument values at function entry. In some cases
|
|
|
|
|
GDB can determine the value of function argument which was passed by the
|
|
|
|
|
function caller, even if the value was modified inside the called function.
|
|
|
|
|
|
|
|
|
|
set debug entry-values
|
|
|
|
|
show debug entry-values
|
|
|
|
|
Control display of debugging info for determining frame argument values at
|
|
|
|
|
function entry and virtual tail call frames.
|
|
|
|
|
|
2011-11-16 01:40:02 +08:00
|
|
|
set basenames-may-differ
|
|
|
|
|
show basenames-may-differ
|
|
|
|
|
Set whether a source file may have multiple base names.
|
|
|
|
|
(A "base name" is the name of a file with the directory part removed.
|
|
|
|
|
Example: The base name of "/home/user/hello.c" is "hello.c".)
|
|
|
|
|
If set, GDB will canonicalize file names (e.g., expand symlinks)
|
|
|
|
|
before comparing them. Canonicalization is an expensive operation,
|
|
|
|
|
but it allows the same file be known by more than one base name.
|
|
|
|
|
If not set (the default), all source files are assumed to have just
|
|
|
|
|
one base name, and gdb will do file name comparisons more efficiently.
|
|
|
|
|
|
2011-11-21 07:59:49 +08:00
|
|
|
set trace-user
|
|
|
|
|
show trace-user
|
|
|
|
|
set trace-notes
|
|
|
|
|
show trace-notes
|
|
|
|
|
Set a user name and notes for the current and any future trace runs.
|
|
|
|
|
This is useful for long-running and/or disconnected traces, to
|
|
|
|
|
inform others (or yourself) as to who is running the trace, supply
|
|
|
|
|
contact information, or otherwise explain what is going on.
|
|
|
|
|
|
|
|
|
|
set trace-stop-notes
|
|
|
|
|
show trace-stop-notes
|
|
|
|
|
Set a note attached to the trace run, that is displayed when the
|
|
|
|
|
trace has been stopped by a tstop command. This is useful for
|
|
|
|
|
instance as an explanation, if you are stopping a trace run that was
|
|
|
|
|
started by someone else.
|
|
|
|
|
|
2011-05-12 20:09:17 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
QTEnable
|
|
|
|
|
|
|
|
|
|
Dynamically enable a tracepoint in a started trace experiment.
|
|
|
|
|
|
|
|
|
|
QTDisable
|
|
|
|
|
|
|
|
|
|
Dynamically disable a tracepoint in a started trace experiment.
|
|
|
|
|
|
2011-11-21 07:59:49 +08:00
|
|
|
QTNotes
|
|
|
|
|
|
|
|
|
|
Set the user and notes of the trace run.
|
|
|
|
|
|
|
|
|
|
qTP
|
|
|
|
|
|
|
|
|
|
Query the current status of a tracepoint.
|
|
|
|
|
|
2011-11-15 04:07:25 +08:00
|
|
|
qTMinFTPILen
|
|
|
|
|
|
|
|
|
|
Query the minimum length of instruction at which a fast tracepoint may
|
|
|
|
|
be placed.
|
|
|
|
|
|
2011-07-26 Paul Pluzhnikov <ppluzhnikov@google.com>
* NEWS: Mention dcache configuration.
* dcache.c (dcache_set_list, dcache_show_list): New variables.
(dcache_size, dcache_line_size): New variables.
(LINE_SIZE_MASK, XFORM, MASK): Adjust.
(struct dcache_block): Make it expandable.
(struct dcache_struct): New field.
(dcache_invalidate): Discard freelist upon dcache_line_size changes.
(dcache_hit, dcache_alloc, dcache_peek_byte): Adjust.
(dcache_poke_byte, dcache_print_line): Adjust.
(set_dcache_size, set_dcache_line_size): New functions.
(set_dcache_command, show_dcache_command): New functions.
(_initialize_dcache): Add new commands.
doc/ChangeLog:
2011-07-26 Paul Pluzhnikov <ppluzhnikov@google.com>
* gdb.texinfo (Caching Remote Data): Document {set,show} dcache
size and line-size.
2011-07-26 23:24:02 +08:00
|
|
|
* Dcache size (number of lines) and line-size are now runtime-configurable
|
|
|
|
|
via "set dcache line" and "set dcache line-size" commands.
|
|
|
|
|
|
2011-08-15 00:17:09 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Texas Instruments TMS320C6x tic6x-*-*
|
|
|
|
|
|
2011-11-29 11:49:09 +08:00
|
|
|
* New Simulators
|
|
|
|
|
|
|
|
|
|
Renesas RL78 rl78-*-elf
|
|
|
|
|
|
2011-09-05 01:41:40 +08:00
|
|
|
*** Changes in GDB 7.3.1
|
|
|
|
|
|
|
|
|
|
* The build failure for NetBSD and OpenBSD targets have now been fixed.
|
|
|
|
|
|
2011-04-04 00:55:15 +08:00
|
|
|
*** Changes in GDB 7.3
|
2010-07-08 01:52:37 +08:00
|
|
|
|
2011-02-16 05:17:53 +08:00
|
|
|
* GDB has a new command: "thread find [REGEXP]".
|
|
|
|
|
It finds the thread id whose name, target id, or thread extra info
|
|
|
|
|
matches the given regular expression.
|
|
|
|
|
|
2011-02-05 02:45:15 +08:00
|
|
|
* The "catch syscall" command now works on mips*-linux* targets.
|
|
|
|
|
|
2011-01-12 23:02:12 +08:00
|
|
|
* The -data-disassemble MI command now supports modes 2 and 3 for
|
|
|
|
|
dumping the instruction opcodes.
|
|
|
|
|
|
2010-12-08 01:26:06 +08:00
|
|
|
* New command line options
|
|
|
|
|
|
|
|
|
|
-data-directory DIR Specify DIR as the "data-directory".
|
|
|
|
|
This is mostly for testing purposes.
|
|
|
|
|
|
2010-12-16 01:28:00 +08:00
|
|
|
* The "maint set python auto-load on|off" command has been renamed to
|
|
|
|
|
"set auto-load-scripts on|off".
|
|
|
|
|
|
2010-11-06 00:55:40 +08:00
|
|
|
* GDB has a new command: "set directories".
|
|
|
|
|
It is like the "dir" command except that it replaces the
|
|
|
|
|
source path list instead of augmenting it.
|
|
|
|
|
|
2011-01-20 01:21:39 +08:00
|
|
|
* GDB now understands thread names.
|
|
|
|
|
|
|
|
|
|
On GNU/Linux, "info threads" will display the thread name as set by
|
|
|
|
|
prctl or pthread_setname_np.
|
|
|
|
|
|
|
|
|
|
There is also a new command, "thread name", which can be used to
|
|
|
|
|
assign a name internally for GDB to display.
|
|
|
|
|
|
2010-11-05 22:31:30 +08:00
|
|
|
* OpenCL C
|
|
|
|
|
Initial support for the OpenCL C language (http://www.khronos.org/opencl)
|
|
|
|
|
has been integrated into GDB.
|
|
|
|
|
|
2010-08-03 17:38:16 +08:00
|
|
|
* Python scripting
|
|
|
|
|
|
2011-03-22 18:04:23 +08:00
|
|
|
** The function gdb.Write now accepts an optional keyword 'stream'.
|
|
|
|
|
This keyword, when provided, will direct the output to either
|
|
|
|
|
stdout, stderr, or GDB's logging output.
|
|
|
|
|
|
2011-03-16 17:49:44 +08:00
|
|
|
** Parameters can now be be sub-classed in Python, and in particular
|
|
|
|
|
you may implement the get_set_doc and get_show_doc functions.
|
|
|
|
|
This improves how Parameter set/show documentation is processed
|
|
|
|
|
and allows for more dynamic content.
|
|
|
|
|
|
2011-03-17 17:36:17 +08:00
|
|
|
** Symbols, Symbol Table, Symbol Table and Line, Object Files,
|
|
|
|
|
Inferior, Inferior Thread, Blocks, and Block Iterator APIs now
|
|
|
|
|
have an is_valid method.
|
|
|
|
|
|
2011-03-15 05:45:21 +08:00
|
|
|
** Breakpoints can now be sub-classed in Python, and in particular
|
|
|
|
|
you may implement a 'stop' function that is executed each time
|
|
|
|
|
the inferior reaches that breakpoint.
|
|
|
|
|
|
2011-02-23 06:48:12 +08:00
|
|
|
** New function gdb.lookup_global_symbol looks up a global symbol.
|
|
|
|
|
|
2010-08-03 17:38:16 +08:00
|
|
|
** GDB values in Python are now callable if the value represents a
|
|
|
|
|
function. For example, if 'some_value' represents a function that
|
|
|
|
|
takes two integer parameters and returns a value, you can call
|
|
|
|
|
that function like so:
|
|
|
|
|
|
|
|
|
|
result = some_value (10,20)
|
|
|
|
|
|
2010-10-14 04:08:46 +08:00
|
|
|
** Module gdb.types has been added.
|
|
|
|
|
It contains a collection of utilities for working with gdb.Types objects:
|
|
|
|
|
get_basic_type, has_field, make_enum_dict.
|
|
|
|
|
|
New python module gdb.printing, and new commands info pretty-printer,
enable pretty-printer, disable pretty-printer.
* NEWS: Mention them.
* data-directory/Makefile.in (PYTHON_FILES): Add gdb/printing.py,
gdb/command/__init__.py, gdb/command/pretty_printers.py.
* python/lib/gdb/__init__.py: Install pretty-printer commands.
* python/lib/gdb/printing.py: New file.
* python/lib/gdb/command/__init__.py: New file.
* python/lib/gdb/command/pretty_printers.py: New file.
doc/
* gdb.texinfo (Pretty Printing): Expand into three sections,
introduction, example, and commands.
(Python API): Delete section Disabling Pretty-Printers, merge into
Selecting Pretty-Printers.
(Writing a Pretty-Printer): New section. Move the pretty-printer
example here, and reformat to match python coding style. Add a second
example using the gdb.printing module.
(Python modules): Add gdb.printing.
testsuite/
* gdb.python/py-pp-maint.c: New file.
* gdb.python/py-pp-maint.exp: New file.
* gdb.python/py-pp-maint.py: New file.
2010-11-03 06:44:13 +08:00
|
|
|
** Module gdb.printing has been added.
|
|
|
|
|
It contains utilities for writing and registering pretty-printers.
|
|
|
|
|
New classes: PrettyPrinter, SubPrettyPrinter,
|
|
|
|
|
RegexpCollectionPrettyPrinter.
|
|
|
|
|
New function: register_pretty_printer.
|
|
|
|
|
|
|
|
|
|
** New commands "info pretty-printers", "enable pretty-printer" and
|
|
|
|
|
"disable pretty-printer" have been added.
|
|
|
|
|
|
2010-11-06 00:55:40 +08:00
|
|
|
** gdb.parameter("directories") is now available.
|
|
|
|
|
|
2011-01-07 05:10:53 +08:00
|
|
|
** New function gdb.newest_frame returns the newest frame in the
|
|
|
|
|
selected thread.
|
|
|
|
|
|
2011-01-20 01:21:39 +08:00
|
|
|
** The gdb.InferiorThread class has a new "name" attribute. This
|
|
|
|
|
holds the thread's name.
|
|
|
|
|
|
Add Python support for GDB events.
2011-02-04 Sami Wagiaalla <swagiaal@redhat.com>
* gdb.python/py-evthreads.c: New file.
* gdb.python/py-evthreads.exp: New file.
* gdb.python/py-events.py: New file.
* gdb.python/py-events.exp: New file.
* gdb.python/py-events.c: New file.
2011-02-04 Sami Wagiaalla <swagiaal@redhat.com>
Oguz Kayral <oguzkayral@gmail.com>
* python/py-inferior.c (python_on_normal_stop): New function.
(python_on_resume): New function.
(python_inferior_exit): New function.
(gdbpy_initialize_inferior): Add normal_stop, target_resumed, and
inferior_exit observers.
* python/py-evtregistry.c: New file.
* python/py-threadevent.c : New file.
* python/py-event.c: New file.
* python/py-evts.c: New file.
* python/py-continueevent.c: New file.
* python/py-bpevent.c: New file.
* python/py-signalevent.c: New file.
* python/py-exetiedevent.c: New file.
* python/py-breakpoint.c (gdbpy_breakpoint_from_bpstats): New function.
Move struct breakpoint_object from here...
* python/python-internal.h: ... to here.
* python/py-event.h: New file.
* python/py-events.h: New file.
* Makefile.in (SUBDIR_PYTHON_OBS): Add py-breakpointstopevent.o,
py-continueevent.o, py-event.o, py-eventregistry.o, py-events.o,
py-exitedevent.o, py-signalstopevent.o, and py-stopevent.o.
(SUBDIR_PYTHON_SRCS): Add py-breakpointstopevent.c,
py-continueevent.c, py-event.c, py-eventregistry.c, py-events.c,
py-exitedevent.c, py-signalstopevent.c, and py-stopevent.c.
Add build rules for all the above.
2011-02-05 05:54:16 +08:00
|
|
|
** Python Support for Inferior events.
|
|
|
|
|
Python scripts can add observers to be notified of events
|
2011-03-15 01:48:54 +08:00
|
|
|
occurring in the process being debugged.
|
2011-02-05 13:27:23 +08:00
|
|
|
The following events are currently supported:
|
|
|
|
|
- gdb.events.cont Continue event.
|
|
|
|
|
- gdb.events.exited Inferior exited event.
|
|
|
|
|
- gdb.events.stop Signal received, and Breakpoint hit events.
|
|
|
|
|
|
2010-08-18 05:34:12 +08:00
|
|
|
* C++ Improvements:
|
|
|
|
|
|
|
|
|
|
** GDB now puts template parameters in scope when debugging in an
|
|
|
|
|
instantiation. For example, if you have:
|
|
|
|
|
|
|
|
|
|
template<int X> int func (void) { return X; }
|
|
|
|
|
|
|
|
|
|
then if you step into func<5>, "print X" will show "5". This
|
|
|
|
|
feature requires proper debuginfo support from the compiler; it
|
|
|
|
|
was added to GCC 4.5.
|
|
|
|
|
|
2010-12-11 04:33:44 +08:00
|
|
|
** The motion commands "next", "finish", "until", and "advance" now
|
|
|
|
|
work better when exceptions are thrown. In particular, GDB will
|
|
|
|
|
no longer lose control of the inferior; instead, the GDB will
|
|
|
|
|
stop the inferior at the point at which the exception is caught.
|
|
|
|
|
This functionality requires a change in the exception handling
|
|
|
|
|
code that was introduced in GCC 4.5.
|
|
|
|
|
|
2010-12-02 00:49:41 +08:00
|
|
|
* GDB now follows GCC's rules on accessing volatile objects when
|
|
|
|
|
reading or writing target state during expression evaluation.
|
|
|
|
|
One notable difference to prior behavior is that "print x = 0"
|
|
|
|
|
no longer generates a read of x; the value of the assignment is
|
|
|
|
|
now always taken directly from the value being assigned.
|
|
|
|
|
|
2010-07-28 04:44:33 +08:00
|
|
|
* GDB now has some support for using labels in the program's source in
|
|
|
|
|
linespecs. For instance, you can use "advance label" to continue
|
|
|
|
|
execution to a label.
|
|
|
|
|
|
|
|
|
|
* GDB now has support for reading and writing a new .gdb_index
|
|
|
|
|
section. This section holds a fast index of DWARF debugging
|
|
|
|
|
information and can be used to greatly speed up GDB startup and
|
|
|
|
|
operation. See the documentation for `save gdb-index' for details.
|
|
|
|
|
|
2010-08-17 05:15:46 +08:00
|
|
|
* The "watch" command now accepts an optional "-location" argument.
|
2010-08-17 05:19:29 +08:00
|
|
|
When used, this causes GDB to watch the memory referred to by the
|
2010-08-17 05:15:46 +08:00
|
|
|
expression. Such a watchpoint is never deleted due to it going out
|
|
|
|
|
of scope.
|
|
|
|
|
|
2010-08-27 03:47:23 +08:00
|
|
|
* GDB now supports thread debugging of core dumps on GNU/Linux.
|
|
|
|
|
|
|
|
|
|
GDB now activates thread debugging using the libthread_db library
|
|
|
|
|
when debugging GNU/Linux core dumps, similarly to when debugging
|
|
|
|
|
live processes. As a result, when debugging a core dump file, GDB
|
|
|
|
|
is now able to display pthread_t ids of threads. For example, "info
|
|
|
|
|
threads" shows the same output as when debugging the process when it
|
|
|
|
|
was live. In earlier releases, you'd see something like this:
|
|
|
|
|
|
|
|
|
|
(gdb) info threads
|
|
|
|
|
* 1 LWP 6780 main () at main.c:10
|
|
|
|
|
|
|
|
|
|
While now you see this:
|
|
|
|
|
|
|
|
|
|
(gdb) info threads
|
|
|
|
|
* 1 Thread 0x7f0f5712a700 (LWP 6780) main () at main.c:10
|
|
|
|
|
|
|
|
|
|
It is also now possible to inspect TLS variables when debugging core
|
|
|
|
|
dumps.
|
|
|
|
|
|
|
|
|
|
When debugging a core dump generated on a machine other than the one
|
|
|
|
|
used to run GDB, you may need to point GDB at the correct
|
|
|
|
|
libthread_db library with the "set libthread-db-search-path"
|
|
|
|
|
command. See the user manual for more details on this command.
|
|
|
|
|
|
2011-03-31 22:32:49 +08:00
|
|
|
* When natively debugging programs on PowerPC BookE processors running
|
|
|
|
|
a Linux kernel version 2.6.34 or later, GDB supports ranged breakpoints,
|
|
|
|
|
which stop execution of the inferior whenever it executes an instruction
|
|
|
|
|
at any address within the specified range. See the "PowerPC Embedded"
|
|
|
|
|
section in the user manual for more details.
|
|
|
|
|
|
2010-09-02 04:47:02 +08:00
|
|
|
* New features in the GDB remote stub, GDBserver
|
|
|
|
|
|
2010-09-14 04:37:34 +08:00
|
|
|
** GDBserver is now supported on PowerPC LynxOS (versions 4.x and 5.x),
|
|
|
|
|
and i686 LynxOS (version 5.x).
|
2010-09-02 04:47:02 +08:00
|
|
|
|
2010-12-30 00:15:42 +08:00
|
|
|
** GDBserver is now supported on Blackfin Linux.
|
|
|
|
|
|
2011-01-20 04:41:11 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
ia64 HP-UX ia64-*-hpux*
|
|
|
|
|
|
2010-12-30 00:11:49 +08:00
|
|
|
* New targets:
|
|
|
|
|
|
|
|
|
|
Analog Devices, Inc. Blackfin Processor bfin-*
|
|
|
|
|
|
2010-09-29 05:40:23 +08:00
|
|
|
* Ada task switching is now supported on sparc-elf targets when
|
|
|
|
|
debugging a program using the Ravenscar Profile. For more information,
|
|
|
|
|
see the "Tasking Support when using the Ravenscar Profile" section
|
|
|
|
|
in the GDB user manual.
|
|
|
|
|
|
2010-11-03 02:55:54 +08:00
|
|
|
* Guile support was removed.
|
|
|
|
|
|
2010-12-16 21:05:28 +08:00
|
|
|
* New features in the GNU simulator
|
|
|
|
|
|
|
|
|
|
** The --map-info flag lists all known core mappings.
|
|
|
|
|
|
2011-03-30 01:57:21 +08:00
|
|
|
** CFI flashes may be simulated via the "cfi" device.
|
|
|
|
|
|
2010-07-08 23:41:56 +08:00
|
|
|
*** Changes in GDB 7.2
|
2010-02-19 08:35:53 +08:00
|
|
|
|
2010-07-22 18:52:02 +08:00
|
|
|
* Shared library support for remote targets by default
|
|
|
|
|
|
|
|
|
|
When GDB is configured for a generic, non-OS specific target, like
|
|
|
|
|
for example, --target=arm-eabi or one of the many *-*-elf targets,
|
|
|
|
|
GDB now queries remote stubs for loaded shared libraries using the
|
|
|
|
|
`qXfer:libraries:read' packet. Previously, shared library support
|
|
|
|
|
was always disabled for such configurations.
|
|
|
|
|
|
2010-06-26 02:19:31 +08:00
|
|
|
* C++ Improvements:
|
|
|
|
|
|
|
|
|
|
** Argument Dependent Lookup (ADL)
|
|
|
|
|
|
|
|
|
|
In C++ ADL lookup directs function search to the namespaces of its
|
|
|
|
|
arguments even if the namespace has not been imported.
|
|
|
|
|
For example:
|
|
|
|
|
namespace A
|
|
|
|
|
{
|
|
|
|
|
class B { };
|
|
|
|
|
void foo (B) { }
|
|
|
|
|
}
|
|
|
|
|
...
|
|
|
|
|
A::B b
|
|
|
|
|
foo(b)
|
|
|
|
|
Here the compiler will search for `foo' in the namespace of 'b'
|
|
|
|
|
and find A::foo. GDB now supports this. This construct is commonly
|
|
|
|
|
used in the Standard Template Library for operators.
|
|
|
|
|
|
|
|
|
|
** Improved User Defined Operator Support
|
|
|
|
|
|
|
|
|
|
In addition to member operators, GDB now supports lookup of operators
|
|
|
|
|
defined in a namespace and imported with a `using' directive, operators
|
|
|
|
|
defined in the global scope, operators imported implicitly from an
|
|
|
|
|
anonymous namespace, and the ADL operators mentioned in the previous
|
|
|
|
|
entry.
|
|
|
|
|
GDB now also supports proper overload resolution for all the previously
|
|
|
|
|
mentioned flavors of operators.
|
|
|
|
|
|
2010-06-30 00:53:10 +08:00
|
|
|
** static const class members
|
|
|
|
|
|
|
|
|
|
Printing of static const class members that are initialized in the
|
|
|
|
|
class definition has been fixed.
|
|
|
|
|
|
2010-04-16 15:49:37 +08:00
|
|
|
* Windows Thread Information Block access.
|
|
|
|
|
|
|
|
|
|
On Windows targets, GDB now supports displaying the Windows Thread
|
|
|
|
|
Information Block (TIB) structure. This structure is visible either
|
|
|
|
|
by using the new command `info w32 thread-information-block' or, by
|
|
|
|
|
dereferencing the new convenience variable named `$_tlb', a
|
|
|
|
|
thread-specific pointer to the TIB. This feature is also supported
|
|
|
|
|
when remote debugging using GDBserver.
|
|
|
|
|
|
Static tracepoints support, and UST integration.
gdb/gdbserver/
* configure.ac: Handle --with-ust. substitute ustlibs and ustinc.
* mem-break.c (uninsert_all_breakpoints)
(reinsert_all_breakpoints): New.
* mem-break.h (reinsert_all_breakpoints, uninsert_all_breakpoints):
* tracepoint.c (ust_loaded, helper_thread_id, cmd_buf): New.
(gdb_agent_ust_loaded, helper_thread_id)
(gdb_agent_helper_thread_id): New macros.
(struct ipa_sym_addresses): Add addr_ust_loaded,
addr_helper_thread_id, addr_cmd_buf.
(symbol_list): Add ust_loaded, helper_thread_id, cmd_buf.
(in_process_agent_loaded_ust): New.
(write_e_ust_not_loaded): New.
(maybe_write_ipa_ust_not_loaded): New.
(struct collect_static_trace_data_action): New.
(enum tracepoint_type) <static_tracepoint>: New.
(struct tracepoint) <handle>: Mention static tracepoints.
(struct static_tracepoint_ctx): New.
(CMD_BUF_SIZE): New.
(add_tracepoint_action): Handle static tracepoint actions.
(unprobe_marker_at): New.
(clear_installed_tracepoints): Handle static tracepoints.
(cmd_qtdp): Handle static tracepoints.
(probe_marker_at): New.
(cmd_qtstart): Handle static tracepoints.
(response_tracepoint): Handle static tracepoints.
(cmd_qtfstm, cmd_qtsstm, cmd_qtstmat): New.
(handle_tracepoint_query): Handle qTfSTM, qTsSTM and qTSTMat.
(get_context_regcache): Handle static tracepoints.
(do_action_at_tracepoint): Handle static tracepoint actions.
(traceframe_find_block_type): Handle static trace data blocks.
(traceframe_read_sdata): New.
(download_tracepoints): Download static tracepoint actions.
[HAVE_UST] Include ust/ust.h, dlfcn.h, sys/socket.h, and sys/un.h.
(GDB_PROBE_NAME): New.
(ust_ops): New.
(GET_UST_SYM): New.
(USTF): New.
(dlsym_ust): New.
(ust_marker_to_static_tracepoint): New.
(gdb_probe): New.
(collect_ust_data_at_tracepoint): New.
(gdb_ust_probe): New.
(UNIX_PATH_MAX, SOCK_DIR): New.
(gdb_ust_connect_sync_socket): New.
(resume_thread, stop_thread): New.
(run_inferior_command): New.
(init_named_socket): New.
(gdb_ust_socket_init): New.
(cstr_to_hexstr): New.
(next_st): New.
(first_marker, next_marker): New.
(response_ust_marker): New.
(cmd_qtfstm, cmd_qtsstm): New.
(unprobe_marker_at, probe_marker_at): New.
(cmd_qtstmat, gdb_ust_thread): New.
(gdb_ust_init): New.
(initialize_tracepoint_ftlib): Call gdb_ust_init.
* linux-amd64-ipa.c [HAVE_UST]: Include ust/processor.h
(ST_REGENTRY): New.
(x86_64_st_collect_regmap): New.
(X86_64_NUM_ST_COLLECT_GREGS): New.
(AMD64_RIP_REGNUM): New.
(supply_static_tracepoint_registers): New.
* linux-i386-ipa.c [HAVE_UST]: Include ust/processor.h
(ST_REGENTRY): New.
(i386_st_collect_regmap): New.
(i386_NUM_ST_COLLECT_GREGS): New.
(supply_static_tracepoint_registers): New.
* server.c (handle_query): Handle qXfer:statictrace:read.
<qSupported>: Report support for StaticTracepoints, and
qXfer:statictrace:read features.
* server.h (traceframe_read_sdata)
(supply_static_tracepoint_registers): Declare.
* remote-utils.c (convert_int_to_ascii, hexchars, ishex, tohex)
(unpack_varlen_hex): Include in IPA build.
* Makefile.in (ustlibs, ustinc): New.
(IPA_OBJS): Add remote-utils-ipa.o.
($(IPA_LIB)): Link -ldl and -lpthread.
(UST_CFLAGS): New.
(IPAGENT_CFLAGS): Add UST_CFLAGS.
* config.in, configure: Regenerate.
gdb/
* NEWS: Mention new support for static tracepoints.
(New packets): Mention qTfSTM, qTsSTM, qTSTMat and
qXfer:statictrace:read.
(New features in the GDB remote stub, GDBserver): Mention static
tracepoints support using an UST based backend.
(New commands): Mention "info static-tracepoint-markers" and
"strace".
* breakpoint.c (is_marker_spec): New.
(is_tracepoint): Handle static tracepoints.
(validate_commands_for_breakpoint): Static tracepoints can't do
while-stepping.
(static_tracepoints_here): New.
(bpstat_what): Handle static tracepoints.
(print_one_breakpoint_location, allocate_bp_location, mention):
Ditto.
(create_breakpoint_sal): Ditto.
(decode_static_tracepoint_spec): New.
(create_breakpoint): Replace `hardwareflag', and `traceflag' with
`type_wanted'. Adjust. Handle static tracepoint marker
locations.
(break_command_1): Adjust.
(update_static_tracepoint): New.
(update_breakpoint_locations): Handle static tracepoints.
(breakpoint_re_set_one): Handle static tracepoint marker
locations.
(disable_command, enable_command): Handle static tracepoints.
(trace_command, ftrace_command): Adjust.
(strace_command): New.
(create_tracepoint_from_upload): Adjust.
(save_breakpoints): Handle static tracepoints.
(_initialize_breakpoint): Install the "strace" command.
* breakpoint.h (enum bptype): New bp_static_tracepoint type.
(struct breakpoint): New fields static_trace_marker_id and
static_trace_marker_id_idx.
(breakpoints_here_p): Declare.
(create_breakpoint): Adjust.
(static_tracepoints_here): Declare.
* remote.c (struct remote_state) <static_tracepoints>: New field.
(PACKET_qXfer_statictrace_read, PACKET_StaticTracepoints): New.
(remote_static_tracepoint_marker_at): New.
(remote_static_tracepoint_markers_by_strid): New.
(remote_static_tracepoint_feature): New.
(remote_disconnected_tracing_feature): Handle "StaticTracepoints".
(remote_xfer_partial): Handle TARGET_OBJECT_STATIC_TRACE_DATA.
(remote_supports_static_tracepoints): New.
(remote_download_tracepoint): Download static tracepoints.
(init_remote_ops): Install remote_static_tracepoint_marker_at and
remote_static_tracepoint_markers_by_strid.
(_initialize_remote): Install set|show remote static-tracepoints,
and set|show remote read-sdata-object commands.
* target.c (update_current_target): Inherit and default
to_static_tracepoint_marker_at, and
to_static_tracepoint_markers_by_strid.
* target.h (static_tracepoint_marker): Forward declare.
(enum target_object): New object TARGET_OBJECT_STATIC_TRACE_DATA.
(static_tracepoint_marker_p): New typedef.
(DEF_VEC_P(static_tracepoint_marker_p)): New VEC type.
(struct target_ops): New fields to_static_tracepoint_marker_at and
to_static_tracepoint_markers_by_strid.
(target_static_tracepoint_marker_at)
(target_static_tracepoint_markers_by_strid): New.
* tracepoint.c: Include source.h.
(validate_actionline): Handle $_sdata.
(struct collection_list): New field strace_data.
(add_static_trace_data): New.
(clear_collection_list): Clear strace_data.
(stringify_collection_list): Account for a possible static trace
data collection.
(encode_actions_1): Encode an $_sdata collection.
(parse_tracepoint_definition): Handle static tracepoints.
(parse_static_tracepoint_marker_definition): New.
(release_static_tracepoint_marker): New.
(print_one_static_tracepoint_marker): New.
(info_static_tracepoint_markers_command): New.
(sdata_make_value): New.
(_initialize_tracepoint): Create the $_sdata convenience variable.
Add the "info static-tracepoint-markers" command.
Mention $_sdata in the "collect" command's help output.
* tracepoint.h (struct static_tracepoint_marker): New.
(parse_static_tracepoint_marker_definition)
(release_static_tracepoint_marker): Declare.
* mi/mi-cmd-break.c (mi_cmd_break_insert): Adjust.
* python/py-breakpoint.c (bppy_new): Adjust.
doc/
* gdb.texinfo (Convenience Variables): Document $_sdata.
(Commands to Set Tracepoints): Describe static tracepoints. Add
`Listing Static Tracepoint Markers' menu entry. Document
"strace".
(Tracepoint Action Lists): Document collecting $_sdata.
(Listing Static Tracepoint Markers): New subsection.
(Tracepoints support in gdbserver): Mention static tracepoints.
(remote packets, enabling and disabling): Mention
read-sdata-object.
(General Query Packets) <qSupported>: Document qXfer:sdata:read
and StaticTracepoint.
Mention qTfSTM, qTsSTM and qTSTMat as tracepoint packets.
Document qXfer:sdata:read.
(Tracepoint packets): Document qTfSTM, qTsSTM and qTSTMat.
2010-07-01 18:36:12 +08:00
|
|
|
* Static tracepoints
|
|
|
|
|
|
|
|
|
|
Static tracepoints are calls in the user program into a tracing
|
|
|
|
|
library. One such library is a port of the LTTng kernel tracer to
|
|
|
|
|
userspace --- UST (LTTng Userspace Tracer, http://lttng.org/ust).
|
|
|
|
|
When debugging with GDBserver, GDB now supports combining the GDB
|
|
|
|
|
tracepoint machinery with such libraries. For example: the user can
|
|
|
|
|
use GDB to probe a static tracepoint marker (a call from the user
|
|
|
|
|
program into the tracing library) with the new "strace" command (see
|
|
|
|
|
"New commands" below). This creates a "static tracepoint" in the
|
|
|
|
|
breakpoint list, that can be manipulated with the same feature set
|
|
|
|
|
as fast and regular tracepoints. E.g., collect registers, local and
|
|
|
|
|
global variables, collect trace state variables, and define
|
|
|
|
|
tracepoint conditions. In addition, the user can collect extra
|
|
|
|
|
static tracepoint marker specific data, by collecting the new
|
|
|
|
|
$_sdata internal variable. When analyzing the trace buffer, you can
|
|
|
|
|
inspect $_sdata like any other variable available to GDB. For more
|
|
|
|
|
information, see the "Tracepoints" chapter in GDB user manual. New
|
|
|
|
|
remote packets have been defined to support static tracepoints, see
|
|
|
|
|
the "New remote packets" section below.
|
|
|
|
|
|
2010-08-20 07:43:31 +08:00
|
|
|
* Better reconstruction of tracepoints after disconnected tracing
|
|
|
|
|
|
|
|
|
|
GDB will attempt to download the original source form of tracepoint
|
|
|
|
|
definitions when starting a trace run, and then will upload these
|
|
|
|
|
upon reconnection to the target, resulting in a more accurate
|
|
|
|
|
reconstruction of the tracepoints that are in use on the target.
|
|
|
|
|
|
|
|
|
|
* Observer mode
|
|
|
|
|
|
|
|
|
|
You can now exercise direct control over the ways that GDB can
|
|
|
|
|
affect your program. For instance, you can disallow the setting of
|
|
|
|
|
breakpoints, so that the program can run continuously (assuming
|
|
|
|
|
non-stop mode). In addition, the "observer" variable is available
|
|
|
|
|
to switch all of the different controls; in observer mode, GDB
|
|
|
|
|
cannot affect the target's behavior at all, which is useful for
|
|
|
|
|
tasks like diagnosing live systems in the field.
|
|
|
|
|
|
|
|
|
|
* The new convenience variable $_thread holds the number of the
|
|
|
|
|
current thread.
|
|
|
|
|
|
2010-04-16 15:49:37 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
qGetTIBAddr
|
|
|
|
|
|
|
|
|
|
Return the address of the Windows Thread Information Block of a given thread.
|
|
|
|
|
|
2010-05-27 02:19:28 +08:00
|
|
|
qRelocInsn
|
|
|
|
|
|
|
|
|
|
In response to several of the tracepoint packets, the target may now
|
|
|
|
|
also respond with a number of intermediate `qRelocInsn' request
|
|
|
|
|
packets before the final result packet, to have GDB handle
|
|
|
|
|
relocating an instruction to execute at a different address. This
|
|
|
|
|
is particularly useful for stubs that support fast tracepoints. GDB
|
|
|
|
|
reports support for this feature in the qSupported packet.
|
|
|
|
|
|
Static tracepoints support, and UST integration.
gdb/gdbserver/
* configure.ac: Handle --with-ust. substitute ustlibs and ustinc.
* mem-break.c (uninsert_all_breakpoints)
(reinsert_all_breakpoints): New.
* mem-break.h (reinsert_all_breakpoints, uninsert_all_breakpoints):
* tracepoint.c (ust_loaded, helper_thread_id, cmd_buf): New.
(gdb_agent_ust_loaded, helper_thread_id)
(gdb_agent_helper_thread_id): New macros.
(struct ipa_sym_addresses): Add addr_ust_loaded,
addr_helper_thread_id, addr_cmd_buf.
(symbol_list): Add ust_loaded, helper_thread_id, cmd_buf.
(in_process_agent_loaded_ust): New.
(write_e_ust_not_loaded): New.
(maybe_write_ipa_ust_not_loaded): New.
(struct collect_static_trace_data_action): New.
(enum tracepoint_type) <static_tracepoint>: New.
(struct tracepoint) <handle>: Mention static tracepoints.
(struct static_tracepoint_ctx): New.
(CMD_BUF_SIZE): New.
(add_tracepoint_action): Handle static tracepoint actions.
(unprobe_marker_at): New.
(clear_installed_tracepoints): Handle static tracepoints.
(cmd_qtdp): Handle static tracepoints.
(probe_marker_at): New.
(cmd_qtstart): Handle static tracepoints.
(response_tracepoint): Handle static tracepoints.
(cmd_qtfstm, cmd_qtsstm, cmd_qtstmat): New.
(handle_tracepoint_query): Handle qTfSTM, qTsSTM and qTSTMat.
(get_context_regcache): Handle static tracepoints.
(do_action_at_tracepoint): Handle static tracepoint actions.
(traceframe_find_block_type): Handle static trace data blocks.
(traceframe_read_sdata): New.
(download_tracepoints): Download static tracepoint actions.
[HAVE_UST] Include ust/ust.h, dlfcn.h, sys/socket.h, and sys/un.h.
(GDB_PROBE_NAME): New.
(ust_ops): New.
(GET_UST_SYM): New.
(USTF): New.
(dlsym_ust): New.
(ust_marker_to_static_tracepoint): New.
(gdb_probe): New.
(collect_ust_data_at_tracepoint): New.
(gdb_ust_probe): New.
(UNIX_PATH_MAX, SOCK_DIR): New.
(gdb_ust_connect_sync_socket): New.
(resume_thread, stop_thread): New.
(run_inferior_command): New.
(init_named_socket): New.
(gdb_ust_socket_init): New.
(cstr_to_hexstr): New.
(next_st): New.
(first_marker, next_marker): New.
(response_ust_marker): New.
(cmd_qtfstm, cmd_qtsstm): New.
(unprobe_marker_at, probe_marker_at): New.
(cmd_qtstmat, gdb_ust_thread): New.
(gdb_ust_init): New.
(initialize_tracepoint_ftlib): Call gdb_ust_init.
* linux-amd64-ipa.c [HAVE_UST]: Include ust/processor.h
(ST_REGENTRY): New.
(x86_64_st_collect_regmap): New.
(X86_64_NUM_ST_COLLECT_GREGS): New.
(AMD64_RIP_REGNUM): New.
(supply_static_tracepoint_registers): New.
* linux-i386-ipa.c [HAVE_UST]: Include ust/processor.h
(ST_REGENTRY): New.
(i386_st_collect_regmap): New.
(i386_NUM_ST_COLLECT_GREGS): New.
(supply_static_tracepoint_registers): New.
* server.c (handle_query): Handle qXfer:statictrace:read.
<qSupported>: Report support for StaticTracepoints, and
qXfer:statictrace:read features.
* server.h (traceframe_read_sdata)
(supply_static_tracepoint_registers): Declare.
* remote-utils.c (convert_int_to_ascii, hexchars, ishex, tohex)
(unpack_varlen_hex): Include in IPA build.
* Makefile.in (ustlibs, ustinc): New.
(IPA_OBJS): Add remote-utils-ipa.o.
($(IPA_LIB)): Link -ldl and -lpthread.
(UST_CFLAGS): New.
(IPAGENT_CFLAGS): Add UST_CFLAGS.
* config.in, configure: Regenerate.
gdb/
* NEWS: Mention new support for static tracepoints.
(New packets): Mention qTfSTM, qTsSTM, qTSTMat and
qXfer:statictrace:read.
(New features in the GDB remote stub, GDBserver): Mention static
tracepoints support using an UST based backend.
(New commands): Mention "info static-tracepoint-markers" and
"strace".
* breakpoint.c (is_marker_spec): New.
(is_tracepoint): Handle static tracepoints.
(validate_commands_for_breakpoint): Static tracepoints can't do
while-stepping.
(static_tracepoints_here): New.
(bpstat_what): Handle static tracepoints.
(print_one_breakpoint_location, allocate_bp_location, mention):
Ditto.
(create_breakpoint_sal): Ditto.
(decode_static_tracepoint_spec): New.
(create_breakpoint): Replace `hardwareflag', and `traceflag' with
`type_wanted'. Adjust. Handle static tracepoint marker
locations.
(break_command_1): Adjust.
(update_static_tracepoint): New.
(update_breakpoint_locations): Handle static tracepoints.
(breakpoint_re_set_one): Handle static tracepoint marker
locations.
(disable_command, enable_command): Handle static tracepoints.
(trace_command, ftrace_command): Adjust.
(strace_command): New.
(create_tracepoint_from_upload): Adjust.
(save_breakpoints): Handle static tracepoints.
(_initialize_breakpoint): Install the "strace" command.
* breakpoint.h (enum bptype): New bp_static_tracepoint type.
(struct breakpoint): New fields static_trace_marker_id and
static_trace_marker_id_idx.
(breakpoints_here_p): Declare.
(create_breakpoint): Adjust.
(static_tracepoints_here): Declare.
* remote.c (struct remote_state) <static_tracepoints>: New field.
(PACKET_qXfer_statictrace_read, PACKET_StaticTracepoints): New.
(remote_static_tracepoint_marker_at): New.
(remote_static_tracepoint_markers_by_strid): New.
(remote_static_tracepoint_feature): New.
(remote_disconnected_tracing_feature): Handle "StaticTracepoints".
(remote_xfer_partial): Handle TARGET_OBJECT_STATIC_TRACE_DATA.
(remote_supports_static_tracepoints): New.
(remote_download_tracepoint): Download static tracepoints.
(init_remote_ops): Install remote_static_tracepoint_marker_at and
remote_static_tracepoint_markers_by_strid.
(_initialize_remote): Install set|show remote static-tracepoints,
and set|show remote read-sdata-object commands.
* target.c (update_current_target): Inherit and default
to_static_tracepoint_marker_at, and
to_static_tracepoint_markers_by_strid.
* target.h (static_tracepoint_marker): Forward declare.
(enum target_object): New object TARGET_OBJECT_STATIC_TRACE_DATA.
(static_tracepoint_marker_p): New typedef.
(DEF_VEC_P(static_tracepoint_marker_p)): New VEC type.
(struct target_ops): New fields to_static_tracepoint_marker_at and
to_static_tracepoint_markers_by_strid.
(target_static_tracepoint_marker_at)
(target_static_tracepoint_markers_by_strid): New.
* tracepoint.c: Include source.h.
(validate_actionline): Handle $_sdata.
(struct collection_list): New field strace_data.
(add_static_trace_data): New.
(clear_collection_list): Clear strace_data.
(stringify_collection_list): Account for a possible static trace
data collection.
(encode_actions_1): Encode an $_sdata collection.
(parse_tracepoint_definition): Handle static tracepoints.
(parse_static_tracepoint_marker_definition): New.
(release_static_tracepoint_marker): New.
(print_one_static_tracepoint_marker): New.
(info_static_tracepoint_markers_command): New.
(sdata_make_value): New.
(_initialize_tracepoint): Create the $_sdata convenience variable.
Add the "info static-tracepoint-markers" command.
Mention $_sdata in the "collect" command's help output.
* tracepoint.h (struct static_tracepoint_marker): New.
(parse_static_tracepoint_marker_definition)
(release_static_tracepoint_marker): Declare.
* mi/mi-cmd-break.c (mi_cmd_break_insert): Adjust.
* python/py-breakpoint.c (bppy_new): Adjust.
doc/
* gdb.texinfo (Convenience Variables): Document $_sdata.
(Commands to Set Tracepoints): Describe static tracepoints. Add
`Listing Static Tracepoint Markers' menu entry. Document
"strace".
(Tracepoint Action Lists): Document collecting $_sdata.
(Listing Static Tracepoint Markers): New subsection.
(Tracepoints support in gdbserver): Mention static tracepoints.
(remote packets, enabling and disabling): Mention
read-sdata-object.
(General Query Packets) <qSupported>: Document qXfer:sdata:read
and StaticTracepoint.
Mention qTfSTM, qTsSTM and qTSTMat as tracepoint packets.
Document qXfer:sdata:read.
(Tracepoint packets): Document qTfSTM, qTsSTM and qTSTMat.
2010-07-01 18:36:12 +08:00
|
|
|
qTfSTM, qTsSTM
|
|
|
|
|
|
|
|
|
|
List static tracepoint markers in the target program.
|
|
|
|
|
|
|
|
|
|
qTSTMat
|
|
|
|
|
|
|
|
|
|
List static tracepoint markers at a given address in the target
|
|
|
|
|
program.
|
|
|
|
|
|
|
|
|
|
qXfer:statictrace:read
|
|
|
|
|
|
|
|
|
|
Read the static trace data collected (by a `collect $_sdata'
|
|
|
|
|
tracepoint action). The remote stub reports support for this packet
|
|
|
|
|
to gdb's qSupported query.
|
|
|
|
|
|
2010-08-20 07:43:31 +08:00
|
|
|
QAllow
|
|
|
|
|
|
|
|
|
|
Send the current settings of GDB's permission flags.
|
|
|
|
|
|
|
|
|
|
QTDPsrc
|
|
|
|
|
|
|
|
|
|
Send part of the source (textual) form of a tracepoint definition,
|
|
|
|
|
which includes location, conditional, and action list.
|
|
|
|
|
|
2010-04-16 01:45:57 +08:00
|
|
|
* The source command now accepts a -s option to force searching for the
|
|
|
|
|
script in the source search path even if the script name specifies
|
|
|
|
|
a directory.
|
|
|
|
|
|
2010-04-09 23:26:54 +08:00
|
|
|
* New features in the GDB remote stub, GDBserver
|
|
|
|
|
|
Static tracepoints support, and UST integration.
gdb/gdbserver/
* configure.ac: Handle --with-ust. substitute ustlibs and ustinc.
* mem-break.c (uninsert_all_breakpoints)
(reinsert_all_breakpoints): New.
* mem-break.h (reinsert_all_breakpoints, uninsert_all_breakpoints):
* tracepoint.c (ust_loaded, helper_thread_id, cmd_buf): New.
(gdb_agent_ust_loaded, helper_thread_id)
(gdb_agent_helper_thread_id): New macros.
(struct ipa_sym_addresses): Add addr_ust_loaded,
addr_helper_thread_id, addr_cmd_buf.
(symbol_list): Add ust_loaded, helper_thread_id, cmd_buf.
(in_process_agent_loaded_ust): New.
(write_e_ust_not_loaded): New.
(maybe_write_ipa_ust_not_loaded): New.
(struct collect_static_trace_data_action): New.
(enum tracepoint_type) <static_tracepoint>: New.
(struct tracepoint) <handle>: Mention static tracepoints.
(struct static_tracepoint_ctx): New.
(CMD_BUF_SIZE): New.
(add_tracepoint_action): Handle static tracepoint actions.
(unprobe_marker_at): New.
(clear_installed_tracepoints): Handle static tracepoints.
(cmd_qtdp): Handle static tracepoints.
(probe_marker_at): New.
(cmd_qtstart): Handle static tracepoints.
(response_tracepoint): Handle static tracepoints.
(cmd_qtfstm, cmd_qtsstm, cmd_qtstmat): New.
(handle_tracepoint_query): Handle qTfSTM, qTsSTM and qTSTMat.
(get_context_regcache): Handle static tracepoints.
(do_action_at_tracepoint): Handle static tracepoint actions.
(traceframe_find_block_type): Handle static trace data blocks.
(traceframe_read_sdata): New.
(download_tracepoints): Download static tracepoint actions.
[HAVE_UST] Include ust/ust.h, dlfcn.h, sys/socket.h, and sys/un.h.
(GDB_PROBE_NAME): New.
(ust_ops): New.
(GET_UST_SYM): New.
(USTF): New.
(dlsym_ust): New.
(ust_marker_to_static_tracepoint): New.
(gdb_probe): New.
(collect_ust_data_at_tracepoint): New.
(gdb_ust_probe): New.
(UNIX_PATH_MAX, SOCK_DIR): New.
(gdb_ust_connect_sync_socket): New.
(resume_thread, stop_thread): New.
(run_inferior_command): New.
(init_named_socket): New.
(gdb_ust_socket_init): New.
(cstr_to_hexstr): New.
(next_st): New.
(first_marker, next_marker): New.
(response_ust_marker): New.
(cmd_qtfstm, cmd_qtsstm): New.
(unprobe_marker_at, probe_marker_at): New.
(cmd_qtstmat, gdb_ust_thread): New.
(gdb_ust_init): New.
(initialize_tracepoint_ftlib): Call gdb_ust_init.
* linux-amd64-ipa.c [HAVE_UST]: Include ust/processor.h
(ST_REGENTRY): New.
(x86_64_st_collect_regmap): New.
(X86_64_NUM_ST_COLLECT_GREGS): New.
(AMD64_RIP_REGNUM): New.
(supply_static_tracepoint_registers): New.
* linux-i386-ipa.c [HAVE_UST]: Include ust/processor.h
(ST_REGENTRY): New.
(i386_st_collect_regmap): New.
(i386_NUM_ST_COLLECT_GREGS): New.
(supply_static_tracepoint_registers): New.
* server.c (handle_query): Handle qXfer:statictrace:read.
<qSupported>: Report support for StaticTracepoints, and
qXfer:statictrace:read features.
* server.h (traceframe_read_sdata)
(supply_static_tracepoint_registers): Declare.
* remote-utils.c (convert_int_to_ascii, hexchars, ishex, tohex)
(unpack_varlen_hex): Include in IPA build.
* Makefile.in (ustlibs, ustinc): New.
(IPA_OBJS): Add remote-utils-ipa.o.
($(IPA_LIB)): Link -ldl and -lpthread.
(UST_CFLAGS): New.
(IPAGENT_CFLAGS): Add UST_CFLAGS.
* config.in, configure: Regenerate.
gdb/
* NEWS: Mention new support for static tracepoints.
(New packets): Mention qTfSTM, qTsSTM, qTSTMat and
qXfer:statictrace:read.
(New features in the GDB remote stub, GDBserver): Mention static
tracepoints support using an UST based backend.
(New commands): Mention "info static-tracepoint-markers" and
"strace".
* breakpoint.c (is_marker_spec): New.
(is_tracepoint): Handle static tracepoints.
(validate_commands_for_breakpoint): Static tracepoints can't do
while-stepping.
(static_tracepoints_here): New.
(bpstat_what): Handle static tracepoints.
(print_one_breakpoint_location, allocate_bp_location, mention):
Ditto.
(create_breakpoint_sal): Ditto.
(decode_static_tracepoint_spec): New.
(create_breakpoint): Replace `hardwareflag', and `traceflag' with
`type_wanted'. Adjust. Handle static tracepoint marker
locations.
(break_command_1): Adjust.
(update_static_tracepoint): New.
(update_breakpoint_locations): Handle static tracepoints.
(breakpoint_re_set_one): Handle static tracepoint marker
locations.
(disable_command, enable_command): Handle static tracepoints.
(trace_command, ftrace_command): Adjust.
(strace_command): New.
(create_tracepoint_from_upload): Adjust.
(save_breakpoints): Handle static tracepoints.
(_initialize_breakpoint): Install the "strace" command.
* breakpoint.h (enum bptype): New bp_static_tracepoint type.
(struct breakpoint): New fields static_trace_marker_id and
static_trace_marker_id_idx.
(breakpoints_here_p): Declare.
(create_breakpoint): Adjust.
(static_tracepoints_here): Declare.
* remote.c (struct remote_state) <static_tracepoints>: New field.
(PACKET_qXfer_statictrace_read, PACKET_StaticTracepoints): New.
(remote_static_tracepoint_marker_at): New.
(remote_static_tracepoint_markers_by_strid): New.
(remote_static_tracepoint_feature): New.
(remote_disconnected_tracing_feature): Handle "StaticTracepoints".
(remote_xfer_partial): Handle TARGET_OBJECT_STATIC_TRACE_DATA.
(remote_supports_static_tracepoints): New.
(remote_download_tracepoint): Download static tracepoints.
(init_remote_ops): Install remote_static_tracepoint_marker_at and
remote_static_tracepoint_markers_by_strid.
(_initialize_remote): Install set|show remote static-tracepoints,
and set|show remote read-sdata-object commands.
* target.c (update_current_target): Inherit and default
to_static_tracepoint_marker_at, and
to_static_tracepoint_markers_by_strid.
* target.h (static_tracepoint_marker): Forward declare.
(enum target_object): New object TARGET_OBJECT_STATIC_TRACE_DATA.
(static_tracepoint_marker_p): New typedef.
(DEF_VEC_P(static_tracepoint_marker_p)): New VEC type.
(struct target_ops): New fields to_static_tracepoint_marker_at and
to_static_tracepoint_markers_by_strid.
(target_static_tracepoint_marker_at)
(target_static_tracepoint_markers_by_strid): New.
* tracepoint.c: Include source.h.
(validate_actionline): Handle $_sdata.
(struct collection_list): New field strace_data.
(add_static_trace_data): New.
(clear_collection_list): Clear strace_data.
(stringify_collection_list): Account for a possible static trace
data collection.
(encode_actions_1): Encode an $_sdata collection.
(parse_tracepoint_definition): Handle static tracepoints.
(parse_static_tracepoint_marker_definition): New.
(release_static_tracepoint_marker): New.
(print_one_static_tracepoint_marker): New.
(info_static_tracepoint_markers_command): New.
(sdata_make_value): New.
(_initialize_tracepoint): Create the $_sdata convenience variable.
Add the "info static-tracepoint-markers" command.
Mention $_sdata in the "collect" command's help output.
* tracepoint.h (struct static_tracepoint_marker): New.
(parse_static_tracepoint_marker_definition)
(release_static_tracepoint_marker): Declare.
* mi/mi-cmd-break.c (mi_cmd_break_insert): Adjust.
* python/py-breakpoint.c (bppy_new): Adjust.
doc/
* gdb.texinfo (Convenience Variables): Document $_sdata.
(Commands to Set Tracepoints): Describe static tracepoints. Add
`Listing Static Tracepoint Markers' menu entry. Document
"strace".
(Tracepoint Action Lists): Document collecting $_sdata.
(Listing Static Tracepoint Markers): New subsection.
(Tracepoints support in gdbserver): Mention static tracepoints.
(remote packets, enabling and disabling): Mention
read-sdata-object.
(General Query Packets) <qSupported>: Document qXfer:sdata:read
and StaticTracepoint.
Mention qTfSTM, qTsSTM and qTSTMat as tracepoint packets.
Document qXfer:sdata:read.
(Tracepoint packets): Document qTfSTM, qTsSTM and qTSTMat.
2010-07-01 18:36:12 +08:00
|
|
|
- GDBserver now support tracepoints (including fast tracepoints, and
|
|
|
|
|
static tracepoints). The feature is currently supported by the
|
|
|
|
|
i386-linux and amd64-linux builds. See the "Tracepoints support
|
|
|
|
|
in gdbserver" section in the manual for more information.
|
|
|
|
|
|
|
|
|
|
GDBserver JIT compiles the tracepoint's conditional agent
|
|
|
|
|
expression bytecode into native code whenever possible for low
|
|
|
|
|
overhead dynamic tracepoints conditionals. For such tracepoints,
|
|
|
|
|
an expression that examines program state is evaluated when the
|
|
|
|
|
tracepoint is reached, in order to determine whether to capture
|
|
|
|
|
trace data. If the condition is simple and false, processing the
|
|
|
|
|
tracepoint finishes very quickly and no data is gathered.
|
|
|
|
|
|
|
|
|
|
GDBserver interfaces with the UST (LTTng Userspace Tracer) library
|
|
|
|
|
for static tracepoints support.
|
2010-04-09 23:26:54 +08:00
|
|
|
|
2010-04-30 15:04:52 +08:00
|
|
|
- GDBserver now supports x86_64 Windows 64-bit debugging.
|
|
|
|
|
|
2010-03-30 23:45:16 +08:00
|
|
|
* GDB now sends xmlRegisters= in qSupported packet to indicate that
|
|
|
|
|
it understands register description.
|
|
|
|
|
|
2010-03-09 03:20:38 +08:00
|
|
|
* The --batch flag now disables pagination and queries.
|
|
|
|
|
|
2010-03-04 04:19:50 +08:00
|
|
|
* X86 general purpose registers
|
|
|
|
|
|
|
|
|
|
GDB now supports reading/writing byte, word and double-word x86
|
|
|
|
|
general purpose registers directly. This means you can use, say,
|
|
|
|
|
$ah or $ax to refer, respectively, to the byte register AH and
|
|
|
|
|
16-bit word register AX that are actually portions of the 32-bit
|
|
|
|
|
register EAX or 64-bit register RAX.
|
|
|
|
|
|
2010-03-25 05:24:09 +08:00
|
|
|
* The `commands' command now accepts a range of breakpoints to modify.
|
2010-04-01 22:11:24 +08:00
|
|
|
A plain `commands' following a command that creates multiple
|
|
|
|
|
breakpoints affects all the breakpoints set by that command. This
|
|
|
|
|
applies to breakpoints set by `rbreak', and also applies when a
|
|
|
|
|
single `break' command creates multiple breakpoints (e.g.,
|
|
|
|
|
breakpoints on overloaded c++ functions).
|
2010-03-25 05:24:09 +08:00
|
|
|
|
2010-04-23 20:08:07 +08:00
|
|
|
* The `rbreak' command now accepts a filename specification as part of
|
|
|
|
|
its argument, limiting the functions selected by the regex to those
|
|
|
|
|
in the specified file.
|
|
|
|
|
|
2010-04-24 21:12:56 +08:00
|
|
|
* Support for remote debugging Windows and SymbianOS shared libraries
|
|
|
|
|
from Unix hosts has been improved. Non Windows GDB builds now can
|
|
|
|
|
understand target reported file names that follow MS-DOS based file
|
|
|
|
|
system semantics, such as file names that include drive letters and
|
|
|
|
|
use the backslash character as directory separator. This makes it
|
|
|
|
|
possible to transparently use the "set sysroot" and "set
|
|
|
|
|
solib-search-path" on Unix hosts to point as host copies of the
|
|
|
|
|
target's shared libraries. See the new command "set
|
|
|
|
|
target-file-system-kind" described below, and the "Commands to
|
|
|
|
|
specify files" section in the user manual for more information.
|
|
|
|
|
|
2010-04-19 08:48:44 +08:00
|
|
|
* New commands
|
|
|
|
|
|
2010-06-24 14:12:15 +08:00
|
|
|
eval template, expressions...
|
|
|
|
|
Convert the values of one or more expressions under the control
|
|
|
|
|
of the string template to a command line, and call it.
|
|
|
|
|
|
2010-04-24 21:12:56 +08:00
|
|
|
set target-file-system-kind unix|dos-based|auto
|
|
|
|
|
show target-file-system-kind
|
|
|
|
|
Set or show the assumed file system kind for target reported file
|
|
|
|
|
names.
|
|
|
|
|
|
2010-04-19 08:48:44 +08:00
|
|
|
save breakpoints <filename>
|
|
|
|
|
Save all current breakpoint definitions to a file suitable for use
|
|
|
|
|
in a later debugging session. To read the saved breakpoint
|
|
|
|
|
definitions, use the `source' command.
|
|
|
|
|
|
|
|
|
|
`save tracepoints' is a new alias for `save-tracepoints'. The latter
|
|
|
|
|
is now deprecated.
|
|
|
|
|
|
Static tracepoints support, and UST integration.
gdb/gdbserver/
* configure.ac: Handle --with-ust. substitute ustlibs and ustinc.
* mem-break.c (uninsert_all_breakpoints)
(reinsert_all_breakpoints): New.
* mem-break.h (reinsert_all_breakpoints, uninsert_all_breakpoints):
* tracepoint.c (ust_loaded, helper_thread_id, cmd_buf): New.
(gdb_agent_ust_loaded, helper_thread_id)
(gdb_agent_helper_thread_id): New macros.
(struct ipa_sym_addresses): Add addr_ust_loaded,
addr_helper_thread_id, addr_cmd_buf.
(symbol_list): Add ust_loaded, helper_thread_id, cmd_buf.
(in_process_agent_loaded_ust): New.
(write_e_ust_not_loaded): New.
(maybe_write_ipa_ust_not_loaded): New.
(struct collect_static_trace_data_action): New.
(enum tracepoint_type) <static_tracepoint>: New.
(struct tracepoint) <handle>: Mention static tracepoints.
(struct static_tracepoint_ctx): New.
(CMD_BUF_SIZE): New.
(add_tracepoint_action): Handle static tracepoint actions.
(unprobe_marker_at): New.
(clear_installed_tracepoints): Handle static tracepoints.
(cmd_qtdp): Handle static tracepoints.
(probe_marker_at): New.
(cmd_qtstart): Handle static tracepoints.
(response_tracepoint): Handle static tracepoints.
(cmd_qtfstm, cmd_qtsstm, cmd_qtstmat): New.
(handle_tracepoint_query): Handle qTfSTM, qTsSTM and qTSTMat.
(get_context_regcache): Handle static tracepoints.
(do_action_at_tracepoint): Handle static tracepoint actions.
(traceframe_find_block_type): Handle static trace data blocks.
(traceframe_read_sdata): New.
(download_tracepoints): Download static tracepoint actions.
[HAVE_UST] Include ust/ust.h, dlfcn.h, sys/socket.h, and sys/un.h.
(GDB_PROBE_NAME): New.
(ust_ops): New.
(GET_UST_SYM): New.
(USTF): New.
(dlsym_ust): New.
(ust_marker_to_static_tracepoint): New.
(gdb_probe): New.
(collect_ust_data_at_tracepoint): New.
(gdb_ust_probe): New.
(UNIX_PATH_MAX, SOCK_DIR): New.
(gdb_ust_connect_sync_socket): New.
(resume_thread, stop_thread): New.
(run_inferior_command): New.
(init_named_socket): New.
(gdb_ust_socket_init): New.
(cstr_to_hexstr): New.
(next_st): New.
(first_marker, next_marker): New.
(response_ust_marker): New.
(cmd_qtfstm, cmd_qtsstm): New.
(unprobe_marker_at, probe_marker_at): New.
(cmd_qtstmat, gdb_ust_thread): New.
(gdb_ust_init): New.
(initialize_tracepoint_ftlib): Call gdb_ust_init.
* linux-amd64-ipa.c [HAVE_UST]: Include ust/processor.h
(ST_REGENTRY): New.
(x86_64_st_collect_regmap): New.
(X86_64_NUM_ST_COLLECT_GREGS): New.
(AMD64_RIP_REGNUM): New.
(supply_static_tracepoint_registers): New.
* linux-i386-ipa.c [HAVE_UST]: Include ust/processor.h
(ST_REGENTRY): New.
(i386_st_collect_regmap): New.
(i386_NUM_ST_COLLECT_GREGS): New.
(supply_static_tracepoint_registers): New.
* server.c (handle_query): Handle qXfer:statictrace:read.
<qSupported>: Report support for StaticTracepoints, and
qXfer:statictrace:read features.
* server.h (traceframe_read_sdata)
(supply_static_tracepoint_registers): Declare.
* remote-utils.c (convert_int_to_ascii, hexchars, ishex, tohex)
(unpack_varlen_hex): Include in IPA build.
* Makefile.in (ustlibs, ustinc): New.
(IPA_OBJS): Add remote-utils-ipa.o.
($(IPA_LIB)): Link -ldl and -lpthread.
(UST_CFLAGS): New.
(IPAGENT_CFLAGS): Add UST_CFLAGS.
* config.in, configure: Regenerate.
gdb/
* NEWS: Mention new support for static tracepoints.
(New packets): Mention qTfSTM, qTsSTM, qTSTMat and
qXfer:statictrace:read.
(New features in the GDB remote stub, GDBserver): Mention static
tracepoints support using an UST based backend.
(New commands): Mention "info static-tracepoint-markers" and
"strace".
* breakpoint.c (is_marker_spec): New.
(is_tracepoint): Handle static tracepoints.
(validate_commands_for_breakpoint): Static tracepoints can't do
while-stepping.
(static_tracepoints_here): New.
(bpstat_what): Handle static tracepoints.
(print_one_breakpoint_location, allocate_bp_location, mention):
Ditto.
(create_breakpoint_sal): Ditto.
(decode_static_tracepoint_spec): New.
(create_breakpoint): Replace `hardwareflag', and `traceflag' with
`type_wanted'. Adjust. Handle static tracepoint marker
locations.
(break_command_1): Adjust.
(update_static_tracepoint): New.
(update_breakpoint_locations): Handle static tracepoints.
(breakpoint_re_set_one): Handle static tracepoint marker
locations.
(disable_command, enable_command): Handle static tracepoints.
(trace_command, ftrace_command): Adjust.
(strace_command): New.
(create_tracepoint_from_upload): Adjust.
(save_breakpoints): Handle static tracepoints.
(_initialize_breakpoint): Install the "strace" command.
* breakpoint.h (enum bptype): New bp_static_tracepoint type.
(struct breakpoint): New fields static_trace_marker_id and
static_trace_marker_id_idx.
(breakpoints_here_p): Declare.
(create_breakpoint): Adjust.
(static_tracepoints_here): Declare.
* remote.c (struct remote_state) <static_tracepoints>: New field.
(PACKET_qXfer_statictrace_read, PACKET_StaticTracepoints): New.
(remote_static_tracepoint_marker_at): New.
(remote_static_tracepoint_markers_by_strid): New.
(remote_static_tracepoint_feature): New.
(remote_disconnected_tracing_feature): Handle "StaticTracepoints".
(remote_xfer_partial): Handle TARGET_OBJECT_STATIC_TRACE_DATA.
(remote_supports_static_tracepoints): New.
(remote_download_tracepoint): Download static tracepoints.
(init_remote_ops): Install remote_static_tracepoint_marker_at and
remote_static_tracepoint_markers_by_strid.
(_initialize_remote): Install set|show remote static-tracepoints,
and set|show remote read-sdata-object commands.
* target.c (update_current_target): Inherit and default
to_static_tracepoint_marker_at, and
to_static_tracepoint_markers_by_strid.
* target.h (static_tracepoint_marker): Forward declare.
(enum target_object): New object TARGET_OBJECT_STATIC_TRACE_DATA.
(static_tracepoint_marker_p): New typedef.
(DEF_VEC_P(static_tracepoint_marker_p)): New VEC type.
(struct target_ops): New fields to_static_tracepoint_marker_at and
to_static_tracepoint_markers_by_strid.
(target_static_tracepoint_marker_at)
(target_static_tracepoint_markers_by_strid): New.
* tracepoint.c: Include source.h.
(validate_actionline): Handle $_sdata.
(struct collection_list): New field strace_data.
(add_static_trace_data): New.
(clear_collection_list): Clear strace_data.
(stringify_collection_list): Account for a possible static trace
data collection.
(encode_actions_1): Encode an $_sdata collection.
(parse_tracepoint_definition): Handle static tracepoints.
(parse_static_tracepoint_marker_definition): New.
(release_static_tracepoint_marker): New.
(print_one_static_tracepoint_marker): New.
(info_static_tracepoint_markers_command): New.
(sdata_make_value): New.
(_initialize_tracepoint): Create the $_sdata convenience variable.
Add the "info static-tracepoint-markers" command.
Mention $_sdata in the "collect" command's help output.
* tracepoint.h (struct static_tracepoint_marker): New.
(parse_static_tracepoint_marker_definition)
(release_static_tracepoint_marker): Declare.
* mi/mi-cmd-break.c (mi_cmd_break_insert): Adjust.
* python/py-breakpoint.c (bppy_new): Adjust.
doc/
* gdb.texinfo (Convenience Variables): Document $_sdata.
(Commands to Set Tracepoints): Describe static tracepoints. Add
`Listing Static Tracepoint Markers' menu entry. Document
"strace".
(Tracepoint Action Lists): Document collecting $_sdata.
(Listing Static Tracepoint Markers): New subsection.
(Tracepoints support in gdbserver): Mention static tracepoints.
(remote packets, enabling and disabling): Mention
read-sdata-object.
(General Query Packets) <qSupported>: Document qXfer:sdata:read
and StaticTracepoint.
Mention qTfSTM, qTsSTM and qTSTMat as tracepoint packets.
Document qXfer:sdata:read.
(Tracepoint packets): Document qTfSTM, qTsSTM and qTSTMat.
2010-07-01 18:36:12 +08:00
|
|
|
info static-tracepoint-markers
|
|
|
|
|
Display information about static tracepoint markers in the target.
|
|
|
|
|
|
|
|
|
|
strace FN | FILE:LINE | *ADDR | -m MARKER_ID
|
|
|
|
|
Define a static tracepoint by probing a marker at the given
|
|
|
|
|
function, line, address, or marker ID.
|
|
|
|
|
|
2010-08-20 07:43:31 +08:00
|
|
|
set observer on|off
|
|
|
|
|
show observer
|
|
|
|
|
Enable and disable observer mode.
|
|
|
|
|
|
|
|
|
|
set may-write-registers on|off
|
|
|
|
|
set may-write-memory on|off
|
|
|
|
|
set may-insert-breakpoints on|off
|
|
|
|
|
set may-insert-tracepoints on|off
|
|
|
|
|
set may-insert-fast-tracepoints on|off
|
|
|
|
|
set may-interrupt on|off
|
|
|
|
|
Set individual permissions for GDB effects on the target. Note that
|
|
|
|
|
some of these settings can have undesirable or surprising
|
|
|
|
|
consequences, particularly when changed in the middle of a session.
|
|
|
|
|
For instance, disabling the writing of memory can prevent
|
|
|
|
|
breakpoints from being inserted, cause single-stepping to fail, or
|
|
|
|
|
even crash your program, if you disable after breakpoints have been
|
|
|
|
|
inserted. However, GDB should not crash.
|
|
|
|
|
|
|
|
|
|
set record memory-query on|off
|
|
|
|
|
show record memory-query
|
|
|
|
|
Control whether to stop the inferior if memory changes caused
|
|
|
|
|
by an instruction cannot be recorded.
|
|
|
|
|
|
2010-07-28 04:33:40 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
|
|
|
|
disassemble
|
|
|
|
|
The disassemble command now supports "start,+length" form of two arguments.
|
|
|
|
|
|
2010-02-24 Phil Muldoon <pmuldoon@redhat.com>
Tom Tromey <tromey@redhat.com>
Thiago Jung Bauermann <bauerman@br.ibm.com>
* python/python.c (_initialize_python): Call
gdbpy_initialize_symtabs, gdbpy_initialize_symbols and
gdbpy_initialize_blocks.
* python/python-internal.h: Declare struct symbol, block and
symtab_and_line. Declare block_object_type and
symbol_object_type
(gdbpy_lookup_symbol gdbpy_block_for_pc)
(symtab_and_line_to_sal_object, symtab_to_symtab_object)
(symbol_to_symbol_object, block_to_block_object)
(gdbpy_initialize_symtabs,gdbpy_initialize_symbols)
(gdbpy_initialize_blocks ): Declare.
* python/py-frame.c (frapy_block, frapy_function, frapy_find_sal)
(frapy_select): Add methods.
(frapy_read_var): Add symbol branch.
* Makefile.in (SUBDIR_PYTHON_OBS): Add py-symbol, py-symtab,
py-block.
(SUBDIR_PYTHON_SRCS): Likewise.
(py-symbol.o): New rule.
(py-symtab.o): Likewise.
(py-block.o): Likewise.
* python/py-symbol.c: New file.
* python/py-symtab.c: Likewise.
* python/py-block.c: Likewise.
2010-02-24 Phil Muldoon <pmuldoon@redhat.com>
* Makefile.in: Add py-block and py-symbol.
* gdb.python/py-symbol.exp: New File.
* gdb.python/py-symtab.exp: New File.
* gdb.python/py-block.exp: New File.
* gdb.python/py-symbol.c: New File.
* gdb.python/py-block.c: New File.
2010-02-24 Phil Muldoon <pmuldoon@redhat.com>
* gdb.texinfo (Frames In Python): Add block, find_sal, function
and select method descriptions.
(Python API): Add Blocks In Python, Symbols in Python and Symbol
Tables in Python to menu.
(Blocks In Python): New node.
(Symbols In Python): New node.
(Symbol Tables in Python): New node.
2010-02-25 05:18:28 +08:00
|
|
|
* Python scripting
|
|
|
|
|
|
2010-06-29 03:54:04 +08:00
|
|
|
** GDB now provides a new directory location, called the python directory,
|
|
|
|
|
where Python scripts written for GDB can be installed. The location
|
|
|
|
|
of that directory is <data-directory>/python, where <data-directory>
|
|
|
|
|
is the GDB data directory. For more details, see section `Scripting
|
|
|
|
|
GDB using Python' in the manual.
|
|
|
|
|
|
2010-04-09 17:41:43 +08:00
|
|
|
** The GDB Python API now has access to breakpoints, symbols, symbol
|
2010-06-29 05:16:04 +08:00
|
|
|
tables, program spaces, inferiors, threads and frame's code blocks.
|
|
|
|
|
Additionally, GDB Parameters can now be created from the API, and
|
|
|
|
|
manipulated via set/show in the CLI.
|
2010-03-06 04:18:19 +08:00
|
|
|
|
2010-04-16 03:54:13 +08:00
|
|
|
** New functions gdb.target_charset, gdb.target_wide_charset,
|
2010-05-25 23:27:17 +08:00
|
|
|
gdb.progspaces, gdb.current_progspace, and gdb.string_to_argv.
|
|
|
|
|
|
|
|
|
|
** New exception gdb.GdbError.
|
2010-04-16 03:54:13 +08:00
|
|
|
|
|
|
|
|
** Pretty-printers are now also looked up in the current program space.
|
2010-02-24 Phil Muldoon <pmuldoon@redhat.com>
Tom Tromey <tromey@redhat.com>
Thiago Jung Bauermann <bauerman@br.ibm.com>
* python/python.c (_initialize_python): Call
gdbpy_initialize_symtabs, gdbpy_initialize_symbols and
gdbpy_initialize_blocks.
* python/python-internal.h: Declare struct symbol, block and
symtab_and_line. Declare block_object_type and
symbol_object_type
(gdbpy_lookup_symbol gdbpy_block_for_pc)
(symtab_and_line_to_sal_object, symtab_to_symtab_object)
(symbol_to_symbol_object, block_to_block_object)
(gdbpy_initialize_symtabs,gdbpy_initialize_symbols)
(gdbpy_initialize_blocks ): Declare.
* python/py-frame.c (frapy_block, frapy_function, frapy_find_sal)
(frapy_select): Add methods.
(frapy_read_var): Add symbol branch.
* Makefile.in (SUBDIR_PYTHON_OBS): Add py-symbol, py-symtab,
py-block.
(SUBDIR_PYTHON_SRCS): Likewise.
(py-symbol.o): New rule.
(py-symtab.o): Likewise.
(py-block.o): Likewise.
* python/py-symbol.c: New file.
* python/py-symtab.c: Likewise.
* python/py-block.c: Likewise.
2010-02-24 Phil Muldoon <pmuldoon@redhat.com>
* Makefile.in: Add py-block and py-symbol.
* gdb.python/py-symbol.exp: New File.
* gdb.python/py-symtab.exp: New File.
* gdb.python/py-block.exp: New File.
* gdb.python/py-symbol.c: New File.
* gdb.python/py-block.c: New File.
2010-02-24 Phil Muldoon <pmuldoon@redhat.com>
* gdb.texinfo (Frames In Python): Add block, find_sal, function
and select method descriptions.
(Python API): Add Blocks In Python, Symbols in Python and Symbol
Tables in Python to menu.
(Blocks In Python): New node.
(Symbols In Python): New node.
(Symbol Tables in Python): New node.
2010-02-25 05:18:28 +08:00
|
|
|
|
2010-06-05 02:18:28 +08:00
|
|
|
** Pretty-printers can now be individually enabled and disabled.
|
|
|
|
|
|
2010-04-24 00:20:13 +08:00
|
|
|
** GDB now looks for names of Python scripts to auto-load in a
|
|
|
|
|
special section named `.debug_gdb_scripts', in addition to looking
|
|
|
|
|
for a OBJFILE-gdb.py script when OBJFILE is read by the debugger.
|
|
|
|
|
|
2010-03-24 05:32:28 +08:00
|
|
|
* Tracepoint actions were unified with breakpoint commands. In particular,
|
|
|
|
|
there are no longer differences in "info break" output for breakpoints and
|
|
|
|
|
tracepoints and the "commands" command can be used for both tracepoints and
|
|
|
|
|
regular breakpoints.
|
|
|
|
|
|
2010-02-26 23:03:10 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
ARM Symbian arm*-*-symbianelf*
|
|
|
|
|
|
2010-04-29 22:45:39 +08:00
|
|
|
* D language support.
|
|
|
|
|
GDB now supports debugging programs written in the D programming
|
|
|
|
|
language.
|
|
|
|
|
|
2010-07-17 07:19:37 +08:00
|
|
|
* GDB now supports the extended ptrace interface for PowerPC which is
|
|
|
|
|
available since Linux kernel version 2.6.34. This automatically enables
|
|
|
|
|
any hardware breakpoints and additional hardware watchpoints available in
|
|
|
|
|
the processor. The old ptrace interface exposes just one hardware
|
|
|
|
|
watchpoint and no hardware breakpoints.
|
|
|
|
|
|
|
|
|
|
* GDB is now able to use the Data Value Compare (DVC) register available on
|
|
|
|
|
embedded PowerPC processors to implement in hardware simple watchpoint
|
|
|
|
|
conditions of the form:
|
|
|
|
|
|
|
|
|
|
watch ADDRESS|VARIABLE if ADDRESS|VARIABLE == CONSTANT EXPRESSION
|
|
|
|
|
|
|
|
|
|
This works in native GDB running on Linux kernels with the extended ptrace
|
|
|
|
|
interface mentioned above.
|
|
|
|
|
|
2010-02-19 08:35:53 +08:00
|
|
|
*** Changes in GDB 7.1
|
2009-10-08 02:27:22 +08:00
|
|
|
|
2010-02-18 04:08:24 +08:00
|
|
|
* C++ Improvements
|
|
|
|
|
|
|
|
|
|
** Namespace Support
|
2010-02-16 23:52:47 +08:00
|
|
|
|
|
|
|
|
GDB now supports importing of namespaces in C++. This enables the
|
|
|
|
|
user to inspect variables from imported namespaces. Support for
|
|
|
|
|
namepace aliasing has also been added. So, if a namespace is
|
|
|
|
|
aliased in the current scope (e.g. namepace C=A; ) the user can
|
|
|
|
|
print variables using the alias (e.g. (gdb) print C::x).
|
|
|
|
|
|
2010-02-18 04:08:24 +08:00
|
|
|
** Bug Fixes
|
|
|
|
|
|
|
|
|
|
All known bugs relating to the printing of virtual base class were
|
|
|
|
|
fixed. It is now possible to call overloaded static methods using a
|
|
|
|
|
qualified name.
|
|
|
|
|
|
|
|
|
|
** Cast Operators
|
|
|
|
|
|
|
|
|
|
The C++ cast operators static_cast<>, dynamic_cast<>, const_cast<>,
|
|
|
|
|
and reinterpret_cast<> are now handled by the C++ expression parser.
|
|
|
|
|
|
* config/djgpp/fnchange.lst: Add translations for cpu-microblaze.c,
elf32-microblaze.c, microblaze-rom.c, microblaze-linux-tdep.c,
microblaze-tdep.h, microblaze-tdep.c, microblaze-opc.h,
microblaze-opcm.h, microblaze-dis.c, microblaze-dis.h, sim/microblaze,
microblaze.h, and microblaze.isa.
* configure.tgt: Add targets microblaze*-linux-*, microblaze*-xilinx-*.
* Makefile.in: Build microblaze-tdep.o, microblaze-linux-tdep.o.
HFILES_NO_SRCDIR: Add microblaze-tdep.h.
* microblaze-linux-tdep.c: New.
* microblaze-tdep.c: New.
* microblaze-tdep.h: New.
* NEWS: Announce Xilinx MicroBlaze support.
2009-10-16 03:28:52 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Xilinx MicroBlaze microblaze-*-*
|
2009-12-08 08:17:45 +08:00
|
|
|
Renesas RX rx-*-elf
|
* config/djgpp/fnchange.lst: Add translations for cpu-microblaze.c,
elf32-microblaze.c, microblaze-rom.c, microblaze-linux-tdep.c,
microblaze-tdep.h, microblaze-tdep.c, microblaze-opc.h,
microblaze-opcm.h, microblaze-dis.c, microblaze-dis.h, sim/microblaze,
microblaze.h, and microblaze.isa.
* configure.tgt: Add targets microblaze*-linux-*, microblaze*-xilinx-*.
* Makefile.in: Build microblaze-tdep.o, microblaze-linux-tdep.o.
HFILES_NO_SRCDIR: Add microblaze-tdep.h.
* microblaze-linux-tdep.c: New.
* microblaze-tdep.c: New.
* microblaze-tdep.h: New.
* NEWS: Announce Xilinx MicroBlaze support.
2009-10-16 03:28:52 +08:00
|
|
|
|
|
|
|
|
* New Simulators
|
|
|
|
|
|
|
|
|
|
Xilinx MicroBlaze microblaze
|
2009-12-08 08:17:45 +08:00
|
|
|
Renesas RX rx
|
* config/djgpp/fnchange.lst: Add translations for cpu-microblaze.c,
elf32-microblaze.c, microblaze-rom.c, microblaze-linux-tdep.c,
microblaze-tdep.h, microblaze-tdep.c, microblaze-opc.h,
microblaze-opcm.h, microblaze-dis.c, microblaze-dis.h, sim/microblaze,
microblaze.h, and microblaze.isa.
* configure.tgt: Add targets microblaze*-linux-*, microblaze*-xilinx-*.
* Makefile.in: Build microblaze-tdep.o, microblaze-linux-tdep.o.
HFILES_NO_SRCDIR: Add microblaze-tdep.h.
* microblaze-linux-tdep.c: New.
* microblaze-tdep.c: New.
* microblaze-tdep.h: New.
* NEWS: Announce Xilinx MicroBlaze support.
2009-10-16 03:28:52 +08:00
|
|
|
|
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
Add base multi-executable/process support to GDB.
gdb/
* Makefile.in (SFILES): Add progspace.c.
(COMMON_OBS): Add progspace.o.
* progspace.h: New.
* progspace.c: New.
* breakpoint.h (struct bp_target_info) <placed_address_space>: New
field.
(struct bp_location) <pspace>: New field.
(struct breakpoint) <pspace>: New field.
(bpstat_stop_status, breakpoint_here_p)
(moribund_breakpoint_here_p, breakpoint_inserted_here_p)
(regular_breakpoint_inserted_here_p)
(software_breakpoint_inserted_here_p, breakpoint_thread_match)
(set_default_breakpoint): Adjust prototypes.
(remove_breakpoints_pid, breakpoint_program_space_exit): Declare.
(insert_single_step_breakpoint, deprecated_insert_raw_breakpoint):
Adjust prototypes.
* breakpoint.c (executing_startup): Delete.
(default_breakpoint_sspace): New.
(breakpoint_restore_shadows): Skip if the address space doesn't
match.
(update_watchpoint): Record the frame's program space in the
breakpoint location.
(insert_bp_location): Record the address space in target_info.
Adjust to pass the symbol space to solib_name_from_address.
(breakpoint_program_space_exit): New.
(insert_breakpoint_locations): Switch the symbol space and thread
when inserting breakpoints. Don't insert breakpoints in a vfork
parent waiting for vfork done if we're not attached to the vfork
child.
(remove_breakpoints_pid): New.
(reattach_breakpoints): Switch to a thread of PID. Ignore
breakpoints of other symbol spaces.
(create_internal_breakpoint): Store the symbol space in the sal.
(create_longjmp_master_breakpoint): Iterate over all symbol
spaces.
(update_breakpoints_after_exec): Ignore breakpoints for other
symbol spaces.
(remove_breakpoint): Rename to ...
(remove_breakpoint_1): ... this. Pass the breakpoints symbol
space to solib_name_from_address.
(remove_breakpoint): New.
(mark_breakpoints_out): Ignore breakpoints from other symbol
spaces.
(breakpoint_init_inferior): Ditto.
(breakpoint_here_p): Add an address space argument and adjust to
use breakpoint_address_match.
(moribund_breakpoint_here_p): Ditto.
(regular_breakpoint_inserted_here_p): Ditto.
(breakpoint_inserted_here_p): Ditto.
(software_breakpoint_inserted_here_p): Ditto.
(breakpoint_thread_match): Ditto.
(bpstat_check_location): Ditto.
(bpstat_stop_status): Ditto.
(print_breakpoint_location): If there's a location to print,
switch the current symbol space.
(print_one_breakpoint_location): Add `allflag' argument.
(print_one_breakpoint): Ditto. Adjust.
(do_captured_breakpoint_query): Adjust.
(breakpoint_1): Adjust.
(breakpoint_has_pc): Also match the symbol space.
(describe_other_breakpoints): Add a symbol space argument and
adjust.
(set_default_breakpoint): Add a symbol space argument. Set
default_breakpoint_sspace.
(breakpoint_address_match): New.
(check_duplicates_for): Add an address space argument, and adjust.
(set_raw_breakpoint): Record the symbol space in the location and
in the breakpoint.
(set_longjmp_breakpoint): Skip longjmp master breakpoints from
other symbol spaces.
(remove_thread_event_breakpoints, remove_solib_event_breakpoints)
(disable_breakpoints_in_shlibs): Skip breakpoints from other
symbol spaces.
(disable_breakpoints_in_unloaded_shlib): Match symbol spaces.
(create_catchpoint): Set the symbol space in the sal.
(disable_breakpoints_before_startup): Skip breakpoints from other
symbol spaces. Set executing_startup in the current symbol space.
(enable_breakpoints_after_startup): Clear executing_startup in the
current symbol space. Skip breakpoints from other symbol spaces.
(clone_momentary_breakpoint): Also copy the symbol space.
(add_location_to_breakpoint): Set the location's symbol space.
(bp_loc_is_permanent): Switch thread and symbol space.
(create_breakpoint): Adjust.
(expand_line_sal_maybe): Expand comment to mention symbol spaces.
Switch thread and symbol space when reading memory.
(parse_breakpoint_sals): Set the symbol space in the sal.
(break_command_really): Ditto.
(skip_prologue_sal): Switch and space.
(resolve_sal_pc): Ditto.
(watch_command_1): Record the symbol space in the sal.
(create_ada_exception_breakpoint): Adjust.
(clear_command): Adjust. Match symbol spaces.
(update_global_location_list): Use breakpoint_address_match.
(breakpoint_re_set_one): Switch thread and space.
(breakpoint_re_set): Save symbol space.
(breakpoint_re_set_thread): Also reset the symbol space.
(deprecated_insert_raw_breakpoint): Add an address space argument.
Adjust.
(insert_single_step_breakpoint): Ditto.
(single_step_breakpoint_inserted_here_p): Ditto.
(clear_syscall_counts): New.
(_initialize_breakpoint): Install it as inferior_exit observer.
* exec.h: Include "progspace.h".
(exec_bfd, exec_bfd_mtime): New defines.
(exec_close): Declare.
* exec.c: Include "gdbthread.h" and "progspace.h".
(exec_bfd, exec_bfd_mtime, current_target_sections_1): Delete.
(using_exec_ops): New.
(exec_close_1): Rename to exec_close, and make public.
(exec_close): Rename to exec_close_1, and adjust all callers. Add
description. Remove target sections and close executables from
all program spaces.
(exec_file_attach): Add comment.
(add_target_sections): Check on `using_exec_ops' to check if the
target should be pushed.
(remove_target_sections): Only unpush the target if there are no
more target sections in any symbol space.
* gdbcore.h: Include "exec.h".
(exec_bfd, exec_bfd_mtime): Remove declarations.
* frame.h (get_frame_program_space, get_frame_address_space)
(frame_unwind_program_space): Declare.
* frame.c (struct frame_info) <pspace, aspace>: New fields.
(create_sentinel_frame): Add program space argument. Set the
pspace and aspace fields of the frame object.
(get_current_frame, create_new_frame): Adjust.
(get_frame_program_space): New.
(frame_unwind_program_space): New.
(get_frame_address_space): New.
* stack.c (print_frame_info): Adjust.
(print_frame): Use the frame's program space.
* gdbthread.h (any_live_thread_of_process): Declare.
* thread.c (any_live_thread_of_process): New.
(switch_to_thread): Switch the program space as well.
(restore_selected_frame): Don't warn if trying to restore frame
level 0.
* inferior.h: Include "progspace.h".
(detach_fork): Declare.
(struct inferior) <removable, aspace, pspace>
<vfork_parent, vfork_child, pending_detach>
<waiting_for_vfork_done>: New fields.
<terminal_info>: Remove field.
<data, num_data>: New fields.
(register_inferior_data, register_inferior_data_with_cleanup)
(clear_inferior_data, set_inferior_data, inferior_data): Declare.
(exit_inferior, exit_inferior_silent, exit_inferior_num_silent)
(inferior_appeared): Declare.
(find_inferior_pid): Typo.
(find_inferior_id, find_inferior_for_program_space): Declare.
(set_current_inferior, save_current_inferior, prune_inferiors)
(number_of_inferiors): Declare.
(inferior_list): Declare.
* inferior.c: Include "gdbcore.h" and "symfile.h".
(inferior_list): Make public.
(delete_inferior_1): Always delete thread silently.
(find_inferior_id): Make public.
(current_inferior_): New.
(current_inferior): Use it.
(set_current_inferior): New.
(restore_inferior): New.
(save_current_inferior): New.
(free_inferior): Free the per-inferior data.
(add_inferior_silent): Allocate per-inferior data.
Call inferior_appeared.
(delete_threads_of_inferior): New.
(delete_inferior_1): Adjust interface to take an inferior pointer.
(delete_inferior): Adjust.
(delete_inferior_silent): Adjust.
(exit_inferior_1): New.
(exit_inferior): New.
(exit_inferior_silent): New.
(exit_inferior_num_silent): New.
(detach_inferior): Adjust.
(inferior_appeared): New.
(discard_all_inferiors): Adjust.
(find_inferior_id): Make public. Assert pid is not zero.
(find_inferior_for_program_space): New.
(have_inferiors): Check if we have any inferior with pid not zero.
(have_live_inferiors): Go over all pushed targets looking for
process_stratum.
(prune_inferiors): New.
(number_of_inferiors): New.
(print_inferior): Add executable column. Print vfork parent/child
relationships.
(inferior_command): Adjust to cope with not running inferiors.
(remove_inferior_command): New.
(add_inferior_command): New.
(clone_inferior_command): New.
(struct inferior_data): New.
(struct inferior_data_registration): New.
(struct inferior_data_registry): New.
(inferior_data_registry): New.
(register_inferior_data_with_cleanup): New.
(register_inferior_data): New.
(inferior_alloc_data): New.
(inferior_free_data): New.
(clear_inferior_data): New.
(set_inferior_data): New.
(inferior_data): New.
(initialize_inferiors): New.
(_initialize_inferiors): Register "add-inferior",
"remove-inferior" and "clone-inferior" commands.
* objfiles.h: Include "progspace.h".
(struct objfile) <pspace>: New field.
(symfile_objfile, object_files): Don't declare.
(ALL_PSPACE_OBJFILES): New.
(ALL_PSPACE_OBJFILES_SAFE): New.
(ALL_OBJFILES, ALL_OBJFILES_SAFE): Adjust.
(ALL_PSPACE_SYMTABS): New.
(ALL_PRIMARY_SYMTABS): Adjust.
(ALL_PSPACE_PRIMARY_SYMTABS): New.
(ALL_PSYMTABS): Adjust.
(ALL_PSPACE_PSYMTABS): New.
* objfiles.c (object_files, symfile_objfile): Delete.
(struct objfile_sspace_info): New.
(objfiles_pspace_data): New.
(objfiles_pspace_data_cleanup): New.
(get_objfile_pspace_data): New.
(objfiles_changed_p): Delete.
(allocate_objfile): Set the objfile's program space. Adjust to
reference objfiles_changed_p in pspace data.
(free_objfile): Adjust to reference objfiles_changed_p in pspace
data.
(objfile_relocate): Ditto.
(update_section_map): Add pspace argument. Adjust to iterate over
objfiles in the passed in pspace.
(find_pc_section): Delete sections and num_sections statics.
Adjust to refer to program space's objfiles_changed_p. Adjust to
refer to sections and num_sections store in the objfile's pspace
data.
(objfiles_changed): Adjust to reference objfiles_changed_p in
pspace data.
(_initialize_objfiles): New.
* linespec.c (decode_all_digits, decode_dollar): Set the sal's
program space.
* source.c (current_source_pspace): New.
(get_current_source_symtab_and_line): Set the sal's program space.
(set_current_source_symtab_and_line): Set current_source_pspace.
(select_source_symtab): Ditto. Use ALL_OBJFILES.
(forget_cached_source_info): Iterate over all program spaces.
* symfile.c (clear_symtab_users): Adjust.
* symmisc.c (print_symbol_bcache_statistics): Iterate over all
program spaces.
(print_objfile_statistics): Ditto.
(maintenance_print_msymbols): Ditto.
(maintenance_print_objfiles): Ditto.
(maintenance_info_symtabs): Ditto.
(maintenance_info_psymtabs): Ditto.
* symtab.h (SYMTAB_PSPACE): New.
(struct symtab_and_line) <pspace>: New field.
* symtab.c (init_sal): Clear the sal's program space.
(find_pc_sect_symtab): Set the sal's program space. Switch thread
and space.
(append_expanded_sal): Add program space argument. Iterate over
all program spaces.
(expand_line_sal): Iterate over all program spaces. Switch
program space.
* target.h (enum target_waitkind) <TARGET_WAITKIND_VFORK_DONE>: New.
(struct target_ops) <to_thread_address_space>: New field.
(target_thread_address_space): Define.
* target.c (target_detach): Only remove breakpoints from the
inferior we're detaching.
(target_thread_address_space): New.
* defs.h (initialize_progspace): Declare.
* top.c (gdb_init): Call it.
* solist.h (struct so_list) <sspace>: New field.
* solib.h (struct program_space): Forward declare.
(solib_name_from_address): Adjust prototype.
* solib.c (so_list_head): Replace with a macro referencing the
program space.
(update_solib_list): Set the so's program space.
(solib_name_from_address): Add a program space argument and adjust.
* solib-svr4.c (struct svr4_info) <pid>: Delete field.
<interp_text_sect_low, interp_text_sect_high, interp_plt_sect_low>
<interp_plt_sect_high>: New fields.
(svr4_info_p, svr4_info): Delete.
(solib_svr4_sspace_data): New.
(get_svr4_info): Rewrite.
(svr4_sspace_data_cleanup): New.
(open_symbol_file_object): Adjust.
(svr4_default_sos): Adjust.
(svr4_fetch_objfile_link_map): Adjust.
(interp_text_sect_low, interp_text_sect_high, interp_plt_sect_low)
(interp_plt_sect_high): Delete.
(svr4_in_dynsym_resolve_code): Adjust.
(enable_break): Adjust.
(svr4_clear_solib): Revert bit that removed the svr4_info here,
and reinstate clearing debug_base, debug_loader_offset_p,
debug_loader_offset and debug_loader_name.
(_initialize_svr4_solib): Register solib_svr4_pspace_data. Don't
install an inferior_exit observer anymore.
* printcmd.c (struct display) <pspace>: New field.
(display_command): Set the display's sspace.
(do_one_display): Match the display's sspace.
(display_uses_solib_p): Ditto.
* linux-fork.c (detach_fork): Moved to infrun.c.
(_initialize_linux_fork): Moved "detach-on-fork" command to
infrun.c.
* infrun.c (detach_fork): Moved from linux-fork.c.
(proceed_after_vfork_done): New.
(handle_vfork_child_exec_or_exit): New.
(follow_exec_mode_replace, follow_exec_mode_keep)
(follow_exec_mode_names, follow_exec_mode_string)
(show_follow_exec_mode_string): New.
(follow_exec): New. Reinstate the mark_breakpoints_out call.
Remove shared libraries before attaching new executable. If user
wants to keep the inferior, keep it.
(displaced_step_fixup): Adjust to pass an address space to the
breakpoints module.
(resume): Ditto.
(clear_proceed_status): In all-stop mode, always clear the proceed
status of all threads.
(prepare_to_proceed): Adjust to pass an address space to the
breakpoints module.
(proceed): Ditto.
(adjust_pc_after_break): Ditto.
(handle_inferior_event): When handling a process exit, switch the
program space to the inferior's that had exited. Call
handle_vfork_child_exec_or_exit. Adjust to pass an address space
to the breakpoints module. In non-stop mode, when following a
fork and detach-fork is off, also resume the other branch. Handle
TARGET_WAITKIND_VFORK_DONE. Set the program space in sals.
(normal_stop): Prune inferiors.
(_initialize_infrun): Install the new "follow-exec-mode" command.
"detach-on-fork" moved here.
* regcache.h (get_regcache_aspace): Declare.
* regcache.c (struct regcache) <aspace>: New field.
(regcache_xmalloc): Clear the aspace.
(get_regcache_aspace): New.
(regcache_cpy): Copy the aspace field.
(regcache_cpy_no_passthrough): Ditto.
(get_thread_regcache): Fetch the thread's address space from the
target, and store it in the regcache.
* infcall.c (call_function_by_hand): Set the sal's pspace.
* arch-utils.c (default_has_shared_address_space): New.
* arch-utils.h (default_has_shared_address_space): Declare.
* gdbarch.sh (has_shared_address_space): New.
* gdbarch.h, gdbarch.c: Regenerate.
* linux-tdep.c: Include auxv.h, target.h, elf/common.h.
(linux_has_shared_address_space): New.
(_initialize_linux_tdep): Declare.
* arm-tdep.c (arm_software_single_step): Pass the frame's address
space to insert_single_step_breakpoint.
* arm-linux-tdep.c (arm_linux_software_single_step): Pass the
frame's pspace to breakpoint functions.
* cris-tdep.c (crisv32_single_step_through_delay): Ditto.
(cris_software_single_step): Ditto.
* mips-tdep.c (deal_with_atomic_sequence): Add frame argument.
Pass the frame's pspace to breakpoint functions.
(mips_software_single_step): Adjust.
(mips_single_step_through_delay): Adjust.
* rs6000-aix-tdep.c (rs6000_software_single_step): Adjust.
* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Adjust.
* solib-irix.c (enable_break): Adjust to pass the current frame's
address space to breakpoint functions.
* sparc-tdep.c (sparc_software_single_step): Ditto.
* spu-tdep.c (spu_software_single_step): Ditto.
* alpha-tdep.c (alpha_software_single_step): Ditto.
* record.c (record_wait): Adjust to pass an address space to the
breakpoints module.
* fork-child.c (fork_inferior): Set the new inferior's program and
address spaces.
* inf-ptrace.c (inf_ptrace_follow_fork): Copy the parent's program
and address spaces.
(inf_ptrace_attach): Set the inferior's program and address spaces.
* linux-nat.c: Include "solib.h".
(linux_child_follow_fork): Manage parent and child's program and
address spaces. Clone the parent's program space if necessary.
Don't wait for the vfork to be done here. Refuse to resume if
following the vfork parent while leaving the child stopped.
(resume_callback): Don't resume a vfork parent.
(linux_nat_resume): Also check for pending events in the
lp->waitstatus field.
(linux_handle_extended_wait): Report TARGET_WAITKIND_VFORK_DONE
events to the core.
(stop_wait_callback): Don't wait for SIGSTOP on vfork parents.
(cancel_breakpoint): Adjust.
* linux-thread-db.c (thread_db_wait): Don't remove thread event
breakpoints here.
(thread_db_mourn_inferior): Don't mark breakpoints out here.
Remove thread event breakpoints after mourning.
* corelow.c: Include progspace.h.
(core_open): Set the inferior's program and address spaces.
* remote.c (remote_add_inferior): Set the new inferior's program
and address spaces.
(remote_start_remote): Update address spaces.
(extended_remote_create_inferior_1): Don't init the thread list if
we already debugging other inferiors.
* darwin-nat.c (darwin_attach): Set the new inferior's program and
address spaces.
* gnu-nat.c (gnu_attach): Ditto.
* go32-nat.c (go32_create_inferior): Ditto.
* inf-ttrace.c (inf_ttrace_follow_fork, inf_ttrace_attach): Ditto.
* monitor.c (monitor_open): Ditto.
* nto-procfs.c (procfs_attach, procfs_create_inferior): Ditto.
* procfs.c (do_attach): Ditto.
* windows-nat.c (do_initial_windows_stuff): Ditto.
* inflow.c (inferior_process_group)
(terminal_init_inferior_with_pgrp, terminal_inferior,
(terminal_ours_1, inflow_inferior_exit, copy_terminal_info)
(child_terminal_info, new_tty_postfork, set_sigint_trap): Adjust
to use per-inferior data instead of inferior->terminal_info.
(inflow_inferior_data): New.
(inflow_new_inferior): Delete.
(inflow_inferior_data_cleanup): New.
(get_inflow_inferior_data): New.
* mi/mi-interp.c (mi_new_inferior): Rename to...
(mi_inferior_appeared): ... this.
(mi_interpreter_init): Adjust.
* tui/tui-disasm.c: Include "progspace.h".
(tui_set_disassem_content): Pass an address space to
breakpoint_here_p.
* NEWS: Mention multi-program debugging support. Mention new
commands "add-inferior", "clone-inferior", "remove-inferior",
"maint info program-spaces", and new option "set
follow-exec-mode".
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/doc/
* observer.texi (new_inferior): Rename to...
(inferior_appeared): ... this.
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/testsuite/
* gdb.base/foll-vfork.exp: Adjust to spell out "follow-fork".
* gdb.base/foll-exec.exp: Adjust to expect a process id before
"Executing new program".
* gdb.base/foll-fork.exp: Adjust to spell out "follow-fork".
* gdb.base/multi-forks.exp: Ditto. Adjust to the inferior being
left listed after having been killed.
* gdb.base/attach.exp: Adjust to spell out "symbol-file".
* gdb.base/maint.exp: Adjust test.
* Makefile.in (ALL_SUBDIRS): Add gdb.multi.
* gdb.multi/Makefile.in: New.
* gdb.multi/base.exp: New.
* gdb.multi/goodbye.c: New.
* gdb.multi/hangout.c: New.
* gdb.multi/hello.c: New.
* gdb.multi/bkpt-multi-exec.c: New.
* gdb.multi/bkpt-multi-exec.exp: New.
* gdb.multi/crashme.c: New.
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/doc/
* gdb.texinfo (Inferiors): Rename node to ...
(Inferiors and Programs): ... this. Mention running multiple
programs in the same debug session.
<info inferiors>: Mention the new 'Executable' column if "info
inferiors". Update examples. Document the "add-inferior",
"clone-inferior", "remove-inferior" and "maint info
program-spaces" commands.
(Process): Rename node to...
(Forks): ... this. Document "set|show follow-exec-mode".
2009-10-19 17:51:43 +08:00
|
|
|
* Multi-program debugging.
|
|
|
|
|
|
|
|
|
|
GDB now has support for multi-program (a.k.a. multi-executable or
|
|
|
|
|
multi-exec) debugging. This allows for debugging multiple inferiors
|
|
|
|
|
simultaneously each running a different program under the same GDB
|
|
|
|
|
session. See "Debugging Multiple Inferiors and Programs" in the
|
|
|
|
|
manual for more information. This implied some user visible changes
|
|
|
|
|
in the multi-inferior support. For example, "info inferiors" now
|
|
|
|
|
lists inferiors that are not running yet or that have exited
|
|
|
|
|
already. See also "New commands" and "New options" below.
|
|
|
|
|
|
2010-01-07 04:31:28 +08:00
|
|
|
* New tracing features
|
|
|
|
|
|
|
|
|
|
GDB's tracepoint facility now includes several new features:
|
|
|
|
|
|
|
|
|
|
** Trace state variables
|
2009-12-29 07:39:10 +08:00
|
|
|
|
|
|
|
|
GDB tracepoints now include support for trace state variables, which
|
|
|
|
|
are variables managed by the target agent during a tracing
|
|
|
|
|
experiment. They are useful for tracepoints that trigger each
|
|
|
|
|
other, so for instance one tracepoint can count hits in a variable,
|
|
|
|
|
and then a second tracepoint has a condition that is true when the
|
|
|
|
|
count reaches a particular value. Trace state variables share the
|
|
|
|
|
$-syntax of GDB convenience variables, and can appear in both
|
|
|
|
|
tracepoint actions and condition expressions. Use the "tvariable"
|
|
|
|
|
command to create, and "info tvariables" to view; see "Trace State
|
|
|
|
|
Variables" in the manual for more detail.
|
2010-01-06 12:20:27 +08:00
|
|
|
|
2010-01-07 04:31:28 +08:00
|
|
|
** Fast tracepoints
|
2010-01-06 12:20:27 +08:00
|
|
|
|
|
|
|
|
GDB now includes an option for defining fast tracepoints, which
|
|
|
|
|
targets may implement more efficiently, such as by installing a jump
|
|
|
|
|
into the target agent rather than a trap instruction. The resulting
|
|
|
|
|
speedup can be by two orders of magnitude or more, although the
|
|
|
|
|
tradeoff is that some program locations on some target architectures
|
|
|
|
|
might not allow fast tracepoint installation, for instance if the
|
|
|
|
|
instruction to be replaced is shorter than the jump. To request a
|
|
|
|
|
fast tracepoint, use the "ftrace" command, with syntax identical to
|
|
|
|
|
the regular trace command.
|
|
|
|
|
|
2010-01-07 04:31:28 +08:00
|
|
|
** Disconnected tracing
|
|
|
|
|
|
|
|
|
|
It is now possible to detach GDB from the target while it is running
|
|
|
|
|
a trace experiment, then reconnect later to see how the experiment
|
|
|
|
|
is going. In addition, a new variable disconnected-tracing lets you
|
|
|
|
|
tell the target agent whether to continue running a trace if the
|
|
|
|
|
connection is lost unexpectedly.
|
|
|
|
|
|
Add trace file support.
* tracepoint.h (enum trace_stop_reason): New enum.
(struct trace_status): New struct.
(parse_trace_status): Declare.
(struct uploaded_tp): Move here from remote.c,
add fields for actions.
(struct uploaded_tsv): New struct.
* tracepoint.c (tfile_ops): New target vector.
(trace_fd): New global.
(tfile_open): New function.
(tfile_close): New function.
(tfile_files_info): New function.
(tfile_get_trace_status): New function.
(tfile_get_traceframe_address): New function.
(tfile_trace_find): New function.
(tfile_fetch_registers): New function.
(tfile_xfer_partial): New function.
(tfile_get_trace_state_variable_value): New function.
(init_tfile_ops): New function.
(_initialize_tracepoint): Call it, add tfile target.
(trace_status): New global.
(current_trace_status): New function.
(trace_running_p): Remove, change all users to get from
current_trace_status()->running.
(get_trace_status): Remove.
(trace_status_command): Call target_get_trace_status directly,
report more detail including tracing stop reasons.
(trace_find_command): Always allow tfind on a file.
(trace_find_pc_command): Ditto.
(trace_find_tracepoint_command): Ditto.
(trace_find_line_command): Ditto.
(trace_find_range_command): Ditto.
(trace_find_outside_command): Ditto.
(trace_frames_offset, cur_offset): Declare as off_t.
(trace_regblock_size): Rename from reg_size, update users.
(parse_trace_status): New function.
(tfile_interp_line): New function.
(disconnect_or_stop_tracing): Ensure current trace
status before asking what to do.
(stop_reason_names): New global.
(trace_save_command): New command.
(get_uploaded_tp): Move here from remote.c.
(find_matching_tracepoint): Ditto.
(merge_uploaded_tracepoints): New function.
(parse_trace_status): Use stop_reason_names.
(_initialize_tracepoint): Define tsave command.
* target.h (target_ops): New fields to_save_trace_data,
to_upload_tracepoints, to_upload_trace_state_variables,
to_get_raw_trace_data, change to_get_trace_status
to take a pointer to a status struct.
(target_save_trace_data): New macro.
(target_upload_tracepoints): New macro.
(target_upload_trace_state_variables): New macro.
(target_get_raw_trace_data): New macro.
* target.c (update_current_target): Add new methods, change
signature of to_get_trace_status.
* remote.c (hex2bin): Make globally visible.
(bin2hex): Ditto.
(remote_download_trace_state_variable): Download name also.
(remote_get_trace_status): Update parameter, use
parse_trace_status.
(remote_save_trace_data): New function.
(remote_upload_tracepoints): New function.
(remote_upload_trace_state_variables): New function.
(remote_get_raw_trace_data): New function.
(remote_start_remote): Use them.
(_initialize_remote_ops): Add operations.
* ax-gdb.c: Include breakpoint.h.
* breakpoint.c (create_tracepoint_from_upload): Use
break_command_really, return tracepoint, warn about unimplemented
parts.
* NEWS: Mention trace file addition.
* gdb.texinfo (Trace Files): New section.
(Tracepoint Packets): Document QTSave and qTBuffer.
(Trace File Format): New appendix.
* generic/gdbtk-bp.c (gdb_trace_status): Use current_trace_status.
* gdb.trace/tfile.c: New file.
* gdb.trace/tfile.exp: New file.
2010-01-16 06:37:20 +08:00
|
|
|
** Trace files
|
|
|
|
|
|
|
|
|
|
GDB now has the ability to save the trace buffer into a file, and
|
|
|
|
|
then use that file as a target, similarly to you can do with
|
|
|
|
|
corefiles. You can select trace frames, print data that was
|
|
|
|
|
collected in them, and use tstatus to display the state of the
|
|
|
|
|
tracing run at the moment that it was saved. To create a trace
|
|
|
|
|
file, use "tsave <filename>", and to use it, do "target tfile
|
|
|
|
|
<name>".
|
2010-03-19 05:23:35 +08:00
|
|
|
|
|
|
|
|
** Circular trace buffer
|
|
|
|
|
|
|
|
|
|
You can ask the target agent to handle the trace buffer as a
|
|
|
|
|
circular buffer, discarding the oldest trace frames to make room for
|
|
|
|
|
newer ones, by setting circular-trace-buffer to on. This feature may
|
|
|
|
|
not be available for all target agents.
|
|
|
|
|
|
2009-11-24 02:44:11 +08:00
|
|
|
* Changed commands
|
|
|
|
|
|
|
|
|
|
disassemble
|
|
|
|
|
The disassemble command, when invoked with two arguments, now requires
|
|
|
|
|
the arguments to be comma-separated.
|
|
|
|
|
|
2009-12-29 05:29:53 +08:00
|
|
|
info variables
|
|
|
|
|
The info variables command now displays variable definitions. Files
|
|
|
|
|
which only declare a variable are not shown.
|
|
|
|
|
|
2010-01-19 18:19:22 +08:00
|
|
|
source
|
|
|
|
|
The source command is now capable of sourcing Python scripts.
|
|
|
|
|
This feature is dependent on the debugger being build with Python
|
|
|
|
|
support.
|
|
|
|
|
|
|
|
|
|
Related to this enhancement is also the introduction of a new command
|
|
|
|
|
"set script-extension" (see below).
|
|
|
|
|
|
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
Add base multi-executable/process support to GDB.
gdb/
* Makefile.in (SFILES): Add progspace.c.
(COMMON_OBS): Add progspace.o.
* progspace.h: New.
* progspace.c: New.
* breakpoint.h (struct bp_target_info) <placed_address_space>: New
field.
(struct bp_location) <pspace>: New field.
(struct breakpoint) <pspace>: New field.
(bpstat_stop_status, breakpoint_here_p)
(moribund_breakpoint_here_p, breakpoint_inserted_here_p)
(regular_breakpoint_inserted_here_p)
(software_breakpoint_inserted_here_p, breakpoint_thread_match)
(set_default_breakpoint): Adjust prototypes.
(remove_breakpoints_pid, breakpoint_program_space_exit): Declare.
(insert_single_step_breakpoint, deprecated_insert_raw_breakpoint):
Adjust prototypes.
* breakpoint.c (executing_startup): Delete.
(default_breakpoint_sspace): New.
(breakpoint_restore_shadows): Skip if the address space doesn't
match.
(update_watchpoint): Record the frame's program space in the
breakpoint location.
(insert_bp_location): Record the address space in target_info.
Adjust to pass the symbol space to solib_name_from_address.
(breakpoint_program_space_exit): New.
(insert_breakpoint_locations): Switch the symbol space and thread
when inserting breakpoints. Don't insert breakpoints in a vfork
parent waiting for vfork done if we're not attached to the vfork
child.
(remove_breakpoints_pid): New.
(reattach_breakpoints): Switch to a thread of PID. Ignore
breakpoints of other symbol spaces.
(create_internal_breakpoint): Store the symbol space in the sal.
(create_longjmp_master_breakpoint): Iterate over all symbol
spaces.
(update_breakpoints_after_exec): Ignore breakpoints for other
symbol spaces.
(remove_breakpoint): Rename to ...
(remove_breakpoint_1): ... this. Pass the breakpoints symbol
space to solib_name_from_address.
(remove_breakpoint): New.
(mark_breakpoints_out): Ignore breakpoints from other symbol
spaces.
(breakpoint_init_inferior): Ditto.
(breakpoint_here_p): Add an address space argument and adjust to
use breakpoint_address_match.
(moribund_breakpoint_here_p): Ditto.
(regular_breakpoint_inserted_here_p): Ditto.
(breakpoint_inserted_here_p): Ditto.
(software_breakpoint_inserted_here_p): Ditto.
(breakpoint_thread_match): Ditto.
(bpstat_check_location): Ditto.
(bpstat_stop_status): Ditto.
(print_breakpoint_location): If there's a location to print,
switch the current symbol space.
(print_one_breakpoint_location): Add `allflag' argument.
(print_one_breakpoint): Ditto. Adjust.
(do_captured_breakpoint_query): Adjust.
(breakpoint_1): Adjust.
(breakpoint_has_pc): Also match the symbol space.
(describe_other_breakpoints): Add a symbol space argument and
adjust.
(set_default_breakpoint): Add a symbol space argument. Set
default_breakpoint_sspace.
(breakpoint_address_match): New.
(check_duplicates_for): Add an address space argument, and adjust.
(set_raw_breakpoint): Record the symbol space in the location and
in the breakpoint.
(set_longjmp_breakpoint): Skip longjmp master breakpoints from
other symbol spaces.
(remove_thread_event_breakpoints, remove_solib_event_breakpoints)
(disable_breakpoints_in_shlibs): Skip breakpoints from other
symbol spaces.
(disable_breakpoints_in_unloaded_shlib): Match symbol spaces.
(create_catchpoint): Set the symbol space in the sal.
(disable_breakpoints_before_startup): Skip breakpoints from other
symbol spaces. Set executing_startup in the current symbol space.
(enable_breakpoints_after_startup): Clear executing_startup in the
current symbol space. Skip breakpoints from other symbol spaces.
(clone_momentary_breakpoint): Also copy the symbol space.
(add_location_to_breakpoint): Set the location's symbol space.
(bp_loc_is_permanent): Switch thread and symbol space.
(create_breakpoint): Adjust.
(expand_line_sal_maybe): Expand comment to mention symbol spaces.
Switch thread and symbol space when reading memory.
(parse_breakpoint_sals): Set the symbol space in the sal.
(break_command_really): Ditto.
(skip_prologue_sal): Switch and space.
(resolve_sal_pc): Ditto.
(watch_command_1): Record the symbol space in the sal.
(create_ada_exception_breakpoint): Adjust.
(clear_command): Adjust. Match symbol spaces.
(update_global_location_list): Use breakpoint_address_match.
(breakpoint_re_set_one): Switch thread and space.
(breakpoint_re_set): Save symbol space.
(breakpoint_re_set_thread): Also reset the symbol space.
(deprecated_insert_raw_breakpoint): Add an address space argument.
Adjust.
(insert_single_step_breakpoint): Ditto.
(single_step_breakpoint_inserted_here_p): Ditto.
(clear_syscall_counts): New.
(_initialize_breakpoint): Install it as inferior_exit observer.
* exec.h: Include "progspace.h".
(exec_bfd, exec_bfd_mtime): New defines.
(exec_close): Declare.
* exec.c: Include "gdbthread.h" and "progspace.h".
(exec_bfd, exec_bfd_mtime, current_target_sections_1): Delete.
(using_exec_ops): New.
(exec_close_1): Rename to exec_close, and make public.
(exec_close): Rename to exec_close_1, and adjust all callers. Add
description. Remove target sections and close executables from
all program spaces.
(exec_file_attach): Add comment.
(add_target_sections): Check on `using_exec_ops' to check if the
target should be pushed.
(remove_target_sections): Only unpush the target if there are no
more target sections in any symbol space.
* gdbcore.h: Include "exec.h".
(exec_bfd, exec_bfd_mtime): Remove declarations.
* frame.h (get_frame_program_space, get_frame_address_space)
(frame_unwind_program_space): Declare.
* frame.c (struct frame_info) <pspace, aspace>: New fields.
(create_sentinel_frame): Add program space argument. Set the
pspace and aspace fields of the frame object.
(get_current_frame, create_new_frame): Adjust.
(get_frame_program_space): New.
(frame_unwind_program_space): New.
(get_frame_address_space): New.
* stack.c (print_frame_info): Adjust.
(print_frame): Use the frame's program space.
* gdbthread.h (any_live_thread_of_process): Declare.
* thread.c (any_live_thread_of_process): New.
(switch_to_thread): Switch the program space as well.
(restore_selected_frame): Don't warn if trying to restore frame
level 0.
* inferior.h: Include "progspace.h".
(detach_fork): Declare.
(struct inferior) <removable, aspace, pspace>
<vfork_parent, vfork_child, pending_detach>
<waiting_for_vfork_done>: New fields.
<terminal_info>: Remove field.
<data, num_data>: New fields.
(register_inferior_data, register_inferior_data_with_cleanup)
(clear_inferior_data, set_inferior_data, inferior_data): Declare.
(exit_inferior, exit_inferior_silent, exit_inferior_num_silent)
(inferior_appeared): Declare.
(find_inferior_pid): Typo.
(find_inferior_id, find_inferior_for_program_space): Declare.
(set_current_inferior, save_current_inferior, prune_inferiors)
(number_of_inferiors): Declare.
(inferior_list): Declare.
* inferior.c: Include "gdbcore.h" and "symfile.h".
(inferior_list): Make public.
(delete_inferior_1): Always delete thread silently.
(find_inferior_id): Make public.
(current_inferior_): New.
(current_inferior): Use it.
(set_current_inferior): New.
(restore_inferior): New.
(save_current_inferior): New.
(free_inferior): Free the per-inferior data.
(add_inferior_silent): Allocate per-inferior data.
Call inferior_appeared.
(delete_threads_of_inferior): New.
(delete_inferior_1): Adjust interface to take an inferior pointer.
(delete_inferior): Adjust.
(delete_inferior_silent): Adjust.
(exit_inferior_1): New.
(exit_inferior): New.
(exit_inferior_silent): New.
(exit_inferior_num_silent): New.
(detach_inferior): Adjust.
(inferior_appeared): New.
(discard_all_inferiors): Adjust.
(find_inferior_id): Make public. Assert pid is not zero.
(find_inferior_for_program_space): New.
(have_inferiors): Check if we have any inferior with pid not zero.
(have_live_inferiors): Go over all pushed targets looking for
process_stratum.
(prune_inferiors): New.
(number_of_inferiors): New.
(print_inferior): Add executable column. Print vfork parent/child
relationships.
(inferior_command): Adjust to cope with not running inferiors.
(remove_inferior_command): New.
(add_inferior_command): New.
(clone_inferior_command): New.
(struct inferior_data): New.
(struct inferior_data_registration): New.
(struct inferior_data_registry): New.
(inferior_data_registry): New.
(register_inferior_data_with_cleanup): New.
(register_inferior_data): New.
(inferior_alloc_data): New.
(inferior_free_data): New.
(clear_inferior_data): New.
(set_inferior_data): New.
(inferior_data): New.
(initialize_inferiors): New.
(_initialize_inferiors): Register "add-inferior",
"remove-inferior" and "clone-inferior" commands.
* objfiles.h: Include "progspace.h".
(struct objfile) <pspace>: New field.
(symfile_objfile, object_files): Don't declare.
(ALL_PSPACE_OBJFILES): New.
(ALL_PSPACE_OBJFILES_SAFE): New.
(ALL_OBJFILES, ALL_OBJFILES_SAFE): Adjust.
(ALL_PSPACE_SYMTABS): New.
(ALL_PRIMARY_SYMTABS): Adjust.
(ALL_PSPACE_PRIMARY_SYMTABS): New.
(ALL_PSYMTABS): Adjust.
(ALL_PSPACE_PSYMTABS): New.
* objfiles.c (object_files, symfile_objfile): Delete.
(struct objfile_sspace_info): New.
(objfiles_pspace_data): New.
(objfiles_pspace_data_cleanup): New.
(get_objfile_pspace_data): New.
(objfiles_changed_p): Delete.
(allocate_objfile): Set the objfile's program space. Adjust to
reference objfiles_changed_p in pspace data.
(free_objfile): Adjust to reference objfiles_changed_p in pspace
data.
(objfile_relocate): Ditto.
(update_section_map): Add pspace argument. Adjust to iterate over
objfiles in the passed in pspace.
(find_pc_section): Delete sections and num_sections statics.
Adjust to refer to program space's objfiles_changed_p. Adjust to
refer to sections and num_sections store in the objfile's pspace
data.
(objfiles_changed): Adjust to reference objfiles_changed_p in
pspace data.
(_initialize_objfiles): New.
* linespec.c (decode_all_digits, decode_dollar): Set the sal's
program space.
* source.c (current_source_pspace): New.
(get_current_source_symtab_and_line): Set the sal's program space.
(set_current_source_symtab_and_line): Set current_source_pspace.
(select_source_symtab): Ditto. Use ALL_OBJFILES.
(forget_cached_source_info): Iterate over all program spaces.
* symfile.c (clear_symtab_users): Adjust.
* symmisc.c (print_symbol_bcache_statistics): Iterate over all
program spaces.
(print_objfile_statistics): Ditto.
(maintenance_print_msymbols): Ditto.
(maintenance_print_objfiles): Ditto.
(maintenance_info_symtabs): Ditto.
(maintenance_info_psymtabs): Ditto.
* symtab.h (SYMTAB_PSPACE): New.
(struct symtab_and_line) <pspace>: New field.
* symtab.c (init_sal): Clear the sal's program space.
(find_pc_sect_symtab): Set the sal's program space. Switch thread
and space.
(append_expanded_sal): Add program space argument. Iterate over
all program spaces.
(expand_line_sal): Iterate over all program spaces. Switch
program space.
* target.h (enum target_waitkind) <TARGET_WAITKIND_VFORK_DONE>: New.
(struct target_ops) <to_thread_address_space>: New field.
(target_thread_address_space): Define.
* target.c (target_detach): Only remove breakpoints from the
inferior we're detaching.
(target_thread_address_space): New.
* defs.h (initialize_progspace): Declare.
* top.c (gdb_init): Call it.
* solist.h (struct so_list) <sspace>: New field.
* solib.h (struct program_space): Forward declare.
(solib_name_from_address): Adjust prototype.
* solib.c (so_list_head): Replace with a macro referencing the
program space.
(update_solib_list): Set the so's program space.
(solib_name_from_address): Add a program space argument and adjust.
* solib-svr4.c (struct svr4_info) <pid>: Delete field.
<interp_text_sect_low, interp_text_sect_high, interp_plt_sect_low>
<interp_plt_sect_high>: New fields.
(svr4_info_p, svr4_info): Delete.
(solib_svr4_sspace_data): New.
(get_svr4_info): Rewrite.
(svr4_sspace_data_cleanup): New.
(open_symbol_file_object): Adjust.
(svr4_default_sos): Adjust.
(svr4_fetch_objfile_link_map): Adjust.
(interp_text_sect_low, interp_text_sect_high, interp_plt_sect_low)
(interp_plt_sect_high): Delete.
(svr4_in_dynsym_resolve_code): Adjust.
(enable_break): Adjust.
(svr4_clear_solib): Revert bit that removed the svr4_info here,
and reinstate clearing debug_base, debug_loader_offset_p,
debug_loader_offset and debug_loader_name.
(_initialize_svr4_solib): Register solib_svr4_pspace_data. Don't
install an inferior_exit observer anymore.
* printcmd.c (struct display) <pspace>: New field.
(display_command): Set the display's sspace.
(do_one_display): Match the display's sspace.
(display_uses_solib_p): Ditto.
* linux-fork.c (detach_fork): Moved to infrun.c.
(_initialize_linux_fork): Moved "detach-on-fork" command to
infrun.c.
* infrun.c (detach_fork): Moved from linux-fork.c.
(proceed_after_vfork_done): New.
(handle_vfork_child_exec_or_exit): New.
(follow_exec_mode_replace, follow_exec_mode_keep)
(follow_exec_mode_names, follow_exec_mode_string)
(show_follow_exec_mode_string): New.
(follow_exec): New. Reinstate the mark_breakpoints_out call.
Remove shared libraries before attaching new executable. If user
wants to keep the inferior, keep it.
(displaced_step_fixup): Adjust to pass an address space to the
breakpoints module.
(resume): Ditto.
(clear_proceed_status): In all-stop mode, always clear the proceed
status of all threads.
(prepare_to_proceed): Adjust to pass an address space to the
breakpoints module.
(proceed): Ditto.
(adjust_pc_after_break): Ditto.
(handle_inferior_event): When handling a process exit, switch the
program space to the inferior's that had exited. Call
handle_vfork_child_exec_or_exit. Adjust to pass an address space
to the breakpoints module. In non-stop mode, when following a
fork and detach-fork is off, also resume the other branch. Handle
TARGET_WAITKIND_VFORK_DONE. Set the program space in sals.
(normal_stop): Prune inferiors.
(_initialize_infrun): Install the new "follow-exec-mode" command.
"detach-on-fork" moved here.
* regcache.h (get_regcache_aspace): Declare.
* regcache.c (struct regcache) <aspace>: New field.
(regcache_xmalloc): Clear the aspace.
(get_regcache_aspace): New.
(regcache_cpy): Copy the aspace field.
(regcache_cpy_no_passthrough): Ditto.
(get_thread_regcache): Fetch the thread's address space from the
target, and store it in the regcache.
* infcall.c (call_function_by_hand): Set the sal's pspace.
* arch-utils.c (default_has_shared_address_space): New.
* arch-utils.h (default_has_shared_address_space): Declare.
* gdbarch.sh (has_shared_address_space): New.
* gdbarch.h, gdbarch.c: Regenerate.
* linux-tdep.c: Include auxv.h, target.h, elf/common.h.
(linux_has_shared_address_space): New.
(_initialize_linux_tdep): Declare.
* arm-tdep.c (arm_software_single_step): Pass the frame's address
space to insert_single_step_breakpoint.
* arm-linux-tdep.c (arm_linux_software_single_step): Pass the
frame's pspace to breakpoint functions.
* cris-tdep.c (crisv32_single_step_through_delay): Ditto.
(cris_software_single_step): Ditto.
* mips-tdep.c (deal_with_atomic_sequence): Add frame argument.
Pass the frame's pspace to breakpoint functions.
(mips_software_single_step): Adjust.
(mips_single_step_through_delay): Adjust.
* rs6000-aix-tdep.c (rs6000_software_single_step): Adjust.
* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Adjust.
* solib-irix.c (enable_break): Adjust to pass the current frame's
address space to breakpoint functions.
* sparc-tdep.c (sparc_software_single_step): Ditto.
* spu-tdep.c (spu_software_single_step): Ditto.
* alpha-tdep.c (alpha_software_single_step): Ditto.
* record.c (record_wait): Adjust to pass an address space to the
breakpoints module.
* fork-child.c (fork_inferior): Set the new inferior's program and
address spaces.
* inf-ptrace.c (inf_ptrace_follow_fork): Copy the parent's program
and address spaces.
(inf_ptrace_attach): Set the inferior's program and address spaces.
* linux-nat.c: Include "solib.h".
(linux_child_follow_fork): Manage parent and child's program and
address spaces. Clone the parent's program space if necessary.
Don't wait for the vfork to be done here. Refuse to resume if
following the vfork parent while leaving the child stopped.
(resume_callback): Don't resume a vfork parent.
(linux_nat_resume): Also check for pending events in the
lp->waitstatus field.
(linux_handle_extended_wait): Report TARGET_WAITKIND_VFORK_DONE
events to the core.
(stop_wait_callback): Don't wait for SIGSTOP on vfork parents.
(cancel_breakpoint): Adjust.
* linux-thread-db.c (thread_db_wait): Don't remove thread event
breakpoints here.
(thread_db_mourn_inferior): Don't mark breakpoints out here.
Remove thread event breakpoints after mourning.
* corelow.c: Include progspace.h.
(core_open): Set the inferior's program and address spaces.
* remote.c (remote_add_inferior): Set the new inferior's program
and address spaces.
(remote_start_remote): Update address spaces.
(extended_remote_create_inferior_1): Don't init the thread list if
we already debugging other inferiors.
* darwin-nat.c (darwin_attach): Set the new inferior's program and
address spaces.
* gnu-nat.c (gnu_attach): Ditto.
* go32-nat.c (go32_create_inferior): Ditto.
* inf-ttrace.c (inf_ttrace_follow_fork, inf_ttrace_attach): Ditto.
* monitor.c (monitor_open): Ditto.
* nto-procfs.c (procfs_attach, procfs_create_inferior): Ditto.
* procfs.c (do_attach): Ditto.
* windows-nat.c (do_initial_windows_stuff): Ditto.
* inflow.c (inferior_process_group)
(terminal_init_inferior_with_pgrp, terminal_inferior,
(terminal_ours_1, inflow_inferior_exit, copy_terminal_info)
(child_terminal_info, new_tty_postfork, set_sigint_trap): Adjust
to use per-inferior data instead of inferior->terminal_info.
(inflow_inferior_data): New.
(inflow_new_inferior): Delete.
(inflow_inferior_data_cleanup): New.
(get_inflow_inferior_data): New.
* mi/mi-interp.c (mi_new_inferior): Rename to...
(mi_inferior_appeared): ... this.
(mi_interpreter_init): Adjust.
* tui/tui-disasm.c: Include "progspace.h".
(tui_set_disassem_content): Pass an address space to
breakpoint_here_p.
* NEWS: Mention multi-program debugging support. Mention new
commands "add-inferior", "clone-inferior", "remove-inferior",
"maint info program-spaces", and new option "set
follow-exec-mode".
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/doc/
* observer.texi (new_inferior): Rename to...
(inferior_appeared): ... this.
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/testsuite/
* gdb.base/foll-vfork.exp: Adjust to spell out "follow-fork".
* gdb.base/foll-exec.exp: Adjust to expect a process id before
"Executing new program".
* gdb.base/foll-fork.exp: Adjust to spell out "follow-fork".
* gdb.base/multi-forks.exp: Ditto. Adjust to the inferior being
left listed after having been killed.
* gdb.base/attach.exp: Adjust to spell out "symbol-file".
* gdb.base/maint.exp: Adjust test.
* Makefile.in (ALL_SUBDIRS): Add gdb.multi.
* gdb.multi/Makefile.in: New.
* gdb.multi/base.exp: New.
* gdb.multi/goodbye.c: New.
* gdb.multi/hangout.c: New.
* gdb.multi/hello.c: New.
* gdb.multi/bkpt-multi-exec.c: New.
* gdb.multi/bkpt-multi-exec.exp: New.
* gdb.multi/crashme.c: New.
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/doc/
* gdb.texinfo (Inferiors): Rename node to ...
(Inferiors and Programs): ... this. Mention running multiple
programs in the same debug session.
<info inferiors>: Mention the new 'Executable' column if "info
inferiors". Update examples. Document the "add-inferior",
"clone-inferior", "remove-inferior" and "maint info
program-spaces" commands.
(Process): Rename node to...
(Forks): ... this. Document "set|show follow-exec-mode".
2009-10-19 17:51:43 +08:00
|
|
|
* New commands (for set/show, see "New options" below)
|
|
|
|
|
|
2009-11-02 05:20:18 +08:00
|
|
|
record save [<FILENAME>]
|
|
|
|
|
Save a file (in core file format) containing the process record
|
|
|
|
|
execution log for replay debugging at a later time.
|
|
|
|
|
|
|
|
|
|
record restore <FILENAME>
|
|
|
|
|
Restore the process record execution log that was saved at an
|
|
|
|
|
earlier time, for replay debugging.
|
|
|
|
|
|
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
Add base multi-executable/process support to GDB.
gdb/
* Makefile.in (SFILES): Add progspace.c.
(COMMON_OBS): Add progspace.o.
* progspace.h: New.
* progspace.c: New.
* breakpoint.h (struct bp_target_info) <placed_address_space>: New
field.
(struct bp_location) <pspace>: New field.
(struct breakpoint) <pspace>: New field.
(bpstat_stop_status, breakpoint_here_p)
(moribund_breakpoint_here_p, breakpoint_inserted_here_p)
(regular_breakpoint_inserted_here_p)
(software_breakpoint_inserted_here_p, breakpoint_thread_match)
(set_default_breakpoint): Adjust prototypes.
(remove_breakpoints_pid, breakpoint_program_space_exit): Declare.
(insert_single_step_breakpoint, deprecated_insert_raw_breakpoint):
Adjust prototypes.
* breakpoint.c (executing_startup): Delete.
(default_breakpoint_sspace): New.
(breakpoint_restore_shadows): Skip if the address space doesn't
match.
(update_watchpoint): Record the frame's program space in the
breakpoint location.
(insert_bp_location): Record the address space in target_info.
Adjust to pass the symbol space to solib_name_from_address.
(breakpoint_program_space_exit): New.
(insert_breakpoint_locations): Switch the symbol space and thread
when inserting breakpoints. Don't insert breakpoints in a vfork
parent waiting for vfork done if we're not attached to the vfork
child.
(remove_breakpoints_pid): New.
(reattach_breakpoints): Switch to a thread of PID. Ignore
breakpoints of other symbol spaces.
(create_internal_breakpoint): Store the symbol space in the sal.
(create_longjmp_master_breakpoint): Iterate over all symbol
spaces.
(update_breakpoints_after_exec): Ignore breakpoints for other
symbol spaces.
(remove_breakpoint): Rename to ...
(remove_breakpoint_1): ... this. Pass the breakpoints symbol
space to solib_name_from_address.
(remove_breakpoint): New.
(mark_breakpoints_out): Ignore breakpoints from other symbol
spaces.
(breakpoint_init_inferior): Ditto.
(breakpoint_here_p): Add an address space argument and adjust to
use breakpoint_address_match.
(moribund_breakpoint_here_p): Ditto.
(regular_breakpoint_inserted_here_p): Ditto.
(breakpoint_inserted_here_p): Ditto.
(software_breakpoint_inserted_here_p): Ditto.
(breakpoint_thread_match): Ditto.
(bpstat_check_location): Ditto.
(bpstat_stop_status): Ditto.
(print_breakpoint_location): If there's a location to print,
switch the current symbol space.
(print_one_breakpoint_location): Add `allflag' argument.
(print_one_breakpoint): Ditto. Adjust.
(do_captured_breakpoint_query): Adjust.
(breakpoint_1): Adjust.
(breakpoint_has_pc): Also match the symbol space.
(describe_other_breakpoints): Add a symbol space argument and
adjust.
(set_default_breakpoint): Add a symbol space argument. Set
default_breakpoint_sspace.
(breakpoint_address_match): New.
(check_duplicates_for): Add an address space argument, and adjust.
(set_raw_breakpoint): Record the symbol space in the location and
in the breakpoint.
(set_longjmp_breakpoint): Skip longjmp master breakpoints from
other symbol spaces.
(remove_thread_event_breakpoints, remove_solib_event_breakpoints)
(disable_breakpoints_in_shlibs): Skip breakpoints from other
symbol spaces.
(disable_breakpoints_in_unloaded_shlib): Match symbol spaces.
(create_catchpoint): Set the symbol space in the sal.
(disable_breakpoints_before_startup): Skip breakpoints from other
symbol spaces. Set executing_startup in the current symbol space.
(enable_breakpoints_after_startup): Clear executing_startup in the
current symbol space. Skip breakpoints from other symbol spaces.
(clone_momentary_breakpoint): Also copy the symbol space.
(add_location_to_breakpoint): Set the location's symbol space.
(bp_loc_is_permanent): Switch thread and symbol space.
(create_breakpoint): Adjust.
(expand_line_sal_maybe): Expand comment to mention symbol spaces.
Switch thread and symbol space when reading memory.
(parse_breakpoint_sals): Set the symbol space in the sal.
(break_command_really): Ditto.
(skip_prologue_sal): Switch and space.
(resolve_sal_pc): Ditto.
(watch_command_1): Record the symbol space in the sal.
(create_ada_exception_breakpoint): Adjust.
(clear_command): Adjust. Match symbol spaces.
(update_global_location_list): Use breakpoint_address_match.
(breakpoint_re_set_one): Switch thread and space.
(breakpoint_re_set): Save symbol space.
(breakpoint_re_set_thread): Also reset the symbol space.
(deprecated_insert_raw_breakpoint): Add an address space argument.
Adjust.
(insert_single_step_breakpoint): Ditto.
(single_step_breakpoint_inserted_here_p): Ditto.
(clear_syscall_counts): New.
(_initialize_breakpoint): Install it as inferior_exit observer.
* exec.h: Include "progspace.h".
(exec_bfd, exec_bfd_mtime): New defines.
(exec_close): Declare.
* exec.c: Include "gdbthread.h" and "progspace.h".
(exec_bfd, exec_bfd_mtime, current_target_sections_1): Delete.
(using_exec_ops): New.
(exec_close_1): Rename to exec_close, and make public.
(exec_close): Rename to exec_close_1, and adjust all callers. Add
description. Remove target sections and close executables from
all program spaces.
(exec_file_attach): Add comment.
(add_target_sections): Check on `using_exec_ops' to check if the
target should be pushed.
(remove_target_sections): Only unpush the target if there are no
more target sections in any symbol space.
* gdbcore.h: Include "exec.h".
(exec_bfd, exec_bfd_mtime): Remove declarations.
* frame.h (get_frame_program_space, get_frame_address_space)
(frame_unwind_program_space): Declare.
* frame.c (struct frame_info) <pspace, aspace>: New fields.
(create_sentinel_frame): Add program space argument. Set the
pspace and aspace fields of the frame object.
(get_current_frame, create_new_frame): Adjust.
(get_frame_program_space): New.
(frame_unwind_program_space): New.
(get_frame_address_space): New.
* stack.c (print_frame_info): Adjust.
(print_frame): Use the frame's program space.
* gdbthread.h (any_live_thread_of_process): Declare.
* thread.c (any_live_thread_of_process): New.
(switch_to_thread): Switch the program space as well.
(restore_selected_frame): Don't warn if trying to restore frame
level 0.
* inferior.h: Include "progspace.h".
(detach_fork): Declare.
(struct inferior) <removable, aspace, pspace>
<vfork_parent, vfork_child, pending_detach>
<waiting_for_vfork_done>: New fields.
<terminal_info>: Remove field.
<data, num_data>: New fields.
(register_inferior_data, register_inferior_data_with_cleanup)
(clear_inferior_data, set_inferior_data, inferior_data): Declare.
(exit_inferior, exit_inferior_silent, exit_inferior_num_silent)
(inferior_appeared): Declare.
(find_inferior_pid): Typo.
(find_inferior_id, find_inferior_for_program_space): Declare.
(set_current_inferior, save_current_inferior, prune_inferiors)
(number_of_inferiors): Declare.
(inferior_list): Declare.
* inferior.c: Include "gdbcore.h" and "symfile.h".
(inferior_list): Make public.
(delete_inferior_1): Always delete thread silently.
(find_inferior_id): Make public.
(current_inferior_): New.
(current_inferior): Use it.
(set_current_inferior): New.
(restore_inferior): New.
(save_current_inferior): New.
(free_inferior): Free the per-inferior data.
(add_inferior_silent): Allocate per-inferior data.
Call inferior_appeared.
(delete_threads_of_inferior): New.
(delete_inferior_1): Adjust interface to take an inferior pointer.
(delete_inferior): Adjust.
(delete_inferior_silent): Adjust.
(exit_inferior_1): New.
(exit_inferior): New.
(exit_inferior_silent): New.
(exit_inferior_num_silent): New.
(detach_inferior): Adjust.
(inferior_appeared): New.
(discard_all_inferiors): Adjust.
(find_inferior_id): Make public. Assert pid is not zero.
(find_inferior_for_program_space): New.
(have_inferiors): Check if we have any inferior with pid not zero.
(have_live_inferiors): Go over all pushed targets looking for
process_stratum.
(prune_inferiors): New.
(number_of_inferiors): New.
(print_inferior): Add executable column. Print vfork parent/child
relationships.
(inferior_command): Adjust to cope with not running inferiors.
(remove_inferior_command): New.
(add_inferior_command): New.
(clone_inferior_command): New.
(struct inferior_data): New.
(struct inferior_data_registration): New.
(struct inferior_data_registry): New.
(inferior_data_registry): New.
(register_inferior_data_with_cleanup): New.
(register_inferior_data): New.
(inferior_alloc_data): New.
(inferior_free_data): New.
(clear_inferior_data): New.
(set_inferior_data): New.
(inferior_data): New.
(initialize_inferiors): New.
(_initialize_inferiors): Register "add-inferior",
"remove-inferior" and "clone-inferior" commands.
* objfiles.h: Include "progspace.h".
(struct objfile) <pspace>: New field.
(symfile_objfile, object_files): Don't declare.
(ALL_PSPACE_OBJFILES): New.
(ALL_PSPACE_OBJFILES_SAFE): New.
(ALL_OBJFILES, ALL_OBJFILES_SAFE): Adjust.
(ALL_PSPACE_SYMTABS): New.
(ALL_PRIMARY_SYMTABS): Adjust.
(ALL_PSPACE_PRIMARY_SYMTABS): New.
(ALL_PSYMTABS): Adjust.
(ALL_PSPACE_PSYMTABS): New.
* objfiles.c (object_files, symfile_objfile): Delete.
(struct objfile_sspace_info): New.
(objfiles_pspace_data): New.
(objfiles_pspace_data_cleanup): New.
(get_objfile_pspace_data): New.
(objfiles_changed_p): Delete.
(allocate_objfile): Set the objfile's program space. Adjust to
reference objfiles_changed_p in pspace data.
(free_objfile): Adjust to reference objfiles_changed_p in pspace
data.
(objfile_relocate): Ditto.
(update_section_map): Add pspace argument. Adjust to iterate over
objfiles in the passed in pspace.
(find_pc_section): Delete sections and num_sections statics.
Adjust to refer to program space's objfiles_changed_p. Adjust to
refer to sections and num_sections store in the objfile's pspace
data.
(objfiles_changed): Adjust to reference objfiles_changed_p in
pspace data.
(_initialize_objfiles): New.
* linespec.c (decode_all_digits, decode_dollar): Set the sal's
program space.
* source.c (current_source_pspace): New.
(get_current_source_symtab_and_line): Set the sal's program space.
(set_current_source_symtab_and_line): Set current_source_pspace.
(select_source_symtab): Ditto. Use ALL_OBJFILES.
(forget_cached_source_info): Iterate over all program spaces.
* symfile.c (clear_symtab_users): Adjust.
* symmisc.c (print_symbol_bcache_statistics): Iterate over all
program spaces.
(print_objfile_statistics): Ditto.
(maintenance_print_msymbols): Ditto.
(maintenance_print_objfiles): Ditto.
(maintenance_info_symtabs): Ditto.
(maintenance_info_psymtabs): Ditto.
* symtab.h (SYMTAB_PSPACE): New.
(struct symtab_and_line) <pspace>: New field.
* symtab.c (init_sal): Clear the sal's program space.
(find_pc_sect_symtab): Set the sal's program space. Switch thread
and space.
(append_expanded_sal): Add program space argument. Iterate over
all program spaces.
(expand_line_sal): Iterate over all program spaces. Switch
program space.
* target.h (enum target_waitkind) <TARGET_WAITKIND_VFORK_DONE>: New.
(struct target_ops) <to_thread_address_space>: New field.
(target_thread_address_space): Define.
* target.c (target_detach): Only remove breakpoints from the
inferior we're detaching.
(target_thread_address_space): New.
* defs.h (initialize_progspace): Declare.
* top.c (gdb_init): Call it.
* solist.h (struct so_list) <sspace>: New field.
* solib.h (struct program_space): Forward declare.
(solib_name_from_address): Adjust prototype.
* solib.c (so_list_head): Replace with a macro referencing the
program space.
(update_solib_list): Set the so's program space.
(solib_name_from_address): Add a program space argument and adjust.
* solib-svr4.c (struct svr4_info) <pid>: Delete field.
<interp_text_sect_low, interp_text_sect_high, interp_plt_sect_low>
<interp_plt_sect_high>: New fields.
(svr4_info_p, svr4_info): Delete.
(solib_svr4_sspace_data): New.
(get_svr4_info): Rewrite.
(svr4_sspace_data_cleanup): New.
(open_symbol_file_object): Adjust.
(svr4_default_sos): Adjust.
(svr4_fetch_objfile_link_map): Adjust.
(interp_text_sect_low, interp_text_sect_high, interp_plt_sect_low)
(interp_plt_sect_high): Delete.
(svr4_in_dynsym_resolve_code): Adjust.
(enable_break): Adjust.
(svr4_clear_solib): Revert bit that removed the svr4_info here,
and reinstate clearing debug_base, debug_loader_offset_p,
debug_loader_offset and debug_loader_name.
(_initialize_svr4_solib): Register solib_svr4_pspace_data. Don't
install an inferior_exit observer anymore.
* printcmd.c (struct display) <pspace>: New field.
(display_command): Set the display's sspace.
(do_one_display): Match the display's sspace.
(display_uses_solib_p): Ditto.
* linux-fork.c (detach_fork): Moved to infrun.c.
(_initialize_linux_fork): Moved "detach-on-fork" command to
infrun.c.
* infrun.c (detach_fork): Moved from linux-fork.c.
(proceed_after_vfork_done): New.
(handle_vfork_child_exec_or_exit): New.
(follow_exec_mode_replace, follow_exec_mode_keep)
(follow_exec_mode_names, follow_exec_mode_string)
(show_follow_exec_mode_string): New.
(follow_exec): New. Reinstate the mark_breakpoints_out call.
Remove shared libraries before attaching new executable. If user
wants to keep the inferior, keep it.
(displaced_step_fixup): Adjust to pass an address space to the
breakpoints module.
(resume): Ditto.
(clear_proceed_status): In all-stop mode, always clear the proceed
status of all threads.
(prepare_to_proceed): Adjust to pass an address space to the
breakpoints module.
(proceed): Ditto.
(adjust_pc_after_break): Ditto.
(handle_inferior_event): When handling a process exit, switch the
program space to the inferior's that had exited. Call
handle_vfork_child_exec_or_exit. Adjust to pass an address space
to the breakpoints module. In non-stop mode, when following a
fork and detach-fork is off, also resume the other branch. Handle
TARGET_WAITKIND_VFORK_DONE. Set the program space in sals.
(normal_stop): Prune inferiors.
(_initialize_infrun): Install the new "follow-exec-mode" command.
"detach-on-fork" moved here.
* regcache.h (get_regcache_aspace): Declare.
* regcache.c (struct regcache) <aspace>: New field.
(regcache_xmalloc): Clear the aspace.
(get_regcache_aspace): New.
(regcache_cpy): Copy the aspace field.
(regcache_cpy_no_passthrough): Ditto.
(get_thread_regcache): Fetch the thread's address space from the
target, and store it in the regcache.
* infcall.c (call_function_by_hand): Set the sal's pspace.
* arch-utils.c (default_has_shared_address_space): New.
* arch-utils.h (default_has_shared_address_space): Declare.
* gdbarch.sh (has_shared_address_space): New.
* gdbarch.h, gdbarch.c: Regenerate.
* linux-tdep.c: Include auxv.h, target.h, elf/common.h.
(linux_has_shared_address_space): New.
(_initialize_linux_tdep): Declare.
* arm-tdep.c (arm_software_single_step): Pass the frame's address
space to insert_single_step_breakpoint.
* arm-linux-tdep.c (arm_linux_software_single_step): Pass the
frame's pspace to breakpoint functions.
* cris-tdep.c (crisv32_single_step_through_delay): Ditto.
(cris_software_single_step): Ditto.
* mips-tdep.c (deal_with_atomic_sequence): Add frame argument.
Pass the frame's pspace to breakpoint functions.
(mips_software_single_step): Adjust.
(mips_single_step_through_delay): Adjust.
* rs6000-aix-tdep.c (rs6000_software_single_step): Adjust.
* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Adjust.
* solib-irix.c (enable_break): Adjust to pass the current frame's
address space to breakpoint functions.
* sparc-tdep.c (sparc_software_single_step): Ditto.
* spu-tdep.c (spu_software_single_step): Ditto.
* alpha-tdep.c (alpha_software_single_step): Ditto.
* record.c (record_wait): Adjust to pass an address space to the
breakpoints module.
* fork-child.c (fork_inferior): Set the new inferior's program and
address spaces.
* inf-ptrace.c (inf_ptrace_follow_fork): Copy the parent's program
and address spaces.
(inf_ptrace_attach): Set the inferior's program and address spaces.
* linux-nat.c: Include "solib.h".
(linux_child_follow_fork): Manage parent and child's program and
address spaces. Clone the parent's program space if necessary.
Don't wait for the vfork to be done here. Refuse to resume if
following the vfork parent while leaving the child stopped.
(resume_callback): Don't resume a vfork parent.
(linux_nat_resume): Also check for pending events in the
lp->waitstatus field.
(linux_handle_extended_wait): Report TARGET_WAITKIND_VFORK_DONE
events to the core.
(stop_wait_callback): Don't wait for SIGSTOP on vfork parents.
(cancel_breakpoint): Adjust.
* linux-thread-db.c (thread_db_wait): Don't remove thread event
breakpoints here.
(thread_db_mourn_inferior): Don't mark breakpoints out here.
Remove thread event breakpoints after mourning.
* corelow.c: Include progspace.h.
(core_open): Set the inferior's program and address spaces.
* remote.c (remote_add_inferior): Set the new inferior's program
and address spaces.
(remote_start_remote): Update address spaces.
(extended_remote_create_inferior_1): Don't init the thread list if
we already debugging other inferiors.
* darwin-nat.c (darwin_attach): Set the new inferior's program and
address spaces.
* gnu-nat.c (gnu_attach): Ditto.
* go32-nat.c (go32_create_inferior): Ditto.
* inf-ttrace.c (inf_ttrace_follow_fork, inf_ttrace_attach): Ditto.
* monitor.c (monitor_open): Ditto.
* nto-procfs.c (procfs_attach, procfs_create_inferior): Ditto.
* procfs.c (do_attach): Ditto.
* windows-nat.c (do_initial_windows_stuff): Ditto.
* inflow.c (inferior_process_group)
(terminal_init_inferior_with_pgrp, terminal_inferior,
(terminal_ours_1, inflow_inferior_exit, copy_terminal_info)
(child_terminal_info, new_tty_postfork, set_sigint_trap): Adjust
to use per-inferior data instead of inferior->terminal_info.
(inflow_inferior_data): New.
(inflow_new_inferior): Delete.
(inflow_inferior_data_cleanup): New.
(get_inflow_inferior_data): New.
* mi/mi-interp.c (mi_new_inferior): Rename to...
(mi_inferior_appeared): ... this.
(mi_interpreter_init): Adjust.
* tui/tui-disasm.c: Include "progspace.h".
(tui_set_disassem_content): Pass an address space to
breakpoint_here_p.
* NEWS: Mention multi-program debugging support. Mention new
commands "add-inferior", "clone-inferior", "remove-inferior",
"maint info program-spaces", and new option "set
follow-exec-mode".
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/doc/
* observer.texi (new_inferior): Rename to...
(inferior_appeared): ... this.
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/testsuite/
* gdb.base/foll-vfork.exp: Adjust to spell out "follow-fork".
* gdb.base/foll-exec.exp: Adjust to expect a process id before
"Executing new program".
* gdb.base/foll-fork.exp: Adjust to spell out "follow-fork".
* gdb.base/multi-forks.exp: Ditto. Adjust to the inferior being
left listed after having been killed.
* gdb.base/attach.exp: Adjust to spell out "symbol-file".
* gdb.base/maint.exp: Adjust test.
* Makefile.in (ALL_SUBDIRS): Add gdb.multi.
* gdb.multi/Makefile.in: New.
* gdb.multi/base.exp: New.
* gdb.multi/goodbye.c: New.
* gdb.multi/hangout.c: New.
* gdb.multi/hello.c: New.
* gdb.multi/bkpt-multi-exec.c: New.
* gdb.multi/bkpt-multi-exec.exp: New.
* gdb.multi/crashme.c: New.
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/doc/
* gdb.texinfo (Inferiors): Rename node to ...
(Inferiors and Programs): ... this. Mention running multiple
programs in the same debug session.
<info inferiors>: Mention the new 'Executable' column if "info
inferiors". Update examples. Document the "add-inferior",
"clone-inferior", "remove-inferior" and "maint info
program-spaces" commands.
(Process): Rename node to...
(Forks): ... this. Document "set|show follow-exec-mode".
2009-10-19 17:51:43 +08:00
|
|
|
add-inferior [-copies <N>] [-exec <FILENAME>]
|
|
|
|
|
Add a new inferior.
|
|
|
|
|
|
|
|
|
|
clone-inferior [-copies <N>] [ID]
|
|
|
|
|
Make a new inferior ready to execute the same program another
|
|
|
|
|
inferior has loaded.
|
|
|
|
|
|
|
|
|
|
remove-inferior ID
|
|
|
|
|
Remove an inferior.
|
|
|
|
|
|
|
|
|
|
maint info program-spaces
|
|
|
|
|
List the program spaces loaded into GDB.
|
|
|
|
|
|
2009-10-28 23:01:27 +08:00
|
|
|
set remote interrupt-sequence [Ctrl-C | BREAK | BREAK-g]
|
|
|
|
|
show remote interrupt-sequence
|
|
|
|
|
Allow the user to select one of ^C, a BREAK signal or BREAK-g
|
|
|
|
|
as the sequence to the remote target in order to interrupt the execution.
|
|
|
|
|
Ctrl-C is a default. Some system prefers BREAK which is high level of
|
|
|
|
|
serial line for some certain time. Linux kernel prefers BREAK-g, a.k.a
|
|
|
|
|
Magic SysRq g. It is BREAK signal and character 'g'.
|
|
|
|
|
|
|
|
|
|
set remote interrupt-on-connect [on | off]
|
|
|
|
|
show remote interrupt-on-connect
|
|
|
|
|
When interrupt-on-connect is ON, gdb sends interrupt-sequence to
|
|
|
|
|
remote target when gdb connects to it. This is needed when you debug
|
|
|
|
|
Linux kernel.
|
|
|
|
|
|
|
|
|
|
set remotebreak [on | off]
|
|
|
|
|
show remotebreak
|
|
|
|
|
Deprecated. Use "set/show remote interrupt-sequence" instead.
|
|
|
|
|
|
2009-12-29 07:39:10 +08:00
|
|
|
tvariable $NAME [ = EXP ]
|
|
|
|
|
Create or modify a trace state variable.
|
|
|
|
|
|
|
|
|
|
info tvariables
|
|
|
|
|
List trace state variables and their values.
|
|
|
|
|
|
|
|
|
|
delete tvariable $NAME ...
|
|
|
|
|
Delete one or more trace state variables.
|
|
|
|
|
|
2010-01-01 01:47:43 +08:00
|
|
|
teval EXPR, ...
|
|
|
|
|
Evaluate the given expressions without collecting anything into the
|
|
|
|
|
trace buffer. (Valid in tracepoint actions only.)
|
|
|
|
|
|
2010-01-06 12:20:27 +08:00
|
|
|
ftrace FN / FILE:LINE / *ADDR
|
|
|
|
|
Define a fast tracepoint at the given function, line, or address.
|
|
|
|
|
|
2010-01-12 03:29:12 +08:00
|
|
|
* New expression syntax
|
|
|
|
|
|
|
|
|
|
GDB now parses the 0b prefix of binary numbers the same way as GCC does.
|
|
|
|
|
GDB now parses 0b101010 identically with 42.
|
|
|
|
|
|
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
Add base multi-executable/process support to GDB.
gdb/
* Makefile.in (SFILES): Add progspace.c.
(COMMON_OBS): Add progspace.o.
* progspace.h: New.
* progspace.c: New.
* breakpoint.h (struct bp_target_info) <placed_address_space>: New
field.
(struct bp_location) <pspace>: New field.
(struct breakpoint) <pspace>: New field.
(bpstat_stop_status, breakpoint_here_p)
(moribund_breakpoint_here_p, breakpoint_inserted_here_p)
(regular_breakpoint_inserted_here_p)
(software_breakpoint_inserted_here_p, breakpoint_thread_match)
(set_default_breakpoint): Adjust prototypes.
(remove_breakpoints_pid, breakpoint_program_space_exit): Declare.
(insert_single_step_breakpoint, deprecated_insert_raw_breakpoint):
Adjust prototypes.
* breakpoint.c (executing_startup): Delete.
(default_breakpoint_sspace): New.
(breakpoint_restore_shadows): Skip if the address space doesn't
match.
(update_watchpoint): Record the frame's program space in the
breakpoint location.
(insert_bp_location): Record the address space in target_info.
Adjust to pass the symbol space to solib_name_from_address.
(breakpoint_program_space_exit): New.
(insert_breakpoint_locations): Switch the symbol space and thread
when inserting breakpoints. Don't insert breakpoints in a vfork
parent waiting for vfork done if we're not attached to the vfork
child.
(remove_breakpoints_pid): New.
(reattach_breakpoints): Switch to a thread of PID. Ignore
breakpoints of other symbol spaces.
(create_internal_breakpoint): Store the symbol space in the sal.
(create_longjmp_master_breakpoint): Iterate over all symbol
spaces.
(update_breakpoints_after_exec): Ignore breakpoints for other
symbol spaces.
(remove_breakpoint): Rename to ...
(remove_breakpoint_1): ... this. Pass the breakpoints symbol
space to solib_name_from_address.
(remove_breakpoint): New.
(mark_breakpoints_out): Ignore breakpoints from other symbol
spaces.
(breakpoint_init_inferior): Ditto.
(breakpoint_here_p): Add an address space argument and adjust to
use breakpoint_address_match.
(moribund_breakpoint_here_p): Ditto.
(regular_breakpoint_inserted_here_p): Ditto.
(breakpoint_inserted_here_p): Ditto.
(software_breakpoint_inserted_here_p): Ditto.
(breakpoint_thread_match): Ditto.
(bpstat_check_location): Ditto.
(bpstat_stop_status): Ditto.
(print_breakpoint_location): If there's a location to print,
switch the current symbol space.
(print_one_breakpoint_location): Add `allflag' argument.
(print_one_breakpoint): Ditto. Adjust.
(do_captured_breakpoint_query): Adjust.
(breakpoint_1): Adjust.
(breakpoint_has_pc): Also match the symbol space.
(describe_other_breakpoints): Add a symbol space argument and
adjust.
(set_default_breakpoint): Add a symbol space argument. Set
default_breakpoint_sspace.
(breakpoint_address_match): New.
(check_duplicates_for): Add an address space argument, and adjust.
(set_raw_breakpoint): Record the symbol space in the location and
in the breakpoint.
(set_longjmp_breakpoint): Skip longjmp master breakpoints from
other symbol spaces.
(remove_thread_event_breakpoints, remove_solib_event_breakpoints)
(disable_breakpoints_in_shlibs): Skip breakpoints from other
symbol spaces.
(disable_breakpoints_in_unloaded_shlib): Match symbol spaces.
(create_catchpoint): Set the symbol space in the sal.
(disable_breakpoints_before_startup): Skip breakpoints from other
symbol spaces. Set executing_startup in the current symbol space.
(enable_breakpoints_after_startup): Clear executing_startup in the
current symbol space. Skip breakpoints from other symbol spaces.
(clone_momentary_breakpoint): Also copy the symbol space.
(add_location_to_breakpoint): Set the location's symbol space.
(bp_loc_is_permanent): Switch thread and symbol space.
(create_breakpoint): Adjust.
(expand_line_sal_maybe): Expand comment to mention symbol spaces.
Switch thread and symbol space when reading memory.
(parse_breakpoint_sals): Set the symbol space in the sal.
(break_command_really): Ditto.
(skip_prologue_sal): Switch and space.
(resolve_sal_pc): Ditto.
(watch_command_1): Record the symbol space in the sal.
(create_ada_exception_breakpoint): Adjust.
(clear_command): Adjust. Match symbol spaces.
(update_global_location_list): Use breakpoint_address_match.
(breakpoint_re_set_one): Switch thread and space.
(breakpoint_re_set): Save symbol space.
(breakpoint_re_set_thread): Also reset the symbol space.
(deprecated_insert_raw_breakpoint): Add an address space argument.
Adjust.
(insert_single_step_breakpoint): Ditto.
(single_step_breakpoint_inserted_here_p): Ditto.
(clear_syscall_counts): New.
(_initialize_breakpoint): Install it as inferior_exit observer.
* exec.h: Include "progspace.h".
(exec_bfd, exec_bfd_mtime): New defines.
(exec_close): Declare.
* exec.c: Include "gdbthread.h" and "progspace.h".
(exec_bfd, exec_bfd_mtime, current_target_sections_1): Delete.
(using_exec_ops): New.
(exec_close_1): Rename to exec_close, and make public.
(exec_close): Rename to exec_close_1, and adjust all callers. Add
description. Remove target sections and close executables from
all program spaces.
(exec_file_attach): Add comment.
(add_target_sections): Check on `using_exec_ops' to check if the
target should be pushed.
(remove_target_sections): Only unpush the target if there are no
more target sections in any symbol space.
* gdbcore.h: Include "exec.h".
(exec_bfd, exec_bfd_mtime): Remove declarations.
* frame.h (get_frame_program_space, get_frame_address_space)
(frame_unwind_program_space): Declare.
* frame.c (struct frame_info) <pspace, aspace>: New fields.
(create_sentinel_frame): Add program space argument. Set the
pspace and aspace fields of the frame object.
(get_current_frame, create_new_frame): Adjust.
(get_frame_program_space): New.
(frame_unwind_program_space): New.
(get_frame_address_space): New.
* stack.c (print_frame_info): Adjust.
(print_frame): Use the frame's program space.
* gdbthread.h (any_live_thread_of_process): Declare.
* thread.c (any_live_thread_of_process): New.
(switch_to_thread): Switch the program space as well.
(restore_selected_frame): Don't warn if trying to restore frame
level 0.
* inferior.h: Include "progspace.h".
(detach_fork): Declare.
(struct inferior) <removable, aspace, pspace>
<vfork_parent, vfork_child, pending_detach>
<waiting_for_vfork_done>: New fields.
<terminal_info>: Remove field.
<data, num_data>: New fields.
(register_inferior_data, register_inferior_data_with_cleanup)
(clear_inferior_data, set_inferior_data, inferior_data): Declare.
(exit_inferior, exit_inferior_silent, exit_inferior_num_silent)
(inferior_appeared): Declare.
(find_inferior_pid): Typo.
(find_inferior_id, find_inferior_for_program_space): Declare.
(set_current_inferior, save_current_inferior, prune_inferiors)
(number_of_inferiors): Declare.
(inferior_list): Declare.
* inferior.c: Include "gdbcore.h" and "symfile.h".
(inferior_list): Make public.
(delete_inferior_1): Always delete thread silently.
(find_inferior_id): Make public.
(current_inferior_): New.
(current_inferior): Use it.
(set_current_inferior): New.
(restore_inferior): New.
(save_current_inferior): New.
(free_inferior): Free the per-inferior data.
(add_inferior_silent): Allocate per-inferior data.
Call inferior_appeared.
(delete_threads_of_inferior): New.
(delete_inferior_1): Adjust interface to take an inferior pointer.
(delete_inferior): Adjust.
(delete_inferior_silent): Adjust.
(exit_inferior_1): New.
(exit_inferior): New.
(exit_inferior_silent): New.
(exit_inferior_num_silent): New.
(detach_inferior): Adjust.
(inferior_appeared): New.
(discard_all_inferiors): Adjust.
(find_inferior_id): Make public. Assert pid is not zero.
(find_inferior_for_program_space): New.
(have_inferiors): Check if we have any inferior with pid not zero.
(have_live_inferiors): Go over all pushed targets looking for
process_stratum.
(prune_inferiors): New.
(number_of_inferiors): New.
(print_inferior): Add executable column. Print vfork parent/child
relationships.
(inferior_command): Adjust to cope with not running inferiors.
(remove_inferior_command): New.
(add_inferior_command): New.
(clone_inferior_command): New.
(struct inferior_data): New.
(struct inferior_data_registration): New.
(struct inferior_data_registry): New.
(inferior_data_registry): New.
(register_inferior_data_with_cleanup): New.
(register_inferior_data): New.
(inferior_alloc_data): New.
(inferior_free_data): New.
(clear_inferior_data): New.
(set_inferior_data): New.
(inferior_data): New.
(initialize_inferiors): New.
(_initialize_inferiors): Register "add-inferior",
"remove-inferior" and "clone-inferior" commands.
* objfiles.h: Include "progspace.h".
(struct objfile) <pspace>: New field.
(symfile_objfile, object_files): Don't declare.
(ALL_PSPACE_OBJFILES): New.
(ALL_PSPACE_OBJFILES_SAFE): New.
(ALL_OBJFILES, ALL_OBJFILES_SAFE): Adjust.
(ALL_PSPACE_SYMTABS): New.
(ALL_PRIMARY_SYMTABS): Adjust.
(ALL_PSPACE_PRIMARY_SYMTABS): New.
(ALL_PSYMTABS): Adjust.
(ALL_PSPACE_PSYMTABS): New.
* objfiles.c (object_files, symfile_objfile): Delete.
(struct objfile_sspace_info): New.
(objfiles_pspace_data): New.
(objfiles_pspace_data_cleanup): New.
(get_objfile_pspace_data): New.
(objfiles_changed_p): Delete.
(allocate_objfile): Set the objfile's program space. Adjust to
reference objfiles_changed_p in pspace data.
(free_objfile): Adjust to reference objfiles_changed_p in pspace
data.
(objfile_relocate): Ditto.
(update_section_map): Add pspace argument. Adjust to iterate over
objfiles in the passed in pspace.
(find_pc_section): Delete sections and num_sections statics.
Adjust to refer to program space's objfiles_changed_p. Adjust to
refer to sections and num_sections store in the objfile's pspace
data.
(objfiles_changed): Adjust to reference objfiles_changed_p in
pspace data.
(_initialize_objfiles): New.
* linespec.c (decode_all_digits, decode_dollar): Set the sal's
program space.
* source.c (current_source_pspace): New.
(get_current_source_symtab_and_line): Set the sal's program space.
(set_current_source_symtab_and_line): Set current_source_pspace.
(select_source_symtab): Ditto. Use ALL_OBJFILES.
(forget_cached_source_info): Iterate over all program spaces.
* symfile.c (clear_symtab_users): Adjust.
* symmisc.c (print_symbol_bcache_statistics): Iterate over all
program spaces.
(print_objfile_statistics): Ditto.
(maintenance_print_msymbols): Ditto.
(maintenance_print_objfiles): Ditto.
(maintenance_info_symtabs): Ditto.
(maintenance_info_psymtabs): Ditto.
* symtab.h (SYMTAB_PSPACE): New.
(struct symtab_and_line) <pspace>: New field.
* symtab.c (init_sal): Clear the sal's program space.
(find_pc_sect_symtab): Set the sal's program space. Switch thread
and space.
(append_expanded_sal): Add program space argument. Iterate over
all program spaces.
(expand_line_sal): Iterate over all program spaces. Switch
program space.
* target.h (enum target_waitkind) <TARGET_WAITKIND_VFORK_DONE>: New.
(struct target_ops) <to_thread_address_space>: New field.
(target_thread_address_space): Define.
* target.c (target_detach): Only remove breakpoints from the
inferior we're detaching.
(target_thread_address_space): New.
* defs.h (initialize_progspace): Declare.
* top.c (gdb_init): Call it.
* solist.h (struct so_list) <sspace>: New field.
* solib.h (struct program_space): Forward declare.
(solib_name_from_address): Adjust prototype.
* solib.c (so_list_head): Replace with a macro referencing the
program space.
(update_solib_list): Set the so's program space.
(solib_name_from_address): Add a program space argument and adjust.
* solib-svr4.c (struct svr4_info) <pid>: Delete field.
<interp_text_sect_low, interp_text_sect_high, interp_plt_sect_low>
<interp_plt_sect_high>: New fields.
(svr4_info_p, svr4_info): Delete.
(solib_svr4_sspace_data): New.
(get_svr4_info): Rewrite.
(svr4_sspace_data_cleanup): New.
(open_symbol_file_object): Adjust.
(svr4_default_sos): Adjust.
(svr4_fetch_objfile_link_map): Adjust.
(interp_text_sect_low, interp_text_sect_high, interp_plt_sect_low)
(interp_plt_sect_high): Delete.
(svr4_in_dynsym_resolve_code): Adjust.
(enable_break): Adjust.
(svr4_clear_solib): Revert bit that removed the svr4_info here,
and reinstate clearing debug_base, debug_loader_offset_p,
debug_loader_offset and debug_loader_name.
(_initialize_svr4_solib): Register solib_svr4_pspace_data. Don't
install an inferior_exit observer anymore.
* printcmd.c (struct display) <pspace>: New field.
(display_command): Set the display's sspace.
(do_one_display): Match the display's sspace.
(display_uses_solib_p): Ditto.
* linux-fork.c (detach_fork): Moved to infrun.c.
(_initialize_linux_fork): Moved "detach-on-fork" command to
infrun.c.
* infrun.c (detach_fork): Moved from linux-fork.c.
(proceed_after_vfork_done): New.
(handle_vfork_child_exec_or_exit): New.
(follow_exec_mode_replace, follow_exec_mode_keep)
(follow_exec_mode_names, follow_exec_mode_string)
(show_follow_exec_mode_string): New.
(follow_exec): New. Reinstate the mark_breakpoints_out call.
Remove shared libraries before attaching new executable. If user
wants to keep the inferior, keep it.
(displaced_step_fixup): Adjust to pass an address space to the
breakpoints module.
(resume): Ditto.
(clear_proceed_status): In all-stop mode, always clear the proceed
status of all threads.
(prepare_to_proceed): Adjust to pass an address space to the
breakpoints module.
(proceed): Ditto.
(adjust_pc_after_break): Ditto.
(handle_inferior_event): When handling a process exit, switch the
program space to the inferior's that had exited. Call
handle_vfork_child_exec_or_exit. Adjust to pass an address space
to the breakpoints module. In non-stop mode, when following a
fork and detach-fork is off, also resume the other branch. Handle
TARGET_WAITKIND_VFORK_DONE. Set the program space in sals.
(normal_stop): Prune inferiors.
(_initialize_infrun): Install the new "follow-exec-mode" command.
"detach-on-fork" moved here.
* regcache.h (get_regcache_aspace): Declare.
* regcache.c (struct regcache) <aspace>: New field.
(regcache_xmalloc): Clear the aspace.
(get_regcache_aspace): New.
(regcache_cpy): Copy the aspace field.
(regcache_cpy_no_passthrough): Ditto.
(get_thread_regcache): Fetch the thread's address space from the
target, and store it in the regcache.
* infcall.c (call_function_by_hand): Set the sal's pspace.
* arch-utils.c (default_has_shared_address_space): New.
* arch-utils.h (default_has_shared_address_space): Declare.
* gdbarch.sh (has_shared_address_space): New.
* gdbarch.h, gdbarch.c: Regenerate.
* linux-tdep.c: Include auxv.h, target.h, elf/common.h.
(linux_has_shared_address_space): New.
(_initialize_linux_tdep): Declare.
* arm-tdep.c (arm_software_single_step): Pass the frame's address
space to insert_single_step_breakpoint.
* arm-linux-tdep.c (arm_linux_software_single_step): Pass the
frame's pspace to breakpoint functions.
* cris-tdep.c (crisv32_single_step_through_delay): Ditto.
(cris_software_single_step): Ditto.
* mips-tdep.c (deal_with_atomic_sequence): Add frame argument.
Pass the frame's pspace to breakpoint functions.
(mips_software_single_step): Adjust.
(mips_single_step_through_delay): Adjust.
* rs6000-aix-tdep.c (rs6000_software_single_step): Adjust.
* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Adjust.
* solib-irix.c (enable_break): Adjust to pass the current frame's
address space to breakpoint functions.
* sparc-tdep.c (sparc_software_single_step): Ditto.
* spu-tdep.c (spu_software_single_step): Ditto.
* alpha-tdep.c (alpha_software_single_step): Ditto.
* record.c (record_wait): Adjust to pass an address space to the
breakpoints module.
* fork-child.c (fork_inferior): Set the new inferior's program and
address spaces.
* inf-ptrace.c (inf_ptrace_follow_fork): Copy the parent's program
and address spaces.
(inf_ptrace_attach): Set the inferior's program and address spaces.
* linux-nat.c: Include "solib.h".
(linux_child_follow_fork): Manage parent and child's program and
address spaces. Clone the parent's program space if necessary.
Don't wait for the vfork to be done here. Refuse to resume if
following the vfork parent while leaving the child stopped.
(resume_callback): Don't resume a vfork parent.
(linux_nat_resume): Also check for pending events in the
lp->waitstatus field.
(linux_handle_extended_wait): Report TARGET_WAITKIND_VFORK_DONE
events to the core.
(stop_wait_callback): Don't wait for SIGSTOP on vfork parents.
(cancel_breakpoint): Adjust.
* linux-thread-db.c (thread_db_wait): Don't remove thread event
breakpoints here.
(thread_db_mourn_inferior): Don't mark breakpoints out here.
Remove thread event breakpoints after mourning.
* corelow.c: Include progspace.h.
(core_open): Set the inferior's program and address spaces.
* remote.c (remote_add_inferior): Set the new inferior's program
and address spaces.
(remote_start_remote): Update address spaces.
(extended_remote_create_inferior_1): Don't init the thread list if
we already debugging other inferiors.
* darwin-nat.c (darwin_attach): Set the new inferior's program and
address spaces.
* gnu-nat.c (gnu_attach): Ditto.
* go32-nat.c (go32_create_inferior): Ditto.
* inf-ttrace.c (inf_ttrace_follow_fork, inf_ttrace_attach): Ditto.
* monitor.c (monitor_open): Ditto.
* nto-procfs.c (procfs_attach, procfs_create_inferior): Ditto.
* procfs.c (do_attach): Ditto.
* windows-nat.c (do_initial_windows_stuff): Ditto.
* inflow.c (inferior_process_group)
(terminal_init_inferior_with_pgrp, terminal_inferior,
(terminal_ours_1, inflow_inferior_exit, copy_terminal_info)
(child_terminal_info, new_tty_postfork, set_sigint_trap): Adjust
to use per-inferior data instead of inferior->terminal_info.
(inflow_inferior_data): New.
(inflow_new_inferior): Delete.
(inflow_inferior_data_cleanup): New.
(get_inflow_inferior_data): New.
* mi/mi-interp.c (mi_new_inferior): Rename to...
(mi_inferior_appeared): ... this.
(mi_interpreter_init): Adjust.
* tui/tui-disasm.c: Include "progspace.h".
(tui_set_disassem_content): Pass an address space to
breakpoint_here_p.
* NEWS: Mention multi-program debugging support. Mention new
commands "add-inferior", "clone-inferior", "remove-inferior",
"maint info program-spaces", and new option "set
follow-exec-mode".
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/doc/
* observer.texi (new_inferior): Rename to...
(inferior_appeared): ... this.
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/testsuite/
* gdb.base/foll-vfork.exp: Adjust to spell out "follow-fork".
* gdb.base/foll-exec.exp: Adjust to expect a process id before
"Executing new program".
* gdb.base/foll-fork.exp: Adjust to spell out "follow-fork".
* gdb.base/multi-forks.exp: Ditto. Adjust to the inferior being
left listed after having been killed.
* gdb.base/attach.exp: Adjust to spell out "symbol-file".
* gdb.base/maint.exp: Adjust test.
* Makefile.in (ALL_SUBDIRS): Add gdb.multi.
* gdb.multi/Makefile.in: New.
* gdb.multi/base.exp: New.
* gdb.multi/goodbye.c: New.
* gdb.multi/hangout.c: New.
* gdb.multi/hello.c: New.
* gdb.multi/bkpt-multi-exec.c: New.
* gdb.multi/bkpt-multi-exec.exp: New.
* gdb.multi/crashme.c: New.
2009-10-19 Pedro Alves <pedro@codesourcery.com>
Stan Shebs <stan@codesourcery.com>
gdb/doc/
* gdb.texinfo (Inferiors): Rename node to ...
(Inferiors and Programs): ... this. Mention running multiple
programs in the same debug session.
<info inferiors>: Mention the new 'Executable' column if "info
inferiors". Update examples. Document the "add-inferior",
"clone-inferior", "remove-inferior" and "maint info
program-spaces" commands.
(Process): Rename node to...
(Forks): ... this. Document "set|show follow-exec-mode".
2009-10-19 17:51:43 +08:00
|
|
|
* New options
|
|
|
|
|
|
|
|
|
|
set follow-exec-mode new|same
|
|
|
|
|
show follow-exec-mode
|
|
|
|
|
Control whether GDB reuses the same inferior across an exec call or
|
|
|
|
|
creates a new one. This is useful to be able to restart the old
|
|
|
|
|
executable after the inferior having done an exec call.
|
|
|
|
|
|
2009-12-31 00:11:08 +08:00
|
|
|
set default-collect EXPR, ...
|
|
|
|
|
show default-collect
|
|
|
|
|
Define a list of expressions to be collected at each tracepoint.
|
|
|
|
|
This is a useful way to ensure essential items are not overlooked,
|
|
|
|
|
such as registers or a critical global variable.
|
|
|
|
|
|
2010-01-07 04:31:28 +08:00
|
|
|
set disconnected-tracing
|
|
|
|
|
show disconnected-tracing
|
|
|
|
|
If set to 1, the target is instructed to continue tracing if it
|
|
|
|
|
loses its connection to GDB. If 0, the target is to stop tracing
|
|
|
|
|
upon disconnection.
|
|
|
|
|
|
2010-03-19 05:23:35 +08:00
|
|
|
set circular-trace-buffer
|
|
|
|
|
show circular-trace-buffer
|
|
|
|
|
If set to on, the target is instructed to use a circular trace buffer
|
|
|
|
|
and discard the oldest trace frames instead of stopping the trace due
|
|
|
|
|
to a full trace buffer. If set to off, the trace stops when the buffer
|
|
|
|
|
fills up. Some targets may not support this.
|
|
|
|
|
|
2010-01-19 18:19:22 +08:00
|
|
|
set script-extension off|soft|strict
|
|
|
|
|
show script-extension
|
|
|
|
|
If set to "off", the debugger does not perform any script language
|
|
|
|
|
recognition, and all sourced files are assumed to be GDB scripts.
|
|
|
|
|
If set to "soft" (the default), files are sourced according to
|
|
|
|
|
filename extension, falling back to GDB scripts if the first
|
|
|
|
|
evaluation failed.
|
|
|
|
|
If set to "strict", files are sourced according to filename extension.
|
|
|
|
|
|
2010-01-19 18:40:06 +08:00
|
|
|
set ada trust-PAD-over-XVS on|off
|
|
|
|
|
show ada trust-PAD-over-XVS
|
|
|
|
|
If off, activate a workaround against a bug in the debugging information
|
|
|
|
|
generated by the compiler for PAD types (see gcc/exp_dbug.ads in
|
|
|
|
|
the GCC sources for more information about the GNAT encoding and
|
|
|
|
|
PAD types in particular). It is always safe to set this option to
|
|
|
|
|
off, but this introduces a slight performance penalty. The default
|
|
|
|
|
is on.
|
|
|
|
|
|
2010-02-19 00:36:47 +08:00
|
|
|
* Python API Improvements
|
|
|
|
|
|
|
|
|
|
** GDB provides the new class gdb.LazyString. This is useful in
|
|
|
|
|
some pretty-printing cases. The new method gdb.Value.lazy_string
|
|
|
|
|
provides a simple way to create objects of this type.
|
|
|
|
|
|
|
|
|
|
** The fields returned by gdb.Type.fields now have an
|
|
|
|
|
`is_base_class' attribute.
|
|
|
|
|
|
|
|
|
|
** The new method gdb.Type.range returns the range of an array type.
|
|
|
|
|
|
|
|
|
|
** The new method gdb.parse_and_eval can be used to parse and
|
|
|
|
|
evaluate an expression.
|
|
|
|
|
|
2009-12-29 07:39:10 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
QTDV
|
|
|
|
|
Define a trace state variable.
|
|
|
|
|
|
|
|
|
|
qTV
|
|
|
|
|
Get the current value of a trace state variable.
|
|
|
|
|
|
2010-01-07 04:31:28 +08:00
|
|
|
QTDisconnected
|
|
|
|
|
Set desired tracing behavior upon disconnection.
|
|
|
|
|
|
2010-03-19 05:23:35 +08:00
|
|
|
QTBuffer:circular
|
|
|
|
|
Set the trace buffer to be linear or circular.
|
|
|
|
|
|
2010-01-07 04:31:28 +08:00
|
|
|
qTfP, qTsP
|
|
|
|
|
Get data about the tracepoints currently in use.
|
|
|
|
|
|
2009-11-24 04:07:26 +08:00
|
|
|
* Bug fixes
|
|
|
|
|
|
|
|
|
|
Process record now works correctly with hardware watchpoints.
|
|
|
|
|
|
2010-01-10 14:43:01 +08:00
|
|
|
Multiple bug fixes have been made to the mips-irix port, making it
|
|
|
|
|
much more reliable. In particular:
|
|
|
|
|
- Debugging threaded applications is now possible again. Previously,
|
|
|
|
|
GDB would hang while starting the program, or while waiting for
|
|
|
|
|
the program to stop at a breakpoint.
|
|
|
|
|
- Attaching to a running process no longer hangs.
|
|
|
|
|
- An error occurring while loading a core file has been fixed.
|
|
|
|
|
- Changing the value of the PC register now works again. This fixes
|
|
|
|
|
problems observed when using the "jump" command, or when calling
|
|
|
|
|
a function from GDB, or even when assigning a new value to $pc.
|
|
|
|
|
- With the "finish" and "return" commands, the return value for functions
|
|
|
|
|
returning a small array is now correctly printed.
|
|
|
|
|
- It is now possible to break on shared library code which gets executed
|
|
|
|
|
during a shared library init phase (code executed while executing
|
|
|
|
|
their .init section). Previously, the breakpoint would have no effect.
|
|
|
|
|
- GDB is now able to backtrace through the signal handler for
|
|
|
|
|
non-threaded programs.
|
|
|
|
|
|
2010-01-15 05:24:05 +08:00
|
|
|
PIE (Position Independent Executable) programs debugging is now supported.
|
|
|
|
|
This includes debugging execution of PIC (Position Independent Code) shared
|
|
|
|
|
libraries although for that, it should be possible to run such libraries as an
|
|
|
|
|
executable program.
|
|
|
|
|
|
2009-10-08 02:27:22 +08:00
|
|
|
*** Changes in GDB 7.0
|
2008-02-28 04:50:49 +08:00
|
|
|
|
2009-08-21 02:02:48 +08:00
|
|
|
* GDB now has an interface for JIT compilation. Applications that
|
|
|
|
|
dynamically generate code can create symbol files in memory and register
|
|
|
|
|
them with GDB. For users, the feature should work transparently, and
|
|
|
|
|
for JIT developers, the interface is documented in the GDB manual in the
|
|
|
|
|
"JIT Compilation Interface" chapter.
|
|
|
|
|
|
2009-07-15 05:40:34 +08:00
|
|
|
* Tracepoints may now be conditional. The syntax is as for
|
|
|
|
|
breakpoints; either an "if" clause appended to the "trace" command,
|
|
|
|
|
or the "condition" command is available. GDB sends the condition to
|
|
|
|
|
the target for evaluation using the same bytecode format as is used
|
|
|
|
|
for tracepoint actions.
|
|
|
|
|
|
2010-07-28 04:33:40 +08:00
|
|
|
* The disassemble command now supports: an optional /r modifier, print the
|
|
|
|
|
raw instructions in hex as well as in symbolic form, and an optional /m
|
|
|
|
|
modifier to print mixed source+assembly.
|
2009-07-11 22:04:23 +08:00
|
|
|
|
2009-05-06 10:32:42 +08:00
|
|
|
* Process record and replay
|
|
|
|
|
|
|
|
|
|
In a architecture environment that supports ``process record and
|
|
|
|
|
replay'', ``process record and replay'' target can record a log of
|
|
|
|
|
the process execution, and replay it with both forward and reverse
|
|
|
|
|
execute commands.
|
|
|
|
|
|
2009-05-06 02:13:37 +08:00
|
|
|
* Reverse debugging: GDB now has new commands reverse-continue, reverse-
|
|
|
|
|
step, reverse-next, reverse-finish, reverse-stepi, reverse-nexti, and
|
|
|
|
|
set execution-direction {forward|reverse}, for targets that support
|
|
|
|
|
reverse execution.
|
|
|
|
|
|
2009-04-20 David Daney <ddaney@caviumnetworks.com>
* NEWS: Mention MIPS/Linux hardware watchpoint support.
2009-04-20 David Daney <ddaney@caviumnetworks.com>
* mips-linux-nat.c (command.h, gdbcmd.h, gdb_assert.h): New #includes.
(maint_show_dr, super_close): New variables.
(super_fetch_registers, super_store_registers): Make static.
(PTRACE_GET_WATCH_REGS, PTRACE_SET_WATCH_REGS, W_BIT, R_BIT, I_BIT)
(W_MASK, R_MASK, I_MASK, IRW_MASK, MAX_DEBUG_REGISTER): Define.
(pt_watch_style): Define new enum.
(mips32_watch_regs, mips64_watch_regs, pt_watch_regs, mips_watchpoint):
Define new structs.
(watch_readback_valid, watch_readback, current_watches, watch_mirror):
New variables.
(get_irw_mask, get_reg_mask, get_num_valid, get_watchlo)
(set_watchlo, get_watchhi, set_watchhi, mips_show_dr)
(mips_linux_read_watch_registers, mips_linux_can_use_hw_breakpoint)
(mips_linux_stopped_by_watchpoint, mips_linux_stopped_data_address)
(type_to_irw, fill_mask, try_one_watch)
(mips_linux_region_ok_for_hw_watchpoint, write_watchpoint_regs)
(mips_linux_new_thread, populate_regs_from_watches)
(mips_linux_insert_watchpoint, mips_linux_remove_watchpoint)
(mips_linux_close): New functions.
(_initialize_mips_linux_nat): Register watchpoint functions with
the target_ops. Add show-debug-regs maintenance command.
2009-04-20 David Daney <ddaney@caviumnetworks.com>
* infrun.c (handle_inferior_event): Move gegisters_changed call down.
2009-04-21 05:11:06 +08:00
|
|
|
* GDB now supports hardware watchpoints on MIPS/Linux systems. This
|
|
|
|
|
feature is available with a native GDB running on kernel version
|
|
|
|
|
2.6.28 or later.
|
|
|
|
|
|
gdb:
2009-03-19 Tom Tromey <tromey@redhat.com>
Julian Brown <julian@codesourcery.com>
PR i18n/7220, PR i18n/7821, PR exp/8815, PR exp/9103,
PR i18n/9401, PR exp/9613:
* NEWS: Update
* value.h (value_typed_string): Declare.
(val_print_string): Update.
* valprint.h (print_char_chars): Update.
* valprint.c (print_char_chars): Add type argument. Update.
(val_print_string): Likewise.
* valops.c (value_typed_string): New function.
* utils.c (host_char_to_target): New function.
(parse_escape): Use host_char_to_target, host_hex_value. Update.
Remove '^' case.
(no_control_char_error): Remove.
* typeprint.c (print_type_scalar): Update.
* scm-valprint.c (scm_scmval_print): Update.
* scm-lang.h (scm_printchar, scm_printstr): Update.
* scm-lang.c (scm_printchar): Add type argument.
(scm_printstr): Likewise.
* printcmd.c (print_formatted): Update.
(print_scalar_formatted): Update.
(printf_command) <wide_string_arg, wide_char_arg>: New constants.
Handle '%lc' and '%ls'.
* parser-defs.h (struct typed_stoken): New type.
(struct stoken_vector): Likewise.
(write_exp_string_vector): Declare.
* parse.c (write_exp_string_vector): New function.
* p-valprint.c (pascal_val_print): Update.
* p-lang.h (is_pascal_string_type, pascal_printchar,
pascal_printstr): Update.
* p-lang.c (is_pascal_string_type): Remove 'char_size' argument.
Add 'char_type' argument.
(pascal_emit_char): Add type argument.
(pascal_printchar): Likewise.
(pascal_printstr): Likewise.
* objc-lang.c (objc_emit_char): Add type argument.
(objc_printchar): Likewise.
(objc_printstr): Likewise.
* macroexp.c (get_character_constant): Handle unicode characters.
Use c_parse_escape.
(get_string_literal): Handle unicode strings. Use
c_parse_escape.
* m2-valprint.c (print_unpacked_pointer): Update.
(m2_print_array_contents): Update.
(m2_val_print): Update.
* m2-lang.c (m2_emit_char): Add type argument.
(m2_printchar): Likewise.
(m2_printstr): Likewise.
* language.h (struct language_defn) <la_printchar>: Add type
argument.
<la_printstr, la_emitchar>: Likewise.
(LA_PRINT_CHAR): Likewise.
(LA_PRINT_STRING): Likewise.
(LA_EMIT_CHAR): Likewise.
* language.c (unk_lang_emit_char): Add type argument.
(unk_lang_printchar): Likewise.
(unk_lang_printstr): Likewise.
* jv-valprint.c (java_val_print): Update.
* jv-lang.c (java_emit_char): Add type argument.
* f-valprint.c (f_val_print): Update.
* f-lang.c (f_emit_char): Add type argument.
(f_printchar): Likewise.
(f_printstr): Likewise.
* expprint.c (print_subexp_standard): Update.
* charset.h (target_wide_charset): Declare.
(c_target_char_has_backslash_escape, c_parse_backslash,
host_char_print_literally, host_char_to_target,
target_char_to_host, target_char_to_control_char): Remove.
(enum transliterations): New type.
(convert_between_encodings): Declare.
(HOST_ESCAPE_CHAR): New define.
(host_letter_to_control_character, host_hex_value): Declare.
(enum wchar_iterate_result): New enum.
(struct wchar_iterator): Declare.
(make_wchar_iterator, make_cleanup_wchar_iterator, wchar_iterator,
wchar_push_back): Declare.
* charset-list.h: New file.
* c-valprint.c (textual_name): New function.
(textual_element_type): Handle wide character types.
(c_val_print): Pass original type to textual_element_type. Handle
wide character types.
(c_value_print): Use textual_element_type. Pass original type of
value to val_print.
* c-lang.h (enum c_string_type): New type.
(c_printchar, c_printstr): Update.
* c-lang.c (classify_type): New function.
(print_wchar): Likewise.
(c_emit_char): Add type argument. Handle wide characters.
(c_printchar): Likewise.
(c_printstr): Add type argument. Handle wide and multibyte
character sets.
(convert_ucn): New function.
(emit_numeric_character): Likewise.
(convert_octal): Likewise.
(convert_hex): Likewise.
(ADVANCE): New macro.
(convert_escape): New function.
(parse_one_string): Likewise.
(evaluate_subexp_c): Likewise.
(exp_descriptor_c): New global.
(c_language_defn): Use exp_descriptor_c.
(cplus_language_defn): Likewise.
(asm_language_defn): Likewise.
(minimal_language_defn): Likewise.
(charset_for_string_type): New function.
* c-exp.y (%union): Add 'svec' and 'tsval'.
(CHAR): New token.
(exp): Add CHAR production.
(string_exp): Rewrite.
(exp) <string_exp>: Rewrite.
(tempbuf): Now global.
(tempbuf_init): New global.
(parse_string_or_char): New function.
(yylex) <tempbuf>: Now global.
<tokptr, tempbufindex, tempbufsize, token_string, class_prefix>:
Remove.
Handle 'u', 'U', and 'L' prefixes. Call parse_string_or_char.
(c_parse_escape): New function.
* auxv.c (fprint_target_auxv): Update.
* ada-valprint.c (ada_emit_char): Add type argument.
(ada_printchar): Likewise.
(ada_print_scalar): Update.
(printstr): Add type argument. Update calls to ada_emit_char.
(ada_printstr): Add type argument.
(ada_val_print_array): Update.
(ada_val_print_1): Likewise.
* ada-lang.c (emit_char): Add type argument.
* ada-lang.h (ada_emit_char, ada_printchar, ada_printstr): Add
type arguments.
* gdb_locale.h: Include langinfo.h.
* charset.c (_initialize_charset): Set default host charset from
the locale. Don't register charsets. Add target-wide-charset
commands. Call find_charset_names.
(struct charset, struct translation): Remove.
(GDB_DEFAULT_HOST_CHARSET): Remove.
(GDB_DEFAULT_TARGET_WIDE_CHARSET): New define.
(target_wide_charset_name): New global.
(show_host_charset_name): Handle "auto".
(show_target_wide_charset_name): New function.
(host_charset_enum, target_charset_enum): Remove.
(charset_enum): New global.
(all_charsets, register_charset, lookup_charset, all_translations,
register_translation, lookup_translation): Remove.
(simple_charset, ascii_print_literally, ascii_to_control): Remove.
(iso_8859_print_literally, iso_8859_to_control,
iso_8859_family_charset): Remove.
(ebcdic_print_literally, ebcdic_to_control,
ebcdic_family_charset): Remove.
(struct cached_iconv, check_iconv_cache, cached_iconv_convert,
register_iconv_charsets): Remove.
(target_wide_charset_be_name, target_wide_charset_le_name): New
globals.
(identity_either_char_to_other): Remove.
(set_be_le_names, validate): New functions.
(backslashable, backslashed, represented): Remove.
(default_c_target_char_has_backslash_escape): Remove.
(default_c_parse_backslash, iconv_convert): Remove.
(ascii_to_iso_8859_1_table, ascii_to_ebcdic_us_table,
ascii_to_ibm1047_table, iso_8859_1_to_ascii_table,
iso_8859_1_to_ebcdic_us_table, iso_8859_1_to_ibm1047_table,
ebcdic_us_to_ascii_table, ebcdic_us_to_iso_8859_1_table,
ebcdic_us_to_ibm1047_table, ibm1047_to_ascii_table,
ibm1047_to_iso_8859_1_table, ibm1047_to_ebcdic_us_table): Remove.
(table_convert_char, table_translation, simple_table_translation):
Remove.
(current_host_charset, current_target_charset,
c_target_char_has_backslash_escape_func,
c_target_char_has_backslash_escape_baton): Remove.
(c_parse_backslash_func, c_parse_backslash_baton): Remove.
(host_char_to_target_func, host_char_to_target_baton): Remove.
(target_char_to_host_func, target_char_to_host_baton): Remove.
(cached_iconv_host_to_target, cached_iconv_target_to_host):
Remove.
(lookup_charset_or_error, check_valid_host_charset): Remove.
(set_host_and_target_charsets): Remove.
(set_host_charset, set_target_charset): Remove.
(set_host_charset_sfunc, set_target_charset_sfunc): Rewrite.
(set_target_wide_charset_sfunc): New function.
(show_charset): Print target wide character set.
(host_charset, target_charset): Rewrite.
(target_wide_charset): New function.
(c_target_char_has_backslash_escape): Remove.
(c_parse_backslash): Remove.
(host_letter_to_control_character): New function.
(host_char_print_literally): Remove.
(host_hex_value): New function.
(target_char_to_control_char): Remove.
(cleanup_iconv): New function.
(convert_between_encodings): New function.
(target_char_to_host): Remove.
(struct wchar_iterator): Define.
(make_wchar_iterator, make_cleanup_wchar_iterator, wchar_iterator,
wchar_push_back): New functions.
(do_cleanup_iterator): New function.
(char_ptr): New typedef.
(charsets): New global.
(add_one, find_charset_names): New functions.
(default_charset_names): New global.
(auto_host_charset_name): Likewise.
* aclocal.m4, config.in, configure: Rebuild.
* configure.ac: Call AM_LANGINFO_CODESET.
(GDB_DEFAULT_HOST_CHARSET): Default to UTF-8.
(AM_ICONV): Invoke earlier.
* acinclude.m4: Include codeset.m4. Subst LIBICONV_INCLUDE and
LIBICONV_LIBDIR. Check for libiconv in build tree.
* Makefile.in (LIBICONV_LIBDIR, LIBICONV_INCLUDE): New macros.
(INTERNAL_CFLAGS_BASE): Add LIBICONV_INCLUDE.
(INTERNAL_LDFLAGS): Add LIBICONV_LIBDIR.
* gdb_obstack.h (obstack_grow_wstr): New define.
* gdb_wchar.h: New file.
* defs.h: Include it.
gdb/testsuite:
* gdb.base/store.exp: Update for change to escape output.
* gdb.base/callfuncs.exp (fetch_all_registers): Update for change
to escape output.
* gdb.base/pointers.exp: Update for change to escape output.
* gdb.base/long_long.exp (gdb_test_long_long): Update for change
to escape output.
* gdb.base/constvars.exp (do_constvar_tests): Update for change to
escape output.
* gdb.base/call-rt-st.exp (print_struct_call): Update for change
to escape output.
* gdb.cp/ref-types.exp (gdb_start_again): Update for change to
escape output.
* gdb.base/setvar.exp: Update for change to escape output.
* lib/gdb.exp (default_gdb_start): Set LC_CTYPE to C.
* gdb.base/printcmds.exp (test_print_all_chars): Update for change
to escape output.
(test_print_string_constants): Likewise.
* gdb.base/charset.exp (valid_host_charset): Check size of
wchar_t. Handle UCS-2 and UCS-4. Add tests for wide and unicode
cases. Handle "auto"-related output.
* gdb.base/charset.c (char16_t, char32_t): New typedefs.
(uvar, Uvar): New globals.
gdb/doc:
* gdb.texinfo (Character Sets): Remove obsolete text. Document
set target-wide-charset.
(Requirements): Mention iconv.
2009-03-21 07:04:40 +08:00
|
|
|
* GDB now has support for multi-byte and wide character sets on the
|
|
|
|
|
target. Strings whose character type is wchar_t, char16_t, or
|
|
|
|
|
char32_t are now correctly printed. GDB supports wide- and unicode-
|
|
|
|
|
literals in C, that is, L'x', L"string", u'x', u"string", U'x', and
|
|
|
|
|
U"string" syntax. And, GDB allows the "%ls" and "%lc" formats in
|
|
|
|
|
`printf'. This feature requires iconv to work properly; if your
|
|
|
|
|
system does not have a working iconv, GDB can use GNU libiconv. See
|
|
|
|
|
the installation instructions for more information.
|
|
|
|
|
|
2008-08-27 01:30:35 +08:00
|
|
|
* GDB now supports automatic retrieval of shared library files from
|
|
|
|
|
remote targets. To use this feature, specify a system root that begins
|
|
|
|
|
with the `remote:' prefix, either via the `set sysroot' command or via
|
|
|
|
|
the `--with-sysroot' configure-time option.
|
|
|
|
|
|
2009-08-28 05:56:38 +08:00
|
|
|
* "info sharedlibrary" now takes an optional regex of libraries to show,
|
|
|
|
|
and it now reports if a shared library has no debugging information.
|
|
|
|
|
|
2008-07-05 06:30:19 +08:00
|
|
|
* Commands `set debug-file-directory', `set solib-search-path' and `set args'
|
|
|
|
|
now complete on file names.
|
|
|
|
|
|
2008-06-07 04:58:08 +08:00
|
|
|
* When completing in expressions, gdb will attempt to limit
|
|
|
|
|
completions to allowable structure or union fields, where appropriate.
|
|
|
|
|
For instance, consider:
|
|
|
|
|
|
|
|
|
|
# struct example { int f1; double f2; };
|
|
|
|
|
# struct example variable;
|
|
|
|
|
(gdb) p variable.
|
|
|
|
|
|
|
|
|
|
If the user types TAB at the end of this command line, the available
|
|
|
|
|
completions will be "f1" and "f2".
|
|
|
|
|
|
gdb/
* NEWS: Document inlined function support.
* Makefile.in (SFILES): Add inline-frame.c.
(COMMON_OBS): Add inline-frame.o.
* block.c (contained_in): Rewrite to use lexical nesting.
(block_linkage_function): Skip inlined function blocks.
(block_inlined_p): New.
* block.h (struct block): Update comment.
(block_inlined_p): New prototype.
* blockframe.c (get_frame_block): Handle inlined functions.
(get_frame_function): Do not use block_linkage_function.
(block_innermost_frame): Use get_frame_block and contained_in.
* breakpoint.c (watchpoint_check): Remove extra reinit_frame_cache.
Skip over inlined functions. Simplify epilogue check.
(bpstat_check_breakpoint_conditions): Use get_stack_frame_id.
Update comments.
(set_momentary_breakpoint): Only accept non-inlined frames.
(watch_command_1): Use frame_unwind_caller_pc and
frame_unwind_caller_id instead of get_prev_frame.
(until_break_command): Likewise. Use get_stack_frame_id.
* buildsym.c (end_symtab): Set SYMBOL_SYMTAB for block functions.
* dwarf2loc.c (dwarf_expr_frame_base): Use block_linkage_function.
* dwarf2read.c (process_die): Handle DW_TAG_inlined_subroutine.
(read_func_scope, new_symbol): Likewise. Handle arguments specially
for inlined functions without call site information.
(inherit_abstract_dies): Allow tag mismatch for inlined subroutines.
(die_specification): Treat DW_AT_abstract_origin as a specification.
(read_type_die): Handle DW_TAG_inlined_subroutine.
* frame-unwind.c (frame_unwind_init): Add inline_frame_unwind.
* frame.c (fprint_frame_id): Print inline depth.
(fprint_frame_type): Handle INLINE_FRAME and SENTINEL_FRAME.
(skip_inlined_frames, get_stack_frame_id): New.
(frame_unwind_caller_id): Use skip_inlined_frames.
(frame_id_inlined_p): New.
(frame_id_eq): Make the logic match the comments. Add inline_depth
check.
(frame_id_inner): Handle inlined functions.
(frame_unwind_pc): New function, copied from frame_unwind_caller_pc.
(frame_unwind_caller_pc): Use skip_inlined_frames and frame_unwind_pc.
(get_prev_frame_1): Check for inline frames. Split out frame
allocation to get_prev_frame_raw.
(get_prev_frame_raw): New function.
(get_prev_frame): Handle inline frames.
(get_frame_pc): Use frame_unwind_pc.
(get_frame_address_in_block): Skip inlined frames on both sides.
(pc_notcurrent): Delete.
(find_frame_sal): Rewrite to handle inline call sites. Use
get_frame_address_in_block.
(deprecated_update_frame_pc_hack): Make static.
* frame.h: Update comments.
(struct frame_id): Add inline_depth.
(enum frame_type): Add INLINE_FRAME.
(frame_id_inlined_p, get_stack_frame_id): New prototypes.
* gdbthread.h (struct thread_info): Add step_stack_frame_id field.
* infcmd.c (set_step_frame): New function.
(step_once): Use set_step_frame. Handle inlined functions.
(until_next_command): Use set_step_frame.
(finish_backward), finish_forward): Use get_stack_frame_id.
(finish_command): Support inlined functions.
* inferior.h (set_step_info): New prototype.
* infrun.c (RESUME_ALL): Use minus_one_ptid.
(clear_proceed_status): Clear step_stack_frame_id.
(init_wait_for_inferior): Call clear_inline_frame_state.
(init_execution_control_state): Make static.
(set_step_info): New function.
(init_thread_stepping_state): Do not set the symtab or line here.
(stepped_in_from): New function.
(handle_inferior_event): Handle inlined functions. Use set_step_info.
(insert_step_resume_breakpoint_at_frame): Use get_stack_frame_id.
(struct inferior_status): Add step_stack_frame_id.
(save_inferior_status, restore_inferior_status): Save and restore
step_stack_frame_id.
* inline-frame.c, inline-frame.h: New files.
* minsyms.c (prim_record_minimal_symbol_and_info): Use XCALLOC.
* regcache.c (regcache_write_pc): Call reinit_frame_cache.
* s390-tdep.c (s390_prologue_frame_unwind_cache): Handle INLINE_FRAME.
* stack.c (frame_show_address): New.
(print_frame_info, print_frame): Use it.
(find_frame_funname): Use get_frame_function. Handle inlined blocks.
(frame_info): Mark inlined functions.
(backtrace_command_1): Use get_current_user_frame.
(print_frame_local_vars, print_frame_label_vars): Update comments.
(return_command): Refuse inlined functions.
* symtab.c (lookup_symbol_aux_local): Stop at inlined function
boundaries.
(find_function_start_sal): Avoid inlined functions.
(completion_list_add_fields): New function.
(default_make_symbol_completion_list): Use it. Use block_static_block
and block_global_block. Check for inlined functions.
(skip_prologue_using_sal): Avoid line number comparison across
inlining.
* symtab.h (struct symbol): Add is_inlined.
(SYMBOL_INLINED): New.
* target.c (target_resume): Call clear_inline_frame_state.
* valops.c (value_of_variable): Check block_inlined_p.
gdb/doc/
* gdb.texinfo (Debugging Optimized Code): New chapter.
(Compiling for Debugging): Reference it. Move some
text to the new section.
gdb/testsuite/
* gdb.base/break.exp: Add an XFAIL for gcc/36748.
* gdb.cp/annota2.exp: Accept frames-invalid in more places.
* gdb.opt/Makefile.in (EXECUTABLES): Update.
* gdb.opt/clobbered-registers-O2.exp: Update to GPL v3.
* gdb.opt/inline-bt.c, gdb.opt/inline-bt.exp,
gdb.opt/inline-cmds.c, gdb.opt/inline-cmds.exp,
gdb.opt/inline-locals.c, gdb.opt/inline-locals.exp,
gdb.opt/inline-markers.c: New files.
* lib/gdb.exp (skip_inline_frame_tests): New function.
(skip_inline_var_tests): New function.
2009-06-28 08:20:24 +08:00
|
|
|
* Inlined functions are now supported. They show up in backtraces, and
|
|
|
|
|
the "step", "next", and "finish" commands handle them automatically.
|
|
|
|
|
|
2008-09-28 05:40:49 +08:00
|
|
|
* GDB now supports the token-splicing (##) and stringification (#)
|
|
|
|
|
operators when expanding macros. It also supports variable-arity
|
|
|
|
|
macros.
|
|
|
|
|
|
2009-02-07 23:00:57 +08:00
|
|
|
* GDB now supports inspecting extra signal information, exported by
|
* NEWS: Mention ARM VFP support.
* target-descriptions.c (tdesc_register_type): Make public.
(tdesc_unnumbered_register): New function.
(tdesc_register_reggroup_p): Allow missing
pseudo_register_reggroup_p.
* target-descriptions.h (tdesc_register_type): Declare.
(tdesc_unnumbered_register): Declare.
* arm-tdep.c (arm_neon_quad_read, arm_neon_quad_write): New functions.
(arm_push_dummy_call): Use arm_neon_quad_write.
(arm_neon_double_type, arm_neon_quad_type): New functions.
(arm_register_type): Handle VFP and NEON registers. Override the
types of double-precision registers for NEON. Disable FPA registers
if they are not present.
(arm_dwarf_reg_to_regnum): Add current VFP and NEON register numbers.
(arm_return_value): Use arm_neon_quad_write and arm_neon_quad_read.
(arm_register_name): Handle VFP single and NEON quad registers.
(arm_pseudo_read, arm_pseudo_write): New functions.
(arm_gdbarch_init): Check for VFP and NEON in the target description.
Assign numbers to double-precision registers. Register VFP and NEON
pseudo registers. Remove a shadowed "i" variable.
* arm-tdep.h (enum gdb_regnum): Add ARM_D0_REGNUM and
ARM_D31_REGNUM.
(struct gdbarch_tdep): Add have_neon_pseudos, have_neon,
have_vfp_registers, have_vfp_pseudos, neon_double_type,
and neon_quad_type.
* features/Makefile: Make expedite settings only architecture
specific.
(WHICH): Add new ARM descriptions.
* features/arm-with-neon.xml, features/arm-with-vfpv2.c,
features/arm-with-vfpv3.c, features/arm-vfpv2.xml,
features/arm-vfpv3.xml, features/arm-with-vfpv2.xml,
features/arm-with-vfpv3.xml, features/arm-with-neon.c: New files.
* regformats/arm-with-neon.dat, regformats/arm-with-vfpv2.dat,
regformats/arm-with-vfpv3.dat: Generate.
doc/
* gdb.texinfo (ARM Features): Document org.gnu.gdb.arm.vfp and
org.gnu.gdb.arm.neon.
gdbserver/
* linux-low.c (linux_write_memory): Update debugging output.
* Makefile.in (clean): Add new descriptions.
(arm-with-vfpv2.o, arm-with-vfpv2.c, arm-with-vfpv3.o)
(arm-with-vfpv3.c, arm-with-neon.o, arm-with-neon.c): New rules.
* configure.srv: Add new files for arm*-*-linux*.
* linux-arm-low.c: Add new declarations.
(PTRACE_GETVFPREGS, PTRACE_SETVFPREGS): Define if undefined.
(arm_hwcap, HWCAP_VFP, HWCAP_IWMMXT, HWCAP_NEON, HWCAP_VFPv3)
(HWCAP_VFPv3D16): New.
(arm_fill_wmmxregset, arm_store_wmmxregset): Check HWCAP_IWMMXT
instead of __IWMMXT__.
(arm_fill_vfpregset, arm_store_vfpregset, arm_get_hwcap)
(arm_arch_setup): New.
(target_regsets): Remove #ifdef. Add VFP regset.
(the_low_target): Use arm_arch_setup.
testsuite/
* gdb.base/float.exp: Handle VFP registers.
2009-07-29 02:26:51 +08:00
|
|
|
the new $_siginfo convenience variable. The feature is currently
|
|
|
|
|
implemented on linux ARM, i386 and amd64.
|
|
|
|
|
|
|
|
|
|
* GDB can now display the VFP floating point registers and NEON vector
|
|
|
|
|
registers on ARM targets. Both ARM GNU/Linux native GDB and gdbserver
|
|
|
|
|
can provide these registers (requires Linux 2.6.30 or later). Remote
|
|
|
|
|
and simulator targets may also provide them.
|
2009-02-07 23:00:57 +08:00
|
|
|
|
2008-05-10 01:02:03 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
qSearch:memory:
|
|
|
|
|
Search memory for a sequence of bytes.
|
|
|
|
|
|
2008-08-12 23:18:31 +08:00
|
|
|
QStartNoAckMode
|
|
|
|
|
Turn off `+'/`-' protocol acknowledgments to permit more efficient
|
|
|
|
|
operation over reliable transport links. Use of this packet is
|
|
|
|
|
controlled by the `set remote noack-packet' command.
|
|
|
|
|
|
2009-04-18 22:54:00 +08:00
|
|
|
vKill
|
|
|
|
|
Kill the process with the specified process ID. Use this in preference
|
|
|
|
|
to `k' when multiprocess protocol extensions are supported.
|
|
|
|
|
|
2008-12-02 15:57:38 +08:00
|
|
|
qXfer:osdata:read
|
|
|
|
|
Obtains additional operating system information
|
|
|
|
|
|
2009-02-07 23:00:57 +08:00
|
|
|
qXfer:siginfo:read
|
|
|
|
|
qXfer:siginfo:write
|
|
|
|
|
Read or write additional signal information.
|
|
|
|
|
|
2008-06-11 20:56:36 +08:00
|
|
|
* Removed remote protocol undocumented extension
|
|
|
|
|
|
|
|
|
|
An undocumented extension to the remote protocol's `S' stop reply
|
2020-06-05 18:24:20 +08:00
|
|
|
packet that permitted the stub to pass a process id was removed.
|
2008-06-11 20:56:36 +08:00
|
|
|
Remote servers should use the `T' stop reply packet instead.
|
|
|
|
|
|
2008-04-22 19:03:42 +08:00
|
|
|
* GDB now supports multiple function calling conventions according to the
|
2008-05-02 02:50:14 +08:00
|
|
|
DWARF-2 DW_AT_calling_convention function attribute.
|
2008-04-22 19:03:42 +08:00
|
|
|
|
|
|
|
|
* The SH target utilizes the aforementioned change to distinguish between gcc
|
2008-05-02 02:50:14 +08:00
|
|
|
and Renesas calling convention. It also adds the new CLI commands
|
|
|
|
|
`set/show sh calling-convention'.
|
2008-04-22 19:03:42 +08:00
|
|
|
|
2008-04-20 08:03:25 +08:00
|
|
|
* GDB can now read compressed debug sections, as produced by GNU gold
|
|
|
|
|
with the --compress-debug-sections=zlib flag.
|
|
|
|
|
|
2008-04-23 04:29:07 +08:00
|
|
|
* 64-bit core files are now supported on AIX.
|
|
|
|
|
|
2008-10-21 00:18:59 +08:00
|
|
|
* Thread switching is now supported on Tru64.
|
|
|
|
|
|
2008-03-11 07:14:06 +08:00
|
|
|
* Watchpoints can now be set on unreadable memory locations, e.g. addresses
|
|
|
|
|
which will be allocated using malloc later in program execution.
|
|
|
|
|
|
2020-06-05 18:24:20 +08:00
|
|
|
* The qXfer:libraries:read remote protocol packet now allows passing a
|
2008-04-20 08:03:25 +08:00
|
|
|
list of section offsets.
|
2008-03-15 06:30:07 +08:00
|
|
|
|
2008-05-02 02:50:14 +08:00
|
|
|
* On GNU/Linux, GDB can now attach to stopped processes. Several race
|
|
|
|
|
conditions handling signals delivered during attach or thread creation
|
|
|
|
|
have also been fixed.
|
|
|
|
|
|
2008-08-19 18:36:43 +08:00
|
|
|
* GDB now supports the use of DWARF boolean types for Ada's type Boolean.
|
2008-08-21 17:05:32 +08:00
|
|
|
From the user's standpoint, all unqualified instances of True and False
|
|
|
|
|
are treated as the standard definitions, regardless of context.
|
2008-08-19 18:36:43 +08:00
|
|
|
|
2009-04-01 04:21:08 +08:00
|
|
|
* GDB now parses C++ symbol and type names more flexibly. For
|
|
|
|
|
example, given:
|
|
|
|
|
|
|
|
|
|
template<typename T> class C { };
|
|
|
|
|
C<char const *> c;
|
|
|
|
|
|
|
|
|
|
GDB will now correctly handle all of:
|
|
|
|
|
|
|
|
|
|
ptype C<char const *>
|
|
|
|
|
ptype C<char const*>
|
|
|
|
|
ptype C<const char *>
|
|
|
|
|
ptype C<const char*>
|
|
|
|
|
|
2008-03-11 07:14:06 +08:00
|
|
|
* New features in the GDB remote stub, gdbserver
|
|
|
|
|
|
|
|
|
|
- The "--wrapper" command-line argument tells gdbserver to use a
|
|
|
|
|
wrapper program to launch programs for debugging.
|
|
|
|
|
|
2008-05-10 03:17:46 +08:00
|
|
|
- On PowerPC and S/390 targets, it is now possible to use a single
|
|
|
|
|
gdbserver executable to debug both 32-bit and 64-bit programs.
|
|
|
|
|
(This requires gdbserver itself to be built as a 64-bit executable.)
|
|
|
|
|
|
2008-08-12 23:18:31 +08:00
|
|
|
- gdbserver uses the new noack protocol mode for TCP connections to
|
|
|
|
|
reduce communications latency, if also supported and enabled in GDB.
|
|
|
|
|
|
2008-11-16 00:09:51 +08:00
|
|
|
- Support for the sparc64-linux-gnu target is now included in
|
|
|
|
|
gdbserver.
|
|
|
|
|
|
2009-07-02 00:19:14 +08:00
|
|
|
- The amd64-linux build of gdbserver now supports debugging both
|
|
|
|
|
32-bit and 64-bit programs.
|
|
|
|
|
|
|
|
|
|
- The i386-linux, amd64-linux, and i386-win32 builds of gdbserver
|
|
|
|
|
now support hardware watchpoints, and will use them automatically
|
|
|
|
|
as appropriate.
|
|
|
|
|
|
2008-08-07 03:41:33 +08:00
|
|
|
* Python scripting
|
|
|
|
|
|
|
|
|
|
GDB now has support for scripting using Python. Whether this is
|
|
|
|
|
available is determined at configure time.
|
|
|
|
|
|
2009-02-07 05:33:59 +08:00
|
|
|
New GDB commands can now be written in Python.
|
|
|
|
|
|
2008-10-23 06:14:21 +08:00
|
|
|
* Ada tasking support
|
|
|
|
|
|
|
|
|
|
Ada tasks can now be inspected in GDB. The following commands have
|
|
|
|
|
been introduced:
|
|
|
|
|
|
|
|
|
|
info tasks
|
|
|
|
|
Print the list of Ada tasks.
|
|
|
|
|
info task N
|
|
|
|
|
Print detailed information about task number N.
|
|
|
|
|
task
|
|
|
|
|
Print the task number of the current task.
|
|
|
|
|
task N
|
|
|
|
|
Switch the context of debugging to task number N.
|
|
|
|
|
|
2009-01-15 04:40:09 +08:00
|
|
|
* Support for user-defined prefixed commands. The "define" command can
|
|
|
|
|
add new commands to existing prefixes, e.g. "target".
|
|
|
|
|
|
gdb/
2009-07-02 Pedro Alves <pedro@codesourcery.com>
* linux-nat.c (linux_child_follow_fork): If we're staying attached
to the child process, enable event reporting on it. Don't handle
checkpoints here. Instead, add the child fork to the lwp thread
and inferior lists without clobbering the previous inferior. Let
the thread_db layer learn about a new child process, even if
following the parent.
(linux_nat_switch_fork): Delete lwps of the current inferior only,
instead of clearing the whole list. Use thread_change_ptid to
give the core the illusion the new checkpoint is still the same
inferior. Clear the register cache.
(linux_handle_extended_wait): Handle checkpoints here.
(linux_multi_process): Turn on.
* linux-fork.c (struct fork_info) <pc>: Remove field.
(init_fork_list): Do not delete the checkpoint from the inferior
list (it is not there).
(fork_load_infrun_state): Don't switch inferior_ptid here. Pass
the new checkpoint's ptid to linux_nat_switch_fork.
(fork_save_infrun_state): Make static. Don't stop the pc field of
fork_info, it's gone.
(linux_fork_mourn_inferior): Don't delete the checkpoint from the
inferior list, it's not there.
(linux_fork_detach): Ditto.
(delete_fork_command): Replace mention of fork/checkpoint by
checkpoint only.
(detach_fork_command): Likewise. Don't delete the checkpoint from
the inferior list.
(info_forks_command): Adjust.
(restore_detach_fork): Delete.
(checkpointing_pid): New.
(linux_fork_checkpointing_p): New.
(save_detach_fork): Delete.
(checkpoint_command): Delete temp_detach_fork. Don't remove
breakpoints, that's a nop. Store the pid of the process we're
checkpointing, and use make_cleanup_restore_integer to restore it.
Don't reinsert breakpoints here.
(process_command, fork_command): Delete.
(restart_command): Update comments to only mention checkpoints,
not forks.
(_initialize_linux_fork): Delete "fork", "process", "info forks"
commands.
* linux-fork.h (fork_save_infrun_state, fork_list): Delete
declarations.
(linux_fork_checkpointing_p): Declare.
* cli/cli-cmds.c (killlist): New.
* cli/cli-cmds.h (killlist): Declare.
* gdbcmd.h (killlist): Declare.
* inferior.c: Include "gdbthread.h".
(detach_inferior_command, kill_inferior_command)
(inferior_command): New.
(info_inferiors_command): Allow specifying a specific inferior id.
(_initialize_inferiors): Register "inferior", "kill inferior" and
"detach inferior" commands.
* infcmd.c (_initialize_infcmd): Make "kill" a prefix command.
* gdbthread.h (any_thread_of_process): Declare.
* thread.c (any_thread_of_process): New.
* NEWS: Mention multi-inferior debugging. Mention 'info
inferiors', 'inferior', 'detach inferior' and 'kill inferior' as
new commands.
(Removed commands): New section, mentioning that 'info forks',
'fork', 'process', 'delete fork' and 'detach fork' are now gone.
gdb/testsuite/
2009-07-02 Pedro Alves <pedro@codesourcery.com>
* gdb.base/multi-forks.exp: Only run detach-on-fork tests on
linux. Adjust to use "inferior", "info inferiors", "detach
inferior" and "kill inferior" instead of "restart", "info fork",
"detach fork" and "delete fork".
* gdb.base/ending-run.exp: Spell out "info".
* gdb.base/help.exp: Adjust to use test_prefix_command_help for
the "kill" command.
gdb/doc/
2009-07-02 Pedro Alves <pedro@codesourcery.com>
* gdb.texinfo (Debugging multiple inferiors): Document the
"inferior", "detach inferior" and "kill inferior" commands.
(Debugging Programs with Multiple Processes): Adjust to mention
generic "inferior" commands. Delete mention of "detach fork" and
"delete fork". Cross reference to "Debugging multiple inferiors"
section.
2009-07-03 05:57:28 +08:00
|
|
|
* Multi-inferior, multi-process debugging.
|
|
|
|
|
|
|
|
|
|
GDB now has generalized support for multi-inferior debugging. See
|
|
|
|
|
"Debugging Multiple Inferiors" in the manual for more information.
|
|
|
|
|
Although availability still depends on target support, the command
|
|
|
|
|
set is more uniform now. The GNU/Linux specific multi-forks support
|
|
|
|
|
has been migrated to this new framework. This implied some user
|
|
|
|
|
visible changes; see "New commands" and also "Removed commands"
|
|
|
|
|
below.
|
|
|
|
|
|
2009-07-21 02:51:42 +08:00
|
|
|
* Target descriptions can now describe the target OS ABI. See the
|
|
|
|
|
"Target Description Format" section in the user manual for more
|
|
|
|
|
information.
|
|
|
|
|
|
2009-07-31 22:39:12 +08:00
|
|
|
* Target descriptions can now describe "compatible" architectures
|
|
|
|
|
to indicate that the target can execute applications for a different
|
|
|
|
|
architecture in addition to those for the main target architecture.
|
|
|
|
|
See the "Target Description Format" section in the user manual for
|
|
|
|
|
more information.
|
|
|
|
|
|
2009-07-31 23:28:27 +08:00
|
|
|
* Multi-architecture debugging.
|
|
|
|
|
|
|
|
|
|
GDB now includes general supports for debugging applications on
|
|
|
|
|
hybrid systems that use more than one single processor architecture
|
|
|
|
|
at the same time. Each such hybrid architecture still requires
|
|
|
|
|
specific support to be added. The only hybrid architecture supported
|
|
|
|
|
in this version of GDB is the Cell Broadband Engine.
|
|
|
|
|
|
|
|
|
|
* GDB now supports integrated debugging of Cell/B.E. applications that
|
|
|
|
|
use both the PPU and SPU architectures. To enable support for hybrid
|
|
|
|
|
Cell/B.E. debugging, you need to configure GDB to support both the
|
|
|
|
|
powerpc-linux or powerpc64-linux and the spu-elf targets, using the
|
|
|
|
|
--enable-targets configure option.
|
|
|
|
|
|
2009-10-05 01:39:30 +08:00
|
|
|
* Non-stop mode debugging.
|
|
|
|
|
|
|
|
|
|
For some targets, GDB now supports an optional mode of operation in
|
|
|
|
|
which you can examine stopped threads while other threads continue
|
|
|
|
|
to execute freely. This is referred to as non-stop mode, with the
|
|
|
|
|
old mode referred to as all-stop mode. See the "Non-Stop Mode"
|
|
|
|
|
section in the user manual for more information.
|
|
|
|
|
|
|
|
|
|
To be able to support remote non-stop debugging, a remote stub needs
|
|
|
|
|
to implement the non-stop mode remote protocol extensions, as
|
|
|
|
|
described in the "Remote Non-Stop" section of the user manual. The
|
|
|
|
|
GDB remote stub, gdbserver, has been adjusted to support these
|
|
|
|
|
extensions on linux targets.
|
|
|
|
|
|
2009-04-18 22:54:00 +08:00
|
|
|
* New commands (for set/show, see "New options" below)
|
2008-02-28 04:50:49 +08:00
|
|
|
|
2009-09-15 11:30:08 +08:00
|
|
|
catch syscall [NAME(S) | NUMBER(S)]
|
|
|
|
|
Catch system calls. Arguments, which should be names of system
|
|
|
|
|
calls or their numbers, mean catch only those syscalls. Without
|
|
|
|
|
arguments, every syscall will be caught. When the inferior issues
|
|
|
|
|
any of the specified syscalls, GDB will stop and announce the system
|
|
|
|
|
call, both when it is called and when its call returns. This
|
|
|
|
|
feature is currently available with a native GDB running on the
|
|
|
|
|
Linux Kernel, under the following architectures: x86, x86_64,
|
|
|
|
|
PowerPC and PowerPC64.
|
|
|
|
|
|
2008-05-10 01:02:03 +08:00
|
|
|
find [/size-char] [/max-count] start-address, end-address|+search-space-size,
|
|
|
|
|
val1 [, val2, ...]
|
|
|
|
|
Search memory for a sequence of bytes.
|
|
|
|
|
|
2008-08-07 03:41:33 +08:00
|
|
|
maint set python print-stack
|
|
|
|
|
maint show python print-stack
|
|
|
|
|
Show a stack trace when an error is encountered in a Python script.
|
|
|
|
|
|
|
|
|
|
python [CODE]
|
|
|
|
|
Invoke CODE by passing it to the Python interpreter.
|
|
|
|
|
|
2009-04-18 22:54:00 +08:00
|
|
|
macro define
|
|
|
|
|
macro list
|
|
|
|
|
macro undef
|
|
|
|
|
These allow macros to be defined, undefined, and listed
|
|
|
|
|
interactively.
|
|
|
|
|
|
|
|
|
|
info os processes
|
|
|
|
|
Show operating system information about processes.
|
|
|
|
|
|
gdb/
2009-07-02 Pedro Alves <pedro@codesourcery.com>
* linux-nat.c (linux_child_follow_fork): If we're staying attached
to the child process, enable event reporting on it. Don't handle
checkpoints here. Instead, add the child fork to the lwp thread
and inferior lists without clobbering the previous inferior. Let
the thread_db layer learn about a new child process, even if
following the parent.
(linux_nat_switch_fork): Delete lwps of the current inferior only,
instead of clearing the whole list. Use thread_change_ptid to
give the core the illusion the new checkpoint is still the same
inferior. Clear the register cache.
(linux_handle_extended_wait): Handle checkpoints here.
(linux_multi_process): Turn on.
* linux-fork.c (struct fork_info) <pc>: Remove field.
(init_fork_list): Do not delete the checkpoint from the inferior
list (it is not there).
(fork_load_infrun_state): Don't switch inferior_ptid here. Pass
the new checkpoint's ptid to linux_nat_switch_fork.
(fork_save_infrun_state): Make static. Don't stop the pc field of
fork_info, it's gone.
(linux_fork_mourn_inferior): Don't delete the checkpoint from the
inferior list, it's not there.
(linux_fork_detach): Ditto.
(delete_fork_command): Replace mention of fork/checkpoint by
checkpoint only.
(detach_fork_command): Likewise. Don't delete the checkpoint from
the inferior list.
(info_forks_command): Adjust.
(restore_detach_fork): Delete.
(checkpointing_pid): New.
(linux_fork_checkpointing_p): New.
(save_detach_fork): Delete.
(checkpoint_command): Delete temp_detach_fork. Don't remove
breakpoints, that's a nop. Store the pid of the process we're
checkpointing, and use make_cleanup_restore_integer to restore it.
Don't reinsert breakpoints here.
(process_command, fork_command): Delete.
(restart_command): Update comments to only mention checkpoints,
not forks.
(_initialize_linux_fork): Delete "fork", "process", "info forks"
commands.
* linux-fork.h (fork_save_infrun_state, fork_list): Delete
declarations.
(linux_fork_checkpointing_p): Declare.
* cli/cli-cmds.c (killlist): New.
* cli/cli-cmds.h (killlist): Declare.
* gdbcmd.h (killlist): Declare.
* inferior.c: Include "gdbthread.h".
(detach_inferior_command, kill_inferior_command)
(inferior_command): New.
(info_inferiors_command): Allow specifying a specific inferior id.
(_initialize_inferiors): Register "inferior", "kill inferior" and
"detach inferior" commands.
* infcmd.c (_initialize_infcmd): Make "kill" a prefix command.
* gdbthread.h (any_thread_of_process): Declare.
* thread.c (any_thread_of_process): New.
* NEWS: Mention multi-inferior debugging. Mention 'info
inferiors', 'inferior', 'detach inferior' and 'kill inferior' as
new commands.
(Removed commands): New section, mentioning that 'info forks',
'fork', 'process', 'delete fork' and 'detach fork' are now gone.
gdb/testsuite/
2009-07-02 Pedro Alves <pedro@codesourcery.com>
* gdb.base/multi-forks.exp: Only run detach-on-fork tests on
linux. Adjust to use "inferior", "info inferiors", "detach
inferior" and "kill inferior" instead of "restart", "info fork",
"detach fork" and "delete fork".
* gdb.base/ending-run.exp: Spell out "info".
* gdb.base/help.exp: Adjust to use test_prefix_command_help for
the "kill" command.
gdb/doc/
2009-07-02 Pedro Alves <pedro@codesourcery.com>
* gdb.texinfo (Debugging multiple inferiors): Document the
"inferior", "detach inferior" and "kill inferior" commands.
(Debugging Programs with Multiple Processes): Adjust to mention
generic "inferior" commands. Delete mention of "detach fork" and
"delete fork". Cross reference to "Debugging multiple inferiors"
section.
2009-07-03 05:57:28 +08:00
|
|
|
info inferiors
|
|
|
|
|
List the inferiors currently under GDB's control.
|
|
|
|
|
|
|
|
|
|
inferior NUM
|
|
|
|
|
Switch focus to inferior number NUM.
|
|
|
|
|
|
|
|
|
|
detach inferior NUM
|
|
|
|
|
Detach from inferior number NUM.
|
|
|
|
|
|
|
|
|
|
kill inferior NUM
|
|
|
|
|
Kill inferior number NUM.
|
|
|
|
|
|
2009-04-18 22:54:00 +08:00
|
|
|
* New options
|
|
|
|
|
|
2009-07-31 23:33:50 +08:00
|
|
|
set spu stop-on-load
|
|
|
|
|
show spu stop-on-load
|
|
|
|
|
Control whether to stop for new SPE threads during Cell/B.E. debugging.
|
|
|
|
|
|
2009-07-31 23:35:38 +08:00
|
|
|
set spu auto-flush-cache
|
|
|
|
|
show spu auto-flush-cache
|
|
|
|
|
Control whether to automatically flush the software-managed cache
|
|
|
|
|
during Cell/B.E. debugging.
|
|
|
|
|
|
2009-04-18 22:54:00 +08:00
|
|
|
set sh calling-convention
|
|
|
|
|
show sh calling-convention
|
|
|
|
|
Control the calling convention used when calling SH target functions.
|
|
|
|
|
|
2008-07-11 00:44:47 +08:00
|
|
|
set debug timestamp
|
2008-02-28 04:50:49 +08:00
|
|
|
show debug timestamp
|
2009-04-18 22:54:00 +08:00
|
|
|
Control display of timestamps with GDB debugging output.
|
|
|
|
|
|
|
|
|
|
set disassemble-next-line
|
|
|
|
|
show disassemble-next-line
|
|
|
|
|
Control display of disassembled source lines or instructions when
|
|
|
|
|
the debuggee stops.
|
|
|
|
|
|
|
|
|
|
set remote noack-packet
|
|
|
|
|
show remote noack-packet
|
|
|
|
|
Set/show the use of remote protocol QStartNoAckMode packet. See above
|
|
|
|
|
under "New remote packets."
|
|
|
|
|
|
|
|
|
|
set remote query-attached-packet
|
|
|
|
|
show remote query-attached-packet
|
|
|
|
|
Control use of remote protocol `qAttached' (query-attached) packet.
|
|
|
|
|
|
|
|
|
|
set remote read-siginfo-object
|
|
|
|
|
show remote read-siginfo-object
|
|
|
|
|
Control use of remote protocol `qXfer:siginfo:read' (read-siginfo-object)
|
|
|
|
|
packet.
|
|
|
|
|
|
|
|
|
|
set remote write-siginfo-object
|
|
|
|
|
show remote write-siginfo-object
|
|
|
|
|
Control use of remote protocol `qXfer:siginfo:write' (write-siginfo-object)
|
|
|
|
|
packet.
|
|
|
|
|
|
2009-09-11 05:02:46 +08:00
|
|
|
set remote reverse-continue
|
|
|
|
|
show remote reverse-continue
|
|
|
|
|
Control use of remote protocol 'bc' (reverse-continue) packet.
|
|
|
|
|
|
|
|
|
|
set remote reverse-step
|
|
|
|
|
show remote reverse-step
|
|
|
|
|
Control use of remote protocol 'bs' (reverse-step) packet.
|
|
|
|
|
|
2009-04-18 22:54:00 +08:00
|
|
|
set displaced-stepping
|
|
|
|
|
show displaced-stepping
|
|
|
|
|
Control displaced stepping mode. Displaced stepping is a way to
|
|
|
|
|
single-step over breakpoints without removing them from the debuggee.
|
|
|
|
|
Also known as "out-of-line single-stepping".
|
|
|
|
|
|
|
|
|
|
set debug displaced
|
|
|
|
|
show debug displaced
|
|
|
|
|
Control display of debugging info for displaced stepping.
|
|
|
|
|
|
|
|
|
|
maint set internal-error
|
|
|
|
|
maint show internal-error
|
|
|
|
|
Control what GDB does when an internal error is detected.
|
|
|
|
|
|
|
|
|
|
maint set internal-warning
|
|
|
|
|
maint show internal-warning
|
|
|
|
|
Control what GDB does when an internal warning is detected.
|
2008-02-28 04:50:49 +08:00
|
|
|
|
2008-03-11 07:14:06 +08:00
|
|
|
set exec-wrapper
|
|
|
|
|
show exec-wrapper
|
|
|
|
|
unset exec-wrapper
|
|
|
|
|
Use a wrapper program to launch programs for debugging.
|
2008-03-03 21:24:12 +08:00
|
|
|
|
2008-04-04 23:51:15 +08:00
|
|
|
set multiple-symbols (all|ask|cancel)
|
|
|
|
|
show multiple-symbols
|
|
|
|
|
The value of this variable can be changed to adjust the debugger behavior
|
|
|
|
|
when an expression or a breakpoint location contains an ambiguous symbol
|
|
|
|
|
name (an overloaded function name, for instance).
|
|
|
|
|
|
2008-04-24 18:21:45 +08:00
|
|
|
set breakpoint always-inserted
|
|
|
|
|
show breakpoint always-inserted
|
|
|
|
|
Keep breakpoints always inserted in the target, as opposed to inserting
|
|
|
|
|
them when resuming the target, and removing them when the target stops.
|
|
|
|
|
This option can improve debugger performance on slow remote targets.
|
|
|
|
|
|
2008-05-03 00:00:36 +08:00
|
|
|
set arm fallback-mode (arm|thumb|auto)
|
|
|
|
|
show arm fallback-mode
|
|
|
|
|
set arm force-mode (arm|thumb|auto)
|
|
|
|
|
show arm force-mode
|
|
|
|
|
These commands control how ARM GDB determines whether instructions
|
|
|
|
|
are ARM or Thumb. The default for both settings is auto, which uses
|
|
|
|
|
the current CPSR value for instructions without symbols; previous
|
|
|
|
|
versions of GDB behaved as if "set arm fallback-mode arm".
|
|
|
|
|
|
2022-04-01 17:22:28 +08:00
|
|
|
set arm unwind-secure-frames
|
|
|
|
|
Enable unwinding from Non-secure to Secure mode on Cortex-M with
|
|
|
|
|
Security extension.
|
|
|
|
|
This can trigger security exceptions when unwinding exception stacks.
|
|
|
|
|
|
2008-07-10 17:31:00 +08:00
|
|
|
set disable-randomization
|
|
|
|
|
show disable-randomization
|
|
|
|
|
Standalone programs run with the virtual address space randomization enabled
|
|
|
|
|
by default on some platforms. This option keeps the addresses stable across
|
|
|
|
|
multiple debugging sessions.
|
|
|
|
|
|
2009-04-18 22:54:00 +08:00
|
|
|
set non-stop
|
|
|
|
|
show non-stop
|
|
|
|
|
Control whether other threads are stopped or not when some thread hits
|
|
|
|
|
a breakpoint.
|
|
|
|
|
|
2008-08-20 12:58:34 +08:00
|
|
|
set target-async
|
2009-04-18 22:54:00 +08:00
|
|
|
show target-async
|
2008-08-20 12:58:34 +08:00
|
|
|
Requests that asynchronous execution is enabled in the target, if available.
|
|
|
|
|
In this case, it's possible to resume target in the background, and interact
|
|
|
|
|
with GDB while the target is running. "show target-async" displays the
|
|
|
|
|
current state of asynchronous execution of the target.
|
|
|
|
|
|
gdb:
2009-03-19 Tom Tromey <tromey@redhat.com>
Julian Brown <julian@codesourcery.com>
PR i18n/7220, PR i18n/7821, PR exp/8815, PR exp/9103,
PR i18n/9401, PR exp/9613:
* NEWS: Update
* value.h (value_typed_string): Declare.
(val_print_string): Update.
* valprint.h (print_char_chars): Update.
* valprint.c (print_char_chars): Add type argument. Update.
(val_print_string): Likewise.
* valops.c (value_typed_string): New function.
* utils.c (host_char_to_target): New function.
(parse_escape): Use host_char_to_target, host_hex_value. Update.
Remove '^' case.
(no_control_char_error): Remove.
* typeprint.c (print_type_scalar): Update.
* scm-valprint.c (scm_scmval_print): Update.
* scm-lang.h (scm_printchar, scm_printstr): Update.
* scm-lang.c (scm_printchar): Add type argument.
(scm_printstr): Likewise.
* printcmd.c (print_formatted): Update.
(print_scalar_formatted): Update.
(printf_command) <wide_string_arg, wide_char_arg>: New constants.
Handle '%lc' and '%ls'.
* parser-defs.h (struct typed_stoken): New type.
(struct stoken_vector): Likewise.
(write_exp_string_vector): Declare.
* parse.c (write_exp_string_vector): New function.
* p-valprint.c (pascal_val_print): Update.
* p-lang.h (is_pascal_string_type, pascal_printchar,
pascal_printstr): Update.
* p-lang.c (is_pascal_string_type): Remove 'char_size' argument.
Add 'char_type' argument.
(pascal_emit_char): Add type argument.
(pascal_printchar): Likewise.
(pascal_printstr): Likewise.
* objc-lang.c (objc_emit_char): Add type argument.
(objc_printchar): Likewise.
(objc_printstr): Likewise.
* macroexp.c (get_character_constant): Handle unicode characters.
Use c_parse_escape.
(get_string_literal): Handle unicode strings. Use
c_parse_escape.
* m2-valprint.c (print_unpacked_pointer): Update.
(m2_print_array_contents): Update.
(m2_val_print): Update.
* m2-lang.c (m2_emit_char): Add type argument.
(m2_printchar): Likewise.
(m2_printstr): Likewise.
* language.h (struct language_defn) <la_printchar>: Add type
argument.
<la_printstr, la_emitchar>: Likewise.
(LA_PRINT_CHAR): Likewise.
(LA_PRINT_STRING): Likewise.
(LA_EMIT_CHAR): Likewise.
* language.c (unk_lang_emit_char): Add type argument.
(unk_lang_printchar): Likewise.
(unk_lang_printstr): Likewise.
* jv-valprint.c (java_val_print): Update.
* jv-lang.c (java_emit_char): Add type argument.
* f-valprint.c (f_val_print): Update.
* f-lang.c (f_emit_char): Add type argument.
(f_printchar): Likewise.
(f_printstr): Likewise.
* expprint.c (print_subexp_standard): Update.
* charset.h (target_wide_charset): Declare.
(c_target_char_has_backslash_escape, c_parse_backslash,
host_char_print_literally, host_char_to_target,
target_char_to_host, target_char_to_control_char): Remove.
(enum transliterations): New type.
(convert_between_encodings): Declare.
(HOST_ESCAPE_CHAR): New define.
(host_letter_to_control_character, host_hex_value): Declare.
(enum wchar_iterate_result): New enum.
(struct wchar_iterator): Declare.
(make_wchar_iterator, make_cleanup_wchar_iterator, wchar_iterator,
wchar_push_back): Declare.
* charset-list.h: New file.
* c-valprint.c (textual_name): New function.
(textual_element_type): Handle wide character types.
(c_val_print): Pass original type to textual_element_type. Handle
wide character types.
(c_value_print): Use textual_element_type. Pass original type of
value to val_print.
* c-lang.h (enum c_string_type): New type.
(c_printchar, c_printstr): Update.
* c-lang.c (classify_type): New function.
(print_wchar): Likewise.
(c_emit_char): Add type argument. Handle wide characters.
(c_printchar): Likewise.
(c_printstr): Add type argument. Handle wide and multibyte
character sets.
(convert_ucn): New function.
(emit_numeric_character): Likewise.
(convert_octal): Likewise.
(convert_hex): Likewise.
(ADVANCE): New macro.
(convert_escape): New function.
(parse_one_string): Likewise.
(evaluate_subexp_c): Likewise.
(exp_descriptor_c): New global.
(c_language_defn): Use exp_descriptor_c.
(cplus_language_defn): Likewise.
(asm_language_defn): Likewise.
(minimal_language_defn): Likewise.
(charset_for_string_type): New function.
* c-exp.y (%union): Add 'svec' and 'tsval'.
(CHAR): New token.
(exp): Add CHAR production.
(string_exp): Rewrite.
(exp) <string_exp>: Rewrite.
(tempbuf): Now global.
(tempbuf_init): New global.
(parse_string_or_char): New function.
(yylex) <tempbuf>: Now global.
<tokptr, tempbufindex, tempbufsize, token_string, class_prefix>:
Remove.
Handle 'u', 'U', and 'L' prefixes. Call parse_string_or_char.
(c_parse_escape): New function.
* auxv.c (fprint_target_auxv): Update.
* ada-valprint.c (ada_emit_char): Add type argument.
(ada_printchar): Likewise.
(ada_print_scalar): Update.
(printstr): Add type argument. Update calls to ada_emit_char.
(ada_printstr): Add type argument.
(ada_val_print_array): Update.
(ada_val_print_1): Likewise.
* ada-lang.c (emit_char): Add type argument.
* ada-lang.h (ada_emit_char, ada_printchar, ada_printstr): Add
type arguments.
* gdb_locale.h: Include langinfo.h.
* charset.c (_initialize_charset): Set default host charset from
the locale. Don't register charsets. Add target-wide-charset
commands. Call find_charset_names.
(struct charset, struct translation): Remove.
(GDB_DEFAULT_HOST_CHARSET): Remove.
(GDB_DEFAULT_TARGET_WIDE_CHARSET): New define.
(target_wide_charset_name): New global.
(show_host_charset_name): Handle "auto".
(show_target_wide_charset_name): New function.
(host_charset_enum, target_charset_enum): Remove.
(charset_enum): New global.
(all_charsets, register_charset, lookup_charset, all_translations,
register_translation, lookup_translation): Remove.
(simple_charset, ascii_print_literally, ascii_to_control): Remove.
(iso_8859_print_literally, iso_8859_to_control,
iso_8859_family_charset): Remove.
(ebcdic_print_literally, ebcdic_to_control,
ebcdic_family_charset): Remove.
(struct cached_iconv, check_iconv_cache, cached_iconv_convert,
register_iconv_charsets): Remove.
(target_wide_charset_be_name, target_wide_charset_le_name): New
globals.
(identity_either_char_to_other): Remove.
(set_be_le_names, validate): New functions.
(backslashable, backslashed, represented): Remove.
(default_c_target_char_has_backslash_escape): Remove.
(default_c_parse_backslash, iconv_convert): Remove.
(ascii_to_iso_8859_1_table, ascii_to_ebcdic_us_table,
ascii_to_ibm1047_table, iso_8859_1_to_ascii_table,
iso_8859_1_to_ebcdic_us_table, iso_8859_1_to_ibm1047_table,
ebcdic_us_to_ascii_table, ebcdic_us_to_iso_8859_1_table,
ebcdic_us_to_ibm1047_table, ibm1047_to_ascii_table,
ibm1047_to_iso_8859_1_table, ibm1047_to_ebcdic_us_table): Remove.
(table_convert_char, table_translation, simple_table_translation):
Remove.
(current_host_charset, current_target_charset,
c_target_char_has_backslash_escape_func,
c_target_char_has_backslash_escape_baton): Remove.
(c_parse_backslash_func, c_parse_backslash_baton): Remove.
(host_char_to_target_func, host_char_to_target_baton): Remove.
(target_char_to_host_func, target_char_to_host_baton): Remove.
(cached_iconv_host_to_target, cached_iconv_target_to_host):
Remove.
(lookup_charset_or_error, check_valid_host_charset): Remove.
(set_host_and_target_charsets): Remove.
(set_host_charset, set_target_charset): Remove.
(set_host_charset_sfunc, set_target_charset_sfunc): Rewrite.
(set_target_wide_charset_sfunc): New function.
(show_charset): Print target wide character set.
(host_charset, target_charset): Rewrite.
(target_wide_charset): New function.
(c_target_char_has_backslash_escape): Remove.
(c_parse_backslash): Remove.
(host_letter_to_control_character): New function.
(host_char_print_literally): Remove.
(host_hex_value): New function.
(target_char_to_control_char): Remove.
(cleanup_iconv): New function.
(convert_between_encodings): New function.
(target_char_to_host): Remove.
(struct wchar_iterator): Define.
(make_wchar_iterator, make_cleanup_wchar_iterator, wchar_iterator,
wchar_push_back): New functions.
(do_cleanup_iterator): New function.
(char_ptr): New typedef.
(charsets): New global.
(add_one, find_charset_names): New functions.
(default_charset_names): New global.
(auto_host_charset_name): Likewise.
* aclocal.m4, config.in, configure: Rebuild.
* configure.ac: Call AM_LANGINFO_CODESET.
(GDB_DEFAULT_HOST_CHARSET): Default to UTF-8.
(AM_ICONV): Invoke earlier.
* acinclude.m4: Include codeset.m4. Subst LIBICONV_INCLUDE and
LIBICONV_LIBDIR. Check for libiconv in build tree.
* Makefile.in (LIBICONV_LIBDIR, LIBICONV_INCLUDE): New macros.
(INTERNAL_CFLAGS_BASE): Add LIBICONV_INCLUDE.
(INTERNAL_LDFLAGS): Add LIBICONV_LIBDIR.
* gdb_obstack.h (obstack_grow_wstr): New define.
* gdb_wchar.h: New file.
* defs.h: Include it.
gdb/testsuite:
* gdb.base/store.exp: Update for change to escape output.
* gdb.base/callfuncs.exp (fetch_all_registers): Update for change
to escape output.
* gdb.base/pointers.exp: Update for change to escape output.
* gdb.base/long_long.exp (gdb_test_long_long): Update for change
to escape output.
* gdb.base/constvars.exp (do_constvar_tests): Update for change to
escape output.
* gdb.base/call-rt-st.exp (print_struct_call): Update for change
to escape output.
* gdb.cp/ref-types.exp (gdb_start_again): Update for change to
escape output.
* gdb.base/setvar.exp: Update for change to escape output.
* lib/gdb.exp (default_gdb_start): Set LC_CTYPE to C.
* gdb.base/printcmds.exp (test_print_all_chars): Update for change
to escape output.
(test_print_string_constants): Likewise.
* gdb.base/charset.exp (valid_host_charset): Check size of
wchar_t. Handle UCS-2 and UCS-4. Add tests for wide and unicode
cases. Handle "auto"-related output.
* gdb.base/charset.c (char16_t, char32_t): New typedefs.
(uvar, Uvar): New globals.
gdb/doc:
* gdb.texinfo (Character Sets): Remove obsolete text. Document
set target-wide-charset.
(Requirements): Mention iconv.
2009-03-21 07:04:40 +08:00
|
|
|
set target-wide-charset
|
|
|
|
|
show target-wide-charset
|
|
|
|
|
The target-wide-charset is the name of the character set that GDB
|
|
|
|
|
uses when printing characters whose type is wchar_t.
|
|
|
|
|
|
2009-01-07 01:07:08 +08:00
|
|
|
set tcp auto-retry (on|off)
|
|
|
|
|
show tcp auto-retry
|
|
|
|
|
set tcp connect-timeout
|
|
|
|
|
show tcp connect-timeout
|
|
|
|
|
These commands allow GDB to retry failed TCP connections to a remote stub
|
|
|
|
|
with a specified timeout period; this is useful if the stub is launched
|
|
|
|
|
in parallel with GDB but may not be ready to accept connections immediately.
|
|
|
|
|
|
2009-05-16 00:53:45 +08:00
|
|
|
set libthread-db-search-path
|
|
|
|
|
show libthread-db-search-path
|
|
|
|
|
Control list of directories which GDB will search for appropriate
|
|
|
|
|
libthread_db.
|
|
|
|
|
|
2009-06-11 19:57:46 +08:00
|
|
|
set schedule-multiple (on|off)
|
|
|
|
|
show schedule-multiple
|
|
|
|
|
Allow GDB to resume all threads of all processes or only threads of
|
|
|
|
|
the current process.
|
|
|
|
|
|
2009-09-01 04:18:46 +08:00
|
|
|
set stack-cache
|
|
|
|
|
show stack-cache
|
|
|
|
|
Use more aggressive caching for accesses to the stack. This improves
|
|
|
|
|
performance of remote debugging (particularly backtraces) without
|
|
|
|
|
affecting correctness.
|
|
|
|
|
|
2009-09-11 02:56:45 +08:00
|
|
|
set interactive-mode (on|off|auto)
|
|
|
|
|
show interactive-mode
|
|
|
|
|
Control whether GDB runs in interactive mode (on) or not (off).
|
|
|
|
|
When in interactive mode, GDB waits for the user to answer all
|
|
|
|
|
queries. Otherwise, GDB does not wait and assumes the default
|
|
|
|
|
answer. When set to auto (the default), GDB determines which
|
|
|
|
|
mode to use based on the stdin settings.
|
|
|
|
|
|
gdb/
2009-07-02 Pedro Alves <pedro@codesourcery.com>
* linux-nat.c (linux_child_follow_fork): If we're staying attached
to the child process, enable event reporting on it. Don't handle
checkpoints here. Instead, add the child fork to the lwp thread
and inferior lists without clobbering the previous inferior. Let
the thread_db layer learn about a new child process, even if
following the parent.
(linux_nat_switch_fork): Delete lwps of the current inferior only,
instead of clearing the whole list. Use thread_change_ptid to
give the core the illusion the new checkpoint is still the same
inferior. Clear the register cache.
(linux_handle_extended_wait): Handle checkpoints here.
(linux_multi_process): Turn on.
* linux-fork.c (struct fork_info) <pc>: Remove field.
(init_fork_list): Do not delete the checkpoint from the inferior
list (it is not there).
(fork_load_infrun_state): Don't switch inferior_ptid here. Pass
the new checkpoint's ptid to linux_nat_switch_fork.
(fork_save_infrun_state): Make static. Don't stop the pc field of
fork_info, it's gone.
(linux_fork_mourn_inferior): Don't delete the checkpoint from the
inferior list, it's not there.
(linux_fork_detach): Ditto.
(delete_fork_command): Replace mention of fork/checkpoint by
checkpoint only.
(detach_fork_command): Likewise. Don't delete the checkpoint from
the inferior list.
(info_forks_command): Adjust.
(restore_detach_fork): Delete.
(checkpointing_pid): New.
(linux_fork_checkpointing_p): New.
(save_detach_fork): Delete.
(checkpoint_command): Delete temp_detach_fork. Don't remove
breakpoints, that's a nop. Store the pid of the process we're
checkpointing, and use make_cleanup_restore_integer to restore it.
Don't reinsert breakpoints here.
(process_command, fork_command): Delete.
(restart_command): Update comments to only mention checkpoints,
not forks.
(_initialize_linux_fork): Delete "fork", "process", "info forks"
commands.
* linux-fork.h (fork_save_infrun_state, fork_list): Delete
declarations.
(linux_fork_checkpointing_p): Declare.
* cli/cli-cmds.c (killlist): New.
* cli/cli-cmds.h (killlist): Declare.
* gdbcmd.h (killlist): Declare.
* inferior.c: Include "gdbthread.h".
(detach_inferior_command, kill_inferior_command)
(inferior_command): New.
(info_inferiors_command): Allow specifying a specific inferior id.
(_initialize_inferiors): Register "inferior", "kill inferior" and
"detach inferior" commands.
* infcmd.c (_initialize_infcmd): Make "kill" a prefix command.
* gdbthread.h (any_thread_of_process): Declare.
* thread.c (any_thread_of_process): New.
* NEWS: Mention multi-inferior debugging. Mention 'info
inferiors', 'inferior', 'detach inferior' and 'kill inferior' as
new commands.
(Removed commands): New section, mentioning that 'info forks',
'fork', 'process', 'delete fork' and 'detach fork' are now gone.
gdb/testsuite/
2009-07-02 Pedro Alves <pedro@codesourcery.com>
* gdb.base/multi-forks.exp: Only run detach-on-fork tests on
linux. Adjust to use "inferior", "info inferiors", "detach
inferior" and "kill inferior" instead of "restart", "info fork",
"detach fork" and "delete fork".
* gdb.base/ending-run.exp: Spell out "info".
* gdb.base/help.exp: Adjust to use test_prefix_command_help for
the "kill" command.
gdb/doc/
2009-07-02 Pedro Alves <pedro@codesourcery.com>
* gdb.texinfo (Debugging multiple inferiors): Document the
"inferior", "detach inferior" and "kill inferior" commands.
(Debugging Programs with Multiple Processes): Adjust to mention
generic "inferior" commands. Delete mention of "detach fork" and
"delete fork". Cross reference to "Debugging multiple inferiors"
section.
2009-07-03 05:57:28 +08:00
|
|
|
* Removed commands
|
|
|
|
|
|
|
|
|
|
info forks
|
|
|
|
|
For program forks, this is replaced by the new more generic `info
|
|
|
|
|
inferiors' command. To list checkpoints, you can still use the
|
|
|
|
|
`info checkpoints' command, which was an alias for the `info forks'
|
|
|
|
|
command.
|
|
|
|
|
|
|
|
|
|
fork NUM
|
|
|
|
|
Replaced by the new `inferior' command. To switch between
|
|
|
|
|
checkpoints, you can still use the `restart' command, which was an
|
|
|
|
|
alias for the `fork' command.
|
|
|
|
|
|
|
|
|
|
process PID
|
|
|
|
|
This is removed, since some targets don't have a notion of
|
|
|
|
|
processes. To switch between processes, you can still use the
|
|
|
|
|
`inferior' command using GDB's own inferior number.
|
|
|
|
|
|
|
|
|
|
delete fork NUM
|
|
|
|
|
For program forks, this is replaced by the new more generic `kill
|
|
|
|
|
inferior' command. To delete a checkpoint, you can still use the
|
|
|
|
|
`delete checkpoint' command, which was an alias for the `delete
|
|
|
|
|
fork' command.
|
|
|
|
|
|
|
|
|
|
detach fork NUM
|
|
|
|
|
For program forks, this is replaced by the new more generic `detach
|
|
|
|
|
inferior' command. To detach a checkpoint, you can still use the
|
|
|
|
|
`detach checkpoint' command, which was an alias for the `detach
|
|
|
|
|
fork' command.
|
|
|
|
|
|
2008-11-27 17:23:01 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
x86/x86_64 Darwin i[34567]86-*-darwin*
|
|
|
|
|
|
2009-01-16 12:31:09 +08:00
|
|
|
x86_64 MinGW x86_64-*-mingw*
|
|
|
|
|
|
2008-08-23 01:26:54 +08:00
|
|
|
* New targets
|
|
|
|
|
|
2009-05-18 21:25:35 +08:00
|
|
|
Lattice Mico32 lm32-*
|
2008-08-23 01:26:54 +08:00
|
|
|
x86 DICOS i[34567]86-*-dicos*
|
2009-02-18 01:56:50 +08:00
|
|
|
x86_64 DICOS x86_64-*-dicos*
|
2009-08-06 18:28:38 +08:00
|
|
|
S+core 3 score-*-*
|
2008-08-23 01:26:54 +08:00
|
|
|
|
2009-04-20 04:05:23 +08:00
|
|
|
* The GDB remote stub, gdbserver, now supports x86 Windows CE
|
|
|
|
|
(mingw32ce) debugging.
|
|
|
|
|
|
2008-11-19 04:41:42 +08:00
|
|
|
* Removed commands
|
|
|
|
|
|
|
|
|
|
catch load
|
|
|
|
|
catch unload
|
|
|
|
|
These commands were actually not implemented on any target.
|
|
|
|
|
|
2008-02-28 04:50:49 +08:00
|
|
|
*** Changes in GDB 6.8
|
2007-09-18 03:30:05 +08:00
|
|
|
|
2008-01-19 23:03:50 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
NetBSD/hppa hppa*-*netbsd*
|
2008-02-12 05:58:41 +08:00
|
|
|
Xtensa GNU/Linux xtensa*-*-linux*
|
2008-01-19 23:03:50 +08:00
|
|
|
|
|
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
NetBSD/hppa hppa*-*-netbsd*
|
2020-06-05 18:24:20 +08:00
|
|
|
Xtensa GNU/Linux xtensa*-*-linux*
|
2008-01-19 23:03:50 +08:00
|
|
|
|
2008-01-06 05:50:44 +08:00
|
|
|
* Change in command line behavior -- corefiles vs. process ids.
|
|
|
|
|
|
|
|
|
|
When the '-p NUMBER' or '--pid NUMBER' options are used, and
|
|
|
|
|
attaching to process NUMBER fails, GDB no longer attempts to open a
|
|
|
|
|
core file named NUMBER. Attaching to a program using the -c option
|
|
|
|
|
is no longer supported. Instead, use the '-p' or '--pid' options.
|
|
|
|
|
|
2007-10-21 18:27:49 +08:00
|
|
|
* GDB can now be built as a native debugger for debugging Windows x86
|
|
|
|
|
(mingw32) Portable Executable (PE) programs.
|
|
|
|
|
|
2007-09-28 14:24:20 +08:00
|
|
|
* Pending breakpoints no longer change their number when their address
|
2007-10-04 04:42:08 +08:00
|
|
|
is resolved.
|
2007-09-28 14:24:20 +08:00
|
|
|
|
|
|
|
|
* GDB now supports breakpoints with multiple locations,
|
2007-10-04 04:42:08 +08:00
|
|
|
including breakpoints on C++ constructors, inside C++ templates,
|
|
|
|
|
and in inlined functions.
|
2007-09-28 14:24:20 +08:00
|
|
|
|
2007-12-07 01:07:15 +08:00
|
|
|
* GDB's ability to debug optimized code has been improved. GDB more
|
|
|
|
|
accurately identifies function bodies and lexical blocks that occupy
|
|
|
|
|
more than one contiguous range of addresses.
|
|
|
|
|
|
* NEWS: Document target described register support for PowerPC.
* ppc-tdep.h: Remove ppc_spr constants.
(struct gdbarch_tdep): Remove regs, ppc_sr0_regnum, and
ppc_builtin_type_vec128 members.
(PPC_R0_REGNUM, PPC_F0_REGNUM, PPC_PC_REGNUM, PPC_MSR_REGNUM)
(PPC_CR_REGNUM, PPC_LR_REGNUM, PPC_CTR_REGNUM, PPC_XER_REGNUM)
(PPC_FPSCR_REGNUM, PPC_MQ_REGNUM, PPC_SPE_UPPER_GP0_REGNUM)
(PPC_SPE_ACC_REGNUM, PPC_SPE_FSCR_REGNUM, PPC_VR0_REGNUM)
(PPC_VSCR_REGNUM, PPC_VRSAVE_REGNUM, PPC_NUM_REGS): New constants.
* rs6000-tdep.c: Include preparsed descriptions.
(init_sim_regno_table): Do not iterate over pseudo registers.
Look up segment registers by name. Use sim_spr_register_name
for SPRs.
(rs6000_register_sim_regno): Call init_sim_regno_table here.
(rs6000_builtin_type_vec128): Delete.
(rs6000_register_name): Only handle SPE pseudo registers and upper
halves. Call tdesc_register_name for everything else.
(rs6000_register_type): Delete. Replace with...
(rs6000_pseudo_register_type): ...this new function. Only handle
SPE pseudo registers.
(rs6000_register_reggroup_p): Delete. Replace with...
(rs6000_pseudo_register_reggroup_p): ...this new function. Only
handle SPE pseudo registers.
(rs6000_convert_register_p): Use ppc_fp0_regnum instead of
"struct reg".
(rs6000_register_to_value, rs6000_value_to_register): Remove check
of reg->fpr.
(e500_register_reggroup_p): Delete.
(STR, R, R4, R8, R16, F, P8, R32, R64, R0, A4, S, S4, SN4, S64)
(COMMON_UISA_REGS, PPC_UISA_SPRS, PPC_UISA_NOFP_SPRS)
(PPC_SEGMENT_REGS, PPC_OEA_SPRS, PPC_ALTIVEC_REGS, PPC_SPE_GP_REGS)
(PPC_SPE_UPPER_GP_REGS, PPC_EV_PSEUDO_REGS): Delete macros.
(registers_powerpc, registers_403, registers_403GC, registers_505)
(registers_860, registers_601, registers_602, registers_603)
(registers_604, registers_750, registers_7400, registers_e500): Delete
variables.
(struct variant): Delete nregs, npregs, num_tot_regs, and regs. Add
tdesc.
(tot_num_registers, num_registers, num_pseudo_registers): Delete.
(variants): Delete outdated comment. Use standard target descriptions
instead of "struct reg" arrays.
(init_variants): Delete.
(rs6000_gdbarch_init): Do not guess word size from the BFD
architecture if we have a target description. Select a variant
before creating a new architecture. Use the variant's target
description if the target did not define a register layout.
Validate target-supplied registers. Reject mismatches. Use
fixed register numbers and new constants instead of magic
numbers. Call set_gdbarch_ps_regnum. Call tdesc_use_registers.
(_initialize_rs6000_tdep): Initialize the preparsed target
descriptions.
* target-descriptions.c (tdesc_predefined_types): Add int128 and
uint128.
(tdesc_find_register_early): New function.
(tdesc_numbered_register): Use it.
(tdesc_register_size): New function.
(tdesc_use_registers): Take a target_desc argument. Do not use
gdbarch_target_desc.
* target-descriptions.h (tdesc_use_registers): Update prototype
and comment.
(tdesc_register_size): New prototype.
* Makefile.in (powerpc_32_c, powerpc_403_c, powerpc_403gc_c)
(powerpc_505_c, powerpc_601_c, powerpc_602_c, powerpc_603_c)
(powerpc_604_c, powerpc_64_c, powerpc_7400_c, powerpc_750_c)
(powerpc_860_c, powerpc_e500_c, rs6000_c): New macros.
(rs6000-tdep.o): Update.
* arm-tdep.c (arm_gdbarch_init): Update call to tdesc_use_registers.
* m68k-tdep.c (m68k_gdbarch_init): Likewise.
* mips-tdep.c (mips_gdbarch_init): Likewise.
* gdb.texinfo (Predefined Target Types): Add int128
and uint128.
(Standard Target Features): Add PowerPC features.
* gdb.xml/tdesc-regs.exp: Add PowerPC support.
* sim-ppc.h (sim_spr_register_name): New prototype.
* gdb-sim.c (regnum2spr): Rename to...
(sim_spr_register_name): ... this. Make global.
2007-10-16 03:45:31 +08:00
|
|
|
* Target descriptions can now describe registers for PowerPC.
|
|
|
|
|
|
2007-10-16 04:00:23 +08:00
|
|
|
* The GDB remote stub, gdbserver, now supports the AltiVec and SPE
|
|
|
|
|
registers on PowerPC targets.
|
|
|
|
|
|
2007-10-25 04:49:59 +08:00
|
|
|
* The GDB remote stub, gdbserver, now supports thread debugging on GNU/Linux
|
|
|
|
|
targets even when the libthread_db library is not available.
|
|
|
|
|
|
* remote.c (remote_cmdlist): New variable.
(PACKET_vFile_open, PACKET_vFile_pread, PACKET_vFile_pwrite)
(PACKET_vFile_close, PACKET_vFile_unlink): New constants.
(remote_buffer_add_string, remote_buffer_add_bytes)
(remote_buffer_add_int, remote_hostio_parse_result)
(remote_hostio_send_command, remote_hostio_open, remote_hostio_pwrite)
(remote_hostio_pread, remote_hostio_close, remote_hostio_unlink)
(remote_fileio_errno_to_host, remote_hostio_error, fclose_cleanup)
(remote_hostio_close_cleanup, remote_file_put, remote_file_get)
(remote_file_delete, remote_put_command, remote_get_command)
(remote_delete_command, remote_command): New functions.
(_initialize_remote): Register new packets and commands.
* Makefile.in (gdb_fileio_h): New variable.
(remote.o): Update.
(SUBDIR_MI_OBS): Add mi-cmd-target.o.
(SUBDIR_MI_SRCS): Add mi/mi-cmd-target.c.
(mi-cmd-target.o): New rule.
* mi/mi-cmd-target.c: New file.
* mi/mi-cmds.c (mi_cmds): Add target-file-delete, target-file-get,
and target-file-put.
* mi/mi-cmds.h (mi_cmd_target_file_get, mi_cmd_target_file_put)
(mi_cmd_target_file_delete): Declare.
* remote.h (remote_file_put, remote_file_get, remote_file_delete):
Declare.
* NEWS: Describe new file transfer support.
* gdb.texinfo (Debugging Programs with Multiple Processes): Correct
formatting.
(Remote Debugging): Add File Transfer section.
(Remote Configuration): Document Host I/O packets.
(GDB/MI): Add GDB/MI File Transfer Commands section.
(Remote Protocol): Add Host I/O Packets section.
(Packets): Add vFile.
* Makefile.in (OBS): Add hostio.o.
(hostio.o): New rule.
* server.h (handle_vFile): Declare.
* hostio.c: New file.
* server.c (handle_v_requests): Take packet_len and new_packet_len
for binary packets. Call handle_vFile.
(main): Update call to handle_v_requests.
* gdb.server/file-transfer.exp, gdb.server/transfer.txt,
gdb.mi/mi-file-transfer.exp: New.
2007-12-01 05:50:19 +08:00
|
|
|
* The GDB remote stub, gdbserver, now supports the new file transfer
|
|
|
|
|
commands (remote put, remote get, and remote delete).
|
|
|
|
|
|
* linux-low.c (linux_attach_lwp): Do not _exit after errors.
(linux_kill, linux_detach): Clean up the process list.
* remote-utils.c (remote_open): Improve port number parsing.
(putpkt_binary, input_interrupt): Only send interrupts if the target
is running.
* server.c (extended_protocol): Make static.
(attached): Define earlier.
(exit_requested, response_needed, program_argv): New variables.
(target_running): New.
(start_inferior): Clear attached here.
(attach_inferior): Set attached here.
(require_running): Define.
(handle_query): Use require_running and target_running. Implement
"monitor exit".
(handle_v_attach, handle_v_run): New.
(handle_v_requests): Use require_running. Handle vAttach and vRun.
(gdbserver_usage): Update.
(main): Redo argument parsing. Handle --debug and --multi. Handle
--attach along with other options or after the port. Save
program_argv. Support no initial program. Resynchronize
communication with GDB after an error. Handle "monitor exit".
Use require_running and target_running. Always allow the extended
protocol. Do not error out for Hc0 or Hc-1. Do not automatically
restart in extended mode.
* README: Refer to the GDB manual. Update --attach usage.
* remote.c (struct remote_state): Add cached_wait_status.
(remote_exec_file): New variable.
(PACKET_vAttach, PACKET_vRun): New constants.
(extended_remote_restart): Do not query for status.
(struct start_remote_args): New.
(remote_start_remote): Take it as a second argument. Check
whether the target is running. Issue an error for non-running
non-extended targets. Cache the wait status. Set inferior_ptid
here.
(remote_open_1): Prompt to disconnect non-running targets. Make
sure the target is marked running. Do not set inferior_ptid here.
Update call to remote_start_remote. Do not call remote_check_symbols
if the target is not running.
(remote_detach_1): Rename from remote_detach. Take an EXTENDED
argument. Handle a non-running target.
(remote_detach): Use it.
(extended_remote_detach): New.
(remote_disconnect): Fix typo. Use remoute_mourn_1.
(extended_remote_attach_1, extended_remote_attach)
(extended_async_remote_attach): New.
(remote_vcont_resume): Remove unused variable.
(remote_wait, remote_async_wait): Use any cached wait status.
(putpkt_binary, getpkt): Clear any cached wait status.
(extended_remoute_mourn_1): New.
(extended_remote_mourn): Use it.
(extended_async_remote_mourn, extended_remote_run): New.
(extended_remote_create_inferior_1): New.
(extended_remote_create_inferior): Use it.
(extended_remote_async_create_inferior): Likewise.
(remote_xfer_partial): Skip for non-executing targets.
(init_extended_remote_ops): Set to_detach and to_attach.
(init_extended_async_remote_ops): Likewise. Use
extended_async_remote_mourn.
(_initialize_remote): Register vAttach, vRun, and
set remote exec-file.
* NEWS: Mention vAttach, vRun, and gdbserver extended-remote support.
* gdb.server/ext-attach.c, gdb.server/ext-attach.exp,
gdb.server/ext-run.exp: New files.
* lib/gdbserver-support.exp (gdbserver_download): New.
(gdbserver_start): New. Update gdbserver expected
output.
(gdbserver_spawn): Use them.
(gdbserver_start_extended): New.
* gdb.texinfo (Using the `gdbserver' Program): Add security
warning. Rearrange into subsections and subsubsections. Document
--multi and --debug. Correct --with-sysroot typo. Update --attach
usage. Make load reference clearer. Document monitor exit.
(Remote Configuration): Document set remote exec-file, attach-packet,
and run-packet.
(Packets): Document vAttach and vRun.
2008-01-30 08:51:50 +08:00
|
|
|
* The GDB remote stub, gdbserver, now supports run and attach in
|
|
|
|
|
extended-remote mode.
|
|
|
|
|
|
2007-10-25 13:57:58 +08:00
|
|
|
* hppa*64*-*-hpux11* target broken
|
2008-06-08 06:21:28 +08:00
|
|
|
The debugger is unable to start a program and fails with the following
|
|
|
|
|
error: "Error trying to get information about dynamic linker".
|
|
|
|
|
The gdb-6.7 release is also affected.
|
2007-10-25 13:57:58 +08:00
|
|
|
|
2007-11-17 09:02:01 +08:00
|
|
|
* GDB now supports the --enable-targets= configure option to allow
|
|
|
|
|
building a single GDB executable that supports multiple remote
|
|
|
|
|
target architectures.
|
|
|
|
|
|
2008-02-01 05:07:37 +08:00
|
|
|
* GDB now supports debugging C and C++ programs which use the
|
|
|
|
|
Decimal Floating Point extension. In addition, the PowerPC target
|
|
|
|
|
now has a set of pseudo-registers to inspect decimal float values
|
|
|
|
|
stored in two consecutive float registers.
|
|
|
|
|
|
2008-02-15 04:20:44 +08:00
|
|
|
* The -break-insert MI command can optionally create pending
|
|
|
|
|
breakpoints now.
|
|
|
|
|
|
2008-02-20 02:20:45 +08:00
|
|
|
* Improved support for debugging Ada
|
2008-06-08 06:21:28 +08:00
|
|
|
Many improvements to the Ada language support have been made. These
|
|
|
|
|
include:
|
2008-02-20 02:20:45 +08:00
|
|
|
- Better support for Ada2005 interface types
|
|
|
|
|
- Improved handling of arrays and slices in general
|
|
|
|
|
- Better support for Taft-amendment types
|
|
|
|
|
- The '{type} ADDRESS' expression is now allowed on the left hand-side
|
|
|
|
|
of an assignment
|
|
|
|
|
- Improved command completion in Ada
|
|
|
|
|
- Several bug fixes
|
|
|
|
|
|
2008-06-08 06:21:28 +08:00
|
|
|
* GDB on GNU/Linux and HP/UX can now debug through "exec" of a new
|
|
|
|
|
process.
|
|
|
|
|
|
* remote.c (remote_cmdlist): New variable.
(PACKET_vFile_open, PACKET_vFile_pread, PACKET_vFile_pwrite)
(PACKET_vFile_close, PACKET_vFile_unlink): New constants.
(remote_buffer_add_string, remote_buffer_add_bytes)
(remote_buffer_add_int, remote_hostio_parse_result)
(remote_hostio_send_command, remote_hostio_open, remote_hostio_pwrite)
(remote_hostio_pread, remote_hostio_close, remote_hostio_unlink)
(remote_fileio_errno_to_host, remote_hostio_error, fclose_cleanup)
(remote_hostio_close_cleanup, remote_file_put, remote_file_get)
(remote_file_delete, remote_put_command, remote_get_command)
(remote_delete_command, remote_command): New functions.
(_initialize_remote): Register new packets and commands.
* Makefile.in (gdb_fileio_h): New variable.
(remote.o): Update.
(SUBDIR_MI_OBS): Add mi-cmd-target.o.
(SUBDIR_MI_SRCS): Add mi/mi-cmd-target.c.
(mi-cmd-target.o): New rule.
* mi/mi-cmd-target.c: New file.
* mi/mi-cmds.c (mi_cmds): Add target-file-delete, target-file-get,
and target-file-put.
* mi/mi-cmds.h (mi_cmd_target_file_get, mi_cmd_target_file_put)
(mi_cmd_target_file_delete): Declare.
* remote.h (remote_file_put, remote_file_get, remote_file_delete):
Declare.
* NEWS: Describe new file transfer support.
* gdb.texinfo (Debugging Programs with Multiple Processes): Correct
formatting.
(Remote Debugging): Add File Transfer section.
(Remote Configuration): Document Host I/O packets.
(GDB/MI): Add GDB/MI File Transfer Commands section.
(Remote Protocol): Add Host I/O Packets section.
(Packets): Add vFile.
* Makefile.in (OBS): Add hostio.o.
(hostio.o): New rule.
* server.h (handle_vFile): Declare.
* hostio.c: New file.
* server.c (handle_v_requests): Take packet_len and new_packet_len
for binary packets. Call handle_vFile.
(main): Update call to handle_v_requests.
* gdb.server/file-transfer.exp, gdb.server/transfer.txt,
gdb.mi/mi-file-transfer.exp: New.
2007-12-01 05:50:19 +08:00
|
|
|
* New commands
|
|
|
|
|
|
2008-02-08 03:23:10 +08:00
|
|
|
set print frame-arguments (all|scalars|none)
|
|
|
|
|
show print frame-arguments
|
|
|
|
|
The value of this variable can be changed to control which argument
|
|
|
|
|
values should be printed by the debugger when displaying a frame.
|
|
|
|
|
|
* remote.c (remote_cmdlist): New variable.
(PACKET_vFile_open, PACKET_vFile_pread, PACKET_vFile_pwrite)
(PACKET_vFile_close, PACKET_vFile_unlink): New constants.
(remote_buffer_add_string, remote_buffer_add_bytes)
(remote_buffer_add_int, remote_hostio_parse_result)
(remote_hostio_send_command, remote_hostio_open, remote_hostio_pwrite)
(remote_hostio_pread, remote_hostio_close, remote_hostio_unlink)
(remote_fileio_errno_to_host, remote_hostio_error, fclose_cleanup)
(remote_hostio_close_cleanup, remote_file_put, remote_file_get)
(remote_file_delete, remote_put_command, remote_get_command)
(remote_delete_command, remote_command): New functions.
(_initialize_remote): Register new packets and commands.
* Makefile.in (gdb_fileio_h): New variable.
(remote.o): Update.
(SUBDIR_MI_OBS): Add mi-cmd-target.o.
(SUBDIR_MI_SRCS): Add mi/mi-cmd-target.c.
(mi-cmd-target.o): New rule.
* mi/mi-cmd-target.c: New file.
* mi/mi-cmds.c (mi_cmds): Add target-file-delete, target-file-get,
and target-file-put.
* mi/mi-cmds.h (mi_cmd_target_file_get, mi_cmd_target_file_put)
(mi_cmd_target_file_delete): Declare.
* remote.h (remote_file_put, remote_file_get, remote_file_delete):
Declare.
* NEWS: Describe new file transfer support.
* gdb.texinfo (Debugging Programs with Multiple Processes): Correct
formatting.
(Remote Debugging): Add File Transfer section.
(Remote Configuration): Document Host I/O packets.
(GDB/MI): Add GDB/MI File Transfer Commands section.
(Remote Protocol): Add Host I/O Packets section.
(Packets): Add vFile.
* Makefile.in (OBS): Add hostio.o.
(hostio.o): New rule.
* server.h (handle_vFile): Declare.
* hostio.c: New file.
* server.c (handle_v_requests): Take packet_len and new_packet_len
for binary packets. Call handle_vFile.
(main): Update call to handle_v_requests.
* gdb.server/file-transfer.exp, gdb.server/transfer.txt,
gdb.mi/mi-file-transfer.exp: New.
2007-12-01 05:50:19 +08:00
|
|
|
remote put
|
|
|
|
|
remote get
|
|
|
|
|
remote delete
|
|
|
|
|
Transfer files to and from a remote target, and delete remote files.
|
|
|
|
|
|
|
|
|
|
* New MI commands
|
|
|
|
|
|
|
|
|
|
-target-file-put
|
|
|
|
|
-target-file-get
|
|
|
|
|
-target-file-delete
|
|
|
|
|
Transfer files to and from a remote target, and delete remote files.
|
|
|
|
|
|
|
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
vFile:open:
|
|
|
|
|
vFile:close:
|
|
|
|
|
vFile:pread:
|
|
|
|
|
vFile:pwrite:
|
|
|
|
|
vFile:unlink:
|
|
|
|
|
Open, close, read, write, and delete files on the remote system.
|
2007-11-17 09:02:01 +08:00
|
|
|
|
* linux-low.c (linux_attach_lwp): Do not _exit after errors.
(linux_kill, linux_detach): Clean up the process list.
* remote-utils.c (remote_open): Improve port number parsing.
(putpkt_binary, input_interrupt): Only send interrupts if the target
is running.
* server.c (extended_protocol): Make static.
(attached): Define earlier.
(exit_requested, response_needed, program_argv): New variables.
(target_running): New.
(start_inferior): Clear attached here.
(attach_inferior): Set attached here.
(require_running): Define.
(handle_query): Use require_running and target_running. Implement
"monitor exit".
(handle_v_attach, handle_v_run): New.
(handle_v_requests): Use require_running. Handle vAttach and vRun.
(gdbserver_usage): Update.
(main): Redo argument parsing. Handle --debug and --multi. Handle
--attach along with other options or after the port. Save
program_argv. Support no initial program. Resynchronize
communication with GDB after an error. Handle "monitor exit".
Use require_running and target_running. Always allow the extended
protocol. Do not error out for Hc0 or Hc-1. Do not automatically
restart in extended mode.
* README: Refer to the GDB manual. Update --attach usage.
* remote.c (struct remote_state): Add cached_wait_status.
(remote_exec_file): New variable.
(PACKET_vAttach, PACKET_vRun): New constants.
(extended_remote_restart): Do not query for status.
(struct start_remote_args): New.
(remote_start_remote): Take it as a second argument. Check
whether the target is running. Issue an error for non-running
non-extended targets. Cache the wait status. Set inferior_ptid
here.
(remote_open_1): Prompt to disconnect non-running targets. Make
sure the target is marked running. Do not set inferior_ptid here.
Update call to remote_start_remote. Do not call remote_check_symbols
if the target is not running.
(remote_detach_1): Rename from remote_detach. Take an EXTENDED
argument. Handle a non-running target.
(remote_detach): Use it.
(extended_remote_detach): New.
(remote_disconnect): Fix typo. Use remoute_mourn_1.
(extended_remote_attach_1, extended_remote_attach)
(extended_async_remote_attach): New.
(remote_vcont_resume): Remove unused variable.
(remote_wait, remote_async_wait): Use any cached wait status.
(putpkt_binary, getpkt): Clear any cached wait status.
(extended_remoute_mourn_1): New.
(extended_remote_mourn): Use it.
(extended_async_remote_mourn, extended_remote_run): New.
(extended_remote_create_inferior_1): New.
(extended_remote_create_inferior): Use it.
(extended_remote_async_create_inferior): Likewise.
(remote_xfer_partial): Skip for non-executing targets.
(init_extended_remote_ops): Set to_detach and to_attach.
(init_extended_async_remote_ops): Likewise. Use
extended_async_remote_mourn.
(_initialize_remote): Register vAttach, vRun, and
set remote exec-file.
* NEWS: Mention vAttach, vRun, and gdbserver extended-remote support.
* gdb.server/ext-attach.c, gdb.server/ext-attach.exp,
gdb.server/ext-run.exp: New files.
* lib/gdbserver-support.exp (gdbserver_download): New.
(gdbserver_start): New. Update gdbserver expected
output.
(gdbserver_spawn): Use them.
(gdbserver_start_extended): New.
* gdb.texinfo (Using the `gdbserver' Program): Add security
warning. Rearrange into subsections and subsubsections. Document
--multi and --debug. Correct --with-sysroot typo. Update --attach
usage. Make load reference clearer. Document monitor exit.
(Remote Configuration): Document set remote exec-file, attach-packet,
and run-packet.
(Packets): Document vAttach and vRun.
2008-01-30 08:51:50 +08:00
|
|
|
vAttach
|
|
|
|
|
Attach to an existing process on the remote system, in extended-remote
|
|
|
|
|
mode.
|
|
|
|
|
|
|
|
|
|
vRun
|
|
|
|
|
Run a new process on the remote system, in extended-remote mode.
|
|
|
|
|
|
2007-10-04 04:42:08 +08:00
|
|
|
*** Changes in GDB 6.7
|
2006-11-20 08:16:05 +08:00
|
|
|
|
2007-08-29 03:57:11 +08:00
|
|
|
* Resolved 101 resource leaks, null pointer dereferences, etc. in gdb,
|
|
|
|
|
bfd, libiberty and opcodes, as revealed by static analysis donated by
|
|
|
|
|
Coverity, Inc. (http://scan.coverity.com).
|
|
|
|
|
|
2007-07-03 20:14:44 +08:00
|
|
|
* When looking up multiply-defined global symbols, GDB will now prefer the
|
|
|
|
|
symbol definition in the current shared library if it was built using the
|
|
|
|
|
-Bsymbolic linker option.
|
|
|
|
|
|
2007-05-12 02:31:15 +08:00
|
|
|
* When the Text User Interface (TUI) is not configured, GDB will now
|
|
|
|
|
recognize the -tui command-line option and print a message that the TUI
|
|
|
|
|
is not supported.
|
|
|
|
|
|
2006-11-20 08:16:05 +08:00
|
|
|
* The GDB remote stub, gdbserver, now has lower overhead for high
|
|
|
|
|
frequency signals (e.g. SIGALRM) via the QPassSignals packet.
|
|
|
|
|
|
2006-12-06 05:23:20 +08:00
|
|
|
* GDB for MIPS targets now autodetects whether a remote target provides
|
|
|
|
|
32-bit or 64-bit register values.
|
|
|
|
|
|
* NEWS: Mention pointer to member improvements.
* Makefile.in (gnu-v3-abi.o): Delete special rule.
(eval.o, gnu-v3-abi.o, ia64-tdep.o): Update.
* ada-valprint.c (ada_print_scalar): Update for new type codes.
* c-typeprint.c (c_print_type): Update for new type codes.
(c_type_print_varspec_prefix, c_type_print_varspec_suffix)
(c_type_print_base): Likewise.
(c_type_print_args): Rewrite.
* c-valprint.c (c_val_print): Update for new type codes. Remove
support for references to members. Treat methods like functions.
* cp-abi.c (cplus_print_method_ptr, cplus_method_ptr_size)
(cplus_make_method_ptr, cplus_method_ptr_to_value): New.
* cp-abi.h (cplus_print_method_ptr, cplus_method_ptr_size)
(cplus_make_method_ptr, cplus_method_ptr_to_value): New prototypes.
(struct cp_abi_ops): Add corresponding members.
* cp-valprint.c (cp_print_class_method): Delete.
(cp_find_class_member): New function.
(cp_print_class_member): Use it. Simplify support for bogus
member pointers.
* dwarf2read.c (quirk_gcc_member_function_pointer): Use
lookup_methodptr_type.
(read_tag_ptr_to_member_type): Likewise, and lookup_memberptr_type.
* eval.c (evaluate_subexp_standard): Implement EVAL_SKIP for
OP_SCOPE. Update call to value_aggregate_elt. Rewrite member
pointer support.
(evaluate_subexp_for_address): Handle OP_SCOPE explicitly. Handle
references returned by user defined operators.
* f-typeprint.c (f_print_type, f_type_print_varspec_prefix)
(f_type_print_varspec_suffix): Remove support for member pointers.
* gdbtypes.c (lookup_memberptr_type): Renamed from lookup_member_type
and adjusted.
(smash_to_memberptr_type): Likewise, from smash_to_member_type.
(lookup_methodptr_type): New.
(rank_one_type): Adjust for TYPE_CODE_MEMBERPTR.
(recursive_dump_type): Update for new types.
* gdbtypes.h (enum type_code): Replace TYPE_CODE_MEMBER with
TYPE_CODE_MEMBERPTR and TYPE_CODE_METHODPTR.
(lookup_memberptr_type, lookup_methodptr_type)
(smash_to_memberptr_type): New prototypes.
(smash_to_method_type): Formatting fix.
(lookup_member_type, smash_to_member_type): Delete prototypes.
* gnu-v3-abi.c (gnuv3_get_vtable, gnuv3_get_virtual_fn): New.
Do not rely on debug information for the vptr or the method's
enclosing type. Handle function descriptors for IA64.
(gnuv3_virtual_fn_field): Rewrite using the new functions.
(gnuv3_find_method_in, gnuv3_print_method_ptr)
(gnuv3_method_ptr_size, gnuv3_make_method_ptr)
(gnuv3_method_ptr_to_value): New.
(init_gnuv3_ops): Set new members of gnu_v3_abi_ops.
* hpread.c (hpread_type_lookup): Update for new types.
* infcall.c (value_arg_coerce): Likewise.
* m2-typeprint.c (m2_print_type): Remove explicit support
for member pointers.
* m2-valprint.c (m2_val_print): Likewise.
* p-typeprint.c (pascal_type_print_varspec_prefix)
(pascal_type_print_varspec_suffix, pascal_type_print_base): Likewise.
* p-valprint.c (pascal_val_print): Likewise.
(pascal_object_print_class_method, pascal_object_print_class_member):
Delete.
* p-lang.h (pascal_object_print_class_method)
(pascal_object_print_class_member): Delete prototypes.
* stabsread.c (read_type): Update for new types.
* typeprint.c (print_type_scalar): Likewise.
* valops.c (value_struct_elt_for_reference, value_namespace_elt)
(value_maybe_namespace_elt, value_aggregate_elt): Add want_address
argument. Construct a pointer to member if the address of a
function or data member is requested.
(value_cast_pointers): Don't modify the input value.
(value_cast): Adjust pointer to member handling for new types.
Allow null pointer to member constants. Don't modify the input
value.
(value_ind): Remove pointer to member check. Handle function
descriptors for function pointers.
(value_struct_elt, value_find_oload_method_list, check_field):
Remove pointer to member checks.
* value.c (unpack_long): Allow pointers to data members.
(value_from_longest): Allow member pointers.
* value.h (value_aggregate_elt): Add want_address.
* varobj.c (c_variable_editable): Remove check for members.
* gdbarch.sh: Add vtable_function_descriptors and vbit_in_delta.
* ia64-tdep.c (ia64_convert_from_func_ptr_addr): Handle descriptors
in virtual tables.
(ia64_gdbarch_init): Call set_gdbarch_vtable_function_descriptors.
* c-lang.h (cp_print_class_method): Delete prototype.
* arm-tdep.c (arm_gdbarch_init): Call set_gdbarch_vbit_in_delta.
* mips-tdep.c (mips_gdbarch_init): Likewise.
* gdbarch.c, gdbarch.h: Regenerated.
* gdb.cp/classes.exp (test_pointers_to_class_members): Update expected
output. Test the types of members and member pointers.
* gdb.cp/inherit.exp (test_print_mi_member_types): Remove KFAILs for
gdb/2092.
* gdb.cp/member-ptr.exp: Search for a comment instead of a
statement. Enable for GCC. Update expected output for some tests
and add new tests. Remove obsolete GCC KFAILs. Allow GCC's class
layout.
* gdb.cp/member-ptr.cc (Padding, Padding::vspacer, Base, Base::get_x)
(Base::vget_base, Left, Left::vget, Right, Right::vget, Diamond)
(Diamond::vget_base): New.
(main): Add new tests.
* gdb.cp/printmethod.exp: Update expected output for member functions.
* gdb.cp/virtfunc.exp (test_virtual_calls): Add a KFAIL for
print pEe->D::vg().
2007-01-04 02:05:45 +08:00
|
|
|
* Support for C++ member pointers has been improved.
|
|
|
|
|
|
XML feature description support.
* NEWS: Mention target descriptions, "set tdesc filename",
"unset tdesc filename", "show tdesc filename", and
qXfer:features:read.
* arch-utils.c (choose_architecture_for_target): New function.
(gdbarch_info_fill): Call it.
* target-descriptions.c (struct property): Make members non-const.
(struct target_desc): Add arch member.
(target_description_filename): New variable.
(target_find_description): Try via XML first.
(tdesc_architecture): New.
(free_target_description, make_cleanup_free_target_description): New.
(set_tdesc_property): Call xstrdup.
(set_tdesc_architecture, tdesc_set_cmdlist, tdesc_show_cmdlist)
(tdesc_unset_cmdlist, unset_tdesc_cmd, unset_tdesc_filename_cmd)
(set_tdesc_cmd, show_tdesc_cmd, set_tdesc_filename_cmd)
(show_tdesc_filename_cmd, _initialize_target_descriptions): New.
* target-descriptions.h (tdesc_architecture)
(make_cleanup_free_target_description, set_tdesc_architecture): New
prototypes.
* Makefile.in (SFILES): Add xml-tdesc.c.
(COMMON_OBS): Add xml-tdesc.o.
(target-descriptions.o): Update.
(xml-tdesc.o): New rule.
* xml-tdesc.c, xml-tdesc.h: New files.
* remote.c (PACKET_qXfer_features): New enum.
(remote_protocol_features): Add qXfer:features:read.
(remote_xfer_partial): Handle TARGET_OBJECT_AVAILABLE_FEATURES.
(_initialize_remote): Register qXfer:features:read.
* target.h (enum target_object): Add TARGET_OBJECT_AVAILABLE_FEATURES.
* features/gdb-target.dtd: New file.
* linux-i386-low.c (the_low_target): Set arch_string.
* linux-x86-64-low.c (the_low_target): Likewise.
* linux-low.c (linux_arch_string): New.
(linux_target_ops): Add it.
* linux-low.h (struct linux_target_ops): Add arch_string.
* server.c (write_qxfer_response): Use const void * for DATA.
(get_features_xml): New.
(handle_query): Handle qXfer:features:read. Report it for qSupported.
* target.h (struct target_ops): Add arch_string method.
* gdb.texinfo (Target Descriptions): New section.
(General Query Packets): Add QPassSignals anchor. Mention
qXfer:features:read under qSupported. Expand mentions of
qXfer:memory-map:read and QPassSignals. Document
qXfer:features:read.
2007-01-10 06:55:10 +08:00
|
|
|
* GDB now understands XML target descriptions, which specify the
|
|
|
|
|
target's overall architecture. GDB can read a description from
|
|
|
|
|
a local file or over the remote serial protocol.
|
|
|
|
|
|
2007-09-05 08:51:49 +08:00
|
|
|
* Vectors of single-byte data use a new integer type which is not
|
|
|
|
|
automatically displayed as character or string data.
|
|
|
|
|
|
|
|
|
|
* The /s format now works with the print command. It displays
|
|
|
|
|
arrays of single-byte integers and pointers to single-byte integers
|
|
|
|
|
as strings.
|
2007-01-27 04:54:16 +08:00
|
|
|
|
* Makefile.in (arm-tdep.o, eval.o, target-descriptions.o)
(xml-tdesc.o): Update.
* xml-support.c: Add a comment.
(gdb_xml_enums_boolean): New variable.
(gdb_xml_parse_attr_enum): Use strcasecmp.
* xml-support.h (gdb_xml_enums_boolean): Declare.
* xml-tdesc.c (struct tdesc_parsing_data): Record current_feature,
next_regnum, and current_union.
(tdesc_start_feature, tdesc_start_reg, tdesc_start_union)
(tdesc_end_union, tdesc_start_field, tdesc_start_vector)
(field_attributes, union_children, reg_attributes, union_attributes)
(vector_attributes, feature_attributes, feature_children): New.
(target_children): Make static. Add <feature>.
(tdesc_elements): Make static.
* target-descriptions.c (struct tdesc_reg, tdesc_reg_p, type_p)
(struct tdesc_feature, tdesc_feature_p): New types.
(struct target_desc): Add features member.
(struct tdesc_arch_data, tdesc_data): New.
(target_find_description): Clarify error message. Warn about
ignored register descriptions.
(tdesc_has_registers, tdesc_find_feature, tdesc_feature_name)
(tdesc_named_type, tdesc_data_init, tdesc_data_alloc)
(tdesc_data_cleanup, tdesc_numbered_register)
(tdesc_numbered_register_choices, tdesc_find_register)
(tdesc_register_name, tdesc_register_type)
(tdesc_remote_register_number, tdesc_register_reggroup_p)
(set_tdesc_pseudo_register_name, set_tdesc_pseudo_register_type)
(set_tdesc_pseudo_register_reggroup_p, tdesc_use_registers)
(tdesc_free_reg, tdesc_create_reg, tdesc_free_feature)
(tdesc_create_feature, tdesc_record_type): New.
(free_target_description): Free features.
(_initialize_target_descriptions): Initialize tdesc_data.
* arch-utils.c (default_remote_register_number): New.
* arch-utils.h (default_remote_register_number): New prototype.
* target-descriptions.h (set_tdesc_pseudo_register_name)
(set_tdesc_pseudo_register_type, set_tdesc_pseudo_register_reggroup_p)
(tdesc_use_registers, tdesc_data_alloc, tdesc_data_cleanup)
(tdesc_numbered_register, tdesc_numbered_register_choices)
(tdesc_has_registers, tdesc_find_feature, tdesc_feature_name)
(tdesc_named_type, tdesc_create_feature, tdesc_record_type)
(tdesc_create_reg): Declare.
* gdbarch.sh (remote_register_number): New entry.
* gdbarch.c, gdbarch.h: Regenerate.
* remote.c (init_remote_state): Use gdbarch_remote_register_number.
* features/gdb-target.dtd: Add feature, reg, vector, union, and field.
* arm-tdep.c (arm_register_aliases): New.
(arm_register_name_strings): Rename to...
(arm_register_names): ...this. Make const. Delete the old version.
(current_option, arm_register_byte): Delete.
(set_disassembly_style): Simplify. Do not adjust arm_register_names.
(value_of_arm_user_reg): New.
(arm_gdbarch_init): Verify any described registers. Call
tdesc_use_registers. Don't use arm_register_byte. Create aliases
for standard register names.
(_initialize_arm_tdep): Do not adjust arm_register_names.
* user-regs.c (struct user_reg): Add baton member.
(append_user_reg, user_reg_add_builtin, user_regs_init)
(user_reg_add, value_of_user_reg): Use a baton for user
register functions.
* std-regs.c: Update.
* user-regs.h (user_reg_read_ftype, user_reg_add_builtin)
(user_reg_add): Add baton argument.
* NEWS: Mention target description register support.
* features/arm-core.xml, features/arm-fpa.xml: New.
* eval.c (evaluate_subexp_standard): Allow ptype $register
when the program is not running.
* gdb.texinfo (-target-disconnect): Use @smallexample.
(Requirements): Add anchor for Expat. Update description.
(Target Descriptions): Mention Expat.
(Target Description Format): Document new elements. Use
@smallexample.
(Predefined Target Types, Standard Target Features): New sections.
* doc/gdbint.texinfo (Target Descriptions): New section.
* gdb.xml/single-reg.xml, gdb.xml/tdesc-regs.exp,
gdb.xml/core-only.xml, gdb.xml/extra-regs.xml: New files.
2007-02-09 05:00:36 +08:00
|
|
|
* Target descriptions can now describe target-specific registers,
|
|
|
|
|
for architectures which have implemented the support (currently
|
2007-10-04 04:42:08 +08:00
|
|
|
only ARM, M68K, and MIPS).
|
* Makefile.in (arm-tdep.o, eval.o, target-descriptions.o)
(xml-tdesc.o): Update.
* xml-support.c: Add a comment.
(gdb_xml_enums_boolean): New variable.
(gdb_xml_parse_attr_enum): Use strcasecmp.
* xml-support.h (gdb_xml_enums_boolean): Declare.
* xml-tdesc.c (struct tdesc_parsing_data): Record current_feature,
next_regnum, and current_union.
(tdesc_start_feature, tdesc_start_reg, tdesc_start_union)
(tdesc_end_union, tdesc_start_field, tdesc_start_vector)
(field_attributes, union_children, reg_attributes, union_attributes)
(vector_attributes, feature_attributes, feature_children): New.
(target_children): Make static. Add <feature>.
(tdesc_elements): Make static.
* target-descriptions.c (struct tdesc_reg, tdesc_reg_p, type_p)
(struct tdesc_feature, tdesc_feature_p): New types.
(struct target_desc): Add features member.
(struct tdesc_arch_data, tdesc_data): New.
(target_find_description): Clarify error message. Warn about
ignored register descriptions.
(tdesc_has_registers, tdesc_find_feature, tdesc_feature_name)
(tdesc_named_type, tdesc_data_init, tdesc_data_alloc)
(tdesc_data_cleanup, tdesc_numbered_register)
(tdesc_numbered_register_choices, tdesc_find_register)
(tdesc_register_name, tdesc_register_type)
(tdesc_remote_register_number, tdesc_register_reggroup_p)
(set_tdesc_pseudo_register_name, set_tdesc_pseudo_register_type)
(set_tdesc_pseudo_register_reggroup_p, tdesc_use_registers)
(tdesc_free_reg, tdesc_create_reg, tdesc_free_feature)
(tdesc_create_feature, tdesc_record_type): New.
(free_target_description): Free features.
(_initialize_target_descriptions): Initialize tdesc_data.
* arch-utils.c (default_remote_register_number): New.
* arch-utils.h (default_remote_register_number): New prototype.
* target-descriptions.h (set_tdesc_pseudo_register_name)
(set_tdesc_pseudo_register_type, set_tdesc_pseudo_register_reggroup_p)
(tdesc_use_registers, tdesc_data_alloc, tdesc_data_cleanup)
(tdesc_numbered_register, tdesc_numbered_register_choices)
(tdesc_has_registers, tdesc_find_feature, tdesc_feature_name)
(tdesc_named_type, tdesc_create_feature, tdesc_record_type)
(tdesc_create_reg): Declare.
* gdbarch.sh (remote_register_number): New entry.
* gdbarch.c, gdbarch.h: Regenerate.
* remote.c (init_remote_state): Use gdbarch_remote_register_number.
* features/gdb-target.dtd: Add feature, reg, vector, union, and field.
* arm-tdep.c (arm_register_aliases): New.
(arm_register_name_strings): Rename to...
(arm_register_names): ...this. Make const. Delete the old version.
(current_option, arm_register_byte): Delete.
(set_disassembly_style): Simplify. Do not adjust arm_register_names.
(value_of_arm_user_reg): New.
(arm_gdbarch_init): Verify any described registers. Call
tdesc_use_registers. Don't use arm_register_byte. Create aliases
for standard register names.
(_initialize_arm_tdep): Do not adjust arm_register_names.
* user-regs.c (struct user_reg): Add baton member.
(append_user_reg, user_reg_add_builtin, user_regs_init)
(user_reg_add, value_of_user_reg): Use a baton for user
register functions.
* std-regs.c: Update.
* user-regs.h (user_reg_read_ftype, user_reg_add_builtin)
(user_reg_add): Add baton argument.
* NEWS: Mention target description register support.
* features/arm-core.xml, features/arm-fpa.xml: New.
* eval.c (evaluate_subexp_standard): Allow ptype $register
when the program is not running.
* gdb.texinfo (-target-disconnect): Use @smallexample.
(Requirements): Add anchor for Expat. Update description.
(Target Descriptions): Mention Expat.
(Target Description Format): Document new elements. Use
@smallexample.
(Predefined Target Types, Standard Target Features): New sections.
* doc/gdbint.texinfo (Target Descriptions): New section.
* gdb.xml/single-reg.xml, gdb.xml/tdesc-regs.exp,
gdb.xml/core-only.xml, gdb.xml/extra-regs.xml: New files.
2007-02-09 05:00:36 +08:00
|
|
|
|
2007-02-27 03:20:21 +08:00
|
|
|
* GDB and the GDB remote stub, gdbserver, now support the XScale
|
|
|
|
|
iWMMXt coprocessor.
|
* features/Makefile, features/arm-with-iwmmxt.xml,
features/gdbserver-regs.xsl, features/number-regs.xsl,
features/sort-regs.xsl, features/xscale-iwmmxt.xml: New files.
* regformats/arm-with-iwmmxt.dat: Generate.
* NEWS: Mention iWMMXt.
* gdb.arch/iwmmxt-regs.c, gdb.arch/iwmmxt-regs.exp: New.
* Makefile.in (OBS): Add $(XML_BUILTIN).
(XML_DIR, XML_TARGET, XML_FILES, XML_BUILTIN): New.
(clean): Update.
(target.xml, xml-builtin.c, stamp-xml, arm-with-iwmmxt.o)
(arm-with-iwmmxt.c): New.
* config.in, configure: Regenerate.
* configure.ac: Check for iWMMXt. Handle srv_xmltarget,
srv_xmlbuiltin, and srv_xmlfiles. Define USE_XML.
* configure.srv: Mention srv_xmltarget and srv_xmlfiles.
(arm*-*-linux*): Add iWMMXt and regset support.
* linux-arm-low.c (PTRACE_GETWMMXREGS, PTRACE_SETWMMXREGS): Define.
(arm_fill_gregset, arm_store_gregset, arm_fill_wmmxregset)
(arm_store_wmmxregset, target_regsets): New.
* server.c (get_features_xml): Take annex argument. Check builtin
XML documents.
(handle_query): Handle multiple annexes.
2007-02-09 05:39:04 +08:00
|
|
|
|
2007-03-31 18:42:22 +08:00
|
|
|
* The GDB remote stub, gdbserver, has been updated to support
|
|
|
|
|
ARM Windows CE (mingw32ce) debugging, and GDB Windows CE support
|
|
|
|
|
has been rewritten to use the standard GDB remote protocol.
|
|
|
|
|
|
2007-05-07 19:49:05 +08:00
|
|
|
* GDB can now step into C++ functions which are called through thunks.
|
|
|
|
|
|
2007-05-12 04:17:18 +08:00
|
|
|
* GDB for the Cell/B.E. SPU now supports overlay debugging.
|
|
|
|
|
|
2007-06-18 23:46:38 +08:00
|
|
|
* The GDB remote protocol "qOffsets" packet can now honor ELF segment
|
|
|
|
|
layout. It also supports a TextSeg= and DataSeg= response when only
|
|
|
|
|
segment base addresses (rather than offsets) are available.
|
|
|
|
|
|
2007-06-21 23:18:51 +08:00
|
|
|
* The /i format now outputs any trailing branch delay slot instructions
|
|
|
|
|
immediately following the last instruction within the count specified.
|
|
|
|
|
|
2007-07-03 06:01:09 +08:00
|
|
|
* The GDB remote protocol "T" stop reply packet now supports a
|
|
|
|
|
"library" response. Combined with the new "qXfer:libraries:read"
|
|
|
|
|
packet, this response allows GDB to debug shared libraries on targets
|
|
|
|
|
where the operating system manages the list of loaded libraries (e.g.
|
|
|
|
|
Windows and SymbianOS).
|
2007-07-17 Pedro Alves <pedro_alves@portugalmail.pt>
Daniel Jacobowitz <dan@codesourcery.com>
* config/i386/cygwin.mt (TDEPFILES): Add solib-target.o.
* coff-pe-read.c (read_pe_exported_syms): Delete verbose
printf.
* NEWS: Mention gdbserver DLL support.
* gdb.base/unload.c (dlopen, dlsym, dlclose, dlerror): Define
for __WIN32__.
(SHLIB_NAME): Delete definition. Always pass dlerror to fprintf.
* gdb.base/unload.exp: Use shared library test routines.
* inferiors.c (all_dlls, dlls_changed, get_dll): New.
(add_thread): Minor cleanups.
(clear_inferiors): Move lower in the file. Clear the DLL
list.
(free_one_dll, match_dll, loaded_dll, unloaded_dll, clear_list): New.
* remote-utils.c (prepare_resume_reply): Check dlls_changed.
(xml_escape_text): New.
* server.c (handle_query): Handle qXfer:libraries:read. Report it
for qSupported.
(handle_v_cont): Report errors.
(gdbserver_version): Update.
(main): Correct size of own_buf. Do not report initial DLL events.
* server.h (struct dll_info, all_dlls, dlls_changed, loaded_dll)
(unloaded_dll, xml_escape_text): New.
* win32-low.c (enum target_waitkind): Update comments.
(win32_add_one_solib, get_image_name, winapi_EnumProcessModules)
(winapi_GetModuleInformation, winapi_GetModuleFileNameExA)
(win32_EnumProcessModules, win32_GetModuleInformation)
(win32_GetModuleFileNameExA, load_psapi, psapi_get_dll_name)
(winapi_CreateToolhelp32Snapshot, winapi_Module32First)
(winapi_Module32Next, win32_CreateToolhelp32Snapshot)
(win32_Module32First, win32_Module32Next, load_toolhelp)
(toolhelp_get_dll_name, handle_load_dll, handle_unload_dll): New.
(get_child_debug_event): Handle DLL events.
(win32_wait): Likewise.
2007-07-17 20:51:41 +08:00
|
|
|
|
|
|
|
|
* The GDB remote stub, gdbserver, now supports dynamic link libraries
|
|
|
|
|
(DLLs) on Windows and Windows CE targets.
|
2007-09-03 03:56:05 +08:00
|
|
|
|
|
|
|
|
* GDB now supports a faster verification that a .debug file matches its binary
|
|
|
|
|
according to its build-id signature, if the signature is present.
|
2007-07-03 06:01:09 +08:00
|
|
|
|
2006-12-06 05:23:20 +08:00
|
|
|
* New commands
|
|
|
|
|
|
2007-05-22 18:57:12 +08:00
|
|
|
set remoteflow
|
|
|
|
|
show remoteflow
|
|
|
|
|
Enable or disable hardware flow control (RTS/CTS) on the serial port
|
|
|
|
|
when debugging using remote targets.
|
|
|
|
|
|
2006-12-06 05:23:20 +08:00
|
|
|
set mem inaccessible-by-default
|
|
|
|
|
show mem inaccessible-by-default
|
|
|
|
|
If the target supplies a memory map, for instance via the remote
|
|
|
|
|
protocol's "qXfer:memory-map:read" packet, setting this variable
|
|
|
|
|
prevents GDB from accessing memory outside the memory map. This
|
|
|
|
|
is useful for targets with memory mapped registers or which react
|
|
|
|
|
badly to accesses of unmapped address space.
|
|
|
|
|
|
|
|
|
|
set breakpoint auto-hw
|
|
|
|
|
show breakpoint auto-hw
|
|
|
|
|
If the target supplies a memory map, for instance via the remote
|
|
|
|
|
protocol's "qXfer:memory-map:read" packet, setting this variable
|
|
|
|
|
lets GDB use hardware breakpoints automatically for memory regions
|
|
|
|
|
where it can not use software breakpoints. This covers both the
|
|
|
|
|
"break" command and internal breakpoints used for other commands
|
|
|
|
|
including "next" and "finish".
|
|
|
|
|
|
2007-01-05 16:22:43 +08:00
|
|
|
catch exception
|
|
|
|
|
catch exception unhandled
|
|
|
|
|
Stop the program execution when Ada exceptions are raised.
|
|
|
|
|
|
|
|
|
|
catch assert
|
|
|
|
|
Stop the program execution when an Ada assertion failed.
|
|
|
|
|
|
2007-01-09 02:56:30 +08:00
|
|
|
set sysroot
|
|
|
|
|
show sysroot
|
|
|
|
|
Set an alternate system root for target files. This is a more
|
|
|
|
|
general version of "set solib-absolute-prefix", which is now
|
|
|
|
|
an alias to "set sysroot".
|
|
|
|
|
|
2007-06-15 20:40:46 +08:00
|
|
|
info spu
|
|
|
|
|
Provide extended SPU facility status information. This set of
|
|
|
|
|
commands is available only when debugging the Cell/B.E. SPU
|
|
|
|
|
architecture.
|
|
|
|
|
|
2006-12-16 07:57:35 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
OpenBSD/sh sh*-*openbsd*
|
|
|
|
|
|
XML feature description support.
* NEWS: Mention target descriptions, "set tdesc filename",
"unset tdesc filename", "show tdesc filename", and
qXfer:features:read.
* arch-utils.c (choose_architecture_for_target): New function.
(gdbarch_info_fill): Call it.
* target-descriptions.c (struct property): Make members non-const.
(struct target_desc): Add arch member.
(target_description_filename): New variable.
(target_find_description): Try via XML first.
(tdesc_architecture): New.
(free_target_description, make_cleanup_free_target_description): New.
(set_tdesc_property): Call xstrdup.
(set_tdesc_architecture, tdesc_set_cmdlist, tdesc_show_cmdlist)
(tdesc_unset_cmdlist, unset_tdesc_cmd, unset_tdesc_filename_cmd)
(set_tdesc_cmd, show_tdesc_cmd, set_tdesc_filename_cmd)
(show_tdesc_filename_cmd, _initialize_target_descriptions): New.
* target-descriptions.h (tdesc_architecture)
(make_cleanup_free_target_description, set_tdesc_architecture): New
prototypes.
* Makefile.in (SFILES): Add xml-tdesc.c.
(COMMON_OBS): Add xml-tdesc.o.
(target-descriptions.o): Update.
(xml-tdesc.o): New rule.
* xml-tdesc.c, xml-tdesc.h: New files.
* remote.c (PACKET_qXfer_features): New enum.
(remote_protocol_features): Add qXfer:features:read.
(remote_xfer_partial): Handle TARGET_OBJECT_AVAILABLE_FEATURES.
(_initialize_remote): Register qXfer:features:read.
* target.h (enum target_object): Add TARGET_OBJECT_AVAILABLE_FEATURES.
* features/gdb-target.dtd: New file.
* linux-i386-low.c (the_low_target): Set arch_string.
* linux-x86-64-low.c (the_low_target): Likewise.
* linux-low.c (linux_arch_string): New.
(linux_target_ops): Add it.
* linux-low.h (struct linux_target_ops): Add arch_string.
* server.c (write_qxfer_response): Use const void * for DATA.
(get_features_xml): New.
(handle_query): Handle qXfer:features:read. Report it for qSupported.
* target.h (struct target_ops): Add arch_string method.
* gdb.texinfo (Target Descriptions): New section.
(General Query Packets): Add QPassSignals anchor. Mention
qXfer:features:read under qSupported. Expand mentions of
qXfer:memory-map:read and QPassSignals. Document
qXfer:features:read.
2007-01-10 06:55:10 +08:00
|
|
|
set tdesc filename
|
|
|
|
|
unset tdesc filename
|
|
|
|
|
show tdesc filename
|
|
|
|
|
Use the specified local file as an XML target description, and do
|
|
|
|
|
not query the target for its built-in description.
|
|
|
|
|
|
2006-12-06 05:23:20 +08:00
|
|
|
* New targets
|
|
|
|
|
|
2006-12-16 07:45:04 +08:00
|
|
|
OpenBSD/sh sh*-*-openbsd*
|
2006-12-06 05:23:20 +08:00
|
|
|
MIPS64 GNU/Linux (gdbserver) mips64-linux-gnu
|
2007-02-25 01:37:28 +08:00
|
|
|
Toshiba Media Processor mep-elf
|
2006-12-06 05:23:20 +08:00
|
|
|
|
2006-11-20 08:16:05 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
QPassSignals:
|
|
|
|
|
Ignore the specified signals; pass them directly to the debugged program
|
|
|
|
|
without stopping other threads or reporting them to GDB.
|
|
|
|
|
|
XML feature description support.
* NEWS: Mention target descriptions, "set tdesc filename",
"unset tdesc filename", "show tdesc filename", and
qXfer:features:read.
* arch-utils.c (choose_architecture_for_target): New function.
(gdbarch_info_fill): Call it.
* target-descriptions.c (struct property): Make members non-const.
(struct target_desc): Add arch member.
(target_description_filename): New variable.
(target_find_description): Try via XML first.
(tdesc_architecture): New.
(free_target_description, make_cleanup_free_target_description): New.
(set_tdesc_property): Call xstrdup.
(set_tdesc_architecture, tdesc_set_cmdlist, tdesc_show_cmdlist)
(tdesc_unset_cmdlist, unset_tdesc_cmd, unset_tdesc_filename_cmd)
(set_tdesc_cmd, show_tdesc_cmd, set_tdesc_filename_cmd)
(show_tdesc_filename_cmd, _initialize_target_descriptions): New.
* target-descriptions.h (tdesc_architecture)
(make_cleanup_free_target_description, set_tdesc_architecture): New
prototypes.
* Makefile.in (SFILES): Add xml-tdesc.c.
(COMMON_OBS): Add xml-tdesc.o.
(target-descriptions.o): Update.
(xml-tdesc.o): New rule.
* xml-tdesc.c, xml-tdesc.h: New files.
* remote.c (PACKET_qXfer_features): New enum.
(remote_protocol_features): Add qXfer:features:read.
(remote_xfer_partial): Handle TARGET_OBJECT_AVAILABLE_FEATURES.
(_initialize_remote): Register qXfer:features:read.
* target.h (enum target_object): Add TARGET_OBJECT_AVAILABLE_FEATURES.
* features/gdb-target.dtd: New file.
* linux-i386-low.c (the_low_target): Set arch_string.
* linux-x86-64-low.c (the_low_target): Likewise.
* linux-low.c (linux_arch_string): New.
(linux_target_ops): Add it.
* linux-low.h (struct linux_target_ops): Add arch_string.
* server.c (write_qxfer_response): Use const void * for DATA.
(get_features_xml): New.
(handle_query): Handle qXfer:features:read. Report it for qSupported.
* target.h (struct target_ops): Add arch_string method.
* gdb.texinfo (Target Descriptions): New section.
(General Query Packets): Add QPassSignals anchor. Mention
qXfer:features:read under qSupported. Expand mentions of
qXfer:memory-map:read and QPassSignals. Document
qXfer:features:read.
2007-01-10 06:55:10 +08:00
|
|
|
qXfer:features:read:
|
|
|
|
|
Read an XML target description from the target, which describes its
|
|
|
|
|
features.
|
2006-11-20 08:16:05 +08:00
|
|
|
|
2007-06-15 20:40:46 +08:00
|
|
|
qXfer:spu:read:
|
|
|
|
|
qXfer:spu:write:
|
|
|
|
|
Read or write contents of an spufs file on the target system. These
|
|
|
|
|
packets are available only on the Cell/B.E. SPU architecture.
|
|
|
|
|
|
2007-07-03 06:01:09 +08:00
|
|
|
qXfer:libraries:read:
|
|
|
|
|
Report the loaded shared libraries. Combined with new "T" packet
|
|
|
|
|
response, this packet allows GDB to debug shared libraries on
|
|
|
|
|
targets where the operating system manages the list of loaded
|
|
|
|
|
libraries (e.g. Windows and SymbianOS).
|
|
|
|
|
|
* Makefile.in (coff_solib_h, coff-solib.o, i386v-nat.o, lynx-nat.o)
(remote-st.o, uw-thread.o): Delete.
(HFILES_NO_SRCDIR, ALLDEPFILES): Update.
* configure.host: Move hppa*-*-hiux*, i[34567]86-ncr-*,
i[34567]86-*-dgux*, i[34567]86-*-lynxos*, i[34567]86-*-sco3.2v5*,
i[34567]86-*-sco3.2v4*, i[34567]86-*-sco*, i[34567]86-*-sysv4.2*,
i[34567]86-*-sysv4*, i[34567]86-*-sysv5*, i[34567]86-*-unixware2*,
i[34567]86-*-unixware*, i[34567]86-*-sysv*, i[34567]86-*-isc*, and
rs6000-*-lynxos* to an obsoletion stanza.
* configure.tgt: Move hppa*-*-hiux*, i[34567]86-ncr-*,
i[34567]86-*-lynxos*, m68*-cisco*-*, m68*-tandem-*, m68*-*-os68k*,
and rs6000-*-lynxos* to an obsoletion stanza. Do not mention
i[34567]86-*-netware*.
* NEWS: Mention deleted targets.
* coff-solib.c, coff-solib.h, i386v-nat.c, lynx-nat.c, remote-st.c,
uw-thread.c, config/nm-lynx.h, config/i386/i386sco.mh,
config/i386/i386sco4.mh, config/i386/i386sco5.mh, config/i386/i386v.mh,
config/i386/i386v4.mh, config/i386/i386v42mp.mh,
config/i386/ncr3000.mh, config/i386/ncr3000.mt,
config/i386/nm-i386sco.h, config/i386/nm-i386sco4.h,
config/i386/nm-i386sco5.h, config/i386/nm-i386v.h,
config/i386/nm-i386v4.h, config/i386/nm-i386v42mp.h,
config/m68k/cisco.mt, config/m68k/os68k.mt, config/m68k/st2000.mt,
config/m68k/tm-cisco.h, config/m68k/tm-os68k.h,
config/rs6000/rs6000lynx.mh, config/rs6000/rs6000lynx.mt,
config/rs6000/tm-rs6000ly.h: Delete files.
2007-03-30 03:58:29 +08:00
|
|
|
* Removed targets
|
|
|
|
|
|
|
|
|
|
Support for these obsolete configurations has been removed.
|
|
|
|
|
|
2007-05-07 07:04:26 +08:00
|
|
|
alpha*-*-osf1*
|
|
|
|
|
alpha*-*-osf2*
|
* MAINTAINERS: Remove d10v entry.
* Makefile.in (SFILES): Remove dwarfread.c.
(COMMON_OBS): Remove dwarfread.o.
(gdb_sim_d10v_h, abug-rom.o, cpu32bug-rom.o, d10v-tdep.o, dwarfread.o)
(remote-est.o, rom68k-rom.o): Delete.
* NEWS: Mention removal of d10v, target abug, target cpu32bug,
target est, target rom68k, and DWARF 1.
* configure.tgt: Mark d10v as removed.
* dwarf2read.c: Doc update.
* elfread.c (struct elfinfo): Remove dboffset, dbsize, lnoffset,
and lnsize.
(elf_locate_sections): Do not set them.
(elf_symfile_read): Do not call dwarf_build_psymtabs.
* symfile.h (dwarf_build_psymtabs): Delete prototype.
* config/m68k/monitor.mt (TDEPFILES): Prune.
* abug-rom.c, cpu32bug-rom.c, d10v-tdep.c, dwarfread.c,
remote-est.c, rom68k-rom.c, config/d10v/d10v.mt: Delete.
* gdb.texinfo (M68K): Remove obsolete ROM monitors.
* gdbint.texinfo (DWARF 1): Delete section and other dwarfread.c
references.
* gdb.asm/asm-source.exp: Remove d10v case.
* lib/gdb.exp (skip_cplus_tests): Likewise.
* gdb.asm/d10v.inc: Deleted.
2007-03-31 01:21:48 +08:00
|
|
|
d10v-*-*
|
* Makefile.in (coff_solib_h, coff-solib.o, i386v-nat.o, lynx-nat.o)
(remote-st.o, uw-thread.o): Delete.
(HFILES_NO_SRCDIR, ALLDEPFILES): Update.
* configure.host: Move hppa*-*-hiux*, i[34567]86-ncr-*,
i[34567]86-*-dgux*, i[34567]86-*-lynxos*, i[34567]86-*-sco3.2v5*,
i[34567]86-*-sco3.2v4*, i[34567]86-*-sco*, i[34567]86-*-sysv4.2*,
i[34567]86-*-sysv4*, i[34567]86-*-sysv5*, i[34567]86-*-unixware2*,
i[34567]86-*-unixware*, i[34567]86-*-sysv*, i[34567]86-*-isc*, and
rs6000-*-lynxos* to an obsoletion stanza.
* configure.tgt: Move hppa*-*-hiux*, i[34567]86-ncr-*,
i[34567]86-*-lynxos*, m68*-cisco*-*, m68*-tandem-*, m68*-*-os68k*,
and rs6000-*-lynxos* to an obsoletion stanza. Do not mention
i[34567]86-*-netware*.
* NEWS: Mention deleted targets.
* coff-solib.c, coff-solib.h, i386v-nat.c, lynx-nat.c, remote-st.c,
uw-thread.c, config/nm-lynx.h, config/i386/i386sco.mh,
config/i386/i386sco4.mh, config/i386/i386sco5.mh, config/i386/i386v.mh,
config/i386/i386v4.mh, config/i386/i386v42mp.mh,
config/i386/ncr3000.mh, config/i386/ncr3000.mt,
config/i386/nm-i386sco.h, config/i386/nm-i386sco4.h,
config/i386/nm-i386sco5.h, config/i386/nm-i386v.h,
config/i386/nm-i386v4.h, config/i386/nm-i386v42mp.h,
config/m68k/cisco.mt, config/m68k/os68k.mt, config/m68k/st2000.mt,
config/m68k/tm-cisco.h, config/m68k/tm-os68k.h,
config/rs6000/rs6000lynx.mh, config/rs6000/rs6000lynx.mt,
config/rs6000/tm-rs6000ly.h: Delete files.
2007-03-30 03:58:29 +08:00
|
|
|
hppa*-*-hiux*
|
|
|
|
|
i[34567]86-ncr-*
|
|
|
|
|
i[34567]86-*-dgux*
|
|
|
|
|
i[34567]86-*-lynxos*
|
|
|
|
|
i[34567]86-*-netware*
|
|
|
|
|
i[34567]86-*-sco3.2v5*
|
|
|
|
|
i[34567]86-*-sco3.2v4*
|
|
|
|
|
i[34567]86-*-sco*
|
|
|
|
|
i[34567]86-*-sysv4.2*
|
|
|
|
|
i[34567]86-*-sysv4*
|
|
|
|
|
i[34567]86-*-sysv5*
|
|
|
|
|
i[34567]86-*-unixware2*
|
|
|
|
|
i[34567]86-*-unixware*
|
|
|
|
|
i[34567]86-*-sysv*
|
|
|
|
|
i[34567]86-*-isc*
|
|
|
|
|
m68*-cisco*-*
|
|
|
|
|
m68*-tandem-*
|
2007-03-31 06:50:33 +08:00
|
|
|
mips*-*-pe
|
* Makefile.in (coff_solib_h, coff-solib.o, i386v-nat.o, lynx-nat.o)
(remote-st.o, uw-thread.o): Delete.
(HFILES_NO_SRCDIR, ALLDEPFILES): Update.
* configure.host: Move hppa*-*-hiux*, i[34567]86-ncr-*,
i[34567]86-*-dgux*, i[34567]86-*-lynxos*, i[34567]86-*-sco3.2v5*,
i[34567]86-*-sco3.2v4*, i[34567]86-*-sco*, i[34567]86-*-sysv4.2*,
i[34567]86-*-sysv4*, i[34567]86-*-sysv5*, i[34567]86-*-unixware2*,
i[34567]86-*-unixware*, i[34567]86-*-sysv*, i[34567]86-*-isc*, and
rs6000-*-lynxos* to an obsoletion stanza.
* configure.tgt: Move hppa*-*-hiux*, i[34567]86-ncr-*,
i[34567]86-*-lynxos*, m68*-cisco*-*, m68*-tandem-*, m68*-*-os68k*,
and rs6000-*-lynxos* to an obsoletion stanza. Do not mention
i[34567]86-*-netware*.
* NEWS: Mention deleted targets.
* coff-solib.c, coff-solib.h, i386v-nat.c, lynx-nat.c, remote-st.c,
uw-thread.c, config/nm-lynx.h, config/i386/i386sco.mh,
config/i386/i386sco4.mh, config/i386/i386sco5.mh, config/i386/i386v.mh,
config/i386/i386v4.mh, config/i386/i386v42mp.mh,
config/i386/ncr3000.mh, config/i386/ncr3000.mt,
config/i386/nm-i386sco.h, config/i386/nm-i386sco4.h,
config/i386/nm-i386sco5.h, config/i386/nm-i386v.h,
config/i386/nm-i386v4.h, config/i386/nm-i386v42mp.h,
config/m68k/cisco.mt, config/m68k/os68k.mt, config/m68k/st2000.mt,
config/m68k/tm-cisco.h, config/m68k/tm-os68k.h,
config/rs6000/rs6000lynx.mh, config/rs6000/rs6000lynx.mt,
config/rs6000/tm-rs6000ly.h: Delete files.
2007-03-30 03:58:29 +08:00
|
|
|
rs6000-*-lynxos*
|
2007-03-31 06:50:33 +08:00
|
|
|
sh*-*-pe
|
* Makefile.in (coff_solib_h, coff-solib.o, i386v-nat.o, lynx-nat.o)
(remote-st.o, uw-thread.o): Delete.
(HFILES_NO_SRCDIR, ALLDEPFILES): Update.
* configure.host: Move hppa*-*-hiux*, i[34567]86-ncr-*,
i[34567]86-*-dgux*, i[34567]86-*-lynxos*, i[34567]86-*-sco3.2v5*,
i[34567]86-*-sco3.2v4*, i[34567]86-*-sco*, i[34567]86-*-sysv4.2*,
i[34567]86-*-sysv4*, i[34567]86-*-sysv5*, i[34567]86-*-unixware2*,
i[34567]86-*-unixware*, i[34567]86-*-sysv*, i[34567]86-*-isc*, and
rs6000-*-lynxos* to an obsoletion stanza.
* configure.tgt: Move hppa*-*-hiux*, i[34567]86-ncr-*,
i[34567]86-*-lynxos*, m68*-cisco*-*, m68*-tandem-*, m68*-*-os68k*,
and rs6000-*-lynxos* to an obsoletion stanza. Do not mention
i[34567]86-*-netware*.
* NEWS: Mention deleted targets.
* coff-solib.c, coff-solib.h, i386v-nat.c, lynx-nat.c, remote-st.c,
uw-thread.c, config/nm-lynx.h, config/i386/i386sco.mh,
config/i386/i386sco4.mh, config/i386/i386sco5.mh, config/i386/i386v.mh,
config/i386/i386v4.mh, config/i386/i386v42mp.mh,
config/i386/ncr3000.mh, config/i386/ncr3000.mt,
config/i386/nm-i386sco.h, config/i386/nm-i386sco4.h,
config/i386/nm-i386sco5.h, config/i386/nm-i386v.h,
config/i386/nm-i386v4.h, config/i386/nm-i386v42mp.h,
config/m68k/cisco.mt, config/m68k/os68k.mt, config/m68k/st2000.mt,
config/m68k/tm-cisco.h, config/m68k/tm-os68k.h,
config/rs6000/rs6000lynx.mh, config/rs6000/rs6000lynx.mt,
config/rs6000/tm-rs6000ly.h: Delete files.
2007-03-30 03:58:29 +08:00
|
|
|
|
* MAINTAINERS: Remove d10v entry.
* Makefile.in (SFILES): Remove dwarfread.c.
(COMMON_OBS): Remove dwarfread.o.
(gdb_sim_d10v_h, abug-rom.o, cpu32bug-rom.o, d10v-tdep.o, dwarfread.o)
(remote-est.o, rom68k-rom.o): Delete.
* NEWS: Mention removal of d10v, target abug, target cpu32bug,
target est, target rom68k, and DWARF 1.
* configure.tgt: Mark d10v as removed.
* dwarf2read.c: Doc update.
* elfread.c (struct elfinfo): Remove dboffset, dbsize, lnoffset,
and lnsize.
(elf_locate_sections): Do not set them.
(elf_symfile_read): Do not call dwarf_build_psymtabs.
* symfile.h (dwarf_build_psymtabs): Delete prototype.
* config/m68k/monitor.mt (TDEPFILES): Prune.
* abug-rom.c, cpu32bug-rom.c, d10v-tdep.c, dwarfread.c,
remote-est.c, rom68k-rom.c, config/d10v/d10v.mt: Delete.
* gdb.texinfo (M68K): Remove obsolete ROM monitors.
* gdbint.texinfo (DWARF 1): Delete section and other dwarfread.c
references.
* gdb.asm/asm-source.exp: Remove d10v case.
* lib/gdb.exp (skip_cplus_tests): Likewise.
* gdb.asm/d10v.inc: Deleted.
2007-03-31 01:21:48 +08:00
|
|
|
* Other removed features
|
|
|
|
|
|
|
|
|
|
target abug
|
|
|
|
|
target cpu32bug
|
|
|
|
|
target est
|
|
|
|
|
target rom68k
|
|
|
|
|
|
|
|
|
|
Various m68k-only ROM monitors.
|
|
|
|
|
|
* mips-mdebug-tdep.c, mips-mdebug-tdep.h, ocd.c, ocd.h, ppc-bdm.c,
remote-e7000.c, remote-hms.c, remote-utils.c, remote-utils.h,
scm-exp.c, scm-lang.c, scm-lang.h, scm-tags.h, scm-valprint.c,
ser-e7kpc.c, sh3-rom.c, stop-gdb.c: Delete.
* Makefile.in: Remove references to deleted files.
* README: Do not mention deleted ROM monitor interfaces.
* defs.h (enum language): Delete language_scm.
* expprint.c (print_subexp_standard): Do not handle OP_EXPRSTRING.
(dump_subexp_body_standard): Likewise.
* parse.c (operator_length_standard): Likewise.
* expression.h (enum exp_opcode): Delete OP_EXPRSTRING.
* remote-mips.c: Do not include remote-utils.h.
* remote-sim.c: Likewise. Use remote_debug instead of sr_get_debug
throughout.
* value.c: Do not include scm-lang.h.
(unpack_long): Delete scm_unpack call.
* config/h8300/h8300.mt, config/mips/embed.mt,
config/powerpc/ppc-eabi.mt, config/powerpc/ppc-sim.mt,
config/sh/embed.mt, config/sh/linux.mt: Remove references to
deleted files.
* NEWS: Mention removed files.
* gdb.texinfo (Memory): Reference Remote Debugging chapter.
(Character Sets, Caching Data of Remote Targets): Likewise.
(Targets): Delete Remote node. Move its text...
(Debugging Remote Programs): ...to here. Delete description
of the "remote" command.
(Remote configuration): Delete description of "set remotedevice"
and "show remotedevice".
(Embedded Processors): Delete H8/300, H8/500, and SH nodes.
2007-04-13 22:17:47 +08:00
|
|
|
target hms
|
|
|
|
|
target e7000
|
|
|
|
|
target sh3
|
|
|
|
|
target sh3e
|
|
|
|
|
|
|
|
|
|
Various Renesas ROM monitors and debugging interfaces for SH and
|
|
|
|
|
H8/300.
|
|
|
|
|
|
|
|
|
|
target ocd
|
|
|
|
|
|
|
|
|
|
Support for a Macraigor serial interface to on-chip debugging.
|
|
|
|
|
GDB does not directly support the newer parallel or USB
|
|
|
|
|
interfaces.
|
|
|
|
|
|
* MAINTAINERS: Remove d10v entry.
* Makefile.in (SFILES): Remove dwarfread.c.
(COMMON_OBS): Remove dwarfread.o.
(gdb_sim_d10v_h, abug-rom.o, cpu32bug-rom.o, d10v-tdep.o, dwarfread.o)
(remote-est.o, rom68k-rom.o): Delete.
* NEWS: Mention removal of d10v, target abug, target cpu32bug,
target est, target rom68k, and DWARF 1.
* configure.tgt: Mark d10v as removed.
* dwarf2read.c: Doc update.
* elfread.c (struct elfinfo): Remove dboffset, dbsize, lnoffset,
and lnsize.
(elf_locate_sections): Do not set them.
(elf_symfile_read): Do not call dwarf_build_psymtabs.
* symfile.h (dwarf_build_psymtabs): Delete prototype.
* config/m68k/monitor.mt (TDEPFILES): Prune.
* abug-rom.c, cpu32bug-rom.c, d10v-tdep.c, dwarfread.c,
remote-est.c, rom68k-rom.c, config/d10v/d10v.mt: Delete.
* gdb.texinfo (M68K): Remove obsolete ROM monitors.
* gdbint.texinfo (DWARF 1): Delete section and other dwarfread.c
references.
* gdb.asm/asm-source.exp: Remove d10v case.
* lib/gdb.exp (skip_cplus_tests): Likewise.
* gdb.asm/d10v.inc: Deleted.
2007-03-31 01:21:48 +08:00
|
|
|
DWARF 1 support
|
|
|
|
|
|
|
|
|
|
A debug information format. The predecessor to DWARF 2 and
|
|
|
|
|
DWARF 3, which are still supported.
|
|
|
|
|
|
2007-04-13 21:56:19 +08:00
|
|
|
Support for the HP aCC compiler on HP-UX/PA-RISC
|
|
|
|
|
|
|
|
|
|
SOM-encapsulated symbolic debugging information, automatic
|
|
|
|
|
invocation of pxdb, and the aCC custom C++ ABI. This does not
|
|
|
|
|
affect HP-UX for Itanium or GCC for HP-UX/PA-RISC. Code compiled
|
|
|
|
|
with aCC can still be debugged on an assembly level.
|
|
|
|
|
|
* mips-mdebug-tdep.c, mips-mdebug-tdep.h, ocd.c, ocd.h, ppc-bdm.c,
remote-e7000.c, remote-hms.c, remote-utils.c, remote-utils.h,
scm-exp.c, scm-lang.c, scm-lang.h, scm-tags.h, scm-valprint.c,
ser-e7kpc.c, sh3-rom.c, stop-gdb.c: Delete.
* Makefile.in: Remove references to deleted files.
* README: Do not mention deleted ROM monitor interfaces.
* defs.h (enum language): Delete language_scm.
* expprint.c (print_subexp_standard): Do not handle OP_EXPRSTRING.
(dump_subexp_body_standard): Likewise.
* parse.c (operator_length_standard): Likewise.
* expression.h (enum exp_opcode): Delete OP_EXPRSTRING.
* remote-mips.c: Do not include remote-utils.h.
* remote-sim.c: Likewise. Use remote_debug instead of sr_get_debug
throughout.
* value.c: Do not include scm-lang.h.
(unpack_long): Delete scm_unpack call.
* config/h8300/h8300.mt, config/mips/embed.mt,
config/powerpc/ppc-eabi.mt, config/powerpc/ppc-sim.mt,
config/sh/embed.mt, config/sh/linux.mt: Remove references to
deleted files.
* NEWS: Mention removed files.
* gdb.texinfo (Memory): Reference Remote Debugging chapter.
(Character Sets, Caching Data of Remote Targets): Likewise.
(Targets): Delete Remote node. Move its text...
(Debugging Remote Programs): ...to here. Delete description
of the "remote" command.
(Remote configuration): Delete description of "set remotedevice"
and "show remotedevice".
(Embedded Processors): Delete H8/300, H8/500, and SH nodes.
2007-04-13 22:17:47 +08:00
|
|
|
MIPS ".pdr" sections
|
|
|
|
|
|
|
|
|
|
A MIPS-specific format used to describe stack frame layout
|
|
|
|
|
in debugging information.
|
|
|
|
|
|
|
|
|
|
Scheme support
|
|
|
|
|
|
|
|
|
|
GDB could work with an older version of Guile to debug
|
|
|
|
|
the interpreter and Scheme programs running in it.
|
|
|
|
|
|
* NEWS: Mention removed "set mips stack-arg-size" and "set mips
saved-gpreg-size".
* mips-tdep.c (MIPS32_REGSIZE, MIPS64_REGSIZE): New constants.
(size_auto, size_32, size_64, size_enums, mips_abi_regsize_string)
(mips_stack_argsize_string, mips_stack_argsize): Delete.
(mips_abi_regsize): Simplify.
(mips_eabi_push_dummy_call, mips_n32n64_push_dummy_call)
(mips_n32n64_return_value, mips_o32_push_dummy_call)
(mips_o32_return_value, mips_o64_push_dummy_call)
(mips_o64_return_value): Propogate constant register sizes. Use the
ABI register size instead of mips_stack_argsize.
(mips_dump_tdep): Don't print mips_stack_argsize.
(_initialize_mips_tdep): Remove saved-gpreg-size and stack-arg-size
settings.
* gdb.texinfo (MIPS): Remove documentation for set mips saved-gpreg-size,
show mips saved-gpreg-size, and set mips stack-arg-size.
2007-05-16 22:16:32 +08:00
|
|
|
set mips stack-arg-size
|
|
|
|
|
set mips saved-gpreg-size
|
|
|
|
|
|
|
|
|
|
Use "set mips abi" to control parameter passing for MIPS.
|
|
|
|
|
|
2006-11-20 08:16:05 +08:00
|
|
|
*** Changes in GDB 6.6
|
2006-05-17 03:43:57 +08:00
|
|
|
|
2006-11-15 05:53:59 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Xtensa xtensa-elf
|
2006-11-25 04:19:37 +08:00
|
|
|
Cell Broadband Engine SPU spu-elf
|
2006-11-15 05:53:59 +08:00
|
|
|
|
2006-07-25 02:20:58 +08:00
|
|
|
* GDB can now be configured as a cross-debugger targeting native Windows
|
|
|
|
|
(mingw32) or Cygwin. It can communicate with a remote debugging stub
|
|
|
|
|
running on a Windows system over TCP/IP to debug Windows programs.
|
|
|
|
|
|
|
|
|
|
* The GDB remote stub, gdbserver, has been updated to support Windows and
|
|
|
|
|
Cygwin debugging. Both single-threaded and multi-threaded programs are
|
|
|
|
|
supported.
|
|
|
|
|
|
2006-08-17 04:33:23 +08:00
|
|
|
* The "set trust-readonly-sections" command works again. This command was
|
|
|
|
|
broken in GDB 6.3, 6.4, and 6.5.
|
|
|
|
|
|
2007-01-22 01:48:53 +08:00
|
|
|
* The "load" command now supports writing to flash memory, if the remote
|
|
|
|
|
stub provides the required support.
|
|
|
|
|
|
2006-10-18 23:29:18 +08:00
|
|
|
* Support for GNU/Linux Thread Local Storage (TLS, per-thread variables) no
|
|
|
|
|
longer requires symbolic debug information (e.g. DWARF-2).
|
|
|
|
|
|
2006-08-10 00:50:04 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
set substitute-path
|
|
|
|
|
unset substitute-path
|
|
|
|
|
show substitute-path
|
|
|
|
|
Manage a list of substitution rules that GDB uses to rewrite the name
|
|
|
|
|
of the directories where the sources are located. This can be useful
|
|
|
|
|
for instance when the sources were moved to a different location
|
|
|
|
|
between compilation and debugging.
|
|
|
|
|
|
2006-08-11 20:46:03 +08:00
|
|
|
set trace-commands
|
|
|
|
|
show trace-commands
|
|
|
|
|
Print each CLI command as it is executed. Each command is prefixed with
|
|
|
|
|
a number of `+' symbols representing the nesting depth.
|
|
|
|
|
The source command now has a `-v' option to enable the same feature.
|
|
|
|
|
|
2006-05-17 22:40:39 +08:00
|
|
|
* REMOVED features
|
|
|
|
|
|
|
|
|
|
The ARM Demon monitor support (RDP protocol, "target rdp").
|
|
|
|
|
|
2006-07-06 03:03:47 +08:00
|
|
|
Kernel Object Display, an embedded debugging feature which only worked with
|
|
|
|
|
an obsolete version of Cisco IOS.
|
|
|
|
|
|
2006-08-08 23:48:08 +08:00
|
|
|
The 'set download-write-size' and 'show download-write-size' commands.
|
|
|
|
|
|
2006-06-21 21:57:21 +08:00
|
|
|
* New remote packets
|
|
|
|
|
|
|
|
|
|
qSupported:
|
|
|
|
|
Tell a stub about GDB client features, and request remote target features.
|
|
|
|
|
The first feature implemented is PacketSize, which allows the target to
|
|
|
|
|
specify the size of packets it can handle - to minimize the number of
|
|
|
|
|
packets required and improve performance when connected to a remote
|
|
|
|
|
target.
|
|
|
|
|
|
2006-07-13 02:50:18 +08:00
|
|
|
qXfer:auxv:read:
|
2024-10-06 13:59:48 +08:00
|
|
|
Fetch an OS auxiliary vector from the remote stub. This packet is a
|
2006-07-13 02:50:18 +08:00
|
|
|
more efficient replacement for qPart:auxv:read.
|
|
|
|
|
|
2007-01-22 01:48:53 +08:00
|
|
|
qXfer:memory-map:read:
|
|
|
|
|
Fetch a memory map from the remote stub, including information about
|
|
|
|
|
RAM, ROM, and flash memory devices.
|
|
|
|
|
|
|
|
|
|
vFlashErase:
|
|
|
|
|
vFlashWrite:
|
|
|
|
|
vFlashDone:
|
|
|
|
|
Erase and program a flash memory device.
|
|
|
|
|
|
2006-07-13 02:50:18 +08:00
|
|
|
* Removed remote packets
|
|
|
|
|
|
|
|
|
|
qPart:auxv:read:
|
|
|
|
|
This packet has been replaced by qXfer:auxv:read. Only GDB 6.4 and 6.5
|
|
|
|
|
used it, and only gdbserver implemented it.
|
|
|
|
|
|
2006-05-17 03:43:57 +08:00
|
|
|
*** Changes in GDB 6.5
|
2005-12-02 19:44:19 +08:00
|
|
|
|
2006-04-21 07:18:48 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Renesas M32C/M16C m32c-elf
|
|
|
|
|
|
|
|
|
|
Morpho Technologies ms1 ms1-elf
|
|
|
|
|
|
2005-12-02 19:44:19 +08:00
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
init-if-undefined Initialize a convenience variable, but
|
|
|
|
|
only if it doesn't already have a value.
|
|
|
|
|
|
2006-01-05 03:34:58 +08:00
|
|
|
The following commands are presently only implemented for native GNU/Linux:
|
|
|
|
|
|
|
|
|
|
checkpoint Save a snapshot of the program state.
|
|
|
|
|
|
|
|
|
|
restart <n> Return the program state to a
|
|
|
|
|
previously saved state.
|
|
|
|
|
|
|
|
|
|
info checkpoints List currently saved checkpoints.
|
|
|
|
|
|
|
|
|
|
delete-checkpoint <n> Delete a previously saved checkpoint.
|
|
|
|
|
|
|
|
|
|
set|show detach-on-fork Tell gdb whether to detach from a newly
|
|
|
|
|
forked process, or to keep debugging it.
|
|
|
|
|
|
|
|
|
|
info forks List forks of the user program that
|
|
|
|
|
are available to be debugged.
|
|
|
|
|
|
|
|
|
|
fork <n> Switch to debugging one of several
|
|
|
|
|
forks of the user program that are
|
|
|
|
|
available to be debugged.
|
|
|
|
|
|
|
|
|
|
delete-fork <n> Delete a fork from the list of forks
|
|
|
|
|
that are available to be debugged (and
|
|
|
|
|
kill the forked process).
|
|
|
|
|
|
|
|
|
|
detach-fork <n> Delete a fork from the list of forks
|
|
|
|
|
that are available to be debugged (and
|
|
|
|
|
allow the process to continue).
|
|
|
|
|
|
2005-12-08 18:35:18 +08:00
|
|
|
* New architecture
|
|
|
|
|
|
|
|
|
|
Morpho Technologies ms2 ms1-elf
|
|
|
|
|
|
* NEWS: Mention native Windows support.
* Makefile.in (gdb_select_h, ser_tcp_h): New.
(ALLDEPFILES): Add ser-mingw.c.
(event-loop.o, inflow.o, mingw-hdep.o, posix-hdep.o, ser-base.o)
(ser-tcp.o, ser-unix.o): Update.
(ser-mingw.o): New rule.
* configure: Regenerated.
* configure.ac: Add ser-mingw.o for mingw32.
* ser-mingw.c: New file.
* event-loop.c: Include "gdb_select.h".
(gdb_select): Remove, moved to mingw-hdep.c and posix-hdep.c.
* ser-base.c: Include "gdb_select.h".
(ser_base_wait_for): Use gdb_select.
* serial.c (serial_for_fd): New function.
(serial_fdopen): Try "terminal" before "hardwire". Initialize
the allocated struct serial.
(serial_wait_handle): New function.
* serial.h (serial_for_fd, serial_wait_handle): New prototypes.
(struct serial_ops) [USE_WIN32API]: Add wait_handle.
* gdb_select.h: New file.
* ser-tcp.c: Include "ser-tcp.h". Remove unused "ser-unix.h" include.
(net_close, net_read_prim, net_write_prim): Make global.
(net_open): Likewise. Pass an exception set to select. Whitespace fix.
Document why we can not use gdb_select.
(_initialize_ser_tcp) [USE_WIN32API]: Do not register TCP support here.
* ser-tcp.h: New file.
* inflow.c (gdb_has_a_terminal): Don't initialize stdin_serial here.
(handle_sigio): Use gdb_select.
(initialize_stdin_serial): New function.
* terminal.h (initialize_stdin_serial): New prototype.
* top.c (gdb_init): Call initialize_stdin_serial.
* mingw-hdep.c (gdb_select): New function, moved from gdb_select in
event-loop.c. Add exception condition support. Use serial_for_fd
and serial_wait_handle. Fix timeout handling.
* posix-hdep.c: Include "gdb_select.h".
(gdb_select): New function.
* remote-st.c (connect_command): Use gdb_select.
* ser-unix.c: Include "gdb_select.h".
(hardwire_send_break, wait_for): Use gdb_select.
2006-02-11 06:01:43 +08:00
|
|
|
* Improved Windows host support
|
|
|
|
|
|
|
|
|
|
GDB now builds as a cross debugger hosted on i686-mingw32, including
|
|
|
|
|
native console support, and remote communications using either
|
|
|
|
|
network sockets or serial ports.
|
|
|
|
|
|
2006-05-21 00:30:18 +08:00
|
|
|
* Improved Modula-2 language support
|
|
|
|
|
|
|
|
|
|
GDB can now print most types in the Modula-2 syntax. This includes:
|
|
|
|
|
basic types, set types, record types, enumerated types, range types,
|
|
|
|
|
pointer types and ARRAY types. Procedure var parameters are correctly
|
|
|
|
|
printed and hexadecimal addresses and character constants are also
|
|
|
|
|
written in the Modula-2 syntax. Best results can be obtained by using
|
|
|
|
|
GNU Modula-2 together with the -gdwarf-2 command line option.
|
|
|
|
|
|
2006-01-21 09:29:04 +08:00
|
|
|
* REMOVED features
|
|
|
|
|
|
|
|
|
|
The ARM rdi-share module.
|
|
|
|
|
|
2006-03-30 06:58:55 +08:00
|
|
|
The Netware NLM debug server.
|
|
|
|
|
|
2005-12-02 19:44:19 +08:00
|
|
|
*** Changes in GDB 6.4
|
2004-10-26 02:50:09 +08:00
|
|
|
|
2005-05-13 05:19:09 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
2005-05-23 04:40:26 +08:00
|
|
|
OpenBSD/arm arm*-*-openbsd*
|
2005-05-13 05:19:09 +08:00
|
|
|
OpenBSD/mips64 mips64-*-openbsd*
|
|
|
|
|
|
2005-08-18 07:02:00 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Morpho Technologies ms1 ms1-elf
|
|
|
|
|
|
2005-11-15 20:38:45 +08:00
|
|
|
* New command line options
|
|
|
|
|
|
|
|
|
|
--batch-silent As for --batch, but totally silent.
|
|
|
|
|
--return-child-result The debugger will exist with the same value
|
|
|
|
|
the child (debugged) program exited with.
|
|
|
|
|
--eval-command COMMAND, -ex COMMAND
|
|
|
|
|
Execute a single GDB CLI command. This may be
|
|
|
|
|
specified multiple times and in conjunction
|
|
|
|
|
with the --command (-x) option.
|
|
|
|
|
|
2005-02-10 05:56:12 +08:00
|
|
|
* Deprecated commands removed
|
|
|
|
|
|
|
|
|
|
The following commands, that were deprecated in 2000, have been
|
|
|
|
|
removed:
|
|
|
|
|
|
|
|
|
|
Command Replacement
|
|
|
|
|
set|show arm disassembly-flavor set|show arm disassembler
|
|
|
|
|
othernames set arm disassembler
|
|
|
|
|
set|show remotedebug set|show debug remote
|
|
|
|
|
set|show archdebug set|show debug arch
|
|
|
|
|
set|show eventdebug set|show debug event
|
|
|
|
|
regs info registers
|
|
|
|
|
|
2005-01-24 03:43:23 +08:00
|
|
|
* New BSD user-level threads support
|
|
|
|
|
|
|
|
|
|
It is now possible to debug programs using the user-level threads
|
|
|
|
|
library on OpenBSD and FreeBSD. Currently supported (target)
|
|
|
|
|
configurations are:
|
|
|
|
|
|
|
|
|
|
FreeBSD/amd64 x86_64-*-freebsd*
|
|
|
|
|
FreeBSD/i386 i386-*-freebsd*
|
|
|
|
|
OpenBSD/i386 i386-*-openbsd*
|
|
|
|
|
|
|
|
|
|
Note that the new kernel threads libraries introduced in FreeBSD 5.x
|
|
|
|
|
are not yet supported.
|
|
|
|
|
|
2004-12-17 07:53:12 +08:00
|
|
|
* New support for Matsushita MN10300 w/sim added
|
|
|
|
|
(Work in progress). mn10300-elf.
|
|
|
|
|
|
2004-11-13 Andrew Cagney <cagney@gnu.org>
* configure.tgt: Delete i[34567]86-*-vxworks*, m68*-netx-*,
m68*-*-vxworks*, mips*-*-vxworks*, powerpc-*-vxworks*, and
sparc-*-vxworks*.
* NEWS: Mention that vxworks was deleted.
* config/m68k/tm-vx68.h, config/mips/tm-vxmips.h: Delete.
* config/powerpc/tm-vxworks.h, config/tm-vxworks.h: Delete.
* config/i386/vxworks.mt, config/m68k/vxworks68.mt: Delete.
* config/mips/vxmips.mt, config/powerpc/vxworks.mt: Delete.
* config/sparc/vxworks.mt, vx-share/dbgRpcLib.h: Delete.
* vx-share/ptrace.h, vx-share/regPacket.h: Delete.
* vx-share/vxTypes.h, vx-share/vxWorks.h: Delete.
* vx-share/wait.h, vx-share/xdr_ld.c: Delete.
* vx-share/xdr_ld.h, vx-share/xdr_ptrace.c: Delete.
* vx-share/xdr_ptrace.h, vx-share/xdr_rdb.c: Delete.
* vx-share/xdr_rdb.h, remote-vxsparc.c: Delete.
* remote-vxmips.c, remote-vx.c: Delete.
* remote-vx68.c: Delete.
* config/m68k/tm-os68k.h: Remove reference to VxWorks.
* config/m68k/os68k.mt, ada-lang.h: Ditto.
* Makefile.in (HFILES_NO_SRCDIR, ALLDEPFILES, remote-vx68.o)
(remote-vx.o, remote-vxmips.o, remote-vxsparc.o): Delete vx files.
2004-11-14 07:10:02 +08:00
|
|
|
* REMOVED configurations and files
|
|
|
|
|
|
|
|
|
|
VxWorks and the XDR protocol *-*-vxworks
|
2004-11-13 Andrew Cagney <cagney@gnu.org>
* NEWS: List h8300*-*-*, mcore-*-*, mn10300-*-*, ns32k-*-*, and
v850-*-* under removed.
* configure.host: Delete ns32k-*-netbsd*.
* configure.tgt: Delete h8300-*-*, mcore*-*-*, mn10300-*-*,
ns32k-*-netbsd*, and v850*-*-*.
* MAINTAINERS: Mark h8300, mcore, mn10300, ns32k, v850 as
"Deleted"
* config/h8300/tm-h8300.h, config/h8300/h8300.mt: Delete.
* h8300-tdep.c, config/mcore/mcore.mt, mcore-rom.c: Delete.
* mcore-tdep.c, config/mn10300/mn10300.mt: Delete.
* mn10300-tdep.c, config/ns32k/nbsdaout.mh: Delete.
* config/ns32k/nbsdaout.mt, config/ns32k/nm-nbsd.h: Delete.
* config/ns32k/nm-nbsdaout.h, config/ns32k/tm-ns32k.h: Delete.
* ns32knbsd-nat.c, ns32knbsd-tdep.c, ns32k-tdep.c: Delete.
* ns32k-tdep.h, config/v850/v850.mt, v850ice.c: Delete.
* v850-tdep.c: Delete.
2004-11-14 08:10:55 +08:00
|
|
|
Motorola MCORE mcore-*-*
|
|
|
|
|
National Semiconductor NS32000 ns32k-*-*
|
2004-10-26 02:50:09 +08:00
|
|
|
|
2005-10-04 08:16:07 +08:00
|
|
|
* New "set print array-indexes" command
|
|
|
|
|
|
|
|
|
|
After turning this setting "on", GDB prints the index of each element
|
|
|
|
|
when displaying arrays. The default is "off" to preserve the previous
|
|
|
|
|
behavior.
|
|
|
|
|
|
2005-11-01 15:30:47 +08:00
|
|
|
* VAX floating point support
|
|
|
|
|
|
|
|
|
|
GDB now supports the not-quite-ieee VAX F and D floating point formats.
|
|
|
|
|
|
2005-11-16 20:49:17 +08:00
|
|
|
* User-defined command support
|
|
|
|
|
|
|
|
|
|
In addition to using $arg0..$arg9 for argument passing, it is now possible
|
|
|
|
|
to use $argc to determine now many arguments have been passed. See the
|
|
|
|
|
section on user-defined commands in the user manual for more information.
|
|
|
|
|
|
2004-10-20 03:43:50 +08:00
|
|
|
*** Changes in GDB 6.3:
|
|
|
|
|
|
2004-12-07 19:06:04 +08:00
|
|
|
* New command line option
|
|
|
|
|
|
|
|
|
|
GDB now accepts -l followed by a number to set the timeout for remote
|
|
|
|
|
debugging.
|
|
|
|
|
|
2004-10-20 03:43:50 +08:00
|
|
|
* GDB works with GCC -feliminate-dwarf2-dups
|
|
|
|
|
|
|
|
|
|
GDB now supports a more compact representation of DWARF-2 debug
|
|
|
|
|
information using DW_FORM_ref_addr references. These are produced
|
|
|
|
|
by GCC with the option -feliminate-dwarf2-dups and also by some
|
|
|
|
|
proprietary compilers. With GCC, you must use GCC 3.3.4 or later
|
|
|
|
|
to use -feliminate-dwarf2-dups.
|
2004-07-19 06:29:40 +08:00
|
|
|
|
2004-11-03 22:33:54 +08:00
|
|
|
* Internationalization
|
|
|
|
|
|
|
|
|
|
When supported by the host system, GDB will be built with
|
|
|
|
|
internationalization (libintl). The task of marking up the sources is
|
|
|
|
|
continued, we're looking forward to our first translation.
|
|
|
|
|
|
2004-11-02 17:41:00 +08:00
|
|
|
* Ada
|
|
|
|
|
|
|
|
|
|
Initial support for debugging programs compiled with the GNAT
|
|
|
|
|
implementation of the Ada programming language has been integrated
|
|
|
|
|
into GDB. In this release, support is limited to expression evaluation.
|
|
|
|
|
|
2004-11-03 22:33:54 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
GNU/Linux/m32r m32r-*-linux-gnu
|
|
|
|
|
|
|
|
|
|
* Remote 'p' packet
|
|
|
|
|
|
|
|
|
|
GDB's remote protocol now includes support for the 'p' packet. This
|
|
|
|
|
packet is used to fetch individual registers from a remote inferior.
|
|
|
|
|
|
|
|
|
|
* END-OF-LIFE registers[] compatibility module
|
|
|
|
|
|
|
|
|
|
GDB's internal register infrastructure has been completely rewritten.
|
|
|
|
|
The new infrastructure making possible the implementation of key new
|
|
|
|
|
features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
|
|
|
|
|
i386 application).
|
|
|
|
|
|
2020-03-06 22:22:23 +08:00
|
|
|
GDB 6.3 will be the last release to include the registers[]
|
2004-11-03 22:33:54 +08:00
|
|
|
compatibility module that allowed out-of-date configurations to
|
|
|
|
|
continue to work. This change directly impacts the following
|
|
|
|
|
configurations:
|
|
|
|
|
|
|
|
|
|
hppa-*-hpux
|
|
|
|
|
ia64-*-aix
|
|
|
|
|
mips-*-irix*
|
|
|
|
|
*-*-lynx
|
|
|
|
|
mips-*-linux-gnu
|
|
|
|
|
sds protocol
|
|
|
|
|
xdr protocol
|
|
|
|
|
powerpc bdm protocol
|
|
|
|
|
|
|
|
|
|
Unless there is activity to revive these configurations, they will be
|
|
|
|
|
made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5.
|
|
|
|
|
|
|
|
|
|
* OBSOLETE configurations and files
|
|
|
|
|
|
|
|
|
|
Configurations that have been declared obsolete in this release have
|
|
|
|
|
been commented out. Unless there is activity to revive these
|
|
|
|
|
configurations, the next release of GDB will have their sources
|
|
|
|
|
permanently REMOVED.
|
|
|
|
|
|
|
|
|
|
h8300-*-*
|
|
|
|
|
mcore-*-*
|
|
|
|
|
mn10300-*-*
|
|
|
|
|
ns32k-*-*
|
|
|
|
|
sh64-*-*
|
|
|
|
|
v850-*-*
|
|
|
|
|
|
2004-08-13 05:44:19 +08:00
|
|
|
*** Changes in GDB 6.2.1:
|
|
|
|
|
|
|
|
|
|
* MIPS `break main; run' gave an heuristic-fence-post warning
|
|
|
|
|
|
|
|
|
|
When attempting to run even a simple program, a warning about
|
|
|
|
|
heuristic-fence-post being hit would be reported. This problem has
|
|
|
|
|
been fixed.
|
|
|
|
|
|
|
|
|
|
* MIPS IRIX 'long double' crashed GDB
|
|
|
|
|
|
|
|
|
|
When examining a long double variable, GDB would get a segmentation
|
|
|
|
|
fault. The crash has been fixed (but GDB 6.2 cannot correctly examine
|
|
|
|
|
IRIX long double values).
|
|
|
|
|
|
|
|
|
|
* VAX and "next"
|
|
|
|
|
|
|
|
|
|
A bug in the VAX stack code was causing problems with the "next"
|
|
|
|
|
command. This problem has been fixed.
|
|
|
|
|
|
2004-07-19 06:29:40 +08:00
|
|
|
*** Changes in GDB 6.2:
|
2004-02-29 10:57:24 +08:00
|
|
|
|
2004-07-29 03:53:39 +08:00
|
|
|
* Fix for ``many threads''
|
|
|
|
|
|
|
|
|
|
On GNU/Linux systems that use the NPTL threads library, a program
|
|
|
|
|
rapidly creating and deleting threads would confuse GDB leading to the
|
|
|
|
|
error message:
|
|
|
|
|
|
|
|
|
|
ptrace: No such process.
|
|
|
|
|
thread_db_get_info: cannot get thread info: generic error
|
|
|
|
|
|
|
|
|
|
This problem has been fixed.
|
|
|
|
|
|
2004-07-17 11:25:11 +08:00
|
|
|
* "-async" and "-noasync" options removed.
|
|
|
|
|
|
|
|
|
|
Support for the broken "-noasync" option has been removed (it caused
|
|
|
|
|
GDB to dump core).
|
|
|
|
|
|
2004-05-26 14:32:01 +08:00
|
|
|
* New ``start'' command.
|
|
|
|
|
|
2020-06-05 18:24:20 +08:00
|
|
|
This command runs the program until the beginning of the main procedure.
|
2004-05-26 14:32:01 +08:00
|
|
|
|
2004-07-11 05:24:01 +08:00
|
|
|
* New BSD Kernel Data Access Library (libkvm) interface
|
|
|
|
|
|
|
|
|
|
Using ``target kvm'' it is now possible to debug kernel core dumps and
|
|
|
|
|
live kernel memory images on various FreeBSD, NetBSD and OpenBSD
|
|
|
|
|
platforms. Currently supported (native-only) configurations are:
|
|
|
|
|
|
|
|
|
|
FreeBSD/amd64 x86_64-*-freebsd*
|
|
|
|
|
FreeBSD/i386 i?86-*-freebsd*
|
|
|
|
|
NetBSD/i386 i?86-*-netbsd*
|
|
|
|
|
NetBSD/m68k m68*-*-netbsd*
|
|
|
|
|
NetBSD/sparc sparc-*-netbsd*
|
|
|
|
|
OpenBSD/amd64 x86_64-*-openbsd*
|
|
|
|
|
OpenBSD/i386 i?86-*-openbsd*
|
|
|
|
|
OpenBSD/m68k m68*-openbsd*
|
|
|
|
|
OpenBSD/sparc sparc-*-openbsd*
|
|
|
|
|
|
2004-05-18 03:16:07 +08:00
|
|
|
* Signal trampoline code overhauled
|
|
|
|
|
|
|
|
|
|
Many generic problems with GDB's signal handling code have been fixed.
|
|
|
|
|
These include: backtraces through non-contiguous stacks; recognition
|
|
|
|
|
of sa_sigaction signal trampolines; backtrace from a NULL pointer
|
|
|
|
|
call; backtrace through a signal trampoline; step into and out of
|
|
|
|
|
signal handlers; and single-stepping in the signal trampoline.
|
|
|
|
|
|
2004-07-22 00:17:56 +08:00
|
|
|
Please note that kernel bugs are a limiting factor here. These
|
|
|
|
|
features have been shown to work on an s390 GNU/Linux system that
|
|
|
|
|
include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702.
|
2004-05-18 03:16:07 +08:00
|
|
|
|
2004-05-07 22:34:35 +08:00
|
|
|
* Cygwin support for DWARF 2 added.
|
|
|
|
|
|
2004-04-15 03:19:12 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
2004-06-30 00:13:07 +08:00
|
|
|
GNU/Linux/hppa hppa*-*-linux*
|
2004-06-26 18:06:35 +08:00
|
|
|
OpenBSD/hppa hppa*-*-openbsd*
|
2004-05-25 05:00:09 +08:00
|
|
|
OpenBSD/m68k m68*-*-openbsd*
|
|
|
|
|
OpenBSD/m88k m88*-*-openbsd*
|
2004-04-23 05:13:06 +08:00
|
|
|
OpenBSD/powerpc powerpc-*-openbsd*
|
2004-04-15 03:19:12 +08:00
|
|
|
NetBSD/vax vax-*-netbsd*
|
2004-04-15 23:10:01 +08:00
|
|
|
OpenBSD/vax vax-*-openbsd*
|
2004-04-15 03:19:12 +08:00
|
|
|
|
2004-07-27 02:30:19 +08:00
|
|
|
* END-OF-LIFE frame compatibility module
|
|
|
|
|
|
|
|
|
|
GDB's internal frame infrastructure has been completely rewritten.
|
|
|
|
|
The new infrastructure making it possible to support key new features
|
|
|
|
|
including DWARF 2 Call Frame Information. To aid in the task of
|
|
|
|
|
migrating old configurations to this new infrastructure, a
|
|
|
|
|
compatibility module, that allowed old configurations to continue to
|
|
|
|
|
work, was also included.
|
|
|
|
|
|
|
|
|
|
GDB 6.2 will be the last release to include this frame compatibility
|
|
|
|
|
module. This change directly impacts the following configurations:
|
|
|
|
|
|
|
|
|
|
h8300-*-*
|
|
|
|
|
mcore-*-*
|
|
|
|
|
mn10300-*-*
|
|
|
|
|
ns32k-*-*
|
|
|
|
|
sh64-*-*
|
|
|
|
|
v850-*-*
|
|
|
|
|
xstormy16-*-*
|
|
|
|
|
|
|
|
|
|
Unless there is activity to revive these configurations, they will be
|
|
|
|
|
made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4.
|
|
|
|
|
|
2004-04-04 Andrew Cagney <cagney@redhat.com>
* config/mips/xm-riscos.h: Delete.
* config/mips/xm-mipsv4.h, config/mips/xm-mips.h: Delete.
* config/mips/tm-mipsv4.h, config/mips/riscos.mh: Delete.
* config/mips/nm-riscos.h, config/mips/nm-news-mips.h: Delete.
* config/mips/nm-mips.h, config/mips/news-mips.mh: Delete.
* config/mips/news-mips.mh, config/m68k/tm-m68kv4.h: Delete.
* config/mips/decstation.mh, config/mips/littlemips.mh: Delete.
* config/mips/mipsv4.mt, config/m68k/tm-sun3.h: Delete.
* config/m68k/xm-sun3os4.h, config/m68k/xm-sun3.h: Delete.
* config/m68k/xm-sun2.h, config/m68k/xm-m68kv4.h: Delete.
* config/m68k/xm-dpx2.h, config/m68k/xm-delta68.h: Delete.
* config/m68k/xm-3b1.h, config/m68k/tm-sun3os4.h: Delete.
* config/m68k/tm-m68klynx.h, config/m68k/tm-dpx2.h: Delete.
* config/m68k/tm-delta68.h, config/m68k/tm-3b1.h: Delete.
* config/m68k/sun3os4.mt, config/m68k/nm-sysv4.h: Delete.
* config/m68k/nm-sun3.h, config/m68k/sun3os4.mh: Delete.
* config/m68k/sun2os3.mh, config/m68k/nm-sun2.h: Delete.
* config/m68k/nm-m68klynx.h, config/m68k/sun3os3.mt: Delete.
* config/m68k/nm-dpx2.h, config/m68k/sun2os3.mt: Delete.
* config/m68k/dpx2.mh, config/m68k/sun3os3.mh: Delete.
* config/m68k/sun2os4.mh, config/m68k/nm-delta68.h: Delete.
* config/m68k/m68kv4.mt, config/m68k/m68klynx.mt: Delete.
* config/m68k/3b1.mt, config/m68k/m68klynx.mh: Delete.
* config/m68k/m68kv4.mh, config/m68k/sun2os4.mt: Delete.
* config/m68k/tm-sun2os4.h, config/m68k/3b1.mh: Delete.
* config/m68k/dpx2.mt, config/m68k/delta68.mt: Delete.
* config/m68k/tm-sun2.h, config/m68k/delta68.mh: Delete.
* configure.tgt: Remove m68000-*-sunos3*, m68000-*-sunos4*,
m68*-bull-sysv*, m68*-att-*, m68*-motorola-*, m68*-*-lynxos*,
m68*-*-sunos3*, m68*-*-sunos4*, m68*-*-sysv4*, mips*-*-sysv4*.
* configure.host: Remove m680[01]0-sun-sunos3*,
m680[01]0-sun-sunos4*, m68*-att-*, m68*-bull*-sysv*,
m68*-*-lynxos*, m68*-*-sysv4*, m68*-motorola-*, m68*-sun-sunos3*,
m68*-sun-sunos4*, m68*-sun-*, mips-dec-*, mips-little-*,
mips-sony-*, mips-*-mach3*, mips-*-sysv4*, mips-*-sysv*,
mips-*-riscos*.
* NEWS: Mention removed systems.
2004-04-05 11:52:43 +08:00
|
|
|
* REMOVED configurations and files
|
|
|
|
|
|
|
|
|
|
Sun 3, running SunOS 3 m68*-*-sunos3*
|
|
|
|
|
Sun 3, running SunOS 4 m68*-*-sunos4*
|
|
|
|
|
Sun 2, running SunOS 3 m68000-*-sunos3*
|
|
|
|
|
Sun 2, running SunOS 4 m68000-*-sunos4*
|
|
|
|
|
Motorola 680x0 running LynxOS m68*-*-lynxos*
|
|
|
|
|
AT&T 3b1/Unix pc m68*-att-*
|
|
|
|
|
Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
|
|
|
|
|
decstation mips-dec-* mips-little-*
|
|
|
|
|
riscos mips-*-riscos* mips-*-sysv*
|
|
|
|
|
sonymips mips-sony-*
|
|
|
|
|
sysv mips*-*-sysv4* (IRIX 5/6 not included)
|
|
|
|
|
|
2004-06-18 01:30:30 +08:00
|
|
|
*** Changes in GDB 6.1.1:
|
|
|
|
|
|
|
|
|
|
* TUI (Text-mode User Interface) built-in (also included in GDB 6.1)
|
|
|
|
|
|
|
|
|
|
The TUI (Text-mode User Interface) is now built as part of a default
|
|
|
|
|
GDB configuration. It is enabled by either selecting the TUI with the
|
|
|
|
|
command line option "-i=tui" or by running the separate "gdbtui"
|
|
|
|
|
program. For more information on the TUI, see the manual "Debugging
|
|
|
|
|
with GDB".
|
|
|
|
|
|
|
|
|
|
* Pending breakpoint support (also included in GDB 6.1)
|
|
|
|
|
|
|
|
|
|
Support has been added to allow you to specify breakpoints in shared
|
|
|
|
|
libraries that have not yet been loaded. If a breakpoint location
|
|
|
|
|
cannot be found, and the "breakpoint pending" option is set to auto,
|
|
|
|
|
GDB queries you if you wish to make the breakpoint pending on a future
|
|
|
|
|
shared-library load. If and when GDB resolves the breakpoint symbol,
|
|
|
|
|
the pending breakpoint is removed as one or more regular breakpoints
|
|
|
|
|
are created.
|
|
|
|
|
|
|
|
|
|
Pending breakpoints are very useful for GCJ Java debugging.
|
|
|
|
|
|
|
|
|
|
* Fixed ISO-C build problems
|
|
|
|
|
|
|
|
|
|
The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
|
|
|
|
|
non ISO-C code that stopped them being built using a more strict ISO-C
|
|
|
|
|
compiler (e.g., IBM's C compiler).
|
|
|
|
|
|
|
|
|
|
* Fixed build problem on IRIX 5
|
|
|
|
|
|
|
|
|
|
Due to header problems with <sys/proc.h>, the file gdb/proc-api.c
|
|
|
|
|
wasn't able to compile compile on an IRIX 5 system.
|
|
|
|
|
|
|
|
|
|
* Added execute permission to gdb/gdbserver/configure
|
|
|
|
|
|
|
|
|
|
The shell script gdb/testsuite/gdb.stabs/configure lacked execute
|
|
|
|
|
permission. This bug would cause configure to fail on a number of
|
|
|
|
|
systems (Solaris, IRIX). Ref: server/519.
|
|
|
|
|
|
|
|
|
|
* Fixed build problem on hpux2.0w-hp-hpux11.00 using the HP ANSI C compiler
|
|
|
|
|
|
|
|
|
|
Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
|
|
|
|
|
has been updated to use constant array sizes.
|
|
|
|
|
|
|
|
|
|
* Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7
|
|
|
|
|
|
|
|
|
|
GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in
|
|
|
|
|
its generated DWARF Call Frame Info. This encoding was causing GDB to
|
|
|
|
|
panic, that panic has been fixed. Ref: gdb/1628.
|
|
|
|
|
|
|
|
|
|
* Fixed a problem when examining parameters in shared library code.
|
|
|
|
|
|
|
|
|
|
When examining parameters in optimized shared library code generated
|
|
|
|
|
by a mainline GCC, GDB would incorrectly report ``Variable "..." is
|
|
|
|
|
not available''. GDB now correctly displays the variable's value.
|
|
|
|
|
|
2004-02-29 10:57:24 +08:00
|
|
|
*** Changes in GDB 6.1:
|
2003-06-23 11:28:14 +08:00
|
|
|
|
2004-01-19 Michael Chastain <mec.gnu@mindspring.com>
* MAINTAINERS: Delete mmalloc.
* Makefile.in: Delete MMALLOC, MMALLOC_CFLAGS, -lmmalloc, mmalloc_h.
* NEWS: Mention removal of --with-malloc.
* acconfig.h: Delete USE_MMALLOC, MMCHECK_FORCE.
* config.in: Regenerate.
* configure: Regenerate.
* configure.in: Delete MMALLOC_CFLAGS, MMALLOC, --with-mmalloc, USE_MMALLOC, MMCHECK_FORCE.
* gdbinit.in: Remove mmalloc.
* utils.c: Delete USE_MMALLOC, NO_MMCHECK, MMCHECK_FORCE, malloc_botch.
* config/alpha/alpha-linux.mh: Delete MMALLOC, MMALLOC_CFLAGS.
* config/i386/go32.mh: Likewise.
* config/i386/interix.mh: Likewise.
* config/powerpc/xm-linux.h: Delete MMAP_BASE_ADDRESS, MMAP_INCREMENT.
2004-01-19 Michael Chastain <mec.gnu@mindspring.com>
* gdbint.texinfo: Delete USE_MMALLOC, NO_MMCHECK, MMCHECK_FORCE,
MMAP_BASE_ADDRESS, MMAP_INCREMENT.
2004-01-20 17:29:18 +08:00
|
|
|
* Removed --with-mmalloc
|
|
|
|
|
|
|
|
|
|
Support for the mmalloc memory manager has been removed, as it
|
|
|
|
|
conflicted with the internal gdb byte cache.
|
|
|
|
|
|
2004-01-12 01:00:38 +08:00
|
|
|
* Changes in AMD64 configurations
|
|
|
|
|
|
|
|
|
|
The AMD64 target now includes the %cs and %ss registers. As a result
|
|
|
|
|
the AMD64 remote protocol has changed; this affects the floating-point
|
|
|
|
|
and SSE registers. If you rely on those registers for your debugging,
|
|
|
|
|
you should upgrade gdbserver on the remote side.
|
|
|
|
|
|
2004-01-03 20:21:09 +08:00
|
|
|
* Revised SPARC target
|
|
|
|
|
|
|
|
|
|
The SPARC target has been completely revised, incorporating the
|
|
|
|
|
FreeBSD/sparc64 support that was added for GDB 6.0. As a result
|
2004-02-06 03:56:33 +08:00
|
|
|
support for LynxOS and SunOS 4 has been dropped. Calling functions
|
|
|
|
|
from within GDB on operating systems with a non-executable stack
|
|
|
|
|
(Solaris, OpenBSD) now works.
|
2004-01-03 20:21:09 +08:00
|
|
|
|
2003-12-04 03:53:11 +08:00
|
|
|
* New C++ demangler
|
|
|
|
|
|
|
|
|
|
GDB has a new C++ demangler which does a better job on the mangled
|
|
|
|
|
names generated by current versions of g++. It also runs faster, so
|
|
|
|
|
with this and other changes gdb should now start faster on large C++
|
|
|
|
|
programs.
|
|
|
|
|
|
2003-11-25 01:02:34 +08:00
|
|
|
* DWARF 2 Location Expressions
|
|
|
|
|
|
|
|
|
|
GDB support for location expressions has been extended to support function
|
|
|
|
|
arguments and frame bases. Older versions of GDB could crash when they
|
|
|
|
|
encountered these.
|
|
|
|
|
|
2004-03-18 01:35:54 +08:00
|
|
|
* C++ nested types and namespaces
|
|
|
|
|
|
|
|
|
|
GDB's support for nested types and namespaces in C++ has been
|
|
|
|
|
improved, especially if you use the DWARF 2 debugging format. (This
|
|
|
|
|
is the default for recent versions of GCC on most platforms.)
|
|
|
|
|
Specifically, if you have a class "Inner" defined within a class or
|
|
|
|
|
namespace "Outer", then GDB realizes that the class's name is
|
|
|
|
|
"Outer::Inner", not simply "Inner". This should greatly reduce the
|
|
|
|
|
frequency of complaints about not finding RTTI symbols. In addition,
|
|
|
|
|
if you are stopped at inside of a function defined within a namespace,
|
|
|
|
|
GDB modifies its name lookup accordingly.
|
|
|
|
|
|
2003-10-19 02:41:22 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
NetBSD/amd64 x86_64-*-netbsd*
|
2004-03-13 21:11:53 +08:00
|
|
|
OpenBSD/amd64 x86_64-*-openbsd*
|
2004-02-21 02:46:34 +08:00
|
|
|
OpenBSD/alpha alpha*-*-openbsd*
|
2004-01-23 07:18:04 +08:00
|
|
|
OpenBSD/sparc sparc-*-openbsd*
|
|
|
|
|
OpenBSD/sparc64 sparc64-*-openbsd*
|
2003-10-19 02:41:22 +08:00
|
|
|
|
2003-10-16 10:36:39 +08:00
|
|
|
* New debugging protocols
|
|
|
|
|
|
|
|
|
|
M32R with SDI protocol m32r-*-elf*
|
|
|
|
|
|
2003-08-17 02:38:46 +08:00
|
|
|
* "set prompt-escape-char" command deleted.
|
|
|
|
|
|
|
|
|
|
The command "set prompt-escape-char" has been deleted. This command,
|
2020-06-05 18:24:20 +08:00
|
|
|
and its very obscure effect on GDB's prompt, was never documented,
|
2003-08-17 02:38:46 +08:00
|
|
|
tested, nor mentioned in the NEWS file.
|
|
|
|
|
|
2003-12-01 Andrew Cagney <cagney@redhat.com>
Obsolete old m68k systems.
* configure.host: Mark m68*-sun-*, m68*-sun-sunos4*,
m68*-sun-sunos3*, m68*-motorola-*, m68*-*-sysv4*, m68*-*-lynxos*,
m68*-bull*-sysv*, m68*-att-*, m680[01]0-sun-sunos4*, and
m680[01]0-sun-sunos3* as obsolete.
* configure.tgt: Mark m68*-*-lynxos*, m68*-*-sunos3*,
m68*-*-sunos4*, m68*-*-sysv4*, m68000-*-sunos3*, m68000-*-sunos4*,
m68*-bull-sysv*, m68*-att-*, and m68*-motorola-*, as obsolete.
* config/m68k/sun3os4.mh: Mark file obsolete.
* config/m68k/xm-sun3os4.h: Mark file obsolete.
* config/m68k/sun3os3.mh: Mark file obsolete.
* config/m68k/nm-sun3.h: Mark file obsolete.
* config/m68k/xm-sun3.h: Mark file obsolete.
* config/m68k/sun2os4.mh: Mark file obsolete.
* config/m68k/sun2os3.mh: Mark file obsolete.
* config/m68k/nm-sun2.h: Mark file obsolete.
* config/m68k/xm-sun2.h: Mark file obsolete.
* config/m68k/m68kv4.mh: Mark file obsolete.
* config/m68k/nm-sysv4.h: Mark file obsolete.
* config/m68k/xm-m68kv4.h: Mark file obsolete.
* config/m68k/m68klynx.mh: Mark file obsolete.
* config/m68k/nm-m68klynx.h: Mark file obsolete.
* config/m68k/dpx2.mh: Mark file obsolete.
* config/m68k/xm-dpx2.h: Mark file obsolete.
* config/m68k/nm-dpx2.h: Mark file obsolete.
* config/m68k/delta68.mh: Mark file obsolete.
* config/m68k/xm-delta68.h: Mark file obsolete.
* config/m68k/nm-delta68.h: Mark file obsolete.
* config/m68k/3b1.mh: Mark file obsolete.
* config/m68k/xm-3b1.h: Mark file obsolete.
* config/m68k/sun3os4.mt: Mark file obsolete.
* config/m68k/tm-sun3os4.h: Mark file obsolete.
* config/m68k/sun3os3.mt: Mark file obsolete.
* config/m68k/tm-sun3.h: Mark file obsolete.
* config/m68k/sun2os4.mt: Mark file obsolete.
* config/m68k/tm-sun2os4.h: Mark file obsolete.
* config/m68k/sun2os3.mt: Mark file obsolete.
* config/m68k/tm-sun2.h: Mark file obsolete.
* config/m68k/m68kv4.mt: Mark file obsolete.
* config/m68k/tm-m68kv4.h: Mark file obsolete.
* config/m68k/m68klynx.mt: Mark file obsolete.
* config/m68k/tm-m68klynx.h: Mark file obsolete.
* config/m68k/dpx2.mt: Mark file obsolete.
* config/m68k/tm-dpx2.h: Mark file obsolete.
* config/m68k/delta68.mt: Mark file obsolete.
* config/m68k/tm-delta68.h: Mark file obsolete.
* config/m68k/3b1.mt: Mark file obsolete.
* config/m68k/tm-3b1.h: Mark file obsolete.
2003-12-01 22:53:42 +08:00
|
|
|
* OBSOLETE configurations and files
|
|
|
|
|
|
|
|
|
|
Configurations that have been declared obsolete in this release have
|
|
|
|
|
been commented out. Unless there is activity to revive these
|
|
|
|
|
configurations, the next release of GDB will have their sources
|
|
|
|
|
permanently REMOVED.
|
|
|
|
|
|
|
|
|
|
Sun 3, running SunOS 3 m68*-*-sunos3*
|
|
|
|
|
Sun 3, running SunOS 4 m68*-*-sunos4*
|
|
|
|
|
Sun 2, running SunOS 3 m68000-*-sunos3*
|
|
|
|
|
Sun 2, running SunOS 4 m68000-*-sunos4*
|
|
|
|
|
Motorola 680x0 running LynxOS m68*-*-lynxos*
|
|
|
|
|
AT&T 3b1/Unix pc m68*-att-*
|
|
|
|
|
Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
|
2003-12-02 05:10:46 +08:00
|
|
|
decstation mips-dec-* mips-little-*
|
|
|
|
|
riscos mips-*-riscos* mips-*-sysv*
|
|
|
|
|
sonymips mips-sony-*
|
|
|
|
|
sysv mips*-*-sysv4* (IRIX 5/6 not included)
|
2003-12-01 Andrew Cagney <cagney@redhat.com>
Obsolete old m68k systems.
* configure.host: Mark m68*-sun-*, m68*-sun-sunos4*,
m68*-sun-sunos3*, m68*-motorola-*, m68*-*-sysv4*, m68*-*-lynxos*,
m68*-bull*-sysv*, m68*-att-*, m680[01]0-sun-sunos4*, and
m680[01]0-sun-sunos3* as obsolete.
* configure.tgt: Mark m68*-*-lynxos*, m68*-*-sunos3*,
m68*-*-sunos4*, m68*-*-sysv4*, m68000-*-sunos3*, m68000-*-sunos4*,
m68*-bull-sysv*, m68*-att-*, and m68*-motorola-*, as obsolete.
* config/m68k/sun3os4.mh: Mark file obsolete.
* config/m68k/xm-sun3os4.h: Mark file obsolete.
* config/m68k/sun3os3.mh: Mark file obsolete.
* config/m68k/nm-sun3.h: Mark file obsolete.
* config/m68k/xm-sun3.h: Mark file obsolete.
* config/m68k/sun2os4.mh: Mark file obsolete.
* config/m68k/sun2os3.mh: Mark file obsolete.
* config/m68k/nm-sun2.h: Mark file obsolete.
* config/m68k/xm-sun2.h: Mark file obsolete.
* config/m68k/m68kv4.mh: Mark file obsolete.
* config/m68k/nm-sysv4.h: Mark file obsolete.
* config/m68k/xm-m68kv4.h: Mark file obsolete.
* config/m68k/m68klynx.mh: Mark file obsolete.
* config/m68k/nm-m68klynx.h: Mark file obsolete.
* config/m68k/dpx2.mh: Mark file obsolete.
* config/m68k/xm-dpx2.h: Mark file obsolete.
* config/m68k/nm-dpx2.h: Mark file obsolete.
* config/m68k/delta68.mh: Mark file obsolete.
* config/m68k/xm-delta68.h: Mark file obsolete.
* config/m68k/nm-delta68.h: Mark file obsolete.
* config/m68k/3b1.mh: Mark file obsolete.
* config/m68k/xm-3b1.h: Mark file obsolete.
* config/m68k/sun3os4.mt: Mark file obsolete.
* config/m68k/tm-sun3os4.h: Mark file obsolete.
* config/m68k/sun3os3.mt: Mark file obsolete.
* config/m68k/tm-sun3.h: Mark file obsolete.
* config/m68k/sun2os4.mt: Mark file obsolete.
* config/m68k/tm-sun2os4.h: Mark file obsolete.
* config/m68k/sun2os3.mt: Mark file obsolete.
* config/m68k/tm-sun2.h: Mark file obsolete.
* config/m68k/m68kv4.mt: Mark file obsolete.
* config/m68k/tm-m68kv4.h: Mark file obsolete.
* config/m68k/m68klynx.mt: Mark file obsolete.
* config/m68k/tm-m68klynx.h: Mark file obsolete.
* config/m68k/dpx2.mt: Mark file obsolete.
* config/m68k/tm-dpx2.h: Mark file obsolete.
* config/m68k/delta68.mt: Mark file obsolete.
* config/m68k/tm-delta68.h: Mark file obsolete.
* config/m68k/3b1.mt: Mark file obsolete.
* config/m68k/tm-3b1.h: Mark file obsolete.
2003-12-01 22:53:42 +08:00
|
|
|
|
2003-09-11 22:00:55 +08:00
|
|
|
* REMOVED configurations and files
|
|
|
|
|
|
|
|
|
|
SGI Irix-4.x mips-sgi-irix4 or iris4
|
|
|
|
|
SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
|
2003-10-06 Andrew Cagney <cagney@redhat.com>
* NEWS: Mention that z8k-zilog-none, z8ksim, mn10200-*-*,
h8500hms, hppa*-*-bsd*, hppa*-*-osf*, hppa*-*-pro*,
mips*-*-mach3*, i[3456]86-sequent-sysv4*, i[3456]86-sequent-sysv*,
i[3456]86-sequent-bsd*, sparclet-*-*, sparclite-fujitsu-none, and
sparclite were removed.
* configure.host, configure.tgt: Remove corresponding tuples.
2003-10-07 03:47:21 +08:00
|
|
|
Z8000 simulator z8k-zilog-none or z8ksim
|
|
|
|
|
Matsushita MN10200 w/simulator mn10200-*-*
|
|
|
|
|
H8/500 simulator h8500-hitachi-hms or h8500hms
|
|
|
|
|
HP/PA running BSD hppa*-*-bsd*
|
|
|
|
|
HP/PA running OSF/1 hppa*-*-osf*
|
|
|
|
|
HP/PA Pro target hppa*-*-pro*
|
|
|
|
|
PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
|
2004-02-23 00:56:34 +08:00
|
|
|
386BSD i[3456]86-*-bsd*
|
2003-10-06 Andrew Cagney <cagney@redhat.com>
* NEWS: Mention that z8k-zilog-none, z8ksim, mn10200-*-*,
h8500hms, hppa*-*-bsd*, hppa*-*-osf*, hppa*-*-pro*,
mips*-*-mach3*, i[3456]86-sequent-sysv4*, i[3456]86-sequent-sysv*,
i[3456]86-sequent-bsd*, sparclet-*-*, sparclite-fujitsu-none, and
sparclite were removed.
* configure.host, configure.tgt: Remove corresponding tuples.
2003-10-07 03:47:21 +08:00
|
|
|
Sequent family i[3456]86-sequent-sysv4*
|
|
|
|
|
i[3456]86-sequent-sysv*
|
|
|
|
|
i[3456]86-sequent-bsd*
|
2004-01-03 20:21:09 +08:00
|
|
|
SPARC running LynxOS sparc-*-lynxos*
|
|
|
|
|
SPARC running SunOS 4 sparc-*-sunos4*
|
2003-10-06 Andrew Cagney <cagney@redhat.com>
* NEWS: Mention that z8k-zilog-none, z8ksim, mn10200-*-*,
h8500hms, hppa*-*-bsd*, hppa*-*-osf*, hppa*-*-pro*,
mips*-*-mach3*, i[3456]86-sequent-sysv4*, i[3456]86-sequent-sysv*,
i[3456]86-sequent-bsd*, sparclet-*-*, sparclite-fujitsu-none, and
sparclite were removed.
* configure.host, configure.tgt: Remove corresponding tuples.
2003-10-07 03:47:21 +08:00
|
|
|
Tsqware Sparclet sparclet-*-*
|
|
|
|
|
Fujitsu SPARClite sparclite-fujitsu-none or sparclite
|
2003-09-11 22:00:55 +08:00
|
|
|
|
2003-07-03 04:51:35 +08:00
|
|
|
*** Changes in GDB 6.0:
|
|
|
|
|
|
2003-09-30 04:17:00 +08:00
|
|
|
* Objective-C
|
|
|
|
|
|
|
|
|
|
Support for debugging the Objective-C programming language has been
|
|
|
|
|
integrated into GDB.
|
|
|
|
|
|
2003-09-26 02:23:56 +08:00
|
|
|
* New backtrace mechanism (includes DWARF 2 Call Frame Information).
|
|
|
|
|
|
|
|
|
|
DWARF 2's Call Frame Information makes available compiler generated
|
|
|
|
|
information that more exactly describes the program's run-time stack.
|
|
|
|
|
By using this information, GDB is able to provide more robust stack
|
|
|
|
|
backtraces.
|
|
|
|
|
|
|
|
|
|
The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
|
|
|
|
|
have been updated to use a new backtrace mechanism which includes
|
|
|
|
|
DWARF 2 CFI support.
|
|
|
|
|
|
|
|
|
|
* Hosted file I/O.
|
|
|
|
|
|
|
|
|
|
GDB's remote protocol has been extended to include support for hosted
|
|
|
|
|
file I/O (where the remote target uses GDB's file system). See GDB's
|
|
|
|
|
remote protocol documentation for details.
|
|
|
|
|
|
|
|
|
|
* All targets using the new architecture framework.
|
|
|
|
|
|
|
|
|
|
All of GDB's targets have been updated to use the new internal
|
|
|
|
|
architecture framework. The way is now open for future GDB releases
|
|
|
|
|
to include cross-architecture native debugging support (i386 on amd64,
|
|
|
|
|
ppc32 on ppc64).
|
|
|
|
|
|
|
|
|
|
* GNU/Linux's Thread Local Storage (TLS)
|
|
|
|
|
|
|
|
|
|
GDB now includes support for for the GNU/Linux implementation of
|
|
|
|
|
per-thread variables.
|
|
|
|
|
|
|
|
|
|
* GNU/Linux's Native POSIX Thread Library (NPTL)
|
|
|
|
|
|
|
|
|
|
GDB's thread code has been updated to work with either the new
|
|
|
|
|
GNU/Linux NPTL thread library or the older "LinuxThreads" library.
|
|
|
|
|
|
|
|
|
|
* Separate debug info.
|
|
|
|
|
|
|
|
|
|
GDB, in conjunction with BINUTILS, now supports a mechanism for
|
|
|
|
|
automatically loading debug information from a separate file. Instead
|
|
|
|
|
of shipping full debug and non-debug versions of system libraries,
|
|
|
|
|
system integrators can now instead ship just the stripped libraries
|
|
|
|
|
and optional debug files.
|
|
|
|
|
|
|
|
|
|
* DWARF 2 Location Expressions
|
|
|
|
|
|
|
|
|
|
DWARF 2 Location Expressions allow the compiler to more completely
|
|
|
|
|
describe the location of variables (even in optimized code) to the
|
|
|
|
|
debugger.
|
|
|
|
|
|
|
|
|
|
GDB now includes preliminary support for location expressions (support
|
|
|
|
|
for DW_OP_piece is still missing).
|
|
|
|
|
|
|
|
|
|
* Java
|
|
|
|
|
|
|
|
|
|
A number of long standing bugs that caused GDB to die while starting a
|
|
|
|
|
Java application have been fixed. GDB's Java support is now
|
|
|
|
|
considered "useable".
|
|
|
|
|
|
2003-08-25 05:21:11 +08:00
|
|
|
* GNU/Linux support for fork, vfork, and exec.
|
|
|
|
|
|
|
|
|
|
The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode"
|
|
|
|
|
commands are now implemented for GNU/Linux. They require a 2.5.x or later
|
|
|
|
|
kernel.
|
|
|
|
|
|
2003-06-29 00:19:07 +08:00
|
|
|
* GDB supports logging output to a file
|
|
|
|
|
|
|
|
|
|
There are two new commands, "set logging" and "show logging", which can be
|
|
|
|
|
used to capture GDB's output to a file.
|
2003-06-23 11:28:14 +08:00
|
|
|
|
2003-06-18 04:28:14 +08:00
|
|
|
* The meaning of "detach" has changed for gdbserver
|
|
|
|
|
|
|
|
|
|
The "detach" command will now resume the application, as documented. To
|
|
|
|
|
disconnect from gdbserver and leave it stopped, use the new "disconnect"
|
|
|
|
|
command.
|
|
|
|
|
|
2003-07-25 03:59:33 +08:00
|
|
|
* d10v, m68hc11 `regs' command deprecated
|
2003-02-03 02:53:22 +08:00
|
|
|
|
|
|
|
|
The `info registers' command has been updated so that it displays the
|
|
|
|
|
registers using a format identical to the old `regs' command.
|
|
|
|
|
|
2003-01-23 07:50:35 +08:00
|
|
|
* Profiling support
|
|
|
|
|
|
|
|
|
|
A new command, "maint set profile on/off", has been added. This command can
|
|
|
|
|
be used to enable or disable profiling while running GDB, to profile a
|
|
|
|
|
session or a set of commands. In addition there is a new configure switch,
|
|
|
|
|
"--enable-profiling", which will cause GDB to be compiled with profiling
|
|
|
|
|
data, for more informative profiling results.
|
|
|
|
|
|
2002-10-02 05:15:43 +08:00
|
|
|
* Default MI syntax changed to "mi2".
|
|
|
|
|
|
|
|
|
|
The default MI (machine interface) syntax, enabled by the command line
|
|
|
|
|
option "-i=mi", has been changed to "mi2". The previous MI syntax,
|
2003-02-05 15:58:40 +08:00
|
|
|
"mi1", can be enabled by specifying the option "-i=mi1".
|
2002-10-02 05:15:43 +08:00
|
|
|
|
|
|
|
|
Support for the original "mi0" syntax (included in GDB 5.0) has been
|
|
|
|
|
removed.
|
|
|
|
|
|
2002-10-24 07:54:33 +08:00
|
|
|
Fix for gdb/192: removed extraneous space when displaying frame level.
|
|
|
|
|
Fix for gdb/672: update changelist is now output in mi list format.
|
|
|
|
|
Fix for gdb/702: a -var-assign that updates the value now shows up
|
|
|
|
|
in a subsequent -var-update.
|
|
|
|
|
|
2003-08-19 02:20:19 +08:00
|
|
|
* New native configurations.
|
|
|
|
|
|
|
|
|
|
FreeBSD/amd64 x86_64-*-freebsd*
|
|
|
|
|
|
2003-05-13 13:40:34 +08:00
|
|
|
* Multi-arched targets.
|
|
|
|
|
|
2003-08-09 06:26:38 +08:00
|
|
|
HP/PA HPUX11 hppa*-*-hpux*
|
2003-10-10 15:13:11 +08:00
|
|
|
Renesas M32R/D w/simulator m32r-*-elf*
|
2003-05-13 13:40:34 +08:00
|
|
|
|
2003-01-02 Andrew Cagney <ac131313@redhat.com>
* valarith.c (value_binop): Delete obsolete code and comments.
* configure.host: Ditto.
* buildsym.h (make_blockvector): Ditto.
* buildsym.c (make_blockvector): Ditto.
* defs.h (enum language): Ditto.
(chill_demangle): Ditto.
* elfread.c (elf_symtab_read): Ditto.
* dwarfread.c (CHILL_PRODUCER): Ditto.
(set_cu_language): Ditto.
(handle_producer): Ditto.
* expprint.c (print_subexp): Ditto.
* gdbtypes.c (chill_varying_type): Ditto.
* gdbtypes.h (builtin_type_chill_bool): Ditto.
(builtin_type_chill_char, builtin_type_chill_long): Ditto.
(builtin_type_chill_ulong, builtin_type_chill_real): Ditto.
(chill_varying_type): Ditto.
* language.h (_LANG_chill): Ditto.
* language.c (binop_result_type, integral_type): Ditto.
(character_type, string_type, structured_type): Ditto.
(lang_bool_type, binop_type_check): Ditto.
* stabsread.h (os9k_stabs): Ditto.
* stabsread.c (os9k_type_vector, dbx_lookup_type): Ditto.
(define_symbol, read_type, read_struct_fields): Ditto.
(read_array_type, read_enum_type, read_huge_number): Ditto.
(read_range_type, start_stabs): Ditto.
* symfile.c (init_filename_language_table): Ditto.
(add_psymbol_with_dem_name_to_list): Ditto.
* symtab.c (symbol_init_language_specific): Ditto.
(symbol_init_demangled_name, symbol_demangled_name): Ditto.
* symtab.h (struct general_symbol_info): Ditto.
(SYMBOL_CHILL_DEMANGLED_NAME): Ditto.
* typeprint.c (typedef_print): Ditto.
* utils.c (fprintf_symbol_filtered): Ditto.
* valops.c (value_cast, search_struct_field, value_slice): Delete
obsolete code.
(varying_to_slice): Delete function.
* value.h (COERCE_VARYING_ARRAY): Delete obsolete macro contents.
(varying_to_slice): Delete declaration.
* MAINTAINERS: Update.
2003-01-02 22:27:27 +08:00
|
|
|
* OBSOLETE configurations and files
|
|
|
|
|
|
|
|
|
|
Configurations that have been declared obsolete in this release have
|
|
|
|
|
been commented out. Unless there is activity to revive these
|
|
|
|
|
configurations, the next release of GDB will have their sources
|
|
|
|
|
permanently REMOVED.
|
|
|
|
|
|
2003-02-05 07:22:25 +08:00
|
|
|
Z8000 simulator z8k-zilog-none or z8ksim
|
2003-02-05 06:49:19 +08:00
|
|
|
Matsushita MN10200 w/simulator mn10200-*-*
|
2003-02-05 06:04:08 +08:00
|
|
|
H8/500 simulator h8500-hitachi-hms or h8500hms
|
2003-03-27 23:23:17 +08:00
|
|
|
HP/PA running BSD hppa*-*-bsd*
|
|
|
|
|
HP/PA running OSF/1 hppa*-*-osf*
|
|
|
|
|
HP/PA Pro target hppa*-*-pro*
|
2003-04-10 00:10:06 +08:00
|
|
|
PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
|
2003-04-10 00:19:52 +08:00
|
|
|
Sequent family i[3456]86-sequent-sysv4*
|
|
|
|
|
i[3456]86-sequent-sysv*
|
|
|
|
|
i[3456]86-sequent-bsd*
|
2003-04-16 22:32:21 +08:00
|
|
|
Tsqware Sparclet sparclet-*-*
|
|
|
|
|
Fujitsu SPARClite sparclite-fujitsu-none or sparclite
|
2003-02-05 06:04:08 +08:00
|
|
|
|
2002-09-21 19:55:17 +08:00
|
|
|
* REMOVED configurations and files
|
|
|
|
|
|
|
|
|
|
V850EA ISA
|
2003-01-02 Andrew Cagney <ac131313@redhat.com>
* valarith.c (value_binop): Delete obsolete code and comments.
* configure.host: Ditto.
* buildsym.h (make_blockvector): Ditto.
* buildsym.c (make_blockvector): Ditto.
* defs.h (enum language): Ditto.
(chill_demangle): Ditto.
* elfread.c (elf_symtab_read): Ditto.
* dwarfread.c (CHILL_PRODUCER): Ditto.
(set_cu_language): Ditto.
(handle_producer): Ditto.
* expprint.c (print_subexp): Ditto.
* gdbtypes.c (chill_varying_type): Ditto.
* gdbtypes.h (builtin_type_chill_bool): Ditto.
(builtin_type_chill_char, builtin_type_chill_long): Ditto.
(builtin_type_chill_ulong, builtin_type_chill_real): Ditto.
(chill_varying_type): Ditto.
* language.h (_LANG_chill): Ditto.
* language.c (binop_result_type, integral_type): Ditto.
(character_type, string_type, structured_type): Ditto.
(lang_bool_type, binop_type_check): Ditto.
* stabsread.h (os9k_stabs): Ditto.
* stabsread.c (os9k_type_vector, dbx_lookup_type): Ditto.
(define_symbol, read_type, read_struct_fields): Ditto.
(read_array_type, read_enum_type, read_huge_number): Ditto.
(read_range_type, start_stabs): Ditto.
* symfile.c (init_filename_language_table): Ditto.
(add_psymbol_with_dem_name_to_list): Ditto.
* symtab.c (symbol_init_language_specific): Ditto.
(symbol_init_demangled_name, symbol_demangled_name): Ditto.
* symtab.h (struct general_symbol_info): Ditto.
(SYMBOL_CHILL_DEMANGLED_NAME): Ditto.
* typeprint.c (typedef_print): Ditto.
* utils.c (fprintf_symbol_filtered): Ditto.
* valops.c (value_cast, search_struct_field, value_slice): Delete
obsolete code.
(varying_to_slice): Delete function.
* value.h (COERCE_VARYING_ARRAY): Delete obsolete macro contents.
(varying_to_slice): Delete declaration.
* MAINTAINERS: Update.
2003-01-02 22:27:27 +08:00
|
|
|
Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
|
|
|
|
|
IBM AIX PS/2 i[3456]86-*-aix
|
|
|
|
|
i386 running Mach 3.0 i[3456]86-*-mach3*
|
|
|
|
|
i386 running Mach i[3456]86-*-mach*
|
|
|
|
|
i386 running OSF/1 i[3456]86-*osf1mk*
|
|
|
|
|
HP/Apollo 68k Family m68*-apollo*-sysv*,
|
|
|
|
|
m68*-apollo*-bsd*,
|
|
|
|
|
m68*-hp-bsd*, m68*-hp-hpux*
|
|
|
|
|
Argonaut Risc Chip (ARC) arc-*-*
|
|
|
|
|
Mitsubishi D30V d30v-*-*
|
|
|
|
|
Fujitsu FR30 fr30-*-elf*
|
|
|
|
|
OS/9000 i[34]86-*-os9k
|
|
|
|
|
I960 with MON960 i960-*-coff
|
2002-09-21 19:55:17 +08:00
|
|
|
|
2002-09-18 07:26:02 +08:00
|
|
|
* MIPS $fp behavior changed
|
|
|
|
|
|
|
|
|
|
The convenience variable $fp, for the MIPS, now consistently returns
|
|
|
|
|
the address of the current frame's base. Previously, depending on the
|
|
|
|
|
context, $fp could refer to either $sp or the current frame's base
|
|
|
|
|
address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
|
|
|
|
|
The GNU Source-Level Debugger''.
|
|
|
|
|
|
2002-09-05 20:13:08 +08:00
|
|
|
*** Changes in GDB 5.3:
|
2002-03-06 06:57:57 +08:00
|
|
|
|
2002-12-04 03:32:10 +08:00
|
|
|
* GNU/Linux shared library multi-threaded performance improved.
|
|
|
|
|
|
|
|
|
|
When debugging a multi-threaded application on GNU/Linux, GDB now uses
|
|
|
|
|
`/proc', in preference to `ptrace' for memory reads. This may result
|
|
|
|
|
in an improvement in the start-up time of multi-threaded, shared
|
|
|
|
|
library applications when run under GDB. One GDB user writes: ``loads
|
|
|
|
|
shared libs like mad''.
|
|
|
|
|
|
2002-08-04 23:12:09 +08:00
|
|
|
* ``gdbserver'' now supports multi-threaded applications on some targets
|
2002-06-14 03:46:19 +08:00
|
|
|
|
2002-08-04 23:12:09 +08:00
|
|
|
Support for debugging multi-threaded applications which use
|
|
|
|
|
the GNU/Linux LinuxThreads package has been added for
|
|
|
|
|
arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
|
|
|
|
|
powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
|
2002-06-14 03:46:19 +08:00
|
|
|
|
2002-05-18 02:02:20 +08:00
|
|
|
* GDB now supports C/C++ preprocessor macros.
|
|
|
|
|
|
|
|
|
|
GDB now expands preprocessor macro invocations in C/C++ expressions,
|
|
|
|
|
and provides various commands for showing macro definitions and how
|
|
|
|
|
they expand.
|
|
|
|
|
|
2002-08-04 08:02:49 +08:00
|
|
|
The new command `macro expand EXPRESSION' expands any macro
|
|
|
|
|
invocations in expression, and shows the result.
|
|
|
|
|
|
|
|
|
|
The new command `show macro MACRO-NAME' shows the definition of the
|
|
|
|
|
macro named MACRO-NAME, and where it was defined.
|
|
|
|
|
|
2002-05-18 02:02:20 +08:00
|
|
|
Most compilers don't include information about macros in the debugging
|
|
|
|
|
information by default. In GCC 3.1, for example, you need to compile
|
|
|
|
|
your program with the options `-gdwarf-2 -g3'. If the macro
|
|
|
|
|
information is present in the executable, GDB will read it.
|
|
|
|
|
|
2002-05-17 18:14:05 +08:00
|
|
|
* Multi-arched targets.
|
|
|
|
|
|
2002-05-27 09:13:12 +08:00
|
|
|
DEC Alpha (partial) alpha*-*-*
|
|
|
|
|
DEC VAX (partial) vax-*-*
|
2002-05-17 18:14:05 +08:00
|
|
|
NEC V850 v850-*-*
|
2002-05-27 09:13:12 +08:00
|
|
|
National Semiconductor NS32000 (partial) ns32k-*-*
|
2002-07-11 01:34:02 +08:00
|
|
|
Motorola 68000 (partial) m68k-*-*
|
|
|
|
|
Motorola MCORE mcore-*-*
|
2002-05-17 18:14:05 +08:00
|
|
|
|
2002-05-04 23:52:42 +08:00
|
|
|
* New targets.
|
2002-04-26 04:48:55 +08:00
|
|
|
|
2002-06-22 05:19:58 +08:00
|
|
|
Fujitsu FRV architecture added by Red Hat frv*-*-*
|
|
|
|
|
|
2002-04-26 04:48:55 +08:00
|
|
|
|
2002-04-25 10:44:05 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
Alpha NetBSD alpha*-*-netbsd*
|
2002-05-10 07:38:20 +08:00
|
|
|
SH NetBSD sh*-*-netbsdelf*
|
2002-05-21 23:58:41 +08:00
|
|
|
MIPS NetBSD mips*-*-netbsd*
|
2002-05-31 08:59:15 +08:00
|
|
|
UltraSPARC NetBSD sparc64-*-netbsd*
|
2002-04-25 10:44:05 +08:00
|
|
|
|
2002-05-04 23:52:42 +08:00
|
|
|
* OBSOLETE configurations and files
|
|
|
|
|
|
|
|
|
|
Configurations that have been declared obsolete in this release have
|
|
|
|
|
been commented out. Unless there is activity to revive these
|
|
|
|
|
configurations, the next release of GDB will have their sources
|
|
|
|
|
permanently REMOVED.
|
|
|
|
|
|
2002-07-14 08:28:46 +08:00
|
|
|
Mitsubishi D30V d30v-*-*
|
2002-07-16 23:19:19 +08:00
|
|
|
OS/9000 i[34]86-*-os9k
|
2002-08-16 06:51:40 +08:00
|
|
|
IBM AIX PS/2 i[3456]86-*-aix
|
2002-07-16 22:30:14 +08:00
|
|
|
Fujitsu FR30 fr30-*-elf*
|
2002-07-25 07:51:36 +08:00
|
|
|
Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
|
2002-08-06 22:12:47 +08:00
|
|
|
Argonaut Risc Chip (ARC) arc-*-*
|
* NEWS: Mention that the i[3456]-*mach3*, i[3456]-*-mach* and
i[3456]-*-osf1mk* configurations have been made obsolete.
* configure.host: Make i[3456]86-*-mach3*, i[3456]86-*mach* and
i[3456]86-*-osf1mk* hosts obsolete.
* confighure.tgt: Make i[3456]86-*-mach3*, i[3456]86-*-osf1mk*
targets obsolete.
* config/i386/i386mach.mh, config/i386/nm-i386mach.h,
config/i386/xm-i386mach.h, config/i386/i386m3.mh,
config/i386/i386m3.mt, config/i386/nm-m3.h,
config/i386/tm-i386m3.h, config/i386/xm-i386m3.h,
config/i386/i386mk.mh, config/i386/i386mk.mt,
config/i386/tm-i386mk.h, config/i386/xm-i386mk.h: Make files
obsolete.
* i386mach-nat.c, i386m3-nat.c: Make files obsolete.
* Makefile.in (ALLDEPFILES): Remove i386mach.c i386m3-nat.c
(i386mach-nat.o, i386m3-nat.o):Make targets obsolete.
2002-08-19 00:32:14 +08:00
|
|
|
i386 running Mach 3.0 i[3456]86-*-mach3*
|
|
|
|
|
i386 running Mach i[3456]86-*-mach*
|
|
|
|
|
i386 running OSF/1 i[3456]86-*osf1mk*
|
2002-08-21 08:57:44 +08:00
|
|
|
HP/Apollo 68k Family m68*-apollo*-sysv*,
|
|
|
|
|
m68*-apollo*-bsd*,
|
|
|
|
|
m68*-hp-bsd*, m68*-hp-hpux*
|
2002-08-23 05:52:45 +08:00
|
|
|
I960 with MON960 i960-*-coff
|
2002-07-14 08:28:46 +08:00
|
|
|
|
2002-08-01 Andrew Cagney <cagney@redhat.com>
* NEWS: Menion that CHILL has been made obsolete.
* gdbtypes.c (chill_varying_type): Make chill references obsolete.
* gdbserver/Makefile.in: Ditto.
* stabsread.c (read_range_type): Ditto.
* gdbtypes.h: Ditto.
* language.c (binop_type_check): Ditto.
(binop_result_type): Ditto.
(integral_type): Ditto.
(character_type): Ditto.
(string_type): Ditto.
(boolean_type): Ditto.
(structured_type): Ditto.
(lang_bool_type): Ditto.
(binop_type_check): Ditto.
* language.h (_LANG_chill): Ditto.
* dwarfread.c (set_cu_language): Ditto.
* dwarfread.c (CHILL_PRODUCER): Ditto.
* dwarfread.c (handle_producer): Ditto.
* expression.h (enum exp_opcode): Ditto.
* eval.c: Ditto for comments.
* typeprint.c (typedef_print) [_LANG_chill]: Ditto.
* expprint.c (print_subexp): Ditto.
(print_subexp): Ditto.
* valops.c (value_cast): Ditto.
(search_struct_field): Ditto.
* value.h (COERCE_VARYING_ARRAY): Ditto.
* symfile.c (init_filename_language_table): Ditto.
(add_psymbol_with_dem_name_to_list): Ditto.
* valarith.c (value_binop): Ditto.
(value_neg): Ditto.
* valops.c (value_slice): Ditto.
* symtab.h (union language_specific): Ditto.
(SYMBOL_INIT_LANGUAGE_SPECIFIC): Ditto.
(SYMBOL_DEMANGLED_NAME): Ditto.
(SYMBOL_CHILL_DEMANGLED_NAME): Ditto.
* defs.h (enum language): Ditto.
* symtab.c (got_symtab): Ditto.
* utils.c (fprintf_symbol_filtered): Ditto.
* ch-typeprint.c: Make file obsolete.
* ch-valprint.c: Make file obsolete.
* ch-lang.h: Make file obsolete.
* ch-exp.c: Make file obsolete.
* ch-lang.c: Make file obsolete.
* Makefile.in (FLAGS_TO_PASS): Do not pass CHILL or CHILLFLAGS or
CHILL_LIB.
(TARGET_FLAGS_TO_PASS): Ditto.
(CHILLFLAGS): Obsolete.
(CHILL): Obsolete.
(CHILL_FOR_TARGET): Obsolete.
(CHILL_LIB): Obsolete.
(SFILES): Remove ch-exp.c, ch-lang.c, ch-typeprint.c and
ch-valprint.c.
(HFILES_NO_SRCDIR): Remove ch-lang.h.
(COMMON_OBS): Remove ch-valprint.o, ch-typeprint.o, ch-exp.o and
ch-lang.o.
(ch-exp.o, ch-lang.o, ch-typeprint.o, ch-valprint.o): Delete
targets.
2002-08-01 Andrew Cagney <cagney@redhat.com>
* stabs.texinfo, gdb.texinfo, gdbint.texinfo: Obsolete references
to CHILL.
2002-08-01 Andrew Cagney <cagney@redhat.com>
* Makefile.in (TARGET_FLAGS_TO_PASS): Remove CHILLFLAGS, CHILL,
CHILL_FOR_TARGET and CHILL_LIB.
* configure.in (configdirs): Remove gdb.chill.
* configure: Regenerate.
* lib/gdb.exp: Obsolete references to chill.
* gdb.fortran/types.exp: Ditto.
* gdb.fortran/exprs.exp: Ditto.
2002-08-02 01:18:35 +08:00
|
|
|
* OBSOLETE languages
|
|
|
|
|
|
|
|
|
|
CHILL, a Pascal like language used by telecommunications companies.
|
|
|
|
|
|
2002-05-04 23:52:42 +08:00
|
|
|
* REMOVED configurations and files
|
|
|
|
|
|
|
|
|
|
AMD 29k family via UDI a29k-amd-udi, udi29k
|
|
|
|
|
A29K VxWorks a29k-*-vxworks
|
|
|
|
|
AMD 29000 embedded, using EBMON a29k-none-none
|
|
|
|
|
AMD 29000 embedded with COFF a29k-none-coff
|
|
|
|
|
AMD 29000 embedded with a.out a29k-none-aout
|
|
|
|
|
|
|
|
|
|
testsuite/gdb.hp/gdb.threads-hp/ directory
|
|
|
|
|
|
2002-04-13 06:31:23 +08:00
|
|
|
* New command "set max-user-call-depth <nnn>"
|
|
|
|
|
|
|
|
|
|
This command allows the user to limit the call depth of user-defined
|
|
|
|
|
commands. The default is 1024.
|
|
|
|
|
|
2002-04-01 01:53:00 +08:00
|
|
|
* Changes in FreeBSD/i386 native debugging.
|
|
|
|
|
|
|
|
|
|
Support for the "generate-core-file" has been added.
|
|
|
|
|
|
2002-03-29 09:32:20 +08:00
|
|
|
* New commands "dump", "append", and "restore".
|
|
|
|
|
|
|
|
|
|
These commands allow data to be copied from target memory
|
|
|
|
|
to a bfd-format or binary file (dump and append), and back
|
|
|
|
|
from a file into memory (restore).
|
2002-03-06 06:57:57 +08:00
|
|
|
|
2002-08-21 21:59:28 +08:00
|
|
|
* Improved "next/step" support on multi-processor Alpha Tru64.
|
|
|
|
|
|
|
|
|
|
The previous single-step mechanism could cause unpredictable problems,
|
|
|
|
|
including the random appearance of SIGSEGV or SIGTRAP signals. The use
|
|
|
|
|
of a software single-step mechanism prevents this.
|
|
|
|
|
|
2002-07-24 05:28:38 +08:00
|
|
|
*** Changes in GDB 5.2.1:
|
|
|
|
|
|
|
|
|
|
* New targets.
|
|
|
|
|
|
|
|
|
|
Atmel AVR avr*-*-*
|
|
|
|
|
|
|
|
|
|
* Bug fixes
|
|
|
|
|
|
|
|
|
|
gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
|
|
|
|
|
mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
|
|
|
|
|
Fix, by Joel Brobecker imported from mainline.
|
|
|
|
|
|
|
|
|
|
gdb/439: gdb/291: On some ELF object files, gdb was reporting:
|
|
|
|
|
dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
|
|
|
|
|
Fix, by Fred Fish, imported from mainline.
|
|
|
|
|
|
|
|
|
|
Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
|
|
|
|
|
Surprisingly enough, it works now.
|
|
|
|
|
By Michal Ludvig, imported from mainline.
|
|
|
|
|
|
|
|
|
|
i386 hardware watchpoint support:
|
|
|
|
|
avoid misses on second run for some targets.
|
|
|
|
|
By Pierre Muller, imported from mainline.
|
|
|
|
|
|
2002-03-06 06:57:57 +08:00
|
|
|
*** Changes in GDB 5.2:
|
2001-11-24 07:01:54 +08:00
|
|
|
|
2002-01-31 11:57:42 +08:00
|
|
|
* New command "set trust-readonly-sections on[off]".
|
|
|
|
|
|
|
|
|
|
This command is a hint that tells gdb that read-only sections
|
|
|
|
|
really are read-only (ie. that their contents will not change).
|
|
|
|
|
In this mode, gdb will go to the object file rather than the
|
|
|
|
|
target to read memory from read-only sections (such as ".text").
|
|
|
|
|
This can be a significant performance improvement on some
|
|
|
|
|
(notably embedded) targets.
|
|
|
|
|
|
2002-01-31 10:33:20 +08:00
|
|
|
* New command "generate-core-file" (or "gcore").
|
|
|
|
|
|
2002-02-11 01:34:05 +08:00
|
|
|
This new gdb command allows the user to drop a core file of the child
|
|
|
|
|
process state at any time. So far it's been implemented only for
|
|
|
|
|
GNU/Linux and Solaris, but should be relatively easily ported to other
|
|
|
|
|
hosts. Argument is core file name (defaults to core.<pid>).
|
2002-01-31 10:33:20 +08:00
|
|
|
|
2002-01-11 09:46:17 +08:00
|
|
|
* New command line option
|
|
|
|
|
|
|
|
|
|
GDB now accepts --pid or -p followed by a process id.
|
|
|
|
|
|
|
|
|
|
* Change in command line behavior -- corefiles vs. process ids.
|
|
|
|
|
|
|
|
|
|
There is a subtle behavior in the way in which GDB handles
|
|
|
|
|
command line arguments. The first non-flag argument is always
|
|
|
|
|
a program to debug, but the second non-flag argument may either
|
|
|
|
|
be a corefile or a process id. Previously, GDB would attempt to
|
|
|
|
|
open the second argument as a corefile, and if that failed, would
|
|
|
|
|
issue a superfluous error message and then attempt to attach it as
|
|
|
|
|
a process. Now, if the second argument begins with a non-digit,
|
|
|
|
|
it will be treated as a corefile. If it begins with a digit,
|
|
|
|
|
GDB will attempt to attach it as a process, and if no such process
|
|
|
|
|
is found, will then attempt to open it as a corefile.
|
|
|
|
|
|
2002-02-20 18:41:20 +08:00
|
|
|
* Changes in ARM configurations.
|
|
|
|
|
|
|
|
|
|
Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
|
|
|
|
|
configuration is fully multi-arch.
|
|
|
|
|
|
2001-11-24 07:01:54 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
2002-02-20 18:41:20 +08:00
|
|
|
ARM NetBSD arm*-*-netbsd*
|
2001-11-24 07:01:54 +08:00
|
|
|
x86 OpenBSD i[3456]86-*-openbsd*
|
2002-02-11 01:34:05 +08:00
|
|
|
AMD x86-64 running GNU/Linux x86_64-*-linux-*
|
2002-03-02 07:27:42 +08:00
|
|
|
Sparc64 running FreeBSD sparc64-*-freebsd*
|
2001-11-24 07:01:54 +08:00
|
|
|
|
2001-12-18 02:13:11 +08:00
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Sanyo XStormy16 xstormy16-elf
|
|
|
|
|
|
2002-01-06 23:02:01 +08:00
|
|
|
* OBSOLETE configurations and files
|
|
|
|
|
|
|
|
|
|
Configurations that have been declared obsolete in this release have
|
|
|
|
|
been commented out. Unless there is activity to revive these
|
|
|
|
|
configurations, the next release of GDB will have their sources
|
|
|
|
|
permanently REMOVED.
|
|
|
|
|
|
|
|
|
|
AMD 29k family via UDI a29k-amd-udi, udi29k
|
|
|
|
|
A29K VxWorks a29k-*-vxworks
|
|
|
|
|
AMD 29000 embedded, using EBMON a29k-none-none
|
|
|
|
|
AMD 29000 embedded with COFF a29k-none-coff
|
|
|
|
|
AMD 29000 embedded with a.out a29k-none-aout
|
|
|
|
|
|
2002-01-19 11:48:21 +08:00
|
|
|
testsuite/gdb.hp/gdb.threads-hp/ directory
|
2002-01-06 23:02:01 +08:00
|
|
|
|
2001-12-02 03:10:00 +08:00
|
|
|
* REMOVED configurations and files
|
|
|
|
|
|
|
|
|
|
TI TMS320C80 tic80-*-*
|
2001-12-02 03:34:37 +08:00
|
|
|
WDC 65816 w65-*-*
|
2001-12-02 05:01:58 +08:00
|
|
|
PowerPC Solaris powerpcle-*-solaris*
|
|
|
|
|
PowerPC Windows NT powerpcle-*-cygwin32
|
|
|
|
|
PowerPC Netware powerpc-*-netware*
|
2001-12-02 05:11:41 +08:00
|
|
|
Harris/CXUX m88k m88*-harris-cxux*
|
2001-12-02 06:02:03 +08:00
|
|
|
Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
|
|
|
|
|
ns32k-utek-sysv* ns32k-utek-*
|
2001-12-02 06:19:30 +08:00
|
|
|
SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
|
2001-12-02 06:34:11 +08:00
|
|
|
Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
|
2001-12-02 07:06:47 +08:00
|
|
|
Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
|
|
|
|
|
ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
|
2002-01-05 13:54:31 +08:00
|
|
|
Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
|
2001-12-02 03:10:00 +08:00
|
|
|
|
2001-11-27 11:09:44 +08:00
|
|
|
* Changes to command line processing
|
|
|
|
|
|
|
|
|
|
The new `--args' feature can be used to specify command-line arguments
|
|
|
|
|
for the inferior from gdb's command line.
|
|
|
|
|
|
2001-11-27 12:15:09 +08:00
|
|
|
* Changes to key bindings
|
|
|
|
|
|
|
|
|
|
There is a new `operate-and-get-next' function bound to `C-o'.
|
|
|
|
|
|
2002-01-24 16:05:31 +08:00
|
|
|
*** Changes in GDB 5.1.1
|
|
|
|
|
|
|
|
|
|
Fix compile problem on DJGPP.
|
|
|
|
|
|
|
|
|
|
Fix a problem with floating-point registers on the i386 being
|
|
|
|
|
corrupted.
|
|
|
|
|
|
|
|
|
|
Fix to stop GDB crashing on .debug_str debug info.
|
|
|
|
|
|
|
|
|
|
Numerous documentation fixes.
|
|
|
|
|
|
|
|
|
|
Numerous testsuite fixes.
|
|
|
|
|
|
2001-10-31 10:53:17 +08:00
|
|
|
*** Changes in GDB 5.1:
|
2000-06-01 07:27:44 +08:00
|
|
|
|
|
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
Alpha FreeBSD alpha*-*-freebsd*
|
|
|
|
|
x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
|
2002-02-11 01:34:05 +08:00
|
|
|
MIPS GNU/Linux mips*-*-linux*
|
2001-07-25 22:46:46 +08:00
|
|
|
MIPS SGI Irix 6.x mips*-sgi-irix6*
|
|
|
|
|
ia64 AIX ia64-*-aix*
|
2002-02-11 01:34:05 +08:00
|
|
|
s390 and s390x GNU/Linux {s390,s390x}-*-linux*
|
2000-06-01 07:27:44 +08:00
|
|
|
|
2000-06-08 14:35:40 +08:00
|
|
|
* New targets
|
|
|
|
|
|
2001-07-15 03:10:30 +08:00
|
|
|
Motorola 68HC11 and 68HC12 m68hc11-elf
|
2001-07-17 00:02:48 +08:00
|
|
|
CRIS cris-axis
|
2002-02-11 01:34:05 +08:00
|
|
|
UltraSparc running GNU/Linux sparc64-*-linux*
|
2001-07-15 03:10:30 +08:00
|
|
|
|
2001-03-23 08:58:48 +08:00
|
|
|
* OBSOLETE configurations and files
|
2000-06-08 14:35:40 +08:00
|
|
|
|
|
|
|
|
x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
|
2001-03-15 09:07:51 +08:00
|
|
|
Harris/CXUX m88k m88*-harris-cxux*
|
2001-04-03 04:57:26 +08:00
|
|
|
Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
|
|
|
|
|
ns32k-utek-sysv* ns32k-utek-*
|
2001-04-04 05:56:01 +08:00
|
|
|
TI TMS320C80 tic80-*-*
|
|
|
|
|
WDC 65816 w65-*-*
|
2001-04-05 22:49:29 +08:00
|
|
|
Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
|
2001-04-07 00:25:22 +08:00
|
|
|
PowerPC Solaris powerpcle-*-solaris*
|
|
|
|
|
PowerPC Windows NT powerpcle-*-cygwin32
|
|
|
|
|
PowerPC Netware powerpc-*-netware*
|
2001-04-12 06:39:07 +08:00
|
|
|
SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
|
2001-04-18 05:20:49 +08:00
|
|
|
Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
|
|
|
|
|
ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
|
2001-04-20 07:56:14 +08:00
|
|
|
Apple Macintosh (MPW) host N/A
|
2000-06-08 14:35:40 +08:00
|
|
|
|
2001-03-23 08:58:48 +08:00
|
|
|
stuff.c (Program to stuff files into a specially prepared space in kdb)
|
|
|
|
|
kdb-start.c (Main loop for the standalone kernel debugger)
|
|
|
|
|
|
2001-02-08 14:30:25 +08:00
|
|
|
Configurations that have been declared obsolete in this release have
|
|
|
|
|
been commented out. Unless there is activity to revive these
|
|
|
|
|
configurations, the next release of GDB will have their sources
|
|
|
|
|
permanently REMOVED.
|
|
|
|
|
|
2001-06-28 11:33:26 +08:00
|
|
|
* REMOVED configurations and files
|
2001-02-08 14:30:25 +08:00
|
|
|
|
|
|
|
|
Altos 3068 m68*-altos-*
|
|
|
|
|
Convex c1-*-*, c2-*-*
|
|
|
|
|
Pyramid pyramid-*-*
|
|
|
|
|
ARM RISCix arm-*-* (as host)
|
|
|
|
|
Tahoe tahoe-*-*
|
2001-06-28 11:33:26 +08:00
|
|
|
ser-ocd.c *-*-*
|
2000-06-08 14:35:40 +08:00
|
|
|
|
2001-09-11 02:13:17 +08:00
|
|
|
* GDB has been converted to ISO C.
|
2001-07-25 22:46:46 +08:00
|
|
|
|
2001-09-11 02:13:17 +08:00
|
|
|
GDB's source code has been converted to ISO C. In particular, the
|
2001-07-25 22:46:46 +08:00
|
|
|
sources are fully protoized, and rely on standard headers being
|
|
|
|
|
present.
|
|
|
|
|
|
2000-06-08 14:35:40 +08:00
|
|
|
* Other news:
|
|
|
|
|
|
2001-07-25 22:46:46 +08:00
|
|
|
* "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
|
|
|
|
|
|
|
|
|
|
* The MI enabled by default.
|
|
|
|
|
|
|
|
|
|
The new machine oriented interface (MI) introduced in GDB 5.0 has been
|
|
|
|
|
revised and enabled by default. Packages which use GDB as a debugging
|
|
|
|
|
engine behind a UI or another front end are encouraged to switch to
|
|
|
|
|
using the GDB/MI interface, instead of the old annotations interface
|
|
|
|
|
which is now deprecated.
|
|
|
|
|
|
|
|
|
|
* Support for debugging Pascal programs.
|
|
|
|
|
|
|
|
|
|
GDB now includes support for debugging Pascal programs. The following
|
|
|
|
|
main features are supported:
|
|
|
|
|
|
|
|
|
|
- Pascal-specific data types such as sets;
|
|
|
|
|
|
|
|
|
|
- automatic recognition of Pascal sources based on file-name
|
|
|
|
|
extension;
|
|
|
|
|
|
|
|
|
|
- Pascal-style display of data types, variables, and functions;
|
|
|
|
|
|
|
|
|
|
- a Pascal expression parser.
|
|
|
|
|
|
|
|
|
|
However, some important features are not yet supported.
|
|
|
|
|
|
|
|
|
|
- Pascal string operations are not supported at all;
|
|
|
|
|
|
|
|
|
|
- there are some problems with boolean types;
|
|
|
|
|
|
|
|
|
|
- Pascal type hexadecimal constants are not supported
|
|
|
|
|
because they conflict with the internal variables format;
|
|
|
|
|
|
|
|
|
|
- support for Pascal objects and classes is not full yet;
|
|
|
|
|
|
|
|
|
|
- unlike Pascal, GDB is case-sensitive for symbol names.
|
|
|
|
|
|
|
|
|
|
* Changes in completion.
|
|
|
|
|
|
|
|
|
|
Commands such as `shell', `run' and `set args', which pass arguments
|
|
|
|
|
to inferior programs, now complete on file names, similar to what
|
|
|
|
|
users expect at the shell prompt.
|
|
|
|
|
|
|
|
|
|
Commands which accept locations, such as `disassemble', `print',
|
|
|
|
|
`breakpoint', `until', etc. now complete on filenames as well as
|
|
|
|
|
program symbols. Thus, if you type "break foob TAB", and the source
|
|
|
|
|
files linked into the programs include `foobar.c', that file name will
|
|
|
|
|
be one of the candidates for completion. However, file names are not
|
|
|
|
|
considered for completion after you typed a colon that delimits a file
|
|
|
|
|
name from a name of a function in that file, as in "break foo.c:bar".
|
|
|
|
|
|
|
|
|
|
`set demangle-style' completes on available demangling styles.
|
|
|
|
|
|
|
|
|
|
* New platform-independent commands:
|
|
|
|
|
|
|
|
|
|
It is now possible to define a post-hook for a command as well as a
|
|
|
|
|
hook that runs before the command. For more details, see the
|
|
|
|
|
documentation of `hookpost' in the GDB manual.
|
|
|
|
|
|
|
|
|
|
* Changes in GNU/Linux native debugging.
|
|
|
|
|
|
2001-08-03 02:42:18 +08:00
|
|
|
Support for debugging multi-threaded programs has been completely
|
|
|
|
|
revised for all platforms except m68k and sparc. You can now debug as
|
|
|
|
|
many threads as your system allows you to have.
|
|
|
|
|
|
2001-07-25 22:46:46 +08:00
|
|
|
Attach/detach is supported for multi-threaded programs.
|
|
|
|
|
|
2001-08-03 02:42:18 +08:00
|
|
|
Support for SSE registers was added for x86. This doesn't work for
|
|
|
|
|
multi-threaded programs though.
|
2001-07-25 22:46:46 +08:00
|
|
|
|
|
|
|
|
* Changes in MIPS configurations.
|
2000-06-08 14:35:40 +08:00
|
|
|
|
|
|
|
|
Multi-arch support is enabled for all MIPS configurations.
|
|
|
|
|
|
2001-07-25 22:46:46 +08:00
|
|
|
GDB can now be built as native debugger on SGI Irix 6.x systems for
|
|
|
|
|
debugging n32 executables. (Debugging 64-bit executables is not yet
|
|
|
|
|
supported.)
|
|
|
|
|
|
|
|
|
|
* Unified support for hardware watchpoints in all x86 configurations.
|
|
|
|
|
|
|
|
|
|
Most (if not all) native x86 configurations support hardware-assisted
|
|
|
|
|
breakpoints and watchpoints in a unified manner. This support
|
|
|
|
|
implements debug register sharing between watchpoints, which allows to
|
|
|
|
|
put a virtually infinite number of watchpoints on the same address,
|
|
|
|
|
and also supports watching regions up to 16 bytes with several debug
|
|
|
|
|
registers.
|
|
|
|
|
|
|
|
|
|
The new maintenance command `maintenance show-debug-regs' toggles
|
|
|
|
|
debugging print-outs in functions that insert, remove, and test
|
|
|
|
|
watchpoints and hardware breakpoints.
|
|
|
|
|
|
|
|
|
|
* Changes in the DJGPP native configuration.
|
|
|
|
|
|
|
|
|
|
New command ``info dos sysinfo'' displays assorted information about
|
|
|
|
|
the CPU, OS, memory, and DPMI server.
|
|
|
|
|
|
|
|
|
|
New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
|
|
|
|
|
display information about segment descriptors stored in GDT, LDT, and
|
|
|
|
|
IDT.
|
|
|
|
|
|
|
|
|
|
New commands ``info dos pde'' and ``info dos pte'' display entries
|
|
|
|
|
from Page Directory and Page Tables (for now works with CWSDPMI only).
|
|
|
|
|
New command ``info dos address-pte'' displays the Page Table entry for
|
|
|
|
|
a given linear address.
|
|
|
|
|
|
|
|
|
|
GDB can now pass command lines longer than 126 characters to the
|
|
|
|
|
program being debugged (requires an update to the libdbg.a library
|
|
|
|
|
which is part of the DJGPP development kit).
|
|
|
|
|
|
|
|
|
|
DWARF2 debug info is now supported.
|
|
|
|
|
|
2001-07-29 16:03:36 +08:00
|
|
|
It is now possible to `step' and `next' through calls to `longjmp'.
|
|
|
|
|
|
2001-07-25 22:46:46 +08:00
|
|
|
* Changes in documentation.
|
|
|
|
|
|
|
|
|
|
All GDB documentation was converted to GFDL, the GNU Free
|
|
|
|
|
Documentation License.
|
|
|
|
|
|
|
|
|
|
Tracepoints-related commands are now fully documented in the GDB
|
|
|
|
|
manual.
|
|
|
|
|
|
|
|
|
|
TUI, the Text-mode User Interface, is now documented in the manual.
|
|
|
|
|
|
|
|
|
|
Tracepoints-related commands are now fully documented in the GDB
|
|
|
|
|
manual.
|
|
|
|
|
|
|
|
|
|
The "GDB Internals" manual now has an index. It also includes
|
|
|
|
|
documentation of `ui_out' functions, GDB coding standards, x86
|
|
|
|
|
hardware watchpoints, and memory region attributes.
|
|
|
|
|
|
2001-05-12 09:34:09 +08:00
|
|
|
* GDB's version number moved to ``version.in''
|
|
|
|
|
|
|
|
|
|
The Makefile variable VERSION has been replaced by the file
|
|
|
|
|
``version.in''. People creating GDB distributions should update the
|
|
|
|
|
contents of this file.
|
|
|
|
|
|
2000-10-24 13:22:11 +08:00
|
|
|
* gdba.el deleted
|
|
|
|
|
|
|
|
|
|
GUD support is now a standard part of the EMACS distribution.
|
2000-06-01 07:27:44 +08:00
|
|
|
|
2000-04-19 15:01:08 +08:00
|
|
|
*** Changes in GDB 5.0:
|
1999-04-27 02:34:20 +08:00
|
|
|
|
2000-04-13 00:51:27 +08:00
|
|
|
* Improved support for debugging FP programs on x86 targets
|
|
|
|
|
|
|
|
|
|
Unified and much-improved support for debugging floating-point
|
|
|
|
|
programs on all x86 targets. In particular, ``info float'' now
|
|
|
|
|
displays the FP registers in the same format on all x86 targets, with
|
|
|
|
|
greater level of detail.
|
|
|
|
|
|
|
|
|
|
* Improvements and bugfixes in hardware-assisted watchpoints
|
|
|
|
|
|
|
|
|
|
It is now possible to watch array elements, struct members, and
|
|
|
|
|
bitfields with hardware-assisted watchpoints. Data-read watchpoints
|
|
|
|
|
on x86 targets no longer erroneously trigger when the address is
|
|
|
|
|
written.
|
|
|
|
|
|
|
|
|
|
* Improvements in the native DJGPP version of GDB
|
|
|
|
|
|
|
|
|
|
The distribution now includes all the scripts and auxiliary files
|
|
|
|
|
necessary to build the native DJGPP version on MS-DOS/MS-Windows
|
|
|
|
|
machines ``out of the box''.
|
|
|
|
|
|
|
|
|
|
The DJGPP version can now debug programs that use signals. It is
|
|
|
|
|
possible to catch signals that happened in the debuggee, deliver
|
|
|
|
|
signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
|
|
|
|
|
would kill the program being debugged.) Programs that hook hardware
|
|
|
|
|
interrupts (keyboard, timer, etc.) can also be debugged.
|
|
|
|
|
|
|
|
|
|
It is now possible to debug DJGPP programs that redirect their
|
|
|
|
|
standard handles or switch them to raw (as opposed to cooked) mode, or
|
|
|
|
|
even close them. The command ``run < foo > bar'' works as expected,
|
|
|
|
|
and ``info terminal'' reports useful information about the debuggee's
|
|
|
|
|
terminal, including raw/cooked mode, redirection, etc.
|
|
|
|
|
|
|
|
|
|
The DJGPP version now uses termios functions for console I/O, which
|
|
|
|
|
enables debugging graphics programs. Interrupting GDB with Ctrl-C
|
|
|
|
|
also works.
|
|
|
|
|
|
|
|
|
|
DOS-style file names with drive letters are now fully supported by
|
|
|
|
|
GDB.
|
|
|
|
|
|
|
|
|
|
It is now possible to debug DJGPP programs that switch their working
|
|
|
|
|
directory. It is also possible to rerun the debuggee any number of
|
|
|
|
|
times without restarting GDB; thus, you can use the same setup,
|
|
|
|
|
breakpoints, etc. for many debugging sessions.
|
|
|
|
|
|
1999-12-23 05:45:38 +08:00
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
ARM GNU/Linux arm*-*-linux*
|
2000-04-04 06:10:45 +08:00
|
|
|
PowerPC GNU/Linux powerpc-*-linux*
|
1999-12-23 05:45:38 +08:00
|
|
|
|
1999-04-27 02:34:20 +08:00
|
|
|
* New targets
|
|
|
|
|
|
1999-08-10 05:36:23 +08:00
|
|
|
Motorola MCore mcore-*-*
|
1999-07-20 07:30:11 +08:00
|
|
|
x86 VxWorks i[3456]86-*-vxworks*
|
|
|
|
|
PowerPC VxWorks powerpc-*-vxworks*
|
1999-04-27 02:34:20 +08:00
|
|
|
TI TMS320C80 tic80-*-*
|
|
|
|
|
|
1999-06-29 00:06:02 +08:00
|
|
|
* OBSOLETE configurations
|
|
|
|
|
|
|
|
|
|
Altos 3068 m68*-altos-*
|
|
|
|
|
Convex c1-*-*, c2-*-*
|
1999-07-08 01:31:57 +08:00
|
|
|
Pyramid pyramid-*-*
|
1999-12-23 05:45:38 +08:00
|
|
|
ARM RISCix arm-*-* (as host)
|
1999-08-31 09:14:27 +08:00
|
|
|
Tahoe tahoe-*-*
|
1999-04-27 02:34:20 +08:00
|
|
|
|
2000-04-19 15:01:08 +08:00
|
|
|
Configurations that have been declared obsolete will be commented out,
|
|
|
|
|
but the code will be left in place. If there is no activity to revive
|
|
|
|
|
these configurations before the next release of GDB, the sources will
|
|
|
|
|
be permanently REMOVED.
|
|
|
|
|
|
2000-05-02 00:12:10 +08:00
|
|
|
* Gould support removed
|
|
|
|
|
|
|
|
|
|
Support for the Gould PowerNode and NP1 has been removed.
|
|
|
|
|
|
2000-04-10 18:52:19 +08:00
|
|
|
* New features for SVR4
|
|
|
|
|
|
|
|
|
|
On SVR4 native platforms (such as Solaris), if you attach to a process
|
|
|
|
|
without first loading a symbol file, GDB will now attempt to locate and
|
|
|
|
|
load symbols from the running process's executable file.
|
|
|
|
|
|
|
|
|
|
* Many C++ enhancements
|
|
|
|
|
|
|
|
|
|
C++ support has been greatly improved. Overload resolution now works properly
|
|
|
|
|
in almost all cases. RTTI support is on the way.
|
|
|
|
|
|
1999-07-20 07:30:11 +08:00
|
|
|
* Remote targets can connect to a sub-program
|
|
|
|
|
|
|
|
|
|
A popen(3) style serial-device has been added. This device starts a
|
|
|
|
|
sub-process (such as a stand-alone simulator) and then communicates
|
|
|
|
|
with that. The sub-program to run is specified using the syntax
|
|
|
|
|
``|<program> <args>'' vis:
|
|
|
|
|
|
|
|
|
|
(gdb) set remotedebug 1
|
|
|
|
|
(gdb) target extended-remote |mn10300-elf-sim program-args
|
|
|
|
|
|
1999-07-12 19:15:22 +08:00
|
|
|
* MIPS 64 remote protocol
|
|
|
|
|
|
|
|
|
|
A long standing bug in the mips64 remote protocol where by GDB
|
2024-10-06 13:59:48 +08:00
|
|
|
expected certain 32 bit registers (ex SR) to be transferred as 32
|
1999-07-12 19:15:22 +08:00
|
|
|
instead of 64 bits has been fixed.
|
|
|
|
|
|
|
|
|
|
The command ``set remote-mips64-transfers-32bit-regs on'' has been
|
|
|
|
|
added to provide backward compatibility with older versions of GDB.
|
|
|
|
|
|
1999-08-10 05:36:23 +08:00
|
|
|
* ``set remotebinarydownload'' replaced by ``set remote X-packet''
|
|
|
|
|
|
|
|
|
|
The command ``set remotebinarydownload'' command has been replaced by
|
|
|
|
|
``set remote X-packet''. Other commands in ``set remote'' family
|
|
|
|
|
include ``set remote P-packet''.
|
|
|
|
|
|
1999-11-09 09:23:30 +08:00
|
|
|
* Breakpoint commands accept ranges.
|
|
|
|
|
|
|
|
|
|
The breakpoint commands ``enable'', ``disable'', and ``delete'' now
|
|
|
|
|
accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
|
|
|
|
|
``tracepoint passcount'' also accepts a range of tracepoints.
|
|
|
|
|
|
2000-04-03 21:24:08 +08:00
|
|
|
* ``apropos'' command added.
|
|
|
|
|
|
|
|
|
|
The ``apropos'' command searches through command names and
|
|
|
|
|
documentation strings, printing out matches, making it much easier to
|
|
|
|
|
try to find a command that does what you are looking for.
|
|
|
|
|
|
2000-04-10 18:52:19 +08:00
|
|
|
* New MI interface
|
|
|
|
|
|
|
|
|
|
A new machine oriented interface (MI) has been added to GDB. This
|
|
|
|
|
interface is designed for debug environments running GDB as a separate
|
2000-04-23 16:15:49 +08:00
|
|
|
process. This is part of the long term libGDB project. See the
|
|
|
|
|
"GDB/MI" chapter of the GDB manual for further information. It can be
|
|
|
|
|
enabled by configuring with:
|
2000-04-10 18:52:19 +08:00
|
|
|
|
|
|
|
|
.../configure --enable-gdbmi
|
|
|
|
|
|
1999-04-16 09:35:26 +08:00
|
|
|
*** Changes in GDB-4.18:
|
|
|
|
|
|
|
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
HP-UX 10.20 hppa*-*-hpux10.20
|
|
|
|
|
HP-UX 11.x hppa*-*-hpux11.0*
|
2002-02-11 01:34:05 +08:00
|
|
|
M68K GNU/Linux m68*-*-linux*
|
1999-04-16 09:35:26 +08:00
|
|
|
|
|
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Fujitsu FR30 fr30-*-elf*
|
|
|
|
|
Intel StrongARM strongarm-*-*
|
|
|
|
|
Mitsubishi D30V d30v-*-*
|
|
|
|
|
|
|
|
|
|
* OBSOLETE configurations
|
|
|
|
|
|
|
|
|
|
Gould PowerNode, NP1 np1-*-*, pn-*-*
|
|
|
|
|
|
|
|
|
|
Configurations that have been declared obsolete will be commented out,
|
|
|
|
|
but the code will be left in place. If there is no activity to revive
|
|
|
|
|
these configurations before the next release of GDB, the sources will
|
|
|
|
|
be permanently REMOVED.
|
|
|
|
|
|
|
|
|
|
* ANSI/ISO C
|
|
|
|
|
|
|
|
|
|
As a compatibility experiment, GDB's source files buildsym.h and
|
|
|
|
|
buildsym.c have been converted to pure standard C, no longer
|
|
|
|
|
containing any K&R compatibility code. We believe that all systems in
|
|
|
|
|
use today either come with a standard C compiler, or have a GCC port
|
|
|
|
|
available. If this is not true, please report the affected
|
|
|
|
|
configuration to bug-gdb@gnu.org immediately. See the README file for
|
|
|
|
|
information about getting a standard C compiler if you don't have one
|
|
|
|
|
already.
|
|
|
|
|
|
|
|
|
|
* Readline 2.2
|
|
|
|
|
|
|
|
|
|
GDB now uses readline 2.2.
|
|
|
|
|
|
|
|
|
|
* set extension-language
|
|
|
|
|
|
|
|
|
|
You can now control the mapping between filename extensions and source
|
|
|
|
|
languages by using the `set extension-language' command. For instance,
|
|
|
|
|
you can ask GDB to treat .c files as C++ by saying
|
|
|
|
|
set extension-language .c c++
|
|
|
|
|
The command `info extensions' lists all of the recognized extensions
|
|
|
|
|
and their associated languages.
|
|
|
|
|
|
|
|
|
|
* Setting processor type for PowerPC and RS/6000
|
|
|
|
|
|
|
|
|
|
When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
|
|
|
|
|
you can use the `set processor' command to specify what variant of the
|
|
|
|
|
PowerPC family you are debugging. The command
|
|
|
|
|
|
|
|
|
|
set processor NAME
|
|
|
|
|
|
|
|
|
|
sets the PowerPC/RS6000 variant to NAME. GDB knows about the
|
|
|
|
|
following PowerPC and RS6000 variants:
|
|
|
|
|
|
|
|
|
|
ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
|
|
|
|
|
rs6000 IBM RS6000 ("POWER") architecture, user-level view
|
|
|
|
|
403 IBM PowerPC 403
|
|
|
|
|
403GC IBM PowerPC 403GC
|
|
|
|
|
505 Motorola PowerPC 505
|
|
|
|
|
860 Motorola PowerPC 860 or 850
|
|
|
|
|
601 Motorola PowerPC 601
|
|
|
|
|
602 Motorola PowerPC 602
|
|
|
|
|
603 Motorola/IBM PowerPC 603 or 603e
|
|
|
|
|
604 Motorola PowerPC 604 or 604e
|
|
|
|
|
750 Motorola/IBM PowerPC 750 or 750
|
|
|
|
|
|
|
|
|
|
At the moment, this command just tells GDB what to name the
|
|
|
|
|
special-purpose processor registers. Since almost all the affected
|
|
|
|
|
registers are inaccessible to user-level programs, this command is
|
|
|
|
|
only useful for remote debugging in its present form.
|
|
|
|
|
|
|
|
|
|
* HP-UX support
|
|
|
|
|
|
|
|
|
|
Thanks to a major code donation from Hewlett-Packard, GDB now has much
|
|
|
|
|
more extensive support for HP-UX. Added features include shared
|
|
|
|
|
library support, kernel threads and hardware watchpoints for 11.00,
|
|
|
|
|
support for HP's ANSI C and C++ compilers, and a compatibility mode
|
|
|
|
|
for xdb and dbx commands.
|
|
|
|
|
|
|
|
|
|
* Catchpoints
|
|
|
|
|
|
|
|
|
|
HP's donation includes the new concept of catchpoints, which is a
|
|
|
|
|
generalization of the old catch command. On HP-UX, it is now possible
|
|
|
|
|
to catch exec, fork, and vfork, as well as library loading.
|
|
|
|
|
|
|
|
|
|
This means that the existing catch command has changed; its first
|
|
|
|
|
argument now specifies the type of catch to be set up. See the
|
|
|
|
|
output of "help catch" for a list of catchpoint types.
|
|
|
|
|
|
|
|
|
|
* Debugging across forks
|
|
|
|
|
|
|
|
|
|
On HP-UX, you can choose which process to debug when a fork() happens
|
|
|
|
|
in the inferior.
|
|
|
|
|
|
|
|
|
|
* TUI
|
|
|
|
|
|
|
|
|
|
HP has donated a curses-based terminal user interface (TUI). To get
|
|
|
|
|
it, build with --enable-tui. Although this can be enabled for any
|
|
|
|
|
configuration, at present it only works for native HP debugging.
|
|
|
|
|
|
|
|
|
|
* GDB remote protocol additions
|
|
|
|
|
|
|
|
|
|
A new protocol packet 'X' that writes binary data is now available.
|
|
|
|
|
Default behavior is to try 'X', then drop back to 'M' if the stub
|
|
|
|
|
fails to respond. The settable variable `remotebinarydownload'
|
|
|
|
|
allows explicit control over the use of 'X'.
|
|
|
|
|
|
|
|
|
|
For 64-bit targets, the memory packets ('M' and 'm') can now contain a
|
|
|
|
|
full 64-bit address. The command
|
|
|
|
|
|
|
|
|
|
set remoteaddresssize 32
|
|
|
|
|
|
|
|
|
|
can be used to revert to the old behaviour. For existing remote stubs
|
|
|
|
|
the change should not be noticed, as the additional address information
|
|
|
|
|
will be discarded.
|
|
|
|
|
|
|
|
|
|
In order to assist in debugging stubs, you may use the maintenance
|
|
|
|
|
command `packet' to send any text string to the stub. For instance,
|
|
|
|
|
|
|
|
|
|
maint packet heythere
|
|
|
|
|
|
|
|
|
|
sends the packet "$heythere#<checksum>". Note that it is very easy to
|
|
|
|
|
disrupt a debugging session by sending the wrong packet at the wrong
|
|
|
|
|
time.
|
|
|
|
|
|
|
|
|
|
The compare-sections command allows you to compare section data on the
|
|
|
|
|
target to what is in the executable file without uploading or
|
|
|
|
|
downloading, by comparing CRC checksums.
|
|
|
|
|
|
|
|
|
|
* Tracing can collect general expressions
|
|
|
|
|
|
|
|
|
|
You may now collect general expressions at tracepoints. This requires
|
|
|
|
|
further additions to the target-side stub; see tracepoint.c and
|
|
|
|
|
doc/agentexpr.texi for further details.
|
|
|
|
|
|
|
|
|
|
* mask-address variable for Mips
|
|
|
|
|
|
|
|
|
|
For Mips targets, you may control the zeroing of the upper 32 bits of
|
|
|
|
|
a 64-bit address by entering `set mask-address on'. This is mainly
|
|
|
|
|
of interest to users of embedded R4xxx and R5xxx processors.
|
|
|
|
|
|
|
|
|
|
* Higher serial baud rates
|
|
|
|
|
|
|
|
|
|
GDB's serial code now allows you to specify baud rates 57600, 115200,
|
|
|
|
|
230400, and 460800 baud. (Note that your host system may not be able
|
|
|
|
|
to achieve all of these rates.)
|
|
|
|
|
|
|
|
|
|
* i960 simulator
|
|
|
|
|
|
|
|
|
|
The i960 configuration now includes an initial implementation of a
|
|
|
|
|
builtin simulator, contributed by Jim Wilson.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.17:
|
|
|
|
|
|
|
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
Alpha GNU/Linux alpha*-*-linux*
|
|
|
|
|
Unixware 2.x i[3456]86-unixware2*
|
|
|
|
|
Irix 6.x mips*-sgi-irix6*
|
|
|
|
|
PowerPC GNU/Linux powerpc-*-linux*
|
|
|
|
|
PowerPC Solaris powerpcle-*-solaris*
|
|
|
|
|
Sparc GNU/Linux sparc-*-linux*
|
|
|
|
|
Motorola sysV68 R3V7.1 m68k-motorola-sysv
|
|
|
|
|
|
|
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
Argonaut Risc Chip (ARC) arc-*-*
|
|
|
|
|
Hitachi H8/300S h8300*-*-*
|
|
|
|
|
Matsushita MN10200 w/simulator mn10200-*-*
|
|
|
|
|
Matsushita MN10300 w/simulator mn10300-*-*
|
|
|
|
|
MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
|
|
|
|
|
MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
|
|
|
|
|
MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
|
|
|
|
|
Mitsubishi D10V w/simulator d10v-*-*
|
|
|
|
|
Mitsubishi M32R/D w/simulator m32r-*-elf*
|
|
|
|
|
Tsqware Sparclet sparclet-*-*
|
|
|
|
|
NEC V850 w/simulator v850-*-*
|
|
|
|
|
|
|
|
|
|
* New debugging protocols
|
|
|
|
|
|
|
|
|
|
ARM with RDI protocol arm*-*-*
|
|
|
|
|
M68K with dBUG monitor m68*-*-{aout,coff,elf}
|
|
|
|
|
DDB and LSI variants of PMON protocol mips*-*-*
|
|
|
|
|
PowerPC with DINK32 monitor powerpc{,le}-*-eabi
|
|
|
|
|
PowerPC with SDS protocol powerpc{,le}-*-eabi
|
|
|
|
|
Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
|
|
|
|
|
|
|
|
|
|
* DWARF 2
|
|
|
|
|
|
|
|
|
|
All configurations can now understand and use the DWARF 2 debugging
|
|
|
|
|
format. The choice is automatic, if the symbol file contains DWARF 2
|
|
|
|
|
information.
|
|
|
|
|
|
|
|
|
|
* Java frontend
|
|
|
|
|
|
|
|
|
|
GDB now includes basic Java language support. This support is
|
|
|
|
|
only useful with Java compilers that produce native machine code.
|
|
|
|
|
|
|
|
|
|
* solib-absolute-prefix and solib-search-path
|
|
|
|
|
|
|
|
|
|
For SunOS and SVR4 shared libraries, you may now set the prefix for
|
|
|
|
|
loading absolute shared library symbol files, and the search path for
|
|
|
|
|
locating non-absolute shared library symbol files.
|
|
|
|
|
|
|
|
|
|
* Live range splitting
|
|
|
|
|
|
|
|
|
|
GDB can now effectively debug code for which GCC has performed live
|
|
|
|
|
range splitting as part of its optimization. See gdb/doc/LRS for
|
|
|
|
|
more details on the expected format of the stabs information.
|
|
|
|
|
|
|
|
|
|
* Hurd support
|
|
|
|
|
|
|
|
|
|
GDB's support for the GNU Hurd, including thread debugging, has been
|
|
|
|
|
updated to work with current versions of the Hurd.
|
|
|
|
|
|
|
|
|
|
* ARM Thumb support
|
|
|
|
|
|
|
|
|
|
GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
|
|
|
|
|
instruction set. ARM GDB automatically detects when Thumb
|
|
|
|
|
instructions are in use, and adjusts disassembly and backtracing
|
|
|
|
|
accordingly.
|
|
|
|
|
|
|
|
|
|
* MIPS16 support
|
|
|
|
|
|
|
|
|
|
GDB's MIPS target configurations now handle the MIP16 16-bit
|
|
|
|
|
instruction set.
|
|
|
|
|
|
|
|
|
|
* Overlay support
|
|
|
|
|
|
|
|
|
|
GDB now includes support for overlays; if an executable has been
|
|
|
|
|
linked such that multiple sections are based at the same address, GDB
|
|
|
|
|
will decide which section to use for symbolic info. You can choose to
|
|
|
|
|
control the decision manually, using overlay commands, or implement
|
|
|
|
|
additional target-side support and use "overlay load-target" to bring
|
|
|
|
|
in the overlay mapping. Do "help overlay" for more detail.
|
|
|
|
|
|
|
|
|
|
* info symbol
|
|
|
|
|
|
|
|
|
|
The command "info symbol <address>" displays information about
|
|
|
|
|
the symbol at the specified address.
|
|
|
|
|
|
|
|
|
|
* Trace support
|
|
|
|
|
|
|
|
|
|
The standard remote protocol now includes an extension that allows
|
|
|
|
|
asynchronous collection and display of trace data. This requires
|
|
|
|
|
extensive support in the target-side debugging stub. Tracing mode
|
|
|
|
|
includes a new interaction mode in GDB and new commands: see the
|
|
|
|
|
file tracepoint.c for more details.
|
|
|
|
|
|
|
|
|
|
* MIPS simulator
|
|
|
|
|
|
|
|
|
|
Configurations for embedded MIPS now include a simulator contributed
|
|
|
|
|
by Cygnus Solutions. The simulator supports the instruction sets
|
|
|
|
|
of most MIPS variants.
|
|
|
|
|
|
|
|
|
|
* Sparc simulator
|
|
|
|
|
|
|
|
|
|
Sparc configurations may now include the ERC32 simulator contributed
|
|
|
|
|
by the European Space Agency. The simulator is not built into
|
|
|
|
|
Sparc targets by default; configure with --enable-sim to include it.
|
|
|
|
|
|
|
|
|
|
* set architecture
|
|
|
|
|
|
|
|
|
|
For target configurations that may include multiple variants of a
|
|
|
|
|
basic architecture (such as MIPS and SH), you may now set the
|
|
|
|
|
architecture explicitly. "set arch" sets, "info arch" lists
|
|
|
|
|
the possible architectures.
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.16:
|
|
|
|
|
|
|
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
Windows 95, x86 Windows NT i[345]86-*-cygwin32
|
|
|
|
|
M68K NetBSD m68k-*-netbsd*
|
|
|
|
|
PowerPC AIX 4.x powerpc-*-aix*
|
|
|
|
|
PowerPC MacOS powerpc-*-macos*
|
|
|
|
|
PowerPC Windows NT powerpcle-*-cygwin32
|
|
|
|
|
RS/6000 AIX 4.x rs6000-*-aix4*
|
|
|
|
|
|
|
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
ARM with RDP protocol arm-*-*
|
|
|
|
|
I960 with MON960 i960-*-coff
|
|
|
|
|
MIPS VxWorks mips*-*-vxworks*
|
|
|
|
|
MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
|
|
|
|
|
PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
|
|
|
|
|
Hitachi SH3 sh-*-*
|
|
|
|
|
Matra Sparclet sparclet-*-*
|
|
|
|
|
|
|
|
|
|
* PowerPC simulator
|
|
|
|
|
|
|
|
|
|
The powerpc-eabi configuration now includes the PSIM simulator,
|
|
|
|
|
contributed by Andrew Cagney, with assistance from Mike Meissner.
|
|
|
|
|
PSIM is a very elaborate model of the PowerPC, including not only
|
|
|
|
|
basic instruction set execution, but also details of execution unit
|
|
|
|
|
performance and I/O hardware. See sim/ppc/README for more details.
|
|
|
|
|
|
|
|
|
|
* Solaris 2.5
|
|
|
|
|
|
|
|
|
|
GDB now works with Solaris 2.5.
|
|
|
|
|
|
|
|
|
|
* Windows 95/NT native
|
|
|
|
|
|
|
|
|
|
GDB will now work as a native debugger on Windows 95 and Windows NT.
|
|
|
|
|
To build it from source, you must use the "gnu-win32" environment,
|
|
|
|
|
which uses a DLL to emulate enough of Unix to run the GNU tools.
|
|
|
|
|
Further information, binaries, and sources are available at
|
|
|
|
|
ftp.cygnus.com, under pub/gnu-win32.
|
|
|
|
|
|
|
|
|
|
* dont-repeat command
|
|
|
|
|
|
|
|
|
|
If a user-defined command includes the command `dont-repeat', then the
|
|
|
|
|
command will not be repeated if the user just types return. This is
|
|
|
|
|
useful if the command is time-consuming to run, so that accidental
|
|
|
|
|
extra keystrokes don't run the same command many times.
|
|
|
|
|
|
|
|
|
|
* Send break instead of ^C
|
|
|
|
|
|
|
|
|
|
The standard remote protocol now includes an option to send a break
|
|
|
|
|
rather than a ^C to the target in order to interrupt it. By default,
|
|
|
|
|
GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
|
|
|
|
|
|
|
|
|
|
* Remote protocol timeout
|
|
|
|
|
|
|
|
|
|
The standard remote protocol includes a new variable `remotetimeout'
|
|
|
|
|
that allows you to set the number of seconds before GDB gives up trying
|
|
|
|
|
to read from the target. The default value is 2.
|
|
|
|
|
|
|
|
|
|
* Automatic tracking of dynamic object loading (HPUX and Solaris only)
|
|
|
|
|
|
|
|
|
|
By default GDB will automatically keep track of objects as they are
|
|
|
|
|
loaded and unloaded by the dynamic linker. By using the command `set
|
|
|
|
|
stop-on-solib-events 1' you can arrange for GDB to stop the inferior
|
|
|
|
|
when shared library events occur, thus allowing you to set breakpoints
|
|
|
|
|
in shared libraries which are explicitly loaded by the inferior.
|
|
|
|
|
|
|
|
|
|
Note this feature does not work on hpux8. On hpux9 you must link
|
|
|
|
|
/usr/lib/end.o into your program. This feature should work
|
|
|
|
|
automatically on hpux10.
|
|
|
|
|
|
|
|
|
|
* Irix 5.x hardware watchpoint support
|
|
|
|
|
|
|
|
|
|
Irix 5 configurations now support the use of hardware watchpoints.
|
|
|
|
|
|
|
|
|
|
* Mips protocol "SYN garbage limit"
|
|
|
|
|
|
|
|
|
|
When debugging a Mips target using the `target mips' protocol, you
|
|
|
|
|
may set the number of characters that GDB will ignore by setting
|
|
|
|
|
the `syn-garbage-limit'. A value of -1 means that GDB will ignore
|
|
|
|
|
every character. The default value is 1050.
|
|
|
|
|
|
|
|
|
|
* Recording and replaying remote debug sessions
|
|
|
|
|
|
|
|
|
|
If you set `remotelogfile' to the name of a file, gdb will write to it
|
|
|
|
|
a recording of a remote debug session. This recording may then be
|
|
|
|
|
replayed back to gdb using "gdbreplay". See gdbserver/README for
|
|
|
|
|
details. This is useful when you have a problem with GDB while doing
|
|
|
|
|
remote debugging; you can make a recording of the session and send it
|
|
|
|
|
to someone else, who can then recreate the problem.
|
|
|
|
|
|
|
|
|
|
* Speedups for remote debugging
|
|
|
|
|
|
|
|
|
|
GDB includes speedups for downloading and stepping MIPS systems using
|
|
|
|
|
the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
|
|
|
|
|
and more efficient S-record downloading.
|
|
|
|
|
|
|
|
|
|
* Memory use reductions and statistics collection
|
|
|
|
|
|
|
|
|
|
GDB now uses less memory and reports statistics about memory usage.
|
|
|
|
|
Try the `maint print statistics' command, for example.
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.15:
|
|
|
|
|
|
|
|
|
|
* Psymtabs for XCOFF
|
|
|
|
|
|
|
|
|
|
The symbol reader for AIX GDB now uses partial symbol tables. This
|
|
|
|
|
can greatly improve startup time, especially for large executables.
|
|
|
|
|
|
|
|
|
|
* Remote targets use caching
|
|
|
|
|
|
|
|
|
|
Remote targets now use a data cache to speed up communication with the
|
|
|
|
|
remote side. The data cache could lead to incorrect results because
|
|
|
|
|
it doesn't know about volatile variables, thus making it impossible to
|
|
|
|
|
debug targets which use memory mapped I/O devices. `set remotecache
|
2020-03-06 22:22:23 +08:00
|
|
|
off' turns the data cache off.
|
1999-04-16 09:35:26 +08:00
|
|
|
|
|
|
|
|
* Remote targets may have threads
|
|
|
|
|
|
|
|
|
|
The standard remote protocol now includes support for multiple threads
|
|
|
|
|
in the target system, using new protocol commands 'H' and 'T'. See
|
|
|
|
|
gdb/remote.c for details.
|
|
|
|
|
|
|
|
|
|
* NetROM support
|
|
|
|
|
|
|
|
|
|
If GDB is configured with `--enable-netrom', then it will include
|
|
|
|
|
support for the NetROM ROM emulator from XLNT Designs. The NetROM
|
|
|
|
|
acts as though it is a bank of ROM on the target board, but you can
|
|
|
|
|
write into it over the network. GDB's support consists only of
|
|
|
|
|
support for fast loading into the emulated ROM; to debug, you must use
|
|
|
|
|
another protocol, such as standard remote protocol. The usual
|
|
|
|
|
sequence is something like
|
|
|
|
|
|
|
|
|
|
target nrom <netrom-hostname>
|
|
|
|
|
load <prog>
|
|
|
|
|
target remote <netrom-hostname>:1235
|
|
|
|
|
|
|
|
|
|
* Macintosh host
|
|
|
|
|
|
|
|
|
|
GDB now includes support for the Apple Macintosh, as a host only. It
|
|
|
|
|
may be run as either an MPW tool or as a standalone application, and
|
|
|
|
|
it can debug through the serial port. All the usual GDB commands are
|
|
|
|
|
available, but to the target command, you must supply "serial" as the
|
|
|
|
|
device type instead of "/dev/ttyXX". See mpw-README in the main
|
|
|
|
|
directory for more information on how to build. The MPW configuration
|
|
|
|
|
scripts */mpw-config.in support only a few targets, and only the
|
|
|
|
|
mips-idt-ecoff target has been tested.
|
|
|
|
|
|
|
|
|
|
* Autoconf
|
|
|
|
|
|
|
|
|
|
GDB configuration now uses autoconf. This is not user-visible,
|
|
|
|
|
but does simplify configuration and building.
|
|
|
|
|
|
|
|
|
|
* hpux10
|
|
|
|
|
|
|
|
|
|
GDB now supports hpux10.
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.14:
|
|
|
|
|
|
|
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
x86 FreeBSD i[345]86-*-freebsd
|
|
|
|
|
x86 NetBSD i[345]86-*-netbsd
|
|
|
|
|
NS32k NetBSD ns32k-*-netbsd
|
|
|
|
|
Sparc NetBSD sparc-*-netbsd
|
|
|
|
|
|
|
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
A29K VxWorks a29k-*-vxworks
|
|
|
|
|
HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
|
|
|
|
|
CPU32 EST-300 emulator m68*-*-est*
|
|
|
|
|
PowerPC ELF powerpc-*-elf
|
|
|
|
|
WDC 65816 w65-*-*
|
|
|
|
|
|
|
|
|
|
* Alpha OSF/1 support for procfs
|
|
|
|
|
|
|
|
|
|
GDB now supports procfs under OSF/1-2.x and higher, which makes it
|
|
|
|
|
possible to attach to running processes. As the mounting of the /proc
|
|
|
|
|
filesystem is optional on the Alpha, GDB automatically determines
|
|
|
|
|
the availability of /proc during startup. This can lead to problems
|
|
|
|
|
if /proc is unmounted after GDB has been started.
|
|
|
|
|
|
|
|
|
|
* Arguments to user-defined commands
|
|
|
|
|
|
|
|
|
|
User commands may accept up to 10 arguments separated by whitespace.
|
|
|
|
|
Arguments are accessed within the user command via $arg0..$arg9. A
|
|
|
|
|
trivial example:
|
|
|
|
|
define adder
|
|
|
|
|
print $arg0 + $arg1 + $arg2
|
|
|
|
|
|
|
|
|
|
To execute the command use:
|
|
|
|
|
adder 1 2 3
|
|
|
|
|
|
|
|
|
|
Defines the command "adder" which prints the sum of its three arguments.
|
|
|
|
|
Note the arguments are text substitutions, so they may reference variables,
|
|
|
|
|
use complex expressions, or even perform inferior function calls.
|
|
|
|
|
|
|
|
|
|
* New `if' and `while' commands
|
|
|
|
|
|
|
|
|
|
This makes it possible to write more sophisticated user-defined
|
|
|
|
|
commands. Both commands take a single argument, which is the
|
|
|
|
|
expression to evaluate, and must be followed by the commands to
|
|
|
|
|
execute, one per line, if the expression is nonzero, the list being
|
|
|
|
|
terminated by the word `end'. The `if' command list may include an
|
|
|
|
|
`else' word, which causes the following commands to be executed only
|
|
|
|
|
if the expression is zero.
|
|
|
|
|
|
|
|
|
|
* Fortran source language mode
|
|
|
|
|
|
|
|
|
|
GDB now includes partial support for Fortran 77. It will recognize
|
|
|
|
|
Fortran programs and can evaluate a subset of Fortran expressions, but
|
|
|
|
|
variables and functions may not be handled correctly. GDB will work
|
|
|
|
|
with G77, but does not yet know much about symbols emitted by other
|
|
|
|
|
Fortran compilers.
|
|
|
|
|
|
|
|
|
|
* Better HPUX support
|
|
|
|
|
|
|
|
|
|
Most debugging facilities now work on dynamic executables for HPPAs
|
|
|
|
|
running hpux9 or later. You can attach to running dynamically linked
|
|
|
|
|
processes, but by default the dynamic libraries will be read-only, so
|
|
|
|
|
for instance you won't be able to put breakpoints in them. To change
|
|
|
|
|
that behavior do the following before running the program:
|
|
|
|
|
|
|
|
|
|
adb -w a.out
|
|
|
|
|
__dld_flags?W 0x5
|
|
|
|
|
control-d
|
|
|
|
|
|
|
|
|
|
This will cause the libraries to be mapped private and read-write.
|
|
|
|
|
To revert to the normal behavior, do this:
|
|
|
|
|
|
|
|
|
|
adb -w a.out
|
|
|
|
|
__dld_flags?W 0x4
|
|
|
|
|
control-d
|
|
|
|
|
|
|
|
|
|
You cannot set breakpoints or examine data in the library until after
|
|
|
|
|
the library is loaded if the function/data symbols do not have
|
|
|
|
|
external linkage.
|
|
|
|
|
|
|
|
|
|
GDB can now also read debug symbols produced by the HP C compiler on
|
|
|
|
|
HPPAs (sorry, no C++, Fortran or 68k support).
|
|
|
|
|
|
|
|
|
|
* Target byte order now dynamically selectable
|
|
|
|
|
|
|
|
|
|
You can choose which byte order to use with a target system, via the
|
|
|
|
|
commands "set endian big" and "set endian little", and you can see the
|
|
|
|
|
current setting by using "show endian". You can also give the command
|
|
|
|
|
"set endian auto", in which case GDB will use the byte order
|
|
|
|
|
associated with the executable. Currently, only embedded MIPS
|
|
|
|
|
configurations support dynamic selection of target byte order.
|
|
|
|
|
|
|
|
|
|
* New DOS host serial code
|
|
|
|
|
|
|
|
|
|
This version uses DPMI interrupts to handle buffered I/O, so you
|
|
|
|
|
no longer need to run asynctsr when debugging boards connected to
|
|
|
|
|
a PC's serial port.
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.13:
|
|
|
|
|
|
|
|
|
|
* New "complete" command
|
|
|
|
|
|
|
|
|
|
This lists all the possible completions for the rest of the line, if it
|
|
|
|
|
were to be given as a command itself. This is intended for use by emacs.
|
|
|
|
|
|
|
|
|
|
* Trailing space optional in prompt
|
|
|
|
|
|
|
|
|
|
"set prompt" no longer adds a space for you after the prompt you set. This
|
|
|
|
|
allows you to set a prompt which ends in a space or one that does not.
|
|
|
|
|
|
|
|
|
|
* Breakpoint hit counts
|
|
|
|
|
|
|
|
|
|
"info break" now displays a count of the number of times the breakpoint
|
|
|
|
|
has been hit. This is especially useful in conjunction with "ignore"; you
|
|
|
|
|
can ignore a large number of breakpoint hits, look at the breakpoint info
|
|
|
|
|
to see how many times the breakpoint was hit, then run again, ignoring one
|
|
|
|
|
less than that number, and this will get you quickly to the last hit of
|
|
|
|
|
that breakpoint.
|
|
|
|
|
|
|
|
|
|
* Ability to stop printing at NULL character
|
|
|
|
|
|
|
|
|
|
"set print null-stop" will cause GDB to stop printing the characters of
|
|
|
|
|
an array when the first NULL is encountered. This is useful when large
|
|
|
|
|
arrays actually contain only short strings.
|
|
|
|
|
|
|
|
|
|
* Shared library breakpoints
|
|
|
|
|
|
|
|
|
|
In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
|
|
|
|
|
breakpoints in shared libraries before the executable is run.
|
|
|
|
|
|
|
|
|
|
* Hardware watchpoints
|
|
|
|
|
|
|
|
|
|
There is a new hardware breakpoint for the watch command for sparclite
|
|
|
|
|
targets. See gdb/sparclite/hw_breakpoint.note.
|
|
|
|
|
|
2002-02-11 01:34:05 +08:00
|
|
|
Hardware watchpoints are also now supported under GNU/Linux.
|
1999-04-16 09:35:26 +08:00
|
|
|
|
|
|
|
|
* Annotations
|
|
|
|
|
|
|
|
|
|
Annotations have been added. These are for use with graphical interfaces,
|
|
|
|
|
and are still experimental. Currently only gdba.el uses these.
|
|
|
|
|
|
|
|
|
|
* Improved Irix 5 support
|
|
|
|
|
|
|
|
|
|
GDB now works properly with Irix 5.2.
|
|
|
|
|
|
|
|
|
|
* Improved HPPA support
|
|
|
|
|
|
|
|
|
|
GDB now works properly with the latest GCC and GAS.
|
|
|
|
|
|
|
|
|
|
* New native configurations
|
|
|
|
|
|
|
|
|
|
Sequent PTX4 i[34]86-sequent-ptx4
|
|
|
|
|
HPPA running OSF/1 hppa*-*-osf*
|
|
|
|
|
Atari TT running SVR4 m68*-*-sysv4*
|
|
|
|
|
RS/6000 LynxOS rs6000-*-lynxos*
|
|
|
|
|
|
|
|
|
|
* New targets
|
|
|
|
|
|
|
|
|
|
OS/9000 i[34]86-*-os9k
|
|
|
|
|
MIPS R4000 mips64*{,el}-*-{ecoff,elf}
|
|
|
|
|
Sparc64 sparc64-*-*
|
|
|
|
|
|
|
|
|
|
* Hitachi SH7000 and E7000-PC ICE support
|
|
|
|
|
|
|
|
|
|
There is now support for communicating with the Hitachi E7000-PC ICE.
|
|
|
|
|
This is available automatically when GDB is configured for the SH.
|
|
|
|
|
|
|
|
|
|
* Fixes
|
|
|
|
|
|
|
|
|
|
As usual, a variety of small fixes and improvements, both generic
|
|
|
|
|
and configuration-specific. See the ChangeLog for more detail.
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.12:
|
|
|
|
|
|
|
|
|
|
* Irix 5 is now supported
|
|
|
|
|
|
|
|
|
|
* HPPA support
|
|
|
|
|
|
|
|
|
|
GDB-4.12 on the HPPA has a number of changes which make it unable
|
|
|
|
|
to debug the output from the currently released versions of GCC and
|
|
|
|
|
GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
|
|
|
|
|
of GCC and GAS, versions of these tools designed to work with GDB-4.12
|
|
|
|
|
can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.11:
|
|
|
|
|
|
|
|
|
|
* User visible changes:
|
|
|
|
|
|
|
|
|
|
* Remote Debugging
|
|
|
|
|
|
|
|
|
|
The "set remotedebug" option is now consistent between the mips remote
|
|
|
|
|
target, remote targets using the gdb-specific protocol, UDI (AMD's
|
|
|
|
|
debug protocol for the 29k) and the 88k bug monitor. It is now an
|
|
|
|
|
integer specifying a debug level (normally 0 or 1, but 2 means more
|
|
|
|
|
debugging info for the mips target).
|
|
|
|
|
|
|
|
|
|
* DEC Alpha native support
|
|
|
|
|
|
|
|
|
|
GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
|
|
|
|
|
debug info, but GDB works fairly well with the DEC compiler and should
|
|
|
|
|
work with a future GCC release. See the README file for a few
|
|
|
|
|
Alpha-specific notes.
|
|
|
|
|
|
|
|
|
|
* Preliminary thread implementation
|
|
|
|
|
|
|
|
|
|
GDB now has preliminary thread support for both SGI/Irix and LynxOS.
|
|
|
|
|
|
|
|
|
|
* LynxOS native and target support for 386
|
|
|
|
|
|
|
|
|
|
This release has been hosted on LynxOS 2.2, and also can be configured
|
|
|
|
|
to remotely debug programs running under LynxOS (see gdb/gdbserver/README
|
|
|
|
|
for details).
|
|
|
|
|
|
|
|
|
|
* Improvements in C++ mangling/demangling.
|
|
|
|
|
|
|
|
|
|
This release has much better g++ debugging, specifically in name
|
|
|
|
|
mangling/demangling, virtual function calls, print virtual table,
|
|
|
|
|
call methods, ...etc.
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.10:
|
|
|
|
|
|
|
|
|
|
* User visible changes:
|
|
|
|
|
|
|
|
|
|
Remote debugging using the GDB-specific (`target remote') protocol now
|
|
|
|
|
supports the `load' command. This is only useful if you have some
|
|
|
|
|
other way of getting the stub to the target system, and you can put it
|
|
|
|
|
somewhere in memory where it won't get clobbered by the download.
|
|
|
|
|
|
|
|
|
|
Filename completion now works.
|
|
|
|
|
|
|
|
|
|
When run under emacs mode, the "info line" command now causes the
|
|
|
|
|
arrow to point to the line specified. Also, "info line" prints
|
|
|
|
|
addresses in symbolic form (as well as hex).
|
|
|
|
|
|
|
|
|
|
All vxworks based targets now support a user settable option, called
|
|
|
|
|
vxworks-timeout. This option represents the number of seconds gdb
|
|
|
|
|
should wait for responses to rpc's. You might want to use this if
|
|
|
|
|
your vxworks target is, perhaps, a slow software simulator or happens
|
|
|
|
|
to be on the far side of a thin network line.
|
|
|
|
|
|
|
|
|
|
* DEC alpha support
|
|
|
|
|
|
|
|
|
|
This release contains support for using a DEC alpha as a GDB host for
|
|
|
|
|
cross debugging. Native alpha debugging is not supported yet.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.9:
|
|
|
|
|
|
|
|
|
|
* Testsuite
|
|
|
|
|
|
|
|
|
|
This is the first GDB release which is accompanied by a matching testsuite.
|
|
|
|
|
The testsuite requires installation of dejagnu, which should be available
|
|
|
|
|
via ftp from most sites that carry GNU software.
|
|
|
|
|
|
|
|
|
|
* C++ demangling
|
|
|
|
|
|
|
|
|
|
'Cfront' style demangling has had its name changed to 'ARM' style, to
|
|
|
|
|
emphasize that it was written from the specifications in the C++ Annotated
|
|
|
|
|
Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
|
|
|
|
|
disclaimers, it still generated too much confusion with users attempting to
|
|
|
|
|
use gdb with AT&T cfront.
|
|
|
|
|
|
|
|
|
|
* Simulators
|
|
|
|
|
|
|
|
|
|
GDB now uses a standard remote interface to a simulator library.
|
|
|
|
|
So far, the library contains simulators for the Zilog Z8001/2, the
|
|
|
|
|
Hitachi H8/300, H8/500 and Super-H.
|
|
|
|
|
|
|
|
|
|
* New targets supported
|
|
|
|
|
|
|
|
|
|
H8/300 simulator h8300-hitachi-hms or h8300hms
|
|
|
|
|
H8/500 simulator h8500-hitachi-hms or h8500hms
|
|
|
|
|
SH simulator sh-hitachi-hms or sh
|
|
|
|
|
Z8000 simulator z8k-zilog-none or z8ksim
|
|
|
|
|
IDT MIPS board over serial line mips-idt-ecoff
|
|
|
|
|
|
|
|
|
|
Cross-debugging to GO32 targets is supported. It requires a custom
|
|
|
|
|
version of the i386-stub.c module which is integrated with the
|
|
|
|
|
GO32 memory extender.
|
|
|
|
|
|
|
|
|
|
* New remote protocols
|
|
|
|
|
|
|
|
|
|
MIPS remote debugging protocol.
|
|
|
|
|
|
|
|
|
|
* New source languages supported
|
|
|
|
|
|
|
|
|
|
This version includes preliminary support for Chill, a Pascal like language
|
|
|
|
|
used by telecommunications companies. Chill support is also being integrated
|
2024-10-06 13:59:48 +08:00
|
|
|
into the GNU compiler, but we don't know when it will be publicly available.
|
1999-04-16 09:35:26 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.8:
|
|
|
|
|
|
|
|
|
|
* HP Precision Architecture supported
|
|
|
|
|
|
|
|
|
|
GDB now supports HP PA-RISC machines running HPUX. A preliminary
|
|
|
|
|
version of this support was available as a set of patches from the
|
|
|
|
|
University of Utah. GDB does not support debugging of programs
|
|
|
|
|
compiled with the HP compiler, because HP will not document their file
|
|
|
|
|
format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
|
|
|
|
|
(as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
|
|
|
|
|
|
|
|
|
|
Many problems in the preliminary version have been fixed.
|
|
|
|
|
|
|
|
|
|
* Faster and better demangling
|
|
|
|
|
|
|
|
|
|
We have improved template demangling and fixed numerous bugs in the GNU style
|
|
|
|
|
demangler. It can now handle type modifiers such as `static' or `const'. Wide
|
|
|
|
|
character types (wchar_t) are now supported. Demangling of each symbol is now
|
|
|
|
|
only done once, and is cached when the symbol table for a file is read in.
|
|
|
|
|
This results in a small increase in memory usage for C programs, a moderate
|
|
|
|
|
increase in memory usage for C++ programs, and a fantastic speedup in
|
|
|
|
|
symbol lookups.
|
|
|
|
|
|
|
|
|
|
`Cfront' style demangling still doesn't work with AT&T cfront. It was written
|
|
|
|
|
from the specifications in the Annotated Reference Manual, which AT&T's
|
|
|
|
|
compiler does not actually implement.
|
|
|
|
|
|
|
|
|
|
* G++ multiple inheritance compiler problem
|
|
|
|
|
|
|
|
|
|
In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
|
|
|
|
|
inheritance lattices was reworked to properly discover ambiguities. We
|
|
|
|
|
recently found an example which causes this new algorithm to fail in a
|
|
|
|
|
very subtle way, producing bad debug information for those classes.
|
|
|
|
|
The file 'gcc.patch' (in this directory) can be applied to gcc to
|
|
|
|
|
circumvent the problem. A future GCC release will contain a complete
|
|
|
|
|
fix.
|
|
|
|
|
|
|
|
|
|
The previous G++ debug info problem (mentioned below for the gdb-4.7
|
|
|
|
|
release) is fixed in gcc version 2.3.2.
|
|
|
|
|
|
|
|
|
|
* Improved configure script
|
|
|
|
|
|
|
|
|
|
The `configure' script will now attempt to guess your system type if
|
|
|
|
|
you don't supply a host system type. The old scheme of supplying a
|
|
|
|
|
host system triplet is preferable over using this. All the magic is
|
|
|
|
|
done in the new `config.guess' script. Examine it for details.
|
|
|
|
|
|
|
|
|
|
We have also brought our configure script much more in line with the FSF's
|
|
|
|
|
version. It now supports the --with-xxx options. In particular,
|
|
|
|
|
`--with-minimal-bfd' can be used to make the GDB binary image smaller.
|
|
|
|
|
The resulting GDB will not be able to read arbitrary object file formats --
|
|
|
|
|
only the format ``expected'' to be used on the configured target system.
|
|
|
|
|
We hope to make this the default in a future release.
|
|
|
|
|
|
|
|
|
|
* Documentation improvements
|
|
|
|
|
|
|
|
|
|
There's new internal documentation on how to modify GDB, and how to
|
|
|
|
|
produce clean changes to the code. We implore people to read it
|
|
|
|
|
before submitting changes.
|
|
|
|
|
|
|
|
|
|
The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
|
|
|
|
|
M4 macros. The new texinfo.tex is provided in this release. Pre-built
|
|
|
|
|
`info' files are also provided. To build `info' files from scratch,
|
|
|
|
|
you will need the latest `makeinfo' release, which will be available in
|
|
|
|
|
a future texinfo-X.Y release.
|
|
|
|
|
|
|
|
|
|
*NOTE* The new texinfo.tex can cause old versions of TeX to hang.
|
|
|
|
|
We're not sure exactly which versions have this problem, but it has
|
|
|
|
|
been seen in 3.0. We highly recommend upgrading to TeX version 3.141
|
|
|
|
|
or better. If that isn't possible, there is a patch in
|
|
|
|
|
`texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
|
|
|
|
|
around this problem.
|
|
|
|
|
|
|
|
|
|
* New features
|
|
|
|
|
|
|
|
|
|
GDB now supports array constants that can be used in expressions typed in by
|
|
|
|
|
the user. The syntax is `{element, element, ...}'. Ie: you can now type
|
|
|
|
|
`print {1, 2, 3}', and it will build up an array in memory malloc'd in
|
|
|
|
|
the target program.
|
|
|
|
|
|
|
|
|
|
The new directory `gdb/sparclite' contains a program that demonstrates
|
|
|
|
|
how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
|
|
|
|
|
|
|
|
|
|
* New native hosts supported
|
|
|
|
|
|
|
|
|
|
HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
|
|
|
|
|
386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
|
|
|
|
|
|
|
|
|
|
* New targets supported
|
|
|
|
|
|
|
|
|
|
AMD 29k family via UDI a29k-amd-udi or udi29k
|
|
|
|
|
|
|
|
|
|
* New file formats supported
|
|
|
|
|
|
|
|
|
|
BFD now supports reading HP/PA-RISC executables (SOM file format?),
|
|
|
|
|
HPUX core files, and SCO 3.2v2 core files.
|
|
|
|
|
|
|
|
|
|
* Major bug fixes
|
|
|
|
|
|
|
|
|
|
Attaching to processes now works again; thanks for the many bug reports.
|
|
|
|
|
|
|
|
|
|
We have also stomped on a bunch of core dumps caused by
|
|
|
|
|
printf_filtered("%s") problems.
|
|
|
|
|
|
|
|
|
|
We eliminated a copyright problem on the rpc and ptrace header files
|
|
|
|
|
for VxWorks, which was discovered at the last minute during the 4.7
|
|
|
|
|
release. You should now be able to build a VxWorks GDB.
|
|
|
|
|
|
|
|
|
|
You can now interrupt gdb while an attached process is running. This
|
|
|
|
|
will cause the attached process to stop, and give control back to GDB.
|
|
|
|
|
|
|
|
|
|
We fixed problems caused by using too many file descriptors
|
|
|
|
|
for reading symbols from object files and libraries. This was
|
|
|
|
|
especially a problem for programs that used many (~100) shared
|
|
|
|
|
libraries.
|
|
|
|
|
|
|
|
|
|
The `step' command now only enters a subroutine if there is line number
|
|
|
|
|
information for the subroutine. Otherwise it acts like the `next'
|
|
|
|
|
command. Previously, `step' would enter subroutines if there was
|
|
|
|
|
any debugging information about the routine. This avoids problems
|
|
|
|
|
when using `cc -g1' on MIPS machines.
|
|
|
|
|
|
|
|
|
|
* Internal improvements
|
|
|
|
|
|
|
|
|
|
GDB's internal interfaces have been improved to make it easier to support
|
|
|
|
|
debugging of multiple languages in the future.
|
|
|
|
|
|
|
|
|
|
GDB now uses a common structure for symbol information internally.
|
|
|
|
|
Minimal symbols (derived from linkage symbols in object files), partial
|
|
|
|
|
symbols (from a quick scan of debug information), and full symbols
|
|
|
|
|
contain a common subset of information, making it easier to write
|
|
|
|
|
shared code that handles any of them.
|
|
|
|
|
|
|
|
|
|
* New command line options
|
|
|
|
|
|
|
|
|
|
We now accept --silent as an alias for --quiet.
|
|
|
|
|
|
|
|
|
|
* Mmalloc licensing
|
|
|
|
|
|
|
|
|
|
The memory-mapped-malloc library is now licensed under the GNU Library
|
|
|
|
|
General Public License.
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.7:
|
|
|
|
|
|
|
|
|
|
* Host/native/target split
|
|
|
|
|
|
|
|
|
|
GDB has had some major internal surgery to untangle the support for
|
|
|
|
|
hosts and remote targets. Now, when you configure GDB for a remote
|
|
|
|
|
target, it will no longer load in all of the support for debugging
|
|
|
|
|
local programs on the host. When fully completed and tested, this will
|
|
|
|
|
ensure that arbitrary host/target combinations are possible.
|
|
|
|
|
|
|
|
|
|
The primary conceptual shift is to separate the non-portable code in
|
|
|
|
|
GDB into three categories. Host specific code is required any time GDB
|
|
|
|
|
is compiled on that host, regardless of the target. Target specific
|
|
|
|
|
code relates to the peculiarities of the target, but can be compiled on
|
|
|
|
|
any host. Native specific code is everything else: it can only be
|
|
|
|
|
built when the host and target are the same system. Child process
|
|
|
|
|
handling and core file support are two common `native' examples.
|
|
|
|
|
|
|
|
|
|
GDB's use of /proc for controlling Unix child processes is now cleaner.
|
|
|
|
|
It has been split out into a single module under the `target_ops' vector,
|
|
|
|
|
plus two native-dependent functions for each system that uses /proc.
|
|
|
|
|
|
|
|
|
|
* New hosts supported
|
|
|
|
|
|
|
|
|
|
HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
|
|
|
|
|
386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
|
|
|
|
|
386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
|
|
|
|
|
|
|
|
|
|
* New targets supported
|
|
|
|
|
|
|
|
|
|
Fujitsu SPARClite sparclite-fujitsu-none or sparclite
|
|
|
|
|
68030 and CPU32 m68030-*-*, m68332-*-*
|
|
|
|
|
|
|
|
|
|
* New native hosts supported
|
|
|
|
|
|
|
|
|
|
386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
|
|
|
|
|
(386bsd is not well tested yet)
|
|
|
|
|
386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
|
|
|
|
|
|
|
|
|
|
* New file formats supported
|
|
|
|
|
|
|
|
|
|
BFD now supports COFF files for the Zilog Z8000 microprocessor. It
|
|
|
|
|
supports reading of `a.out.adobe' object files, which are an a.out
|
|
|
|
|
format extended with minimal information about multiple sections.
|
|
|
|
|
|
|
|
|
|
* New commands
|
|
|
|
|
|
|
|
|
|
`show copying' is the same as the old `info copying'.
|
|
|
|
|
`show warranty' is the same as `info warrantee'.
|
|
|
|
|
These were renamed for consistency. The old commands continue to work.
|
|
|
|
|
|
|
|
|
|
`info handle' is a new alias for `info signals'.
|
|
|
|
|
|
|
|
|
|
You can now define pre-command hooks, which attach arbitrary command
|
|
|
|
|
scripts to any command. The commands in the hook will be executed
|
|
|
|
|
prior to the user's command. You can also create a hook which will be
|
|
|
|
|
executed whenever the program stops. See gdb.texinfo.
|
|
|
|
|
|
|
|
|
|
* C++ improvements
|
|
|
|
|
|
|
|
|
|
We now deal with Cfront style name mangling, and can even extract type
|
|
|
|
|
info from mangled symbols. GDB can automatically figure out which
|
|
|
|
|
symbol mangling style your C++ compiler uses.
|
|
|
|
|
|
|
|
|
|
Calling of methods and virtual functions has been improved as well.
|
|
|
|
|
|
|
|
|
|
* Major bug fixes
|
|
|
|
|
|
2020-06-05 18:24:20 +08:00
|
|
|
The crash that occurred when debugging Sun Ansi-C compiled binaries is
|
1999-04-16 09:35:26 +08:00
|
|
|
fixed. This was due to mishandling of the extra N_SO stabs output
|
|
|
|
|
by the compiler.
|
|
|
|
|
|
|
|
|
|
We also finally got Ultrix 4.2 running in house, and fixed core file
|
|
|
|
|
support, with help from a dozen people on the net.
|
|
|
|
|
|
|
|
|
|
John M. Farrell discovered that the reason that single-stepping was so
|
|
|
|
|
slow on all of the Mips based platforms (primarily SGI and DEC) was
|
|
|
|
|
that we were trying to demangle and lookup a symbol used for internal
|
|
|
|
|
purposes on every instruction that was being stepped through. Changing
|
|
|
|
|
the name of that symbol so that it couldn't be mistaken for a C++
|
|
|
|
|
mangled symbol sped things up a great deal.
|
|
|
|
|
|
|
|
|
|
Rich Pixley sped up symbol lookups in general by getting much smarter
|
|
|
|
|
about when C++ symbol mangling is necessary. This should make symbol
|
|
|
|
|
completion (TAB on the command line) much faster. It's not as fast as
|
|
|
|
|
we'd like, but it's significantly faster than gdb-4.6.
|
|
|
|
|
|
|
|
|
|
* AMD 29k support
|
|
|
|
|
|
|
|
|
|
A new user controllable variable 'call_scratch_address' can
|
|
|
|
|
specify the location of a scratch area to be used when GDB
|
|
|
|
|
calls a function in the target. This is necessary because the
|
|
|
|
|
usual method of putting the scratch area on the stack does not work
|
|
|
|
|
in systems that have separate instruction and data spaces.
|
|
|
|
|
|
|
|
|
|
We integrated changes to support the 29k UDI (Universal Debugger
|
|
|
|
|
Interface), but discovered at the last minute that we didn't have all
|
|
|
|
|
of the appropriate copyright paperwork. We are working with AMD to
|
|
|
|
|
resolve this, and hope to have it available soon.
|
|
|
|
|
|
|
|
|
|
* Remote interfaces
|
|
|
|
|
|
|
|
|
|
We have sped up the remote serial line protocol, especially for targets
|
|
|
|
|
with lots of registers. It now supports a new `expedited status' ('T')
|
|
|
|
|
message which can be used in place of the existing 'S' status message.
|
|
|
|
|
This allows the remote stub to send only the registers that GDB
|
|
|
|
|
needs to make a quick decision about single-stepping or conditional
|
|
|
|
|
breakpoints, eliminating the need to fetch the entire register set for
|
|
|
|
|
each instruction being stepped through.
|
|
|
|
|
|
|
|
|
|
The GDB remote serial protocol now implements a write-through cache for
|
|
|
|
|
registers, only re-reading the registers if the target has run.
|
|
|
|
|
|
|
|
|
|
There is also a new remote serial stub for SPARC processors. You can
|
|
|
|
|
find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
|
|
|
|
|
Fujitsu SPARClite processor, but will run on any stand-alone SPARC
|
|
|
|
|
processor with a serial port.
|
|
|
|
|
|
|
|
|
|
* Configuration
|
|
|
|
|
|
|
|
|
|
Configure.in files have become much easier to read and modify. A new
|
|
|
|
|
`table driven' format makes it more obvious what configurations are
|
|
|
|
|
supported, and what files each one uses.
|
|
|
|
|
|
|
|
|
|
* Library changes
|
|
|
|
|
|
|
|
|
|
There is a new opcodes library which will eventually contain all of the
|
|
|
|
|
disassembly routines and opcode tables. At present, it only contains
|
|
|
|
|
Sparc and Z8000 routines. This will allow the assembler, debugger, and
|
|
|
|
|
disassembler (binutils/objdump) to share these routines.
|
|
|
|
|
|
|
|
|
|
The libiberty library is now copylefted under the GNU Library General
|
|
|
|
|
Public License. This allows more liberal use, and was done so libg++
|
|
|
|
|
can use it. This makes no difference to GDB, since the Library License
|
|
|
|
|
grants all the rights from the General Public License.
|
|
|
|
|
|
|
|
|
|
* Documentation
|
|
|
|
|
|
|
|
|
|
The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
|
|
|
|
|
reference to the stabs symbol info used by the debugger. It is (as far
|
|
|
|
|
as we know) the only published document on this fascinating topic. We
|
|
|
|
|
encourage you to read it, compare it to the stabs information on your
|
|
|
|
|
system, and send improvements on the document in general (to
|
|
|
|
|
bug-gdb@prep.ai.mit.edu).
|
|
|
|
|
|
|
|
|
|
And, of course, many bugs have been fixed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.6:
|
|
|
|
|
|
|
|
|
|
* Better support for C++ function names
|
|
|
|
|
|
|
|
|
|
GDB now accepts as input the "demangled form" of C++ overloaded function
|
|
|
|
|
names and member function names, and can do command completion on such names
|
|
|
|
|
(using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
|
|
|
|
|
single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
|
|
|
|
|
Make use of command completion, it is your friend.
|
|
|
|
|
|
|
|
|
|
GDB also now accepts a variety of C++ mangled symbol formats. They are
|
|
|
|
|
the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
|
|
|
|
|
You can tell GDB which format to use by doing a 'set demangle-style {gnu,
|
|
|
|
|
lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
|
|
|
|
|
for the list of formats.
|
|
|
|
|
|
|
|
|
|
* G++ symbol mangling problem
|
|
|
|
|
|
|
|
|
|
Recent versions of gcc have a bug in how they emit debugging information for
|
|
|
|
|
C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
|
|
|
|
|
directory) can be applied to gcc to fix the problem. Alternatively, if you
|
2020-06-05 18:24:20 +08:00
|
|
|
can't fix gcc, you can #define GCC_MANGLE_BUG when compiling gdb/symtab.c. The
|
1999-04-16 09:35:26 +08:00
|
|
|
usual symptom is difficulty with setting breakpoints on methods. GDB complains
|
|
|
|
|
about the method being non-existent. (We believe that version 2.2.2 of GCC has
|
|
|
|
|
this problem.)
|
|
|
|
|
|
|
|
|
|
* New 'maintenance' command
|
|
|
|
|
|
|
|
|
|
All of the commands related to hacking GDB internals have been moved out of
|
|
|
|
|
the main command set, and now live behind the 'maintenance' command. This
|
|
|
|
|
can also be abbreviated as 'mt'. The following changes were made:
|
|
|
|
|
|
|
|
|
|
dump-me -> maintenance dump-me
|
|
|
|
|
info all-breakpoints -> maintenance info breakpoints
|
|
|
|
|
printmsyms -> maintenance print msyms
|
|
|
|
|
printobjfiles -> maintenance print objfiles
|
|
|
|
|
printpsyms -> maintenance print psymbols
|
|
|
|
|
printsyms -> maintenance print symbols
|
|
|
|
|
|
|
|
|
|
The following commands are new:
|
|
|
|
|
|
|
|
|
|
maintenance demangle Call internal GDB demangler routine to
|
|
|
|
|
demangle a C++ link name and prints the result.
|
|
|
|
|
maintenance print type Print a type chain for a given symbol
|
|
|
|
|
|
|
|
|
|
* Change to .gdbinit file processing
|
|
|
|
|
|
|
|
|
|
We now read the $HOME/.gdbinit file before processing the argv arguments
|
|
|
|
|
(e.g. reading symbol files or core files). This allows global parameters to
|
|
|
|
|
be set, which will apply during the symbol reading. The ./.gdbinit is still
|
|
|
|
|
read after argv processing.
|
|
|
|
|
|
|
|
|
|
* New hosts supported
|
|
|
|
|
|
|
|
|
|
Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
|
|
|
|
|
|
2002-02-11 01:34:05 +08:00
|
|
|
GNU/Linux support i386-unknown-linux or linux
|
1999-04-16 09:35:26 +08:00
|
|
|
|
|
|
|
|
We are also including code to support the HP/PA running BSD and HPUX. This
|
|
|
|
|
is almost guaranteed not to work, as we didn't have time to test or build it
|
|
|
|
|
for this release. We are including it so that the more adventurous (or
|
|
|
|
|
masochistic) of you can play with it. We also had major problems with the
|
|
|
|
|
fact that the compiler that we got from HP doesn't support the -g option.
|
|
|
|
|
It costs extra.
|
|
|
|
|
|
|
|
|
|
* New targets supported
|
|
|
|
|
|
|
|
|
|
Hitachi H8/300 h8300-hitachi-hms or h8300hms
|
|
|
|
|
|
|
|
|
|
* More smarts about finding #include files
|
|
|
|
|
|
|
|
|
|
GDB now remembers the compilation directory for all include files, and for
|
|
|
|
|
all files from which C is generated (like yacc and lex sources). This
|
|
|
|
|
greatly improves GDB's ability to find yacc/lex sources, and include files,
|
|
|
|
|
especially if you are debugging your program from a directory different from
|
|
|
|
|
the one that contains your sources.
|
|
|
|
|
|
|
|
|
|
We also fixed a bug which caused difficulty with listing and setting
|
|
|
|
|
breakpoints in include files which contain C code. (In the past, you had to
|
|
|
|
|
try twice in order to list an include file that you hadn't looked at before.)
|
|
|
|
|
|
|
|
|
|
* Interesting infernals change
|
|
|
|
|
|
|
|
|
|
GDB now deals with arbitrary numbers of sections, where the symbols for each
|
|
|
|
|
section must be relocated relative to that section's landing place in the
|
|
|
|
|
target's address space. This work was needed to support ELF with embedded
|
|
|
|
|
stabs used by Solaris-2.0.
|
|
|
|
|
|
|
|
|
|
* Bug fixes (of course!)
|
|
|
|
|
|
|
|
|
|
There have been loads of fixes for the following things:
|
|
|
|
|
mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
|
|
|
|
|
i960, stabs, DOS(GO32), procfs, etc...
|
|
|
|
|
|
|
|
|
|
See the ChangeLog for details.
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.5:
|
|
|
|
|
|
|
|
|
|
* New machines supported (host and target)
|
|
|
|
|
|
|
|
|
|
IBM RS6000 running AIX rs6000-ibm-aix or rs6000
|
|
|
|
|
|
|
|
|
|
SGI Irix-4.x mips-sgi-irix4 or iris4
|
|
|
|
|
|
|
|
|
|
* New malloc package
|
|
|
|
|
|
|
|
|
|
GDB now uses a new memory manager called mmalloc, based on gmalloc.
|
2020-06-05 18:24:20 +08:00
|
|
|
Mmalloc is capable of handling multiple heaps of memory. It is also
|
1999-04-16 09:35:26 +08:00
|
|
|
capable of saving a heap to a file, and then mapping it back in later.
|
|
|
|
|
This can be used to greatly speedup the startup of GDB by using a
|
|
|
|
|
pre-parsed symbol table which lives in a mmalloc managed heap. For
|
|
|
|
|
more details, please read mmalloc/mmalloc.texi.
|
|
|
|
|
|
|
|
|
|
* info proc
|
|
|
|
|
|
|
|
|
|
The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
|
|
|
|
|
'help info proc' for details.
|
|
|
|
|
|
|
|
|
|
* MIPS ecoff symbol table format
|
|
|
|
|
|
|
|
|
|
The code that reads MIPS symbol table format is now supported on all hosts.
|
|
|
|
|
Thanks to MIPS for releasing the sym.h and symconst.h files to make this
|
|
|
|
|
possible.
|
|
|
|
|
|
|
|
|
|
* File name changes for MS-DOS
|
|
|
|
|
|
|
|
|
|
Many files in the config directories have been renamed to make it easier to
|
|
|
|
|
support GDB on MS-DOSe systems (which have very restrictive file name
|
|
|
|
|
conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
|
|
|
|
|
environment) is close to working but has some remaining problems. Note
|
|
|
|
|
that debugging of DOS programs is not supported, due to limitations
|
|
|
|
|
in the ``operating system'', but it can be used to host cross-debugging.
|
|
|
|
|
|
|
|
|
|
* Cross byte order fixes
|
|
|
|
|
|
|
|
|
|
Many fixes have been made to support cross debugging of Sparc and MIPS
|
|
|
|
|
targets from hosts whose byte order differs.
|
|
|
|
|
|
|
|
|
|
* New -mapped and -readnow options
|
|
|
|
|
|
|
|
|
|
If memory-mapped files are available on your system through the 'mmap'
|
|
|
|
|
system call, you can use the -mapped option on the `file' or
|
|
|
|
|
`symbol-file' commands to cause GDB to write the symbols from your
|
|
|
|
|
program into a reusable file. If the program you are debugging is
|
|
|
|
|
called `/path/fred', the mapped symbol file will be `./fred.syms'.
|
|
|
|
|
Future GDB debugging sessions will notice the presence of this file,
|
|
|
|
|
and will quickly map in symbol information from it, rather than reading
|
|
|
|
|
the symbol table from the executable program. Using the '-mapped'
|
|
|
|
|
option in a GDB `file' or `symbol-file' command has the same effect as
|
|
|
|
|
starting GDB with the '-mapped' command-line option.
|
|
|
|
|
|
|
|
|
|
You can cause GDB to read the entire symbol table immediately by using
|
|
|
|
|
the '-readnow' option with any of the commands that load symbol table
|
|
|
|
|
information (or on the GDB command line). This makes the command
|
|
|
|
|
slower, but makes future operations faster.
|
|
|
|
|
|
|
|
|
|
The -mapped and -readnow options are typically combined in order to
|
|
|
|
|
build a `fred.syms' file that contains complete symbol information.
|
|
|
|
|
A simple GDB invocation to do nothing but build a `.syms' file for future
|
|
|
|
|
use is:
|
|
|
|
|
|
|
|
|
|
gdb -batch -nx -mapped -readnow programname
|
|
|
|
|
|
|
|
|
|
The `.syms' file is specific to the host machine on which GDB is run.
|
|
|
|
|
It holds an exact image of GDB's internal symbol table. It cannot be
|
|
|
|
|
shared across multiple host platforms.
|
|
|
|
|
|
|
|
|
|
* longjmp() handling
|
|
|
|
|
|
|
|
|
|
GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
|
|
|
|
|
siglongjmp() without losing control. This feature has not yet been ported to
|
|
|
|
|
all systems. It currently works on many 386 platforms, all MIPS-based
|
|
|
|
|
platforms (SGI, DECstation, etc), and Sun3/4.
|
|
|
|
|
|
|
|
|
|
* Solaris 2.0
|
|
|
|
|
|
|
|
|
|
Preliminary work has been put in to support the new Solaris OS from Sun. At
|
|
|
|
|
this time, it can control and debug processes, but it is not capable of
|
|
|
|
|
reading symbols.
|
|
|
|
|
|
|
|
|
|
* Bug fixes
|
|
|
|
|
|
|
|
|
|
As always, many many bug fixes. The major areas were with g++, and mipsread.
|
|
|
|
|
People using the MIPS-based platforms should experience fewer mysterious
|
|
|
|
|
crashes and trashed symbol tables.
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.4:
|
|
|
|
|
|
|
|
|
|
* New machines supported (host and target)
|
|
|
|
|
|
|
|
|
|
SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
|
|
|
|
|
(except core files)
|
|
|
|
|
BSD Reno on Vax vax-dec-bsd
|
|
|
|
|
Ultrix on Vax vax-dec-ultrix
|
|
|
|
|
|
|
|
|
|
* New machines supported (target)
|
|
|
|
|
|
|
|
|
|
AMD 29000 embedded, using EBMON a29k-none-none
|
|
|
|
|
|
|
|
|
|
* C++ support
|
|
|
|
|
|
|
|
|
|
GDB continues to improve its handling of C++. `References' work better.
|
|
|
|
|
The demangler has also been improved, and now deals with symbols mangled as
|
|
|
|
|
per the Annotated C++ Reference Guide.
|
|
|
|
|
|
|
|
|
|
GDB also now handles `stabs' symbol information embedded in MIPS
|
|
|
|
|
`ecoff' symbol tables. Since the ecoff format was not easily
|
|
|
|
|
extensible to handle new languages such as C++, this appeared to be a
|
|
|
|
|
good way to put C++ debugging info into MIPS binaries. This option
|
|
|
|
|
will be supported in the GNU C compiler, version 2, when it is
|
|
|
|
|
released.
|
|
|
|
|
|
|
|
|
|
* New features for SVR4
|
|
|
|
|
|
|
|
|
|
GDB now handles SVR4 shared libraries, in the same fashion as SunOS
|
|
|
|
|
shared libraries. Debugging dynamically linked programs should present
|
|
|
|
|
only minor differences from debugging statically linked programs.
|
|
|
|
|
|
|
|
|
|
The `info proc' command will print out information about any process
|
|
|
|
|
on an SVR4 system (including the one you are debugging). At the moment,
|
|
|
|
|
it prints the address mappings of the process.
|
|
|
|
|
|
|
|
|
|
If you bring up GDB on another SVR4 system, please send mail to
|
|
|
|
|
bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
|
|
|
|
|
|
|
|
|
|
* Better dynamic linking support in SunOS
|
|
|
|
|
|
|
|
|
|
Reading symbols from shared libraries which contain debugging symbols
|
|
|
|
|
now works properly. However, there remain issues such as automatic
|
|
|
|
|
skipping of `transfer vector' code during function calls, which
|
|
|
|
|
make it harder to debug code in a shared library, than to debug the
|
|
|
|
|
same code linked statically.
|
|
|
|
|
|
|
|
|
|
* New Getopt
|
|
|
|
|
|
|
|
|
|
GDB is now using the latest `getopt' routines from the FSF. This
|
|
|
|
|
version accepts the -- prefix for options with long names. GDB will
|
|
|
|
|
continue to accept the old forms (-option and +option) as well.
|
|
|
|
|
Various single letter abbreviations for options have been explicity
|
|
|
|
|
added to the option table so that they won't get overshadowed in the
|
|
|
|
|
future by other options that begin with the same letter.
|
|
|
|
|
|
|
|
|
|
* Bugs fixed
|
|
|
|
|
|
|
|
|
|
The `cleanup_undefined_types' bug that many of you noticed has been squashed.
|
|
|
|
|
Many assorted bugs have been handled. Many more remain to be handled.
|
|
|
|
|
See the various ChangeLog files (primarily in gdb and bfd) for details.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.3:
|
|
|
|
|
|
|
|
|
|
* New machines supported (host and target)
|
|
|
|
|
|
|
|
|
|
Amiga 3000 running Amix m68k-cbm-svr4 or amix
|
|
|
|
|
NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
|
|
|
|
|
Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
|
|
|
|
|
|
|
|
|
|
* Almost SCO Unix support
|
|
|
|
|
|
|
|
|
|
We had hoped to support:
|
|
|
|
|
SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
|
|
|
|
|
(except for core file support), but we discovered very late in the release
|
|
|
|
|
that it has problems with process groups that render gdb unusable. Sorry
|
|
|
|
|
about that. I encourage people to fix it and post the fixes.
|
|
|
|
|
|
|
|
|
|
* Preliminary ELF and DWARF support
|
|
|
|
|
|
|
|
|
|
GDB can read ELF object files on System V Release 4, and can handle
|
|
|
|
|
debugging records for C, in DWARF format, in ELF files. This support
|
|
|
|
|
is preliminary. If you bring up GDB on another SVR4 system, please
|
|
|
|
|
send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
|
|
|
|
|
reqired (if any).
|
|
|
|
|
|
|
|
|
|
* New Readline
|
|
|
|
|
|
|
|
|
|
GDB now uses the latest `readline' library. One user-visible change
|
|
|
|
|
is that two tabs will list possible command completions, which previously
|
|
|
|
|
required typing M-? (meta-question mark, or ESC ?).
|
|
|
|
|
|
|
|
|
|
* Bugs fixed
|
|
|
|
|
|
|
|
|
|
The `stepi' bug that many of you noticed has been squashed.
|
|
|
|
|
Many bugs in C++ have been handled. Many more remain to be handled.
|
|
|
|
|
See the various ChangeLog files (primarily in gdb and bfd) for details.
|
|
|
|
|
|
|
|
|
|
* State of the MIPS world (in case you wondered):
|
|
|
|
|
|
|
|
|
|
GDB can understand the symbol tables emitted by the compilers
|
|
|
|
|
supplied by most vendors of MIPS-based machines, including DEC. These
|
|
|
|
|
symbol tables are in a format that essentially nobody else uses.
|
|
|
|
|
|
|
|
|
|
Some versions of gcc come with an assembler post-processor called
|
|
|
|
|
mips-tfile. This program is required if you want to do source-level
|
|
|
|
|
debugging of gcc-compiled programs. I believe FSF does not ship
|
|
|
|
|
mips-tfile with gcc version 1, but it will eventually come with gcc
|
|
|
|
|
version 2.
|
|
|
|
|
|
|
|
|
|
Debugging of g++ output remains a problem. g++ version 1.xx does not
|
|
|
|
|
really support it at all. (If you're lucky, you should be able to get
|
|
|
|
|
line numbers and stack traces to work, but no parameters or local
|
|
|
|
|
variables.) With some work it should be possible to improve the
|
|
|
|
|
situation somewhat.
|
|
|
|
|
|
|
|
|
|
When gcc version 2 is released, you will have somewhat better luck.
|
|
|
|
|
However, even then you will get confusing results for inheritance and
|
|
|
|
|
methods.
|
|
|
|
|
|
|
|
|
|
We will eventually provide full debugging of g++ output on
|
|
|
|
|
DECstations. This will probably involve some kind of stabs-in-ecoff
|
|
|
|
|
encapulation, but the details have not been worked out yet.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.2:
|
|
|
|
|
|
|
|
|
|
* Improved configuration
|
|
|
|
|
|
|
|
|
|
Only one copy of `configure' exists now, and it is not self-modifying.
|
|
|
|
|
Porting BFD is simpler.
|
|
|
|
|
|
|
|
|
|
* Stepping improved
|
|
|
|
|
|
|
|
|
|
The `step' and `next' commands now only stop at the first instruction
|
|
|
|
|
of a source line. This prevents the multiple stops that used to occur
|
|
|
|
|
in switch statements, for-loops, etc. `Step' continues to stop if a
|
|
|
|
|
function that has debugging information is called within the line.
|
|
|
|
|
|
|
|
|
|
* Bug fixing
|
|
|
|
|
|
|
|
|
|
Lots of small bugs fixed. More remain.
|
|
|
|
|
|
|
|
|
|
* New host supported (not target)
|
|
|
|
|
|
|
|
|
|
Intel 386 PC clone running Mach i386-none-mach
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.1:
|
|
|
|
|
|
|
|
|
|
* Multiple source language support
|
|
|
|
|
|
|
|
|
|
GDB now has internal scaffolding to handle several source languages.
|
|
|
|
|
It determines the type of each source file from its filename extension,
|
|
|
|
|
and will switch expression parsing and number formatting to match the
|
|
|
|
|
language of the function in the currently selected stack frame.
|
|
|
|
|
You can also specifically set the language to be used, with
|
|
|
|
|
`set language c' or `set language modula-2'.
|
|
|
|
|
|
|
|
|
|
* GDB and Modula-2
|
|
|
|
|
|
|
|
|
|
GDB now has preliminary support for the GNU Modula-2 compiler,
|
|
|
|
|
currently under development at the State University of New York at
|
|
|
|
|
Buffalo. Development of both GDB and the GNU Modula-2 compiler will
|
|
|
|
|
continue through the fall of 1991 and into 1992.
|
|
|
|
|
|
|
|
|
|
Other Modula-2 compilers are currently not supported, and attempting to
|
|
|
|
|
debug programs compiled with them will likely result in an error as the
|
|
|
|
|
symbol table is read. Feel free to work on it, though!
|
|
|
|
|
|
|
|
|
|
There are hooks in GDB for strict type checking and range checking,
|
|
|
|
|
in the `Modula-2 philosophy', but they do not currently work.
|
|
|
|
|
|
|
|
|
|
* set write on/off
|
|
|
|
|
|
|
|
|
|
GDB can now write to executable and core files (e.g. patch
|
|
|
|
|
a variable's value). You must turn this switch on, specify
|
|
|
|
|
the file ("exec foo" or "core foo"), *then* modify it, e.g.
|
|
|
|
|
by assigning a new value to a variable. Modifications take
|
|
|
|
|
effect immediately.
|
|
|
|
|
|
|
|
|
|
* Automatic SunOS shared library reading
|
|
|
|
|
|
|
|
|
|
When you run your program, GDB automatically determines where its
|
|
|
|
|
shared libraries (if any) have been loaded, and reads their symbols.
|
|
|
|
|
The `share' command is no longer needed. This also works when
|
|
|
|
|
examining core files.
|
|
|
|
|
|
|
|
|
|
* set listsize
|
|
|
|
|
|
|
|
|
|
You can specify the number of lines that the `list' command shows.
|
|
|
|
|
The default is 10.
|
|
|
|
|
|
|
|
|
|
* New machines supported (host and target)
|
|
|
|
|
|
|
|
|
|
SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
|
|
|
|
|
Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
|
|
|
|
|
Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
|
|
|
|
|
|
|
|
|
|
* New hosts supported (not targets)
|
|
|
|
|
|
|
|
|
|
IBM RT/PC: romp-ibm-aix or rtpc
|
|
|
|
|
|
|
|
|
|
* New targets supported (not hosts)
|
|
|
|
|
|
|
|
|
|
AMD 29000 embedded with COFF a29k-none-coff
|
|
|
|
|
AMD 29000 embedded with a.out a29k-none-aout
|
|
|
|
|
Ultracomputer remote kernel debug a29k-nyu-kern
|
|
|
|
|
|
|
|
|
|
* New remote interfaces
|
|
|
|
|
|
|
|
|
|
AMD 29000 Adapt
|
|
|
|
|
AMD 29000 Minimon
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*** Changes in GDB-4.0:
|
|
|
|
|
|
|
|
|
|
* New Facilities
|
|
|
|
|
|
|
|
|
|
Wide output is wrapped at good places to make the output more readable.
|
|
|
|
|
|
|
|
|
|
Gdb now supports cross-debugging from a host machine of one type to a
|
|
|
|
|
target machine of another type. Communication with the target system
|
|
|
|
|
is over serial lines. The ``target'' command handles connecting to the
|
|
|
|
|
remote system; the ``load'' command will download a program into the
|
|
|
|
|
remote system. Serial stubs for the m68k and i386 are provided. Gdb
|
|
|
|
|
also supports debugging of realtime processes running under VxWorks,
|
|
|
|
|
using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
|
|
|
|
|
stub on the target system.
|
|
|
|
|
|
|
|
|
|
New CPUs supported include the AMD 29000 and Intel 960.
|
|
|
|
|
|
|
|
|
|
GDB now reads object files and symbol tables via a ``binary file''
|
|
|
|
|
library, which allows a single copy of GDB to debug programs of multiple
|
|
|
|
|
object file types such as a.out and coff.
|
|
|
|
|
|
|
|
|
|
There is now a GDB reference card in "doc/refcard.tex". (Make targets
|
|
|
|
|
refcard.dvi and refcard.ps are available to format it).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Control-Variable user interface simplified
|
|
|
|
|
|
|
|
|
|
All variables that control the operation of the debugger can be set
|
|
|
|
|
by the ``set'' command, and displayed by the ``show'' command.
|
|
|
|
|
|
|
|
|
|
For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
|
|
|
|
|
``Show prompt'' produces the response:
|
|
|
|
|
Gdb's prompt is new-gdb=>.
|
|
|
|
|
|
|
|
|
|
What follows are the NEW set commands. The command ``help set'' will
|
|
|
|
|
print a complete list of old and new set commands. ``help set FOO''
|
|
|
|
|
will give a longer description of the variable FOO. ``show'' will show
|
|
|
|
|
all of the variable descriptions and their current settings.
|
|
|
|
|
|
|
|
|
|
confirm on/off: Enables warning questions for operations that are
|
|
|
|
|
hard to recover from, e.g. rerunning the program while
|
|
|
|
|
it is already running. Default is ON.
|
|
|
|
|
|
|
|
|
|
editing on/off: Enables EMACS style command line editing
|
|
|
|
|
of input. Previous lines can be recalled with
|
|
|
|
|
control-P, the current line can be edited with control-B,
|
|
|
|
|
you can search for commands with control-R, etc.
|
|
|
|
|
Default is ON.
|
|
|
|
|
|
|
|
|
|
history filename NAME: NAME is where the gdb command history
|
|
|
|
|
will be stored. The default is .gdb_history,
|
|
|
|
|
or the value of the environment variable
|
|
|
|
|
GDBHISTFILE.
|
|
|
|
|
|
|
|
|
|
history size N: The size, in commands, of the command history. The
|
|
|
|
|
default is 256, or the value of the environment variable
|
|
|
|
|
HISTSIZE.
|
|
|
|
|
|
|
|
|
|
history save on/off: If this value is set to ON, the history file will
|
|
|
|
|
be saved after exiting gdb. If set to OFF, the
|
|
|
|
|
file will not be saved. The default is OFF.
|
|
|
|
|
|
|
|
|
|
history expansion on/off: If this value is set to ON, then csh-like
|
|
|
|
|
history expansion will be performed on
|
|
|
|
|
command line input. The default is OFF.
|
|
|
|
|
|
|
|
|
|
radix N: Sets the default radix for input and output. It can be set
|
|
|
|
|
to 8, 10, or 16. Note that the argument to "radix" is interpreted
|
|
|
|
|
in the current radix, so "set radix 10" is always a no-op.
|
|
|
|
|
|
|
|
|
|
height N: This integer value is the number of lines on a page. Default
|
|
|
|
|
is 24, the current `stty rows'' setting, or the ``li#''
|
|
|
|
|
setting from the termcap entry matching the environment
|
|
|
|
|
variable TERM.
|
|
|
|
|
|
|
|
|
|
width N: This integer value is the number of characters on a line.
|
|
|
|
|
Default is 80, the current `stty cols'' setting, or the ``co#''
|
|
|
|
|
setting from the termcap entry matching the environment
|
|
|
|
|
variable TERM.
|
|
|
|
|
|
|
|
|
|
Note: ``set screensize'' is obsolete. Use ``set height'' and
|
|
|
|
|
``set width'' instead.
|
|
|
|
|
|
|
|
|
|
print address on/off: Print memory addresses in various command displays,
|
|
|
|
|
such as stack traces and structure values. Gdb looks
|
|
|
|
|
more ``symbolic'' if you turn this off; it looks more
|
|
|
|
|
``machine level'' with it on. Default is ON.
|
|
|
|
|
|
|
|
|
|
print array on/off: Prettyprint arrays. New convenient format! Default
|
|
|
|
|
is OFF.
|
|
|
|
|
|
|
|
|
|
print demangle on/off: Print C++ symbols in "source" form if on,
|
|
|
|
|
"raw" form if off.
|
|
|
|
|
|
|
|
|
|
print asm-demangle on/off: Same, for assembler level printouts
|
|
|
|
|
like instructions.
|
|
|
|
|
|
|
|
|
|
print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Support for Epoch Environment.
|
|
|
|
|
|
|
|
|
|
The epoch environment is a version of Emacs v18 with windowing. One
|
|
|
|
|
new command, ``inspect'', is identical to ``print'', except that if you
|
|
|
|
|
are running in the epoch environment, the value is printed in its own
|
|
|
|
|
window.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Support for Shared Libraries
|
|
|
|
|
|
|
|
|
|
GDB can now debug programs and core files that use SunOS shared libraries.
|
|
|
|
|
Symbols from a shared library cannot be referenced
|
|
|
|
|
before the shared library has been linked with the program (this
|
|
|
|
|
happens after you type ``run'' and before the function main() is entered).
|
|
|
|
|
At any time after this linking (including when examining core files
|
|
|
|
|
from dynamically linked programs), gdb reads the symbols from each
|
|
|
|
|
shared library when you type the ``sharedlibrary'' command.
|
|
|
|
|
It can be abbreviated ``share''.
|
|
|
|
|
|
|
|
|
|
sharedlibrary REGEXP: Load shared object library symbols for files
|
|
|
|
|
matching a unix regular expression. No argument
|
|
|
|
|
indicates to load symbols for all shared libraries.
|
|
|
|
|
|
|
|
|
|
info sharedlibrary: Status of loaded shared libraries.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Watchpoints
|
|
|
|
|
|
|
|
|
|
A watchpoint stops execution of a program whenever the value of an
|
|
|
|
|
expression changes. Checking for this slows down execution
|
|
|
|
|
tremendously whenever you are in the scope of the expression, but is
|
|
|
|
|
quite useful for catching tough ``bit-spreader'' or pointer misuse
|
|
|
|
|
problems. Some machines such as the 386 have hardware for doing this
|
|
|
|
|
more quickly, and future versions of gdb will use this hardware.
|
|
|
|
|
|
|
|
|
|
watch EXP: Set a watchpoint (breakpoint) for an expression.
|
|
|
|
|
|
|
|
|
|
info watchpoints: Information about your watchpoints.
|
|
|
|
|
|
|
|
|
|
delete N: Deletes watchpoint number N (same as breakpoints).
|
|
|
|
|
disable N: Temporarily turns off watchpoint number N (same as breakpoints).
|
|
|
|
|
enable N: Re-enables watchpoint number N (same as breakpoints).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* C++ multiple inheritance
|
|
|
|
|
|
|
|
|
|
When used with a GCC version 2 compiler, GDB supports multiple inheritance
|
|
|
|
|
for C++ programs.
|
|
|
|
|
|
|
|
|
|
* C++ exception handling
|
|
|
|
|
|
|
|
|
|
Gdb now supports limited C++ exception handling. Besides the existing
|
|
|
|
|
ability to breakpoint on an exception handler, gdb can breakpoint on
|
|
|
|
|
the raising of an exception (before the stack is peeled back to the
|
|
|
|
|
handler's context).
|
|
|
|
|
|
|
|
|
|
catch FOO: If there is a FOO exception handler in the dynamic scope,
|
|
|
|
|
set a breakpoint to catch exceptions which may be raised there.
|
|
|
|
|
Multiple exceptions (``catch foo bar baz'') may be caught.
|
|
|
|
|
|
|
|
|
|
info catch: Lists all exceptions which may be caught in the
|
|
|
|
|
current stack frame.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Minor command changes
|
|
|
|
|
|
|
|
|
|
The command ``call func (arg, arg, ...)'' now acts like the print
|
|
|
|
|
command, except it does not print or save a value if the function's result
|
|
|
|
|
is void. This is similar to dbx usage.
|
|
|
|
|
|
|
|
|
|
The ``up'' and ``down'' commands now always print the frame they end up
|
|
|
|
|
at; ``up-silently'' and `down-silently'' can be used in scripts to change
|
|
|
|
|
frames without printing.
|
|
|
|
|
|
|
|
|
|
* New directory command
|
|
|
|
|
|
|
|
|
|
'dir' now adds directories to the FRONT of the source search path.
|
|
|
|
|
The path starts off empty. Source files that contain debug information
|
|
|
|
|
about the directory in which they were compiled can be found even
|
|
|
|
|
with an empty path; Sun CC and GCC include this information. If GDB can't
|
|
|
|
|
find your source file in the current directory, type "dir .".
|
|
|
|
|
|
|
|
|
|
* Configuring GDB for compilation
|
|
|
|
|
|
|
|
|
|
For normal use, type ``./configure host''. See README or gdb.texinfo
|
|
|
|
|
for more details.
|
|
|
|
|
|
|
|
|
|
GDB now handles cross debugging. If you are remotely debugging between
|
|
|
|
|
two different machines, type ``./configure host -target=targ''.
|
|
|
|
|
Host is the machine where GDB will run; targ is the machine
|
|
|
|
|
where the program that you are debugging will run.
|
