public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Simon Marchi <simark@simark.ca>,
	gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] When getting the locno of a bpstat, handle the case of bp with null locations.
Date: Mon, 21 Nov 2022 00:46:41 +0100	[thread overview]
Message-ID: <58b7e58d0c88199794cf08dc10ade443d36bccd1.camel@skynet.be> (raw)
In-Reply-To: <5464181b-9de6-c242-cdac-58efbf262437@simark.ca>

On Sun, 2022-11-20 at 14:34 -0500, Simon Marchi wrote:
> I ran the testsuite with the patch applied, I saw these unexpected
> failures when running with native-gdbserver or
> native-extended-gdbserver:
> 
> FAIL: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=parent: break cond on target : fork: continue to marker
> FAIL: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=child: break cond on target : fork: continue to marker
> 
> I bisected, and it pointed to the locno patch again.  Probably the
> expected patterns that need to be updated?
Effectively, this test contains some parts running only with gdbserver, and I missed
the needed update of the pattern.
I have posted an RFA with a fix:
[RFA] Fix step-over-syscall.exp matching regexp for $bpnum.$locno matching
https://sourceware.org/pipermail/gdb-patches/2022-November/194020.html

> 
>     continue^M
>     Continuing.^M
>     [New inferior 2 (process 1262224)]^M
>     ^M
>     Thread 1.1 "step-over-fork" hit Breakpoint 4.1, marker () at /home/simark/src/binutils-gdb/gdb/testsuite/gdb.base/step-over-fork.c:22^M
>     22      marker () {}^M
>     (gdb) FAIL: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=parent: break cond on target : fork: continue to marker
> 
> However, I confirm it gets rid of the UNRESOLVEDs due to the ASan
> complaints.  But I don't have time to look at the code right now, sorry.
Thanks for testing and pointing at these regressions (and sorry about these).

There are now 3 RFA fixing some regressions
[RFA] Fix use after free introduced by $_hit_bpnum/$_hit_locno variables.
[RFA] When getting the locno of a bpstat, handle the case of bp with null locations.   
[RFA] Fix step-over-syscall.exp matching regexp for $bpnum.$locno matching

and a fix for an unrelated problem but discovered when validating the above:
[RFA] Fix jump on uninit producer_is_clang of cu.h, rm declared/undefined find_partial_die

The week-end was too busy with the above to search for the dwarf2 leaks also found while
validating the fixes. I might have time next week-end.
 
Thanks
Philippe



  reply	other threads:[~2022-11-20 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 17:30 Philippe Waroquiers
2022-11-20 19:34 ` Simon Marchi
2022-11-20 23:46   ` Philippe Waroquiers [this message]
2022-11-21 15:04 ` Simon Marchi
2022-11-21 21:07   ` Philippe Waroquiers

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=58b7e58d0c88199794cf08dc10ade443d36bccd1.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.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).