public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27526] Attaching to threaded process on glibc 2.33: libthread_db fails to initialize with "generic error"
Date: Fri, 05 Mar 2021 16:59:45 +0000	[thread overview]
Message-ID: <bug-27526-4717-8DIuE3OeII@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27526-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
The stack trace where the lookup for _dl_stack_user happens:

#0  ps_pglobal_lookup (ph=0x60c000037fe8, obj=0x0, name=0x7fffde34e6bd
"_dl_stack_user", sym_addr=0x6170000477c8) at
/home/simark/src/binutils-gdb/gdb/proc-service.c:102
#1  0x00007fffde34c7cc in td_mod_lookup (ps=<optimized out>, mod=mod@entry=0x0,
idx=idx@entry=54, sym_addr=sym_addr@entry=0x6170000477c8) at
td_symbol_list.c:48
#2  0x00007fffde34b131 in __td_ta_stack_user (ta=ta@entry=0x617000047580,
plist=plist@entry=0x7fffffffb000) at td_thr_validate.c:32
#3  0x00007fffde349b8c in td_ta_map_lwp2thr (ta_arg=0x617000047580,
lwpid=1476836, th=0x7fffffffb0a0) at td_ta_map_lwp2thr.c:190
#4  0x000055555d54fbc2 in thread_from_lwp (stopped=0x61700003a700, ptid=...) at
/home/simark/src/binutils-gdb/gdb/linux-thread-db.c:415
#5  0x000055555d554b6b in try_thread_db_load_1 (info=0x60c000037fc0) at
/home/simark/src/binutils-gdb/gdb/linux-thread-db.c:912
#6  0x000055555d555837 in try_thread_db_load (library=0x555560734260
"libthread_db.so.1", check_auto_load_safe=false) at
/home/simark/src/binutils-gdb/gdb/linux-thread-db.c:1014
#7  0x000055555d55689c in try_thread_db_load_from_sdir () at
/home/simark/src/binutils-gdb/gdb/linux-thread-db.c:1091
#8  0x000055555d557450 in thread_db_load_search () at
/home/simark/src/binutils-gdb/gdb/linux-thread-db.c:1146
#9  0x000055555d557d90 in thread_db_load () at
/home/simark/src/binutils-gdb/gdb/linux-thread-db.c:1203
#10 0x000055555d557e72 in check_for_thread_db () at
/home/simark/src/binutils-gdb/gdb/linux-thread-db.c:1246
#11 0x000055555d557fdf in thread_db_new_objfile (objfile=0x614000007040) at
/home/simark/src/binutils-gdb/gdb/linux-thread-db.c:1275
...

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

  reply	other threads:[~2021-03-05 16:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 16:48 [Bug gdb/27526] New: " simark at simark dot ca
2021-03-05 16:59 ` simark at simark dot ca [this message]
2021-03-05 19:12 ` [Bug gdb/27526] " fweimer at redhat dot com
2021-03-07  7:30 ` vries at gcc dot gnu.org
2021-03-07 23:08 ` simark at simark dot ca
2021-03-22  7:16 ` crvisqr at gmail dot com
2021-03-22 13:38 ` simark at simark dot ca
2021-03-31 17:00 ` vries at gcc dot gnu.org
2021-04-02 15:54 ` simark at simark dot ca
2021-05-06 13:04 ` vries at gcc dot gnu.org
2021-05-06 13:05 ` vries at gcc dot gnu.org
2021-05-06 13:20 ` simark at simark dot ca
2021-05-09 23:38 ` brobecker at gnat dot com
2021-06-20 15:55 ` brobecker at gnat dot com
2021-06-21 16:39 ` simark at simark dot ca

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-27526-4717-8DIuE3OeII@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).