public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31254] [gdb, arm] FAIL: gdb.threads/staticthreads.exp: up 10
Date: Thu, 18 Jan 2024 17:12:41 +0000	[thread overview]
Message-ID: <bug-31254-4717-XtDVxTKSIc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31254-4717@http.sourceware.org/bugzilla/>

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

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #8 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
I am not sure this is an glibc issue, I built the gdb testcase
./gdb/testsuite/gdb.threads/staticthreads.c against the glibc master in static
mode an old gdb does seems to get correct backtraces:

$ gdb ./tst-staticthreads
GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
[...]
(gdb) b main
Breakpoint 1 at 0x103cc: file tst-staticthreads.c, line 36.
(gdb) r
[...]
(gdb) b __libc_do_syscall
[...]
(gdb) c
Continuing.
[...]
Breakpoint 2, __libc_do_syscall () at
../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:40
(gdb) thread apply all bt

Thread 2 (LWP 5282 "tst-staticthrea"):
#0  __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:40
#1  0x000153e4 in start_thread (arg=0x696c6720) at pthread_create.c:388
#2  0x0001f198 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone3.S:71
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (LWP 5277 "tst-staticthrea"):
#0  __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:40
#1  0x0003877a in __futex_abstimed_wait_common32 (private=<optimized out>,
cancel=<optimized out>, abstime=<optimized out>, op=<optimized out>,
expected=<optimized out>, futex_word=<optimized out>) at futex-internal.c:40
#2  __futex_abstimed_wait_common (futex_word=0xb6ffc808, expected=5282,
clockid=<optimized out>, abstime=<optimized out>, private=private@entry=128,
cancel=cancel@entry=true) at futex-internal.c:99
#3  0x0003884c in __futex_abstimed_wait_cancelable64 (futex_word=<optimized
out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized
out>, private=private@entry=128) at futex-internal.c:139
#4  0x000163f6 in __pthread_clockjoin_ex (threadid=3070216096,
thread_return=thread_return@entry=0x0, clockid=clockid@entry=0,
abstime=abstime@entry=0x0, block=block@entry=true) at pthread_join_common.c:102
#5  0x00016338 in ___pthread_join (threadid=<optimized out>,
thread_return=thread_return@entry=0x0) at pthread_join.c:24
#6  0x0001041c in main (argc=<optimized out>, argv=<optimized out>) at
tst-staticthreads.c:54

So the unwind information seems to be correct from glibc side.

(I built with thumb enable to mimic what ubunut22 does).

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

  parent reply	other threads:[~2024-01-18 17:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 16:07 [Bug gdb/31254] New: " vries at gcc dot gnu.org
2024-01-17 16:08 ` [Bug gdb/31254] " vries at gcc dot gnu.org
2024-01-17 16:08 ` vries at gcc dot gnu.org
2024-01-17 16:12 ` vries at gcc dot gnu.org
2024-01-17 16:14 ` vries at gcc dot gnu.org
2024-01-17 16:19 ` vries at gcc dot gnu.org
2024-01-17 16:23 ` thiago.bauermann at linaro dot org
2024-01-17 16:37 ` luis.machado at arm dot com
2024-01-17 16:37 ` thiago.bauermann at linaro dot org
2024-01-17 16:44 ` thiago.bauermann at linaro dot org
2024-01-18 17:12 ` adhemerval.zanella at linaro dot org [this message]
2024-01-18 17:42 ` vries at gcc dot gnu.org
2024-01-18 19:15 ` thiago.bauermann at linaro dot org
2024-01-18 19:54 ` thiago.bauermann at linaro dot org
2024-01-19 10:32 ` vries at gcc dot gnu.org
2024-01-19 10:38 ` vries at gcc dot gnu.org
2024-01-24  2:51 ` thiago.bauermann at linaro dot org
2024-01-24  2:55 ` thiago.bauermann at linaro dot org
2024-01-31  4:03 ` thiago.bauermann at linaro dot org
2024-02-01  3:24 ` thiago.bauermann at linaro dot org
2024-02-01 10:04 ` vries at gcc dot gnu.org
2024-02-01 10:10 ` luis.machado at arm dot com
2024-02-01 18:32 ` thiago.bauermann at linaro dot org
2024-02-01 20:28 ` tdevries at suse dot de
2024-02-02  1:39 ` thiago.bauermann at linaro dot org
2024-02-03  3:26 ` thiago.bauermann at linaro dot org
2024-02-05  5:56 ` vries at gcc dot gnu.org
2024-02-05 10:04 ` cvs-commit at gcc dot gnu.org
2024-02-05 10:05 ` [Bug tdep/31254] [gdb/tdep, " vries at gcc dot gnu.org
2024-02-06 21:32 ` cvs-commit at gcc dot gnu.org
2024-02-06 21:33 ` cvs-commit at gcc dot gnu.org
2024-02-07  8:00 ` vries at gcc dot gnu.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-31254-4717-XtDVxTKSIc@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).