Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Unfoldered progam stack under Eclipse Version-Release number of selected component: gdb-headless-16.2-3.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: gdb killed by SIGSEGV journald_cursor: s=6fd17f62c4b24fa0bc69623370bec387;i=945703;b=f0fa6cf37e9a40ee8b8bddca30e8658e;m=1fb69b3a0;t=6345fcf4b3ea9;x=e73c889475a48d65 executable: /usr/libexec/gdb cmdline: arm-none-eabi-gdb --interpreter=mi2 --nx cgroup: 0::/user.slice/user-1000.slice/session-2.scope rootdir: / uid: 1000 kernel: 6.14.4-300.fc42.x86_64 package: gdb-headless-16.2-3.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: handle_fatal_signal comment: Unfoldered progam stack under Eclipse Truncated backtrace: Thread no. 1 (22 frames) #3 handle_fatal_signal at ../../gdb/event-top.c:1039 #4 handle_sigsegv at ../../gdb/event-top.c:1089 #6 extract_integer<unsigned long, std::is_integral<unsigned long> > at ../../gdb/extract-store-integer.c:112 #7 cp_print_value_fields at ../../gdb/cp-valprint.c:326 #8 cp_print_value_fields_pp at ../../gdb/cp-valprint.c:407 #9 cp_print_value at ../../gdb/cp-valprint.c:530 #10 cp_print_value_fields at ../../gdb/cp-valprint.c:162 #11 common_val_print at ../../gdb/valprint.c:1167 #12 mi_cmd_data_evaluate_expression at ../../gdb/mi/mi-main.c:1206 #13 mi_cmd_execute at ../../gdb/mi/mi-main.c:2142 #14 captured_mi_execute_command at ../../gdb/mi/mi-main.c:1828 #15 mi_execute_command at ../../gdb/mi/mi-main.c:1952 #16 mi_execute_command_wrapper at ../../gdb/mi/mi-interp.c:220 #17 mi_execute_command_input_handler at ../../gdb/mi/mi-interp.c:242 #18 gdb_readline_no_editing_callback at ../../gdb/event-top.c:907 #19 stdin_event_handler at ../../gdb/ui.c:154 #20 gdb_wait_for_event at ../../gdbsupport/event-loop.cc:694 #21 gdb_do_one_event at ../../gdbsupport/event-loop.cc:216 #22 start_event_loop at ../../gdb/main.c:402 #23 captured_command_loop at ../../gdb/main.c:466 #24 captured_main at ../../gdb/main.c:1343 #25 gdb_main at ../../gdb/main.c:1362 Potential duplicate: bug 2144192
Created attachment 2088589 [details] File: proc_pid_status
Created attachment 2088590 [details] File: maps
Created attachment 2088591 [details] File: limits
Created attachment 2088592 [details] File: environ
Created attachment 2088593 [details] File: open_fds
Created attachment 2088594 [details] File: mountinfo
Created attachment 2088595 [details] File: os_info
Created attachment 2088596 [details] File: cpuinfo
Created attachment 2088597 [details] File: core_backtrace
Created attachment 2088598 [details] File: dso_list
Created attachment 2088599 [details] File: backtrace
Can you upload the core file associated with the crash when running "arm-none-eabi-gdb --interpreter=mi2 --nx"? To find it, look at the output from running "abrt-cli", then do "abrt-cli info ID" where ID is the hex identifier (left-most field) obtained from looking at the abrt-cli output. Output from the "abrt-cli info" command will show a path (most likely starting with /var/spool/abrt). Look in that directory - you should hopefully see a file named coredump.zst. Upload that file to this bug. Thanks!
I forgot to set the needinfo field for Comment 12 - doing that now. Aleksandrs, please see Comment 12 regarding the info I'd like to have in order to investigate this problem.
Created attachment 2089051 [details] Previous coredump info 2025-04-17, FC41 (In reply to Kevin Buettner from comment #13) > I forgot to set the needinfo field for Comment 12 - doing that now. > Aleksandrs, please see Comment 12 regarding the info I'd like to have in > order to investigate this problem. Unfortunately I lost the relevant coredumps accidentally. I hope the attached coredump info could be useful. I am going to upload the latest one as soon as I face this issue again. Usually it happens once per week or two.
(In reply to Aleksandrs Gumenuks from comment #14) > I am going to upload the latest one as soon as I face this issue again. > Usually it happens once per week or two. Thanks! I'm closing this bug because we don't have much of a chance of reproducing it without the core file.