From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@codesourcery.com>, Doug Evans <dje@google.com>
Subject: Re: [patch] gdbserver: Add support for Z0/Z1 packets
Date: Mon, 22 Jun 2009 19:39:00 -0000 [thread overview]
Message-ID: <4A3FDDCA.2010106@qnx.com> (raw)
In-Reply-To: <200906202301.52782.pedro@codesourcery.com>
Pedro Alves wrote:
> On Friday 19 June 2009 14:55:56, Aleksandar Ristovski wrote:
>
>> RCS file: /cvs/src/src/gdb/gdbserver/target.h,v
>> retrieving revision 1.36
>> diff -u -p -r1.36 target.h
>> --- target.h 1 Apr 2009 22:50:24 -0000 1.36
>> +++ target.h 19 Jun 2009 13:47:44 -0000
>> @@ -213,6 +213,14 @@ struct target_ops
>> int (*read_auxv) (CORE_ADDR offset, unsigned char *myaddr,
>> unsigned int len);
>>
>> + /* Insert and remove breakpoint. Argument TYPE can be:
>> + '0' = software-breakpoint
>> + '1' = hardware-breakpoint
>
> ^ spurious space
>
>> + Returns 0 if successful, 1 otherwise. */
>> +
>> + int (*insert_breakpoint) (char type, CORE_ADDR addr);
>> + int (*remove_breakpoint) (char type, CORE_ADDR addr);
>
> Z0 and Z1 breakpoints also take a 'len' argument, just
> like Z2-Z4. You should also pass those down.
>
> But, Let's take a step back --- why not just rename the
> insert_watchpoint|remove_watchpoint functions to insert_point,remove_point,
> and relax the type checks in server.c:
That was my initial implementation, prior to proposing the
change. Then I looked at target ops in gdb; there we have
two different functions for breakpoint and watchpoint so I
followed that logic (even though the logic there seems to be
incomplete: there is a pair for hw and non-hw breakponts but
only one pair for watchpoints).
But either way is fine with me - just let me know.
Thanks,
--
Aleksandar Ristovski
QNX Software Systems
next prev parent reply other threads:[~2009-06-22 19:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 1:20 Aleksandar Ristovski
2009-06-17 1:35 ` Aleksandar Ristovski
2009-06-19 7:08 ` Doug Evans
2009-06-19 13:56 ` Aleksandar Ristovski
2009-06-20 22:01 ` Pedro Alves
2009-06-22 19:39 ` Aleksandar Ristovski [this message]
2009-06-22 22:46 ` Pedro Alves
2009-06-23 15:18 ` Aleksandar Ristovski
2009-06-23 15:59 ` Pedro Alves
2009-06-23 16:57 ` Aleksandar Ristovski
2009-06-24 18:51 ` Aleksandar Ristovski
2009-06-24 19:01 ` Doug Evans
2009-06-24 19:04 ` Aleksandar Ristovski
2009-06-24 19:10 ` Doug Evans
2009-06-24 19:10 ` Pedro Alves
2009-06-24 19:20 ` Aleksandar Ristovski
2009-06-24 19:28 ` Pedro Alves
2009-06-24 19:25 ` Aleksandar Ristovski
2009-06-25 22:18 ` Pedro Alves
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=4A3FDDCA.2010106@qnx.com \
--to=aristovski@qnx.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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