public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mattst88 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30525] gdb cannot read shared libraries on SPARC64
Date: Tue, 06 Jun 2023 22:27:37 +0000	[thread overview]
Message-ID: <bug-30525-4717-ql7uJziWa0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30525-4717@http.sourceware.org/bugzilla/>

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

Matt Turner <mattst88 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at sourceware dot org,
                   |                            |pedro at palves dot net

--- Comment #1 from Matt Turner <mattst88 at gmail dot com> ---
I've bisected this to commit 05c06f318fd9a112529dfc313e6512b399a645e4.

I bisected between gdb-10-branchpoint and gdb-11-branchpoint. Here's the bisect
log.

git bisect start
# status: waiting for both good and bad commits
# good: [8087c3fa8b5d695e3e29e69d70d0b35ec902ac59] Fix GDB build in infrun.c
when configured with unit tests disabled
git bisect good 8087c3fa8b5d695e3e29e69d70d0b35ec902ac59
# status: waiting for bad commit, 1 good commit known
# bad: [4b51505e33441c6165e7789fa2b6d21930242927] More minor updates to the
how-to-make-a-release documentation
git bisect bad 4b51505e33441c6165e7789fa2b6d21930242927
# good: [616c069a3f1a841e5bc63d20aec8e5b71b499f6c] gdb/dwarf: don't enqueue CU
in maybe_queue_comp_unit if already expanded
git bisect good 616c069a3f1a841e5bc63d20aec8e5b71b499f6c
# good: [ec098003e27d67bca9e9880320e26ab8ad30fe31] gdbsupport: introduce struct
observer
git bisect good ec098003e27d67bca9e9880320e26ab8ad30fe31
# good: [c445a939101ce78dfd62fdbd97906768aca2ed4d] Automatic date update in
version.in
git bisect good c445a939101ce78dfd62fdbd97906768aca2ed4d
# good: [7b2298cbd812320c7f78d41d556ecb174cfdd675] sim: mips: fix uninitialized
register use
git bisect good 7b2298cbd812320c7f78d41d556ecb174cfdd675
# good: [bf1dcdb3910e003c29c278ddb48eb56cfd045138] Consolidate CU language
setting
git bisect good bf1dcdb3910e003c29c278ddb48eb56cfd045138
# good: [4743af62eb6f00c385dccff54df43ae0bbf31cd3] gdb: remove duplicate
declaration of 'find_thread_ptid'
git bisect good 4743af62eb6f00c385dccff54df43ae0bbf31cd3
# good: [9cb74cfd815bfab451546206094b7ab49d382a24] Automatic date update in
version.in
git bisect good 9cb74cfd815bfab451546206094b7ab49d382a24
# bad: [d4a0121347ad9890060709a2a7660e0ac58b4b84] sim: m32r: replace custom
endian helpers with sim-endian
git bisect bad d4a0121347ad9890060709a2a7660e0ac58b4b84
# bad: [ac8ef6961e18664224b55c1eadc611f0e9f1e5b5] opcodes: constify & localize
z80 opcodes
git bisect bad ac8ef6961e18664224b55c1eadc611f0e9f1e5b5
# bad: [05c06f318fd9a112529dfc313e6512b399a645e4] Linux: Access memory even if
threads are running
git bisect bad 05c06f318fd9a112529dfc313e6512b399a645e4
# good: [75a2da57a1bbff8686f56a43aabe1d7e55147894] readelf: Reset file position
to beginning for thin archive members
git bisect good 75a2da57a1bbff8686f56a43aabe1d7e55147894
# first bad commit: [05c06f318fd9a112529dfc313e6512b399a645e4] Linux: Access
memory even if threads are running

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

  parent reply	other threads:[~2023-06-06 22:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 19:19 [Bug gdb/30525] New: " mattst88 at gmail dot com
2023-06-06 19:19 ` [Bug gdb/30525] " mattst88 at gmail dot com
2023-06-06 22:27 ` mattst88 at gmail dot com [this message]
2023-06-07  8:36 ` sam at gentoo dot org
2023-06-07  8:37 ` sam at gentoo dot org
2023-06-07  9:05 ` pedro at palves dot net
2023-06-07 10:19 ` pedro at palves dot net
2023-06-07 10:44 ` pedro at palves dot net
2023-06-07 14:43 ` mattst88 at gmail dot com
2023-06-07 15:18 ` mattst88 at gmail dot com
2023-06-07 15:33 ` mattst88 at gmail dot com
2023-06-07 22:11 ` pedro at palves dot net
2023-06-07 22:12 ` pedro at palves dot net
2023-06-07 23:57 ` mattst88 at gmail dot com
2023-06-14 23:42 ` mattst88 at gmail dot com
2023-06-15 10:39 ` pedro at palves dot net
2023-07-05 13:43 ` pedro at palves dot net
2023-07-06 16:58 ` cvs-commit at gcc dot gnu.org
2023-07-06 20:55 ` sam at gentoo dot org

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-30525-4717-ql7uJziWa0@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).