> On 01/11/2025 16:28, Will Godfrey wrote:
>> Main Engine initialised
>> Segmentation fault (core dumped)
On 02/11/2025 23:28, ichthyo wrote:
We have a segfault, and we need to retrieve the information where
that happens. For that we have two options:
- load the coredump the user provided into a gdb session
and retrieve the stacktrace.
For reference: how to get that stacktrace from the crash file
https://askubuntu.com/a/947532
First, we need to start a docker container with the current Ubuntu
(we mount a directory from the host into the container,
so that we can pass in the crash file provided by Derek)
podman run -v /some/dir/on/host:/pack -it ubuntu:questing-20251007
cd /pack
apt install yoshimi
apt install apport
apt install gdb
apport-unpack _usr_bin_yoshimi.1000.crash yoshiCrash
cd yoshiCrash
ls -l
# Yikes! there is a CoreDump file....
gdb /usr/bin/yoshimi CoreDump
bt
========= This is the Core-Dump ============
#0 0x00005cea0102859c in ?? ()
#1 0x000073f9f156cbfd in Fl_Group::draw_child(Fl_Widget&) const () from
/lib/x86_64-linux-gnu/libfltk.so.1.4
#2 0x000073f9f156ce52 in Fl_Group::draw_children() () from
/lib/x86_64-linux-gnu/libfltk.so.1.4
#3 0x000073f9f156cbfd in Fl_Group::draw_child(Fl_Widget&) const () from
/lib/x86_64-linux-gnu/libfltk.so.1.4
#4 0x000073f9f156ce52 in Fl_Group::draw_children() () from
/lib/x86_64-linux-gnu/libfltk.so.1.4
#5 0x000073f9f15c120b in Fl_Window::draw() () from
/lib/x86_64-linux-gnu/libfltk.so.1.4
#6 0x000073f9f15ec7ee in Fl_Wayland_Window_Driver::flush() () from
/lib/x86_64-linux-gnu/libfltk.so.1.4
#7 0x000073f9f15eab09 in ?? () from /lib/x86_64-linux-gnu/libfltk.so.1.4
#8 0x000073f9f087888c in ?? () from /lib/x86_64-linux-gnu/libdecor-0.so.0
#9 0x000073f9efaa3ed6 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8
#10 0x000073f9efaa0ba6 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8
#11 0x000073f9efaa34ae in ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8
#12 0x000073f9f088698b in ?? () from
/lib/x86_64-linux-gnu/libwayland-client.so.0
#13 0x000073f9f08877c9 in ?? () from
/lib/x86_64-linux-gnu/libwayland-client.so.0
#14 0x000073f9f0887bc3 in wl_display_dispatch_queue_pending () from
/lib/x86_64-linux-gnu/libwayland-client.so.0
#15 0x000073f9f088b33a in wl_display_dispatch_queue_timeout () from
/lib/x86_64-linux-gnu/libwayland-client.so.0
#16 0x000073f9f088b40f in wl_display_dispatch_queue () from
/lib/x86_64-linux-gnu/libwayland-client.so.0
#17 0x000073f9f15e2e5b in ?? () from /lib/x86_64-linux-gnu/libfltk.so.1.4
#18 0x000073f9f15e19d0 in
Fl_Unix_Screen_Driver::poll_or_select_with_delay(double) () from
/lib/x86_64-linux-gnu/libfltk.so.1.4
#19 0x000073f9f15ed9a1 in Fl_Unix_System_Driver::wait(double) () from
/lib/x86_64-linux-gnu/libfltk.so.1.4
#20 0x00005cea0103c7f4 in ?? ()
#21 0x000073f9f06a3d64 in start_thread (arg=<optimized out>) at
./nptl/pthread_create.c:448
#22 0x000073f9f07373bc in __GI___clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
========= End Core-Dump ============
==> What we know now:
- this crash happened when Yoshimi runs with a GUI
- the crash happens, while FLTK draws a widget
- the desktop runs under Wayland
- we are using FLTK 1.4
- *no code of Yoshimi* is directly involved
What we do not know: what widget was about to be drawn?
_______________________________________________
Yoshimi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
