From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix crash in "run" on macOS when gdb is not signed
Date: Tue, 03 Jul 2018 14:16:00 -0000 [thread overview]
Message-ID: <38028d2f-ba08-fd36-6d5f-6a47455e5ccf@redhat.com> (raw)
In-Reply-To: <87o9fpodos.fsf@tromey.com>
On 07/02/2018 04:33 PM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>
> Pedro> I'd try also with "attach", see if something else needs
> Pedro> cleaning up / unwinding.
>
> Thanks. This seemed to work fine.
>
> Pedro> If you try this with MI as is, I think gdb will output a
> Pedro> -thread-group-started notification, and then an ^error.
> Pedro> You may want to call exit_inferior instead so that
> Pedro> gdb outputs a matching -thread-group-exited.
>
> Indeed; I've changed it to use exit_inferior.
>
> Pedro> Otherwise looks fine to me.
>
> How's this?
Looks good.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-07-03 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 18:03 Tom Tromey
2018-06-29 19:31 ` Pedro Alves
2018-07-02 15:33 ` Tom Tromey
2018-07-03 14:16 ` Pedro Alves [this message]
2018-07-04 11:46 ` Pedro Alves
2018-07-04 17:34 ` Tom Tromey
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=38028d2f-ba08-fd36-6d5f-6a47455e5ccf@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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