From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [gdbserver/rfa] CRIS/CRISv32 gdbserver support (part 2)
Date: Mon, 14 Feb 2005 16:17:00 -0000 [thread overview]
Message-ID: <4210936A.2080408@axis.com> (raw)
In-Reply-To: <41FF9274.7030700@axis.com>
Orjan Friberg wrote:
>>
>> What to do about the threaded case? GDB is having so much trouble
>> getting it right that I'd like to make sure gdbserver does from the
>> start.
>>
>> I guess this can be handled completely in the linux-low wrapper
>> functions by switching the current thread and setting watchpoints for
>> each. I think that is correct for all Linux targets using hardware
>> watchpoints, because of the nature of Linux threading.
>
>
> For CRISv32, there might be an additional problem lurking in the
> shadows: we treat the watchpoint registers as global (i.e., only one
> process at a time can use them, and thus they are not saved/restored on
> context switches etc).
>
> Anyway, is this something you want resolved before I commit the
> CRIS/CRISv32 support? (Here's an updated ChangeLog entry and updated
> patches if not.)
Two week ping. (If you want the multi-threaded watchpoint support issue
resolved before the commit please elaborate, if possible, on what needs to be done.)
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2005-02-14 12:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 9:54 Orjan Friberg
2005-01-30 4:54 ` Daniel Jacobowitz
2005-02-01 14:31 ` Orjan Friberg
2005-02-14 16:17 ` Orjan Friberg [this message]
2005-02-24 20:57 ` Daniel Jacobowitz
2005-05-12 13:03 ` Orjan Friberg
2005-05-12 13:11 ` Orjan Friberg
2005-05-12 13:21 ` Daniel Jacobowitz
2005-05-12 13:13 ` Daniel Jacobowitz
2005-05-12 14:59 ` Orjan Friberg
2005-05-18 1:55 ` Daniel Jacobowitz
2005-05-23 12:35 ` Orjan Friberg
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=4210936A.2080408@axis.com \
--to=orjan.friberg@axis.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.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