Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Andrew Cagney <ac131313@ges.redhat.com>,
	Joel Brobecker <brobecker@gnat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA/controversial] move bp by line number past the prologue
Date: Thu, 29 Aug 2002 15:30:00 -0000	[thread overview]
Message-ID: <3D6E9D28.E3A974FA@redhat.com> (raw)
In-Reply-To: <1020829214626.ZM24781@localhost.localdomain>

Kevin Buettner wrote:
> 
> On Aug 29,  4:33pm, Andrew Cagney wrote:
> 
> > > I've reread the thread in which this matter was discussed earlier
> > > (i.e, the "[RFC] breakpoints and function prologues" messages).  Given
> > > that there was such disagreement before, I doubt that everyone will
> > > agree with my point of view.  If this turns out to be the case, might
> > > I suggest a user settable option for controlling whether setting a
> > > breakpoint by line number will always cause the prologue to be
> > > skipped?  That way both sides get the behavior they want.  (GUIs can
> > > set the desired behavior at initialization time.)
> >
> > GUI and CLI behavior should be kept independant.  Running GDB under a
> > GUI, should not affect the CLI.
> 
> Perhaps a different interface is needed for the GUI to use?

I think I would prefer that.  In fact, in order of preference, 
I would prefer:

1) Teach the GUI users that the open curly brace represents the
prologue.
2) see 1.
3) see 1.
4) Provide an interface for GUIs to skip the prologue in this context.
5)....
....
...
...
99) Change the command line behavior.


  reply	other threads:[~2002-08-29 22:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 11:37 Joel Brobecker
2002-08-29 13:20 ` Kevin Buettner
2002-08-29 13:37   ` Andrew Cagney
2002-08-29 14:50     ` Kevin Buettner
2002-08-29 15:30       ` Michael Snyder [this message]
2002-08-30 12:06   ` Joel Brobecker
2002-08-30 17:55     ` Joel Brobecker

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=3D6E9D28.E3A974FA@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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