diff options
| author | Pedro Alves <pedro@palves.net> | 2022-10-17 17:48:35 +0100 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2022-10-17 17:58:41 +0100 |
| commit | 39e9d8670cea9d3d2959387b6d51050b0716eb19 (patch) | |
| tree | 27b534dfcfd213ba719b4dddada6976f21b06a03 /gdb/python | |
| parent | dd05fc7071a6517de13975fcddca861547351266 (diff) | |
| download | binutils-39e9d8670cea9d3d2959387b6d51050b0716eb19.zip binutils-39e9d8670cea9d3d2959387b6d51050b0716eb19.tar.gz binutils-39e9d8670cea9d3d2959387b6d51050b0716eb19.tar.bz2 | |
gdbarch-components.py: Remove spurious space from "frame_info_ptr " params
If you run gdbarch.py today, you'll get local modifications compared
to what's in the tree, like:
--- c/gdb/gdbarch-gen.h
+++ w/gdb/gdbarch-gen.h
@@ -315,8 +315,8 @@ extern void set_gdbarch_register_type (struct gdbarch *gdbarch, gdbarch_register
should match the address at which the breakpoint was set in the dummy
frame. */
-typedef struct frame_id (gdbarch_dummy_id_ftype) (struct gdbarch *gdbarch, frame_info_ptr this_frame);
-extern struct frame_id gdbarch_dummy_id (struct gdbarch *gdbarch, frame_info_ptr this_frame);
+typedef struct frame_id (gdbarch_dummy_id_ftype) (struct gdbarch *gdbarch, frame_info_ptr this_frame);
+extern struct frame_id gdbarch_dummy_id (struct gdbarch *gdbarch, frame_info_ptr this_frame);
extern void set_gdbarch_dummy_id (struct gdbarch *gdbarch, gdbarch_dummy_id_ftype *dummy_id);
etc.
The extra space comes from the "frame_info_ptr " param that appears in
a number of gdbarch methods in gdbarch-components.py. With the extra
space removed, running ./gdbarch.py generates the exact code that's in
the tree already.
Change-Id: If7d20b8c6b2fd9ff466142a01bd2611c9ef9f53e
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions