From: Daniel Jacobowitz <drow@false.org>
To: Jitendra Pawar <jitendra@linsyssoft.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: h/w watchpoint pointer initialization patch.
Date: Sun, 22 Jan 2006 20:22:00 -0000 [thread overview]
Message-ID: <20060122202214.GA27224@nevyn.them.org> (raw)
In-Reply-To: <1137490473.3508.33.camel@chanakya.linsyssoft.com>
On Tue, Jan 17, 2006 at 03:04:33PM +0530, Jitendra Pawar wrote:
> Hi All,
> While debugging cvs gdb, I put a h/w watch point, when this watch point
> hits gdb calls target_insert_watchpoint macro. This macro defination is
> present in target.h as bellow:
>
> #define target_insert_watchpoint(addr, len, type) \
> (*current_target.to_insert_watchpoint) (addr, len, type)
>
> In case of remote debugging *current_target.to_insert_watchpoint points
> to remote_target_insert_watchpoint function, but while native debugging
> it should points to <host_arch>_insert_watchpoint (e.g.
> i386_insert_watchpoint) instead it points to return_minus_one function.
>
> This patch removes declaration of macros in file gdb/config/i386/nm-
> i386.h for insertion and removal of h/w watchpoints. Instead it
> initializes register access methods in gdb/i386-linux-nat.c file.
> That fixes the above problem.
I can't understand your explanation - what went wrong? Why? If you're
running a native i386-linux GDB, then nm-i386.h should have been
included before target.h, and the right function should have been
called.
Do you mean it the other way round, i.e. that you needed this patch for
watchpoints to work when remote debugging? In which case something
like this is definitely necessary; but the patch can't be right because
Linux isn't the only i386 target using nm-i386.h. They all need to be
converted together.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-01-22 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 9:35 Jitendra Pawar
2006-01-22 20:22 ` Daniel Jacobowitz [this message]
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=20060122202214.GA27224@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jitendra@linsyssoft.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