Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA,RFC] TARGET_ADJUST_BREAKPOINT_ADDRESS - patch 3 of 4
Date: Tue, 07 Oct 2003 21:55:00 -0000	[thread overview]
Message-ID: <6480-Tue07Oct2003234954+0200-eliz@elta.co.il> (raw)
In-Reply-To: <1031004064353.ZM25456@localhost.localdomain> (message from Kevin Buettner on Fri, 3 Oct 2003 23:43:53 -0700)

> Date: Fri, 3 Oct 2003 23:43:53 -0700
> From: Kevin Buettner <kevinb@redhat.com>
> 
> I would also like to hear from Eli.  If it's not clear from my words
> above, I'll state again that I feel very strongly that a warning is
> more appropriate than a mere informational message which might be
> missed by the user.  The adjustment of a breakpoint *should* cause the
> user to be alarmed since the expected breakpoint behavior could be
> significantly altered.
> 
> So...
> 
> Michael S: Okay?
> 
> Eli: Comments?

First, let me thank you so much for taking the time to explain this
issue in so many words, let alone investigate the problems and write
the code and the docs.

As for the issue itself: I'm not 100% sold on your arguments, but
given my total lack of experience with any platform like the FR-V, I
don't see how I can in good faith avoid a total surrender! ;-)

So it's okay with me to have this as a warning, but let me make 2
suggestions that will allow me to swallow this frog and smile, too:

  . Please add some of the technical reasons for breakpoint
    adjustment into gdbint.texinfo (yes, I know that you wrote a
    patch for that, but the message I'm replying to has so much more
    info that it'd be a pity not to retain some of it for posterity).

  . Please add to gdb.texinfo a description of the warning message,
    whereby the exact message is cited followed by an explanation of
    why is this of interest to the user (e.g., that code rearrangement
    could have messed up line numbers, and the user should consider
    putting a breakpoint on other/additional lines).  Please add a
    @cindex entry to that description citing the beginning of the
    message text, like this:

     @cindex breakpoint address adjusted

    This way, a user who wants to understand the message needs to
    type "i breakpoint address adjusted RET" and read the node
    presented to her.

Thanks again for all your efforts.


  reply	other threads:[~2003-10-07 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04  6:44 Kevin Buettner
2003-10-07 21:55 ` Eli Zaretskii [this message]
2003-10-07 23:12 ` Michael Snyder
2003-10-13 23:54   ` Kevin Buettner

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=6480-Tue07Oct2003234954+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --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