public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "thiago.bauermann 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, 01 Feb 2024 18:32:41 +0000	[thread overview]
Message-ID: <bug-31254-4717-OevYcofyBw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31254-4717@http.sourceware.org/bugzilla/>

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

--- Comment #20 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org> ---
(In reply to Tom de Vries from comment #18)
> (In reply to Thiago Jung Bauermann from comment #17)
> > I'll see if I can make arm-tdep.c add a hook in objfiles_changed () so that
> > it can detect that the objfiles where reloaded and re-read the exception
> > tables. Or perhaps it's cleaner to convert objfiles_changed () into an
> > observer.
> 
> I triggered the reread using "shell touch <file>" in the gdb script, and
> then set a breakpoint on arm_exidx_new_objfile.  It triggered on the file
> command, and on the reread at run command.  So I'm not sure this approach is
> necessary.

Thanks for checking.

> Perhaps we're looking at a regression since this commit:
> ...
> commit a2726d4ff80168a8134c68cb798e3f5f537b0eba
> Author: Luis Machado <luis.machado@linaro.org>
> Date:   Thu Oct 31 16:30:44 2019 -0300
> 
>     [ARM] Store exception handling information per-bfd instead of per-objfile
> ...
> 
> I wonder if this fixes it:
> ...
> diff --git a/gdb/arm-tdep.c b/gdb/arm-tdep.c
> index ecffb9223e1..4f68af75a4b 100644
> --- a/gdb/arm-tdep.c
> +++ b/gdb/arm-tdep.c
> @@ -2704,7 +2704,7 @@ arm_exidx_new_objfile (struct objfile *objfile)
>        if (n_bytes || n_words)
>  	{
>  	  gdb_byte *p = entry
> -	    = (gdb_byte *) obstack_alloc (&objfile->objfile_obstack,
> +	    = (gdb_byte *) obstack_alloc (&objfile->per_bfd->storage_obstack,
>  					  n_bytes + n_words * 4 + 1);
>  
>  	  while (n_bytes--)
> ...

Indeed it does! I was previously reproducing the problem in the first few
tries.
The loop has been running the testcase for more than 200 times now and it
always passes.

Thank you for the patch! Will you post it on the mailing list?

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

  parent reply	other threads:[~2024-02-01 18:32 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
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 [this message]
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-OevYcofyBw@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).