From: Luis Machado <luis.machado@arm.com>
To: Jan Kratochvil <jkratochvil@azul.com>
Cc: gdb-patches@sourceware.org, Alan Hayward <alan.hayward@arm.com>
Subject: Re: [PING] [PATCH] gdb/arm: Fix backtrace for pthread_cond_timedwait
Date: Fri, 24 Feb 2023 16:56:12 +0000 [thread overview]
Message-ID: <02d34e87-a8a6-4038-1e97-bb821707d308@arm.com> (raw)
In-Reply-To: <Y/i94l8g+t1QmSUT@host1.jankratochvil.net>
Hi,
On 2/24/23 13:38, Jan Kratochvil wrote:
> On Sat, 21 Jan 2023 01:41:00 +0800, Luis Machado wrote:
>> I've attached a gdb.log file. Hopefully that will bring some light. Please note I used
>> "nosharedlibrary" to remove the symbols for my test.
>
> I think that was the problem. With "nosharedlibrary" even the exidx section is
> not read.
>
> Could you test the v3 patch I have sent along?
I gave this a try across Ubuntu 22.04/20.04 and aarch64/arm. All of them run like so:
PASS: gdb.arch/arm-pthread_cond_timedwait-bt.exp: advance breakhere
UNTESTED: gdb.arch/arm-pthread_cond_timedwait-bt.exp: pc points to svc
PASS: gdb.arch/arm-pthread_cond_timedwait-bt.exp: successfully compiled posix threads test case
PASS: gdb.arch/arm-pthread_cond_timedwait-bt.exp: thread 2 for svc check
Is that what you were expecting to see?
next prev parent reply other threads:[~2023-02-24 16:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 8:48 Jan Kratochvil
2023-01-16 16:10 ` [PING] " Jan Kratochvil
2023-01-17 11:14 ` Luis Machado
2023-01-18 11:51 ` Jan Kratochvil
2023-01-18 14:22 ` Luis Machado
2022-12-31 8:48 ` [PATCH v2] " Jan Kratochvil
2023-01-19 3:15 ` [PING] [PATCH] " Jan Kratochvil
2023-01-20 17:41 ` Luis Machado
2022-12-31 8:48 ` [PATCH v3] " Jan Kratochvil
2023-02-24 13:38 ` [PING] [PATCH] " Jan Kratochvil
2023-02-24 16:56 ` Luis Machado [this message]
2022-12-31 8:48 ` [PATCH v4] " Jan Kratochvil
2023-02-25 10:04 ` [PING] [PATCH] " Jan Kratochvil
2023-03-20 12:51 ` [PING^2] " Jan Kratochvil
2023-03-30 14:30 ` Luis Machado
2023-03-30 16:09 ` Luis Machado
2023-04-01 13:49 ` [committed] " Jan Kratochvil
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=02d34e87-a8a6-4038-1e97-bb821707d308@arm.com \
--to=luis.machado@arm.com \
--cc=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=jkratochvil@azul.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).