From: Andrew Cagney <ac131313@redhat.com>
To: Alain Magloire <alain@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB/MI lawyer for Thread Creation
Date: Tue, 06 May 2003 21:51:00 -0000 [thread overview]
Message-ID: <3EB82E49.2010207@redhat.com> (raw)
In-Reply-To: <200305062131.RAA16749@node1.ott.qnx.com>
> Bonjour
>
> Need a MI protocol guru for this. When threads are created gdb is sending
>
> gdb -i mi
> ~"[NEW Thread 1024 (LWP 8288)]\n"
>
>
> Useless for MI, how about a new OOB ?
>
> *thread,thread-id="8288"
>
>
> or a new async-notify ?
>
> =thread,thread-id="8288"
>
> Only "*stopped" is currently define as a possible oob.
BTW, co/build kseitz_interps-20020528-branch, it also generates
breakpoint notify events.
I think that notify is correct (although it could be argued that exec is
a legetimate class (the difference is a bit arbitrary).
Andrew
next prev parent reply other threads:[~2003-05-06 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 21:31 Alain Magloire
2003-05-06 21:51 ` Andrew Cagney [this message]
2003-05-07 15:19 ` Event notification (was Re: GDB/MI lawyer for Thread Creation) Alain Magloire
2003-05-07 16:16 ` Andrew Cagney
2003-05-07 18:56 ` Alain Magloire
2003-05-16 3:14 ` Andrew Cagney
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=3EB82E49.2010207@redhat.com \
--to=ac131313@redhat.com \
--cc=alain@qnx.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).