From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Hui Zhu <teawater@gmail.com>
Subject: Re: [RFA Precord] Disable process record in amd64
Date: Wed, 13 May 2009 10:18:00 -0000 [thread overview]
Message-ID: <200905131118.02697.pedro@codesourcery.com> (raw)
In-Reply-To: <daef60380905130107g27f33764lfdc001ebad883bbc@mail.gmail.com>
On Wednesday 13 May 2009 09:07:03, Hui Zhu wrote:
> Hi,
>
> The i386 process record can't work together with amd64 now. So I make
> a patch to disable it in amd64.
It would be better to move the `set_gdbarch_process_record (gdbarch, i386_process_record)'
call to tdep files where precord will actually work --- in this
case, i386-linux-tdep.c --- instead of having i386-tdep.c assume
precord support. We've done the exact same thing for displaced
stepping.
>
> 2009-05-13 Hui Zhu <teawater@gmail.com>
>
> * amd64-tdep.c (amd64_init_abi): Disable process record
> function that set in i386_gdbarch_init.
> * i386-tdep.c (i386_gdbarch_init): Call
> set_gdbarch_process_record before gdbarch_init_osabi to make
> process record can be disable in gdbarch_init_osabi.
>
> Thanks,
> Hui
>
> ---
> amd64-tdep.c | 3 +++
> i386-tdep.c | 4 ++--
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> --- a/amd64-tdep.c
> +++ b/amd64-tdep.c
> @@ -2049,6 +2049,9 @@ amd64_init_abi (struct gdbarch_info info
> amd64_regset_from_core_section);
>
> set_gdbarch_get_longjmp_target (gdbarch, amd64_get_longjmp_target);
> +
> + /* Disable process record function that set in i386_gdbarch_init. */
> + set_gdbarch_process_record (gdbarch, 0);
> }
> \f
>
> --- a/i386-tdep.c
> +++ b/i386-tdep.c
> @@ -5256,6 +5256,8 @@ i386_gdbarch_init (struct gdbarch_info i
>
> frame_base_set_default (gdbarch, &i386_frame_base);
>
> + set_gdbarch_process_record (gdbarch, i386_process_record);
> +
> /* Hook in ABI-specific overrides, if they have been registered. */
> gdbarch_init_osabi (info, gdbarch);
>
> @@ -5277,8 +5279,6 @@ i386_gdbarch_init (struct gdbarch_info i
> set_gdbarch_skip_permanent_breakpoint (gdbarch,
> i386_skip_permanent_breakpoint);
>
> - set_gdbarch_process_record (gdbarch, i386_process_record);
> -
> return gdbarch;
> }
>
--
Pedro Alves
next prev parent reply other threads:[~2009-05-13 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 8:07 Hui Zhu
2009-05-13 10:18 ` Pedro Alves [this message]
2009-05-13 10:24 ` Mark Kettenis
2009-05-13 16:31 ` Hui Zhu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905131118.02697.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox