From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: rearnsha@arm.com
Cc: eliz@gnu.org, pedro@codesourcery.com, gdb@sourceware.org,
dje@google.com, temp@sourceboost.com
Subject: Re: Getting pissed off by gdb. Please help with stepping in.
Date: Fri, 19 Mar 2010 10:41:00 -0000 [thread overview]
Message-ID: <201003191039.o2JAdKtj018316@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <1268992264.6009.4.camel@e200601-lin.cambridge.arm.com> (message from Richard Earnshaw on Fri, 19 Mar 2010 09:51:04 +0000)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
> From: Richard Earnshaw <rearnsha@arm.com>
> Date: Fri, 19 Mar 2010 09:51:04 +0000
>
> On Thu, 2010-03-18 at 20:53 +0100, Mark Kettenis wrote:
>
> > Because different users expect different things. I for example would
> > be somewhat annoyed by having to issue an extra "step". And the
> > argument that this is what people that are familliar with Visual
> > Studio are used to is pretty weak. GDB users are used the GDB behaviour!
>
> They might be used to it, but that won't stop them hating it! I'm in
> agreement with those that want step at the end of a function to not
> enter then next call. It's a right royal pain having to have a sequence
> such as
>
> step
> <ret>
> <ret>
> <ret>
>
> &*%^%^£$*&(*^ I've done one too many <ret>s, now I've got to restart my
> debugging session and do it all again
>
> step
> <ret>
> <ret>
> finish
> step
Sorry, but I must be missing something. Howe can you end up doing too
many "step"s in the foo(bar()) scenario? I mean, if you do one step
too many, finding yourself stepping into foo() wheras you really
wanted to step over foo(), you can simply use "finish". There is no
need to restart your session.
next prev parent reply other threads:[~2010-03-19 10:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 2:39 temp
2010-03-18 3:00 ` Hui Zhu
2010-03-18 3:03 ` Nathan Froyd
2010-03-18 7:22 ` Doug Evans
2010-03-18 9:07 ` Eli Zaretskii
2010-03-18 15:10 ` Doug Evans
2010-03-18 15:21 ` Pedro Alves
2010-03-18 18:33 ` Eli Zaretskii
2010-03-18 18:55 ` Pedro Alves
2010-03-18 19:38 ` Eli Zaretskii
2010-03-18 19:54 ` Mark Kettenis
2010-03-18 20:43 ` Doug Evans
2010-03-18 20:51 ` Michael Snyder
2010-03-18 21:17 ` Pedro Alves
2010-03-18 21:12 ` Eli Zaretskii
2010-03-18 23:37 ` Paul Hilfinger
2010-03-19 9:51 ` Richard Earnshaw
2010-03-19 10:41 ` Mark Kettenis [this message]
2010-03-19 13:19 ` Eli Zaretskii
2010-03-19 10:19 ` André Pönitz
2010-03-18 15:28 ` Doug Evans
2010-03-18 18:31 ` Eli Zaretskii
2010-03-18 18:37 ` Paul Koning
2010-03-18 19:06 ` Doug Evans
2010-03-18 20:48 ` Jonas Maebe
2010-03-18 13:33 ` Daniel Jacobowitz
2010-03-18 14:06 ` André Pönitz
2010-03-18 14:13 ` Daniel Jacobowitz
2010-03-18 14:33 ` André Pönitz
2010-03-18 14:39 ` Daniel Jacobowitz
2010-03-18 14:54 ` André Pönitz
2010-03-18 15:40 ` Doug Evans
2010-03-18 17:41 ` Michael Snyder
2010-03-18 22:44 ` temp
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=201003191039.o2JAdKtj018316@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=rearnsha@arm.com \
--cc=temp@sourceboost.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