public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17968] [ppc64] SEGV in ppc64_elf_get_synthetic_symtab reading a separate debug file
Date: Sun, 15 Feb 2015 23:43:00 -0000	[thread overview]
Message-ID: <bug-17968-4717-i6PveIlZwz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17968-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17968

--- Comment #1 from Martin Sebor <msebor at redhat dot com> ---
The following test case reduced from a build of the kernel module in the
problem Description reproduces the SEGV with the top of trunk.  Tthough the
program faults in a different function, Valgrind reports the same Invalid read.

$ set -x && cat t.c && gcc -c -g t.c && cat t.lds && ld -r -T t.lds --build-id
-o t.ko t.o && cp t.ko t.sym.ko && objcopy --only-keep-debug t.ko t.ko.debug &&
strip --strip-debug t.ko && objcopy --add-gnu-debuglink=t.ko.debug t.ko &&
/build/gdb-fsf/gdb/gdb -q -batch t.sym.ko && /build/gdb-fsf/gdb/gdb -q -batch
t.ko; set +x
+ cat t.c
void foo (void) __attribute__ ((section (".bar")));
void foo (void) { }

+ gcc -c -g t.c
+ cat t.lds
SECTIONS {
  .foobar : { *(.bar) }
}
+ ld -r -T t.lds --build-id -o t.ko t.o
+ cp t.ko t.sym.ko
+ objcopy --only-keep-debug t.ko t.ko.debug
+ strip --strip-debug t.ko
+ objcopy --add-gnu-debuglink=t.ko.debug t.ko
+ /build/gdb-fsf/gdb/gdb -q -batch t.sym.ko
+ /build/gdb-fsf/gdb/gdb -q -batch t.ko
Segmentation fault

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  reply	other threads:[~2015-02-15 23:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 10:30 [Bug gdb/17968] New: " msebor at redhat dot com
2015-02-15 23:43 ` msebor at redhat dot com [this message]
2015-02-16  2:33 ` [Bug gdb/17968] " msebor at redhat dot com
2015-02-16 22:33 ` sergiodj at redhat dot com
2021-05-18 20:48 ` cel at us dot ibm.com
2021-05-18 20:50 ` cel at us dot ibm.com
2021-10-05 20:20 ` will_schmidt at vnet dot ibm.com

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=bug-17968-4717-i6PveIlZwz@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).