From: Luis Machado <luis.machado@arm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Fix gdb.gdb/python-helper.exp + cleanups
Date: Fri, 23 Sep 2022 18:02:24 +0100 [thread overview]
Message-ID: <b337c322-62c9-0170-6c84-b4768141d415@arm.com> (raw)
In-Reply-To: <20220923141801.1106678-1-simon.marchi@polymtl.ca>
On 9/23/22 15:17, Simon Marchi via Gdb-patches wrote:
> My patches that touched TYPE_LENGTH and TYPE_TARGET_TYPE caused
> regressions in gdb.gdb/python-helper.exp. I forgot to update
> gdb-gdb.py.in, as always.
>
> It looks like my CI doesn't run the test properly. Because inserting the
> first breakpoint times out, do_self_tests skips the test. I also had
> troubles running the test locally due to these timeouts. So the first
> two patches address problems related to that, and the third one is the
> actual fix.
>
> Simon Marchi (3):
> gdb/testsuite: bump duration for the whole test in do_self_tests
> gdb/testsuite: use gdb_test in gdb.gdb/python-helper.exp
> gdb/testsuite: update field names in gdb-gdb.py.in
>
> gdb/gdb-gdb.py.in | 4 +-
> gdb/testsuite/gdb.gdb/python-helper.exp | 88 +++++--------------------
> gdb/testsuite/lib/gdb.exp | 8 +--
> gdb/testsuite/lib/selftest-support.exp | 36 +++-------
> 4 files changed, 31 insertions(+), 105 deletions(-)
>
>
> base-commit: 8e037eae6823caf5b9cb5b4feb3de838abb25956
Thanks for the series. I tested this on my end and it seems to work nicely.
The only hiccup I noticed is when GDB runs into a SIGSEGV due to the guile
interpreter hitting GC_find_limit_with_bound. I'm not sure why this happens. Maybe
it is a problem with guile and armhf.
I don't think it is a flaw with the patch though. We'd have to go out of our way
to handle something like this in the testcase.
So this series LGTM.
next prev parent reply other threads:[~2022-09-23 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:17 Simon Marchi
2022-09-23 14:17 ` [PATCH 1/3] gdb/testsuite: bump duration for the whole test in do_self_tests Simon Marchi
2022-09-23 14:18 ` [PATCH 2/3] gdb/testsuite: use gdb_test in gdb.gdb/python-helper.exp Simon Marchi
2022-09-23 14:18 ` [PATCH 3/3] gdb/testsuite: update field names in gdb-gdb.py.in Simon Marchi
2022-09-23 17:02 ` Luis Machado [this message]
2022-09-23 21:35 ` [PATCH 0/3] Fix gdb.gdb/python-helper.exp + cleanups Tom de Vries
2022-09-26 18:01 ` Simon Marchi
2022-09-26 18:39 ` Tom de Vries
2022-09-26 21:33 ` Simon Marchi
2022-09-27 10:34 ` Bruno Larsen
2022-09-27 10:42 ` Luis Machado
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=b337c322-62c9-0170-6c84-b4768141d415@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).