Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [gdbserver/patch] Z packet support
Date: Thu, 24 Feb 2005 20:53:00 -0000	[thread overview]
Message-ID: <20050224203834.GB11751@nevyn.them.org> (raw)
In-Reply-To: <41FF7127.5030604@axis.com>

On Tue, Feb 01, 2005 at 01:08:07PM +0100, Orjan Friberg wrote:
> Daniel Jacobowitz wrote:
> >
> >You missed the most important problem with the previous posting, I'm
> >afraid - it's still whitespace mangled.  Please don't send patches
> >using format=flowed; it's very good for text, but lousy for data.
> >Either disable it or just attach them.  I've more or less figured out
> >the algorithm by which it ate your patch, but it's pretty tedious to
> >hand-merge; could you resend?
> 
> Sure.  (Until I figure it out, I'll be attaching patches instead of 
> inlining them.  Sorry for the trouble.)
> 
> >CORE_ADDR is always a long long in gdbserver, so your sizeof (addr)
> >probably doesn't work right for 32-bit targets.  I guess sizeof (void
> >*) is always right for this, though... at least for the kinds of
> >targets gdbserver supports now.
> 
> FWIW, recurse.exp and watchpoints.exp ran fine on CRISv32 (32-bit target) 
> when a 64-bit address was sent.  I changed it nonetheless, and tweaked the 
> comment.

I was going to implement the matching bits for i386, but never found
the time.  No point in my holding up your work any longer.  I am still
not clear on how this will handle threads but it sounds like CRIS
kernel bugs mean that that doesn't matter to you; it's irrelevant if
you've only got one copy of the debug registers.  I may come back to
revisit the names of the functions if anyone ever implements hardware
breakpoint support.

The patch is OK.  Please make sure to include a full changelog entry,
and update the copyright years in any files you touch.


-- 
Daniel Jacobowitz
CodeSourcery, LLC


  parent reply	other threads:[~2005-02-24 20:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 15:13 Orjan Friberg
2004-12-07  2:44 ` Daniel Jacobowitz
2004-12-16 18:46   ` Orjan Friberg
2005-01-12 13:35   ` Orjan Friberg
2005-01-30  4:40     ` Daniel Jacobowitz
2005-02-01 12:09       ` Orjan Friberg
2005-02-14 14:42         ` Orjan Friberg
2005-02-24 20:53         ` Daniel Jacobowitz [this message]
2005-05-12 12:34           ` Orjan Friberg
2005-01-30 15:32 Paul Schlie
2005-01-30 15:38 ` Daniel Jacobowitz
2005-01-30 15:57   ` Paul Schlie
2005-01-30 17:36     ` Daniel Jacobowitz
2005-01-30 19:55       ` Paul Schlie
2005-01-30 20:38         ` Daniel Jacobowitz

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=20050224203834.GB11751@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=orjan.friberg@axis.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