tech-toolchain archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
gdb repeatedly detects "new process"
I'm debugging a problem in my NetBSD port of Self (selflanguage.org)
and gdb gets very confused easily... It's i386 (-m32) code on amd64,
but still. This is on stock 11.1 amd64
$ gdb -q --args ./Self -s Snapshot --resetXDisplays
Reading symbols from ./Self...
(gdb) b XInternAtom
Breakpoint 1 at 0x804c6c0
(gdb) r
Starting program: /home/uwe/work/self/self/build-debug/vm/Self -s Snapshot --resetXDisplays
init.cpp: calling abort_init
...
for I386: SaveOutgoingArgumentsOfPatchedFrames = true
[New process 20036]
Welcome to the Self system! (2024.1/0)
[Tue Nov 10 18:42:16 2026] info -- Scheduler started (according to snapshotAction schedulerInitial)
owner@[Unknown hostName] 2> desktop open
[New process 20036]
[Switching to LWP 20036 of process 20036]
Thread 3 "" hit Breakpoint 1, XInternAtom (dpy=0x884a000, name=0x876d940 "WM_PROTOCOLS", onlyIfExists=0)
at /home/uwe/work/netbsd/ro/src-release-11/../xsrc-release-11/external/mit/libX11/dist/src/IntAtom.c:173
173 if (!name)
(gdb) n
[New process 20036]
/usr/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb/infrun.c:6706: internal-error: finish_step_over: Assertion `ecs->event_thread->control.trap_expected' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0x818bfb _Z22gdb_internal_backtracev
0x6dbf87 _ZL17internal_vproblemP16internal_problemPKciS2_P13__va_list_tag
0x6dc2b7 _Z15internal_verrorPKciS0_P13__va_list_tag
0xaf5d57 _Z18internal_error_locPKciS0_z
0x7c92ef _ZL16finish_step_overP23execution_control_state
0x7ce0cf _ZL18handle_signal_stopP23execution_control_state
0x7cf750 _ZL21handle_inferior_eventP23execution_control_state
0x7d0ff1 _Z20fetch_inferior_eventv
0x819200 _Z26check_async_event_handlersv
0xaf052e _Z16gdb_do_one_eventi
0x7988bd _ZL21captured_command_loopv
0x79b257 _Z8gdb_mainP18captured_main_args
0xbd5377 main
---------------------
/usr/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb/infrun.c:6706: internal-error: finish_step_over: 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)
In a different run (hence the different PID) if I ask about its idea
of the child state (instead of calling that "n" that sends it into the
tailspin):
(gdb) info threads
Id Target Id Frame
1 LWP 20119 of process 20119 "" XInternAtom (dpy=0x884a000,
name=0x876d700 "WM_PROTOCOLS", onlyIfExists=0)
at /home/uwe/work/netbsd/ro/src-release-11/../xsrc-release-11/external/mit/libX11/dist/src/IntAtom.c:173
2 LWP 20119 of process 20119 "" XInternAtom (dpy=0x884a000,
name=0x876d700 "WM_PROTOCOLS", onlyIfExists=0)
at /home/uwe/work/netbsd/ro/src-release-11/../xsrc-release-11/external/mit/libX11/dist/src/IntAtom.c:173
* 3 LWP 20119 of process 20119 "" XInternAtom (dpy=0x884a000,
name=0x876d700 "WM_PROTOCOLS", onlyIfExists=0)
at /home/uwe/work/netbsd/ro/src-release-11/../xsrc-release-11/external/mit/libX11/dist/src/IntAtom.c:173
Why does gdb randomly decides (repeatedly, too) that it sees a
[New process 20036]
The program is not threaded:
$ ldd Self
Self:
-lXext.7 => /usr/X11R7/lib/i386/libXext.so.7
-lX11.7 => /home/uwe/lib/i386/libX11.so.7
-lxcb.2 => /home/uwe/lib/i386/libxcb.so.2
-lXau.7 => /usr/X11R7/lib/i386/libXau.so.7
-lc.12 => /usr/lib/i386/libc.so.12
-lXdmcp.7 => /usr/X11R7/lib/i386/libXdmcp.so.7
-lgcc_s.1 => /usr/lib/i386/libgcc_s.so.1
-lXft.3 => /usr/X11R7/lib/i386/libXft.so.3
-lfontconfig.2 => /usr/X11R7/lib/i386/libfontconfig.so.2
-lexpat.2 => /usr/lib/i386/libexpat.so.2
-lfreetype.19 => /usr/X11R7/lib/i386/libfreetype.so.19
-lz.1 => /usr/lib/i386/libz.so.1
-lbz2.1 => /usr/lib/i386/libbz2.so.1
-lXrandr.3 => /usr/X11R7/lib/i386/libXrandr.so.3
-lXrender.2 => /usr/X11R7/lib/i386/libXrender.so.2
-lterminfo.2 => /usr/lib/i386/libterminfo.so.2
-ljemalloc.0 => /usr/lib/i386/libjemalloc.so.0
-lstdc++.9 => /usr/lib/i386/libstdc++.so.9
-lm.0 => /usr/lib/i386/libm.so.0
Any ideas?
TIA.
-uwe
Home |
Main Index |
Thread Index |
Old Index