From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [patch] Fix sepdebug.exp build-id occasional FAILs
Date: Mon, 10 Dec 2007 14:07:00 -0000 [thread overview]
Message-ID: <20071210002051.GA506@host0.dyn.jankratochvil.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
Hi,
a bug in my own code - a forgotten binary type, I should learn better Tcl.
It FAILs only for specific deterministically-random build-id hashes, this one
4edd6ca0c5be6b98d27ae5f0b31bbfe782ebd2aa
was read incorrectly as
4edd6ca07e6b98d27ae5f0b31bbfe782ebaa
resulting in
FAIL: build-id: breakpoint function, optimized file
FAIL: build-id: breakpoint small function, optimized file
FAIL: build-id: run until function breakpoint, optimized file
FAIL: build-id: run until function breakpoint, optimized file
FAIL: build-id: run until breakpoint set at small function, optimized file
Approval requested although the fix is obvious.
Sorry,
Jan
[-- Attachment #2: gdb-cvs-build_id_debug_filename_get-binary.patch --]
[-- Type: text/plain, Size: 491 bytes --]
2007-12-09 Jan Kratochvil <jan.kratochvil@redhat.com>
* lib/gdb.exp (build_id_debug_filename_get): OBJCOPY pipe being read
must be set to binary.
--- ./gdb/testsuite/lib/gdb.exp 9 Dec 2007 11:21:21 -0000 1.93
+++ ./gdb/testsuite/lib/gdb.exp 10 Dec 2007 00:14:55 -0000
@@ -2500,6 +2500,7 @@ proc build_id_debug_filename_get { exec
return ""
}
set fi [open $tmp]
+ fconfigure $fi -translation binary
# Skip the NOTE header.
read $fi 16
set data [read $fi]
next reply other threads:[~2007-12-10 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 14:07 Jan Kratochvil [this message]
2007-12-10 15:19 ` 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=20071210002051.GA506@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sources.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