From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Verify byte-by-byte if both files are the same on "remote:" [Re: [rfc] False separate debuginfo warning with "remot
Date: Mon, 10 Oct 2011 21:23:00 -0000 [thread overview]
Message-ID: <201110102123.p9ALNSjr021999@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:
> On Mon, 10 Oct 2011 15:47:57 +0200, Ulrich Weigand wrote:
> > So this no longer handles the st_ino == 0 case. I think we still need to do
> > that, to cope with filesystems (e.g. on Windows?) where stat works, but does
> > not provide inode numbers ... Two files with zero st_ino should not be
> > considered equal.
>
> I believe the code is right. st_ino == 0 will verified_as_different = 0,
> therefore this code does not make any assumption about such files.
>
> FYI I reordered the condition for some negligible btter performance.
Yes, you're right. Sorry, I misread the original patch ...
> gdb/
> 2011-10-10 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Fix separate debuginfo warning with "remote:" access.
> * objfiles.h (struct objfile): New fields crc32 and crc32_p.
> * symfile.c (get_file_crc): New function with the code moved from ...
> (separate_debug_file_exists): ... this function, specifically variables
> buffer and count. New variable verified_as_different, set it. Remove
> file_crc initialization. Verify also if both files are not the same
> manually, if needed.
Looks good to me.
Thanks,
Ulrich
--
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-10 21:23 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 ` Ulrich Weigand [this message]
2011-10-11 12:58 ` [patch] Verify byte-by-byte if both files are the same on "remote:" [Re: [rfc] False separate debuginfo warning with "remot Jan Kratochvil
2011-10-11 19:07 ` [commit] Fix condition (Re: [patch] Verify byte-by-byte if both files are the same on "remote:") Ulrich Weigand
2011-10-11 20:06 ` 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=201110102123.p9ALNSjr021999@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