public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jkratochvil@azul.com>
To: Luis Machado <luis.machado@arm.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 21:38:42 +0800	[thread overview]
Message-ID: <Y/i94l8g+t1QmSUT@host1.jankratochvil.net> (raw)
In-Reply-To: <1cb89b33-4656-6588-c677-1907241a252f@arm.com>

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?


Thanks,
Jan

  parent reply	other threads:[~2023-02-24 13:38 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             ` Jan Kratochvil [this message]
2023-02-24 16:56               ` [PING] [PATCH] " Luis Machado
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=Y/i94l8g+t1QmSUT@host1.jankratochvil.net \
    --to=jkratochvil@azul.com \
    --cc=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@arm.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).