Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [WIP] pending breakpoint support
Date: Wed, 19 Nov 2003 19:47:00 -0000	[thread overview]
Message-ID: <8765hg5eux.fsf@fleche.redhat.com> (raw)
In-Reply-To: <3FBAC14D.4060002@redhat.com>

>>>>> "Jeff" == J Johnston <jjohnstn@redhat.com> writes:

Jeff> I have been hacking around with supporting "future-break"
Jeff> functionality (note, I said "hacking").

Jeff> If the call fails, then I simply give the user the option as
Jeff> marking it as pending.

This sounds great for interactive use.  For breakpoints set by IDEs,
it would be useful to have flag saying "please mark this as pending".

For instance, Insight saves all the breakpoints you set.  When opening
an old session, it tries to set them again programatically.  In this
case we already know the breakpoint is ok (or was last time around,
which is "close enough"), so we'd like not to ask the user anything.
There are similar scenarios for Emacs and Eclipse.

Tom


  parent reply	other threads:[~2003-11-19 19:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19  1:03 J. Johnston
2003-11-19  6:03 ` Eli Zaretskii
2003-11-19 15:07 ` Daniel Jacobowitz
2003-11-19 23:32   ` J. Johnston
2003-11-19 23:52     ` Andrew Cagney
2003-11-21 22:46     ` J. Johnston
2003-11-25 23:20       ` Thomas Fitzsimmons
2003-11-26 20:02         ` J. Johnston
2003-11-26 20:30           ` Michael Snyder
2003-11-26 21:23             ` Thomas Fitzsimmons
2003-11-26 14:37       ` Andrew Cagney
2003-12-05  4:57       ` Daniel Jacobowitz
2003-11-19 19:47 ` Tom Tromey [this message]
     [not found] <1069259237.12557.ezmlm@sources.redhat.com>
2003-11-19 19:38 ` Jim Ingham

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=8765hg5eux.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@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