From: Michael Snyder <msnyder@vmware.com>
To: Doug Evans <dje@google.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
"eliz@gnu.org" <eliz@gnu.org>,
"pedro@codesourcery.com" <pedro@codesourcery.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
"temp@sourceboost.com" <temp@sourceboost.com>
Subject: Re: Getting pissed off by gdb. Please help with stepping in.
Date: Thu, 18 Mar 2010 20:51:00 -0000 [thread overview]
Message-ID: <4BA29262.1080509@vmware.com> (raw)
In-Reply-To: <e394668d1003181343j42e9354eka076afaf715ed2d7@mail.gmail.com>
Doug Evans wrote:
> On Thu, Mar 18, 2010 at 12:53 PM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>>> Date: Thu, 18 Mar 2010 21:38:18 +0200
>>> From: Eli Zaretskii <eliz@gnu.org>
>>>
>>>> From: Pedro Alves <pedro@codesourcery.com>
>>>> Date: Thu, 18 Mar 2010 18:55:39 +0000
>>>> Cc: dje@google.com,
>>>> temp@sourceboost.com
>>>>
>>>> Users often find this behaviour unexpected (I've often
>>>> wished GDB would behave like what the OP is suggesting too).
>>> Then why don't we change the behavior to match what users expect?
>> 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!
>
> That argument is pretty weak too IMO.
> This isn't a VS vs GDB discussion.
Am I the only one who remembers that gdb used to have the behavior that
is being discussed, and it was deliberately changed to behave the way it
does today?
My admittedly fallable memory cells are telling me that it was Fernando
Nasser who championed the change, which means that it would have been
at least five years ago.
If I am right, the argument then was that the new behavior (what gdb
has today) was closer to what users would expect.
next prev parent reply other threads:[~2010-03-18 20:51 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 [this message]
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
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=4BA29262.1080509@vmware.com \
--to=msnyder@vmware.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=pedro@codesourcery.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