Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Hannes Domani via gdb-patches" <gdb-patches@sourceware.org>
To: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3] Implement debugging of WOW64 processes
Date: Wed, 04 Mar 2020 19:46:00 -0000	[thread overview]
Message-ID: <667267301.7060481.1583351203448@mail.yahoo.com> (raw)
In-Reply-To: <711a3001-da27-4400-5d11-93ed14e503f2@simark.ca>

 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


  reply	other threads:[~2020-03-04 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200304191632.14947-1-ssbssa.ref@yahoo.de>
2020-03-04 19:17 ` Hannes Domani via gdb-patches
2020-03-04 19:32   ` Simon Marchi
2020-03-04 19:46     ` Hannes Domani via gdb-patches [this message]
2020-03-04 20:07       ` Simon Marchi
2020-03-04 20:18         ` Hannes Domani via gdb-patches
2020-03-04 20:45           ` Simon Marchi

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=667267301.7060481.1583351203448@mail.yahoo.com \
    --to=gdb-patches@sourceware.org \
    --cc=ssbssa@yahoo.de \
    /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