From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: Re: Single stepping and threads
Date: Wed, 29 Nov 2006 16:38:00 -0000 [thread overview]
Message-ID: <20061129163844.GN9968@adacore.com> (raw)
In-Reply-To: <20061129132535.GA28834@nevyn.them.org>
> > I would say yes. A step should be a few instructions, while stepping
> > over a call is potentially a much larger number of instructions.
> > As a result, stepping over without letting the other threads go would
> > more likely cause a lock.
>
> I think you mean "no" then?
Oops, sorry, I meant "no".
One of my coworkers expressed his opinion as follow:
<<
I would find it confusing if "step" and "next" behave differently with
respect to threads, because they seem like basically the same thing.
"Next is just like step, except that it goes over calls" seems simple to
me. "Next is just like step, except that it goes over calls, and has
some subtle difference regarding threads" seems more complicated to me.
So I would suggest leaving the default as "off", or else changing it
to "on".
>>
--
Joel
next prev parent reply other threads:[~2006-11-29 16:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 5:29 Daniel Jacobowitz
2006-11-29 5:58 ` Joel Brobecker
2006-11-29 13:25 ` Daniel Jacobowitz
2006-11-29 16:38 ` Joel Brobecker [this message]
2006-11-30 13:54 ` Daniel Jacobowitz
2006-11-30 23:36 ` Michael Snyder
2006-11-30 23:54 ` Joel Brobecker
2006-12-01 1:02 ` Daniel Jacobowitz
2006-12-01 22:43 ` Michael Snyder
2006-12-02 16:27 ` Rob Quill
2006-12-02 16:33 ` Daniel Jacobowitz
2006-12-02 16:36 ` Joel Brobecker
2006-12-04 19:50 ` Michael Snyder
2006-11-30 8:44 ` Robert Dewar
2006-11-30 23:32 ` Michael Snyder
2006-11-30 23:26 ` Michael Snyder
2006-11-30 23:31 ` Joel Brobecker
2006-11-29 12:41 ` Mark Kettenis
2006-11-29 13:36 ` Daniel Jacobowitz
2006-11-30 23:38 ` Michael Snyder
2006-11-30 23:22 ` Michael Snyder
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=20061129163844.GN9968@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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