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 1/2] Display ExceptionRecord for $_siginfo
Date: Tue, 11 Feb 2020 16:56:00 -0000	[thread overview]
Message-ID: <2078124319.2610999.1581440165388@mail.yahoo.com> (raw)
In-Reply-To: <874kvx9m8t.fsf@tromey.com>

 Am Dienstag, 11. Februar 2020, 16:28:37 MEZ hat Tom Tromey <tom@tromey.com> Folgendes geschrieben:

> >>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
>
> Simon> Huh... I was going to say that it shouldn't be a global variable,
> Simon> but a per-inferior thing (or is it per-thread?), but pretty much
> Simon> all the state is already global...  so I guess it's fine.  I
> Simon> gather that the windows-nat does not support debugging multiple
> Simon> inferiors?  Same for win32-low in gdbserver?
>
> Yes, that's correct.  I think it could be implemented, just nobody has
> done it yet.

How does debugging multiple inferiors work exactly?
Is this only possible with async mode (which doesn't work on Windows)?


Regards
Hannes Domani


      reply	other threads:[~2020-02-11 16:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200117153140.2231-1-ssbssa.ref@yahoo.de>
2020-01-17 15:32 ` Hannes Domani via gdb-patches
2020-01-17 15:36   ` [PATCH 2/2] Use enums for human-readable exception information Hannes Domani via gdb-patches
2020-02-07 22:02     ` Simon Marchi
2020-02-07 21:56   ` [PATCH 1/2] Display ExceptionRecord for $_siginfo Simon Marchi
2020-02-07 22:07     ` Simon Marchi
2020-02-07 22:17       ` Hannes Domani via gdb-patches
2020-02-07 22:14     ` Hannes Domani via gdb-patches
2020-02-11 15:28     ` Tom Tromey
2020-02-11 16:56       ` Hannes Domani via gdb-patches [this message]

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=2078124319.2610999.1581440165388@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