public inbox for gdbadmin@sourceware.org
help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Cc: Linaro Toolchain Working Group
<linaro-toolchain@lists.linaro.org>,
Joel Brobecker <brobecker@adacore.com>,
gdbadmin@sourceware.org, gdb-testers@sourceware.org
Subject: Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1426-gb960445a459: FAIL: 1 regressions on arm
Date: Wed, 31 Jan 2024 12:36:43 -0300 [thread overview]
Message-ID: <87bk91qzuc.fsf@linaro.org> (raw)
In-Reply-To: <EA23A47E-A0AE-4769-B510-F52F479B1DDA@linaro.org>
Hello,
This is recorded as GDB bug #31254¹. I've been investigating it and
yesterday I realised it's a memory corruption issue in a data structure
used by the Arm unwinder which uses exception tables.
I hope to have a fix for it soon™.
¹ https://sourceware.org/bugzilla/show_bug.cgi?id=31254
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org> writes:
> Hi All,
>
> This is a false positive, obviously. We do our best to filter out flaky tests, but in
> this case "gdb.threads/staticthreads.exp: up 10" PASSed twice in the previous run, and
> then FAILed twice in the next run. Sneaky!
>
> Re. the FAIL, the testcase expects to be " in main .*" after "up 10", but ends up in
> pthread_join() instead:
> ===
> up 10
> #4 0x0001b864 in pthread_join ()
> (gdb) FAIL: gdb.threads/staticthreads.exp: up 10
> ===
> See [1] for details.
>
> [1]
> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/00-sumfiles/gdb.log.1.xz
> .
>
> Hi Thiago,
>
> Would you please investigate whether ending up in pthread_join() is expected/reasonable
> for 32-bit ARM? In other words, whether we have a GDB bug exposed by staticthreads.exp or
> the testcase needs to be generalized a bit.
>
> Thank you,
--
Thiago
prev parent reply other threads:[~2024-01-31 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 21:30 ci_notify
2024-01-31 7:15 ` Maxim Kuvyrkov
2024-01-31 15:36 ` Thiago Jung Bauermann [this message]
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=87bk91qzuc.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=brobecker@adacore.com \
--cc=gdb-testers@sourceware.org \
--cc=gdbadmin@sourceware.org \
--cc=linaro-toolchain@lists.linaro.org \
--cc=maxim.kuvyrkov@linaro.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).