From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA] Make ppc-linux-nat insert/remove breakpoint and watchpoint functions return -1.
Date: Wed, 06 Jul 2011 16:12:00 -0000 [thread overview]
Message-ID: <20110706161150.GD2407@adacore.com> (raw)
In-Reply-To: <m3vcvfpic9.fsf@fleche.redhat.com>
> >>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
>
> Thiago> target_{insert,remove}_{hw_breakpoint,watchpoint,mask_watchpoint} are
> Thiago> supposed to return 0, 1 and -1 for success, unsupported and error,
> Thiago> respectively.
>
> I looked around for anything saying this, and couldn't find it.
> Well -- I found it for target_insert_mask_watchpoint, but not other
> cases.
>
> And, at least in breakpoint.c:insert_bp_location, it seems to me that
> the return value is expected to be an errno in one case -- search for
> safe_strerror.
>
> Maybe this code is in error? I really couldn't say; but it seems
> inconsistent at best. Perhaps only parts of your patch could go in
> as-is, what do you think?
Looking at target.h:
| /* Insert a breakpoint at address BP_TGT->placed_address in the target
| machine. Result is 0 for success, or an errno value. */
|
| extern int target_insert_breakpoint (struct gdbarch *gdbarch,
| struct bp_target_info *bp_tgt);
It's a little bit confusing because some methods are implemented
inside the target_ops vector, while some others are documented
via the target_... function. That being said, it's ultra important
IMO in that case that we add the documentation wherever missing,
because these are used by all ports. And I remember scratching
my head quite a bit a while ago when I was working on watchpoint
support for VxWorks.
In any case, all this rambling to say that breakpoint.c is correct
in this case.
--
Joel
next prev parent reply other threads:[~2011-07-06 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 20:29 Thiago Jung Bauermann
2011-07-06 15:03 ` Tom Tromey
2011-07-06 16:12 ` Joel Brobecker [this message]
2011-07-06 16:36 ` Joel Brobecker
2011-07-06 19:38 ` Thiago Jung Bauermann
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=20110706161150.GD2407@adacore.com \
--to=brobecker@adacore.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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