Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.base/infcall-failure.exp on freebsd
Date: Tue, 24 Jun 2025 14:57:36 -0700	[thread overview]
Message-ID: <20250624145736.039cbc48@f41-zbm-amd> (raw)
In-Reply-To: <20250624211401.13950-1-tdevries@suse.de>

On Tue, 24 Jun 2025 23:14:01 +0200
Tom de Vries <tdevries@suse.de> wrote:

> On x86_64-freebsd with test-case gdb.base/infcall-failure.exp I get:
> ...
> (gdb) continue
> Continuing.
> 
> Program received signal SIGSEGV, Segmentation fault.
> Address not mapped to object.
> 0x0000000000400522 in func_segfault () at infcall-failure.c:24
> 24	  return *p;	/* Segfault here.  */
> Error in testing condition for breakpoint 2:
> The program being debugged was signaled while in a function called from
> GDB. GDB remains in the frame where the signal was received.
> To change this behavior use "set unwind-on-signal on".
> Evaluation of the expression containing the function
> (func_segfault) will be abandoned.
> When the function is done executing, GDB will silently stop.
> (gdb) FAIL: $exp: target_async=on: target_non_stop=on: \
>   run_cond_hits_segfault_test: continue
> ...
> 
> The problem is that the regexp in the test-case doesn't expect the
> "Address not mapped to object." bit.
> 
> Fix this by updating the regexp.
> 
> Tested on x86_64-freebsd and x86_64-linux.

LGTM.

Approved-by: Kevin Buettner <kevinb@redhat.com>


      reply	other threads:[~2025-06-24 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 21:14 Tom de Vries
2025-06-24 21:57 ` Kevin Buettner [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=20250624145736.039cbc48@f41-zbm-amd \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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