Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [patch] ia64: Fix breakpoints memory shadow
Date: Sat, 22 Nov 2008 19:08:00 -0000	[thread overview]
Message-ID: <uy6zchubn.fsf@gnu.org> (raw)
In-Reply-To: <20081120144936.GA25926@host0.dyn.jankratochvil.net>

> Date: Thu, 20 Nov 2008 15:49:36 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
> 
> gdb/doc/
> 2008-11-20  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* gdbint.texinfo (Target Conditionals): Extend the
> 	gdbarch_breakpoint_from_pc description.

This part is approved, thanks.

However, I'm slightly worried by these parts in your code:

> +  instr_breakpoint = slotN_contents (bundle_mem, slotnum);
> +  if (instr_breakpoint != IA64_BREAKPOINT)
> +    warning (_("Breakpoint removal cannot find the placed breakpoint at %s"),
> +             paddr_nz (bp_tgt->placed_address));

Can this happen as part of normal GDB behavior?  If not, we should
make this internal_error, I think.  If indeed this is a warning, we
should tell users what to do with such a warning, either as part of
the message or at least in the manual.

> +  if (slotnum > 2)
> +    error (_("Can't insert breakpoint for slot numbers greater than 2."));

Similarly here: assuming slot numbers are not something exposed to the
user, I'd be bewildered if presented with such a message.  If this is
an internal GDB error (a.k.a. bug), let's treat it like one.

(Yes, I do realize that there's already a similar call to `error'
elsewhere in the existing GDB code.  My comments apply to that place
as well.)


  parent reply	other threads:[~2008-11-22 11:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 17:52 Jan Kratochvil
2008-10-30  1:51 ` Joel Brobecker
2008-10-31  0:03   ` Jan Kratochvil
2008-11-01 18:54     ` Joel Brobecker
2008-11-11 20:20       ` Jan Kratochvil
2008-11-13 14:27         ` Joel Brobecker
2008-11-21  1:11           ` Jan Kratochvil
2008-11-22 18:35             ` Joel Brobecker
2008-11-22 19:08             ` Eli Zaretskii [this message]
2008-11-24  2:25               ` Joel Brobecker
2008-11-24  7:09                 ` Jan Kratochvil
2008-11-25 17:49                   ` Joel Brobecker
2008-11-27  0:41                     ` Jan Kratochvil

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=uy6zchubn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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