From: Tomas Martinec <fyzmat@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: Stepping of multithreaded application
Date: Tue, 17 May 2011 14:07:00 -0000 [thread overview]
Message-ID: <BANLkTimPbpfPXb7mDbSRyRPZyOu4xn_6-A@mail.gmail.com> (raw)
In-Reply-To: <201105171303.06804.pedro@codesourcery.com>
> Hmm. This is making me very nervous on changing GDB's
> age old behavior... Who knows which old targets out
> there are assuming:
>
> - "Hc 0" to mean continue all threads
> - "Hc $FOO" to continue/step only thread $FOO
>
> and picking the 's' (step) thread from the previous Hg ?
>
> I fear we'd be switching from one broken behavior to
> another. Since new stubs can just vCont, I'm now
> inclined to leave things as is.
Ok, I am fine with that.
Tomas
prev parent reply other threads:[~2011-05-17 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 16:27 Tomas Martinec
2011-05-10 18:37 ` Pedro Alves
2011-05-11 6:06 ` Tomas Martinec
2011-05-11 17:29 ` Pedro Alves
2011-05-12 10:45 ` Tomas Martinec
2011-05-16 11:17 ` Pedro Alves
2011-05-16 15:23 ` Tomas Martinec
2011-05-17 12:03 ` Pedro Alves
2011-05-17 14:07 ` Tomas Martinec [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=BANLkTimPbpfPXb7mDbSRyRPZyOu4xn_6-A@mail.gmail.com \
--to=fyzmat@gmail.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.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