Re: bin/58216: gdb breakpoints do not always work

[Rhialto <rhialto%falu.nl@localhost>]

The following reply was made to PR bin/58216; it has been noted by GNATS.

From: Rhialto <rhialto%falu.nl@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
	Rhialto <rhialto%falu.nl@localhost>
Subject: Re: bin/58216: gdb breakpoints do not always work
Date: Tue, 30 Apr 2024 20:05:40 +0200

 Yes and no.
 
 I set security.pax.mprotect.ptrace=2 (thanks for the hint!).
 
 The breakpoint is hit, but the internal error still gets triggered (same
 as with the hardware breakpoint). 
 
 (gdb) break mmap
 Breakpoint 1 at 0x7311cd1795f2: mmap. (2 locations)
 (gdb) c
 Continuing.
 [Switching to LWP 1491 of process 1491]
 
 Thread 10 "" hit Breakpoint 1, _mmap (addr=addr@entry=0x0, len=8192,
     prot=prot@entry=3, flags=flags@entry=1, fd=13, offset=4512096256)
     at /usr/src/lib/libc/sys/mmap.c:59
 59      {
 (gdb) c
 Continuing.
 [New process 1491]
 /usr/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb/infrun.c:5683: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n) n
 
 This is a bug, please report it.  For instructions, see:
 <https://www.gnu.org/software/gdb/bugs/>.
 
 /usr/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb/infrun.c:5683: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Unable to dump core, use `ulimit -c unlimited' before executing GDB next time.
 Command aborted.
 (gdb) q
 A debugging session is active.
 
         Inferior 1 [process 1491] will be detached.
 
 Quit anyway? (y or n) y
 Detaching from program: /usr/X11R7-9.3/bin/X, process 1491
 [Inferior 1 (process 1491) detached]
 murthe.0:~$
 
 At this point, X is still terminated, even though it doesn't say so
 here.