This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v3] Implement debugging of WOW64 processes
- From: "Hannes Domani via gdb-patches" <gdb-patches at sourceware dot org>
- To: Gdb-patches <gdb-patches at sourceware dot org>
- Date: Wed, 4 Mar 2020 19:46:43 +0000 (UTC)
- Subject: Re: [PATCH v3] Implement debugging of WOW64 processes
- References: <20200304191632.14947-1-ssbssa.ref@yahoo.de> <20200304191632.14947-1-ssbssa@yahoo.de> <711a3001-da27-4400-5d11-93ed14e503f2@simark.ca>
- Reply-to: Hannes Domani <ssbssa at yahoo dot de>
Am Mittwoch, 4. März 2020, 20:32:52 MEZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:
> On 2020-03-04 2:16 p.m., Hannes Domani via gdb-patches wrote:
> > @@ -99,7 +99,5 @@ void _initialize_amd64_windows_nat ();
> > void
> > _initialize_amd64_windows_nat ()
> > {
> > - windows_set_context_register_offsets (mappings);
> > - windows_set_segment_register_p (amd64_windows_segment_register_p);
> > x86_set_debug_register_length (8);
> > }
>
> Does x86_set_debug_register_length need to be adjusted based on the type of the
> process? With the current code, it will be set to 8 even if debugging a WOW64
> process, is that what we want?
I don't really know what this is for, but I haven't had any problem so far like this.
Besides, there is this comment in x86-nat.c:
void
x86_set_debug_register_length (int len)
{
/* This function should be called only once for each native target. */
gdb_assert (x86_dr_low.debug_register_length == 0);
...
Regards
Hannes Domani