Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nicholas Clifton <nickc@redhat.com>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>,
	       Binutils Development <binutils@sourceware.org>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [buildbot] GDB regression on 85880250e591a51624d24db653aaace0c5ce5943
Date: Fri, 09 Jan 2015 21:59:00 -0000	[thread overview]
Message-ID: <54B04F25.6080206@redhat.com> (raw)
In-Reply-To: <87h9w34nso.fsf@sergiodj.net>

Hi Sergio,

> Nick's commit:

Thanks for reporting this.  I have fixed the bug with the patch below.

> On a side note, I can't find Nick's message mentioning the patch on the
> binutils ml.

That's because the message is in PR 17512, where a lot of the recent 
patches to minor file formats can be found.

Cheers
   Nick

bfd/ChangeLog

2015-01-09  Nick Clifton  <nickc@redhat.com>

	* tekhex.c (getvalue): Fix thinko in test for correct extraction
	of value.
	(getsym): Return false if there was not enough data to extract the
	symbol.

diff --git a/bfd/tekhex.c b/bfd/tekhex.c
index 9444117..94b4773 100644
--- a/bfd/tekhex.c
+++ b/bfd/tekhex.c
@@ -288,7 +288,7 @@ getvalue (char **srcp, bfd_vma *valuep, char * endp)

    *srcp = src;
    *valuep = value;
-  return len == 0;
+  return len == -1U;
  }

  static bfd_boolean
@@ -309,7 +309,7 @@ getsym (char *dstp, char **srcp, unsigned int *lenp, 
char * endp)
    dstp[i] = 0;
    *srcp = src + i;
    *lenp = len;
-  return TRUE;
+  return i == len;
  }

  static struct data_struct *


  reply	other threads:[~2015-01-09 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 21:11 Sergio Durigan Junior
2015-01-09 21:59 ` Nicholas Clifton [this message]
2015-01-09 22:24   ` Sergio Durigan Junior

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=54B04F25.6080206@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@sergiodj.net \
    /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