Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Stan Shebs <stan@codesourcery.com>
Subject: Re: [PATCH/commit] Handle errors in tracepoint target agent
Date: Fri, 26 Mar 2010 12:40:00 -0000	[thread overview]
Message-ID: <4BACAB4A.2060005@codesourcery.com> (raw)
In-Reply-To: <201003261113.40865.pedro@codesourcery.com>

Pedro Alves wrote:
> On Friday 26 March 2010 01:55:50, Stan Shebs wrote:
>   
>> For the record, here's what I ended up committing.  
>>     
>
> (For the record, if a patch ends up different to how it was
> being discussed, a chance for commenting before checking in
> would be really appreciated.)
>   
It seemed uncontroversial, but I guess not. :-)
> +	      for (p = p1; p < p2; p++)
> +		if (!((*p >= '0' && *p <= '9')
> +		      || (*p >= 'a' && *p <= 'f')
> +		      || (*p >= 'A' && *p <= 'F')))
> +		  break;
>   
Oh triple yuck.  Let's just make a new utility function - an ishex-type 
test shouldn't be coded more than once, or maybe twice, in a program.
> If you really insist in handling this in FSF gdb as well,
> then I'd like to merge this patch above to head, otherwise, 
> I'd rather just remove all the plain string handling from
> FSF gdb, and put that patch in our tree only.  (I don't
> really see the point in carrying that workaround forever in
> FSF gdb).
>   
Alright alright.  My interest in the subject is now totally exhausted, 
we'll just do the hex strings here.

Stan


  reply	other threads:[~2010-03-26 12:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26  1:56 Stan Shebs
2010-03-26 11:13 ` Pedro Alves
2010-03-26 12:40   ` Stan Shebs [this message]
2010-03-26 13:38     ` Pedro Alves
2010-03-26 14:17       ` Pedro Alves
2010-03-26 11:40 ` Pedro Alves
2010-03-26 12:50   ` Stan Shebs
2010-03-26 14:44     ` Pedro Alves
2010-03-26 15:20       ` Stan Shebs
2010-03-26 15:28         ` Eli Zaretskii
2010-03-26 15:53         ` 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=4BACAB4A.2060005@codesourcery.com \
    --to=stan@codesourcery.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