From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch 2/2] Add hppa-linux target to gdb
Date: Mon, 05 Apr 2004 20:02:00 -0000 [thread overview]
Message-ID: <4071BB3B.3080304@gnu.org> (raw)
In-Reply-To: <20040404174532.GR750@tausq.org>
> * config/pa/nm-linux.h: New file.
With regard to the nm- additions, many of these:
> +#define CANNOT_FETCH_REGISTER(regno) pa_cannot_fetch_register(regno)
> +extern int pa_cannot_fetch_register (int regno);
> +
> +#define CANNOT_STORE_REGISTER(regno) pa_cannot_store_register(regno)
> +extern int pa_cannot_store_register (int regno);
> +
> +#define HAVE_STEPPABLE_WATCHPOINT 1
> +#define STOPPED_BY_WATCHPOINT(W) \
> + pa_linux_stopped_by_watchpoint (PIDGET(inferior_ptid))
> +extern CORE_ADDR pa_linux_stopped_by_watchpoint (int);
> +
> +#define target_insert_watchpoint(addr, len, type) \
> + pa_linux_insert_watchpoint (PIDGET(inferior_ptid), addr, len, type)
> +extern int pa_linux_insert_watchpoint (int pid, CORE_ADDR addr,
> + int len, int rw);
> +
> +#define target_remove_watchpoint(addr, len, type) \
> + pa_linux_remove_watchpoint (PIDGET(inferior_ptid), addr, len)
> +extern int pa_linux_remove_watchpoint (int pid, CORE_ADDR addr, int len);
> +
> +/* Hardware watchpoints */
> +
> +#define TARGET_HAS_HARDWARE_WATCHPOINTS
> +
> +#define TARGET_CAN_USE_HARDWARE_WATCHPOINT(type, cnt, ot) \
> + (type == bp_hardware_watchpoint)
> +
now live in the target vector. Can I suggest removing them for the
moment, we can come back to it later.
For the tm- file, it, other than for shlibs, shouldn't be necessary.
We're all going to need to finish multi-arching this beastie.
Andrew
next prev parent reply other threads:[~2004-04-05 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 17:44 Randolph Chung
2004-04-04 17:47 ` Randolph Chung
2004-04-05 20:02 ` Andrew Cagney [this message]
2004-04-05 20:05 ` Randolph Chung
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=4071BB3B.3080304@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.org \
/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