From: Kevin Buettner <kevinb@redhat.com>
To: Grace Sainsbury <graces@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa] insert_hw_breakpoint
Date: Mon, 12 Aug 2002 13:27:00 -0000 [thread overview]
Message-ID: <1020812202745.ZM918@localhost.localdomain> (raw)
In-Reply-To: Grace Sainsbury <graces@redhat.com> "[rfa] insert_hw_breakpoint" (Aug 12, 4:04pm)
On Aug 12, 4:04pm, Grace Sainsbury wrote:
> - len = strlen (shadow);
> - len = len ? len : 1;
> + BREAKPOINT_FROM_PC (&addr, &len);
> +
> if (remote_protocol_Z[Z_PACKET_HARDWARE_BP].support == PACKET_DISABLE)
> error ("Can't set hardware breakpoint without the '%s' (%s) packet\n",
> remote_protocol_Z[Z_PACKET_HARDWARE_BP].name,
> @@ -5027,7 +5027,8 @@
> char *buf = alloca (rs->remote_packet_size);
> char *p = buf;
>
> - len = sizeof (shadow);
> + BREAKPOINT_FROM_PC (&addr, &len);
> +
> if (remote_protocol_Z[Z_PACKET_HARDWARE_BP].support == PACKET_DISABLE)
> error ("Can't clear hardware breakpoint without the '%s' (%s) packet\n",
> remote_protocol_Z[Z_PACKET_HARDWARE_BP].name,
Do stubs actually care about this length field for the packets under
consideration?
I agree that the use of strlen() and sizeof() seem dubious if not
outright wrong, but, unfortunately, not all architectures can define
a sensible BREAKPOINT_FROM_PC. (*) I would like to see gdb relying less
on BREAKPOINT_FROM_PC, not more.
(*) E.g, IA-64. For IA-64, I did define a BREAKPOINT_FROM_PC, but I
would have preferred not to. The values returned by
ia64_breakpoint_from_pc() are fairly arbitrary and are of absolutely
no use for saving/restoring actual breakpoints.
Kevin
next prev parent reply other threads:[~2002-08-12 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 13:04 Grace Sainsbury
2002-08-12 13:27 ` Kevin Buettner [this message]
2002-08-13 8:59 ` Andrew Cagney
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=1020812202745.ZM918@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=graces@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