From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: gdb-patches@sourceware.org
Subject: [commit] Fix condition (Re: [patch] Verify byte-by-byte if both files are the same on "remote:")
Date: Tue, 11 Oct 2011 19:07:00 -0000 [thread overview]
Message-ID: <201110111906.p9BJ6h8k023538@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20111010202141.GA27651@host1.jankratochvil.net> from "Jan Kratochvil" at Oct 10, 2011 10:21:42 PM
Jan Kratochvil wrote:
> + if (verified_as_different || parent_objfile->crc32 != crc)
> + warning (_("the debug information found in \"%s\""
> + " does not match \"%s\" (CRC mismatch).\n"),
> + name, parent_objfile->name);
I just noticed that this still causes spurious warnings since the
condition is incorrect: we want to skip the warning if the parent's
CRC matches the (potential) debuginfo *file* CRC, not the CRC the
debuginfo is supposed to have.
Fixed by the patch below. Tested on arm-linux-gnueabi in remote
testing using --with-sysroot=remote: with no more spurious CRC
mismatch warnings. Committed to mainline as obvious.
Bye,
Ulrich
ChangeLog:
* symfile.c (separate_debug_file_exists): Fix condition.
Index: gdb/symfile.c
===================================================================
RCS file: /cvs/src/src/gdb/symfile.c,v
retrieving revision 1.318
diff -u -p -r1.318 symfile.c
--- gdb/symfile.c 11 Oct 2011 12:58:08 -0000 1.318
+++ gdb/symfile.c 11 Oct 2011 18:33:12 -0000
@@ -1418,7 +1418,7 @@ separate_debug_file_exists (const char *
return 0;
}
- if (verified_as_different || parent_objfile->crc32 != crc)
+ if (verified_as_different || parent_objfile->crc32 != file_crc)
warning (_("the debug information found in \"%s\""
" does not match \"%s\" (CRC mismatch).\n"),
name, parent_objfile->name);
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2011-10-11 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 13:53 [rfc] False separate debuginfo warning with "remote:" access Ulrich Weigand
2011-10-10 8:38 ` [patch] Verify byte-by-byte if both files are the same on "remote:" [Re: [rfc] False separate debuginfo warning with "remote:" access] Jan Kratochvil
2011-10-10 8:49 ` Jan Kratochvil
2011-10-10 13:48 ` [patch] Verify byte-by-byte if both files are the same on "remote:" [Re: [rfc] False separate debuginfo warning with "remote:" Ulrich Weigand
2011-10-10 20:22 ` Jan Kratochvil
2011-10-10 21:23 ` [patch] Verify byte-by-byte if both files are the same on "remote:" [Re: [rfc] False separate debuginfo warning with "remot Ulrich Weigand
2011-10-11 12:58 ` Jan Kratochvil
2011-10-11 19:07 ` Ulrich Weigand [this message]
2011-10-11 20:06 ` [commit] Fix condition (Re: [patch] Verify byte-by-byte if both files are the same on "remote:") Jan Kratochvil
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=201110111906.p9BJ6h8k023538@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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