Created attachment 1935546 [details] coredump (zstd compressed) While diagnosing a crash in dleyna-renderer $ abrt-cli report ....... <...> ('report_uReport' completed successfully) Generating backtrace Backtrace is generated and saved, 36514 bytes Backtrace parsing failed for . 15:0: Function call in the frame header misses mandatory "at file.c:xy" section Looking for similar problems in bugzilla Reporting is disabled because the generated backtrace has low informational value. Generated backtrace shows NULL pointer was used $ cat backtrace : No such file or directory. [New LWP 138679] [New LWP 138685] [New LWP 138681] [New LWP 138708] [New LWP 138684] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/dleyna-renderer-service'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000000000 in ?? () [Current thread is 1 (Thread 0x7f35748e4840 (LWP 138679))] Thread 1 (Thread 0x7f35748e4840 (LWP 138679)): #0 0x0000000000000000 in () #1 0x00007f35757e5a8a in g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x5623f12aa000, hash_table=0x5623f12cd810<error reading variable: Cannot access memory at address 0x4>) at ../glib/ghash.c:474 node_hash = <optimized out> hash_value = <optimized out> have_tombstone = 0 step = 0 node_index = <optimized out> first_tombstone = 0 node_hash = <optimized out> __func__ = "g_hash_table_lookup" #2 g_hash_table_lookup (hash_table=0x5623f12cd810<error reading variable: Cannot access memory at address 0x4>, key=key@entry=0x5623f12aa000) at ../glib/ghash.c:1540 node_hash = <optimized out> __func__ = "g_hash_table_lookup" #3 0x00007f35758fbb3f in prv_server_available_cb (cp=<optimized out>, proxy=proxy@entry=0x5623f129ba20 [GUPnPDeviceProxy], user_data=0x5623f12a8c60) at ../libdleyna/renderer/upnp.c:174 upnp = 0x5623f12a8c60 udn = 0x5623f12aa000 "uuid:6b58de40-d510-373e-12a6-7da4a8e9514b" device = <optimized out> ip_address = 0x5623f12ca540 "192.168.0.151" context = <optimized out> queue_id = <optimized out> i = <optimized out> priv_t = 0x7f35640197e0 <...> Through the debugger it's obvious it's the result of a call through a NULL function pointer $ coredumpctl debug ...... <...> [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/dleyna-renderer-service'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000000000 in ?? () [Current thread is 1 (Thread 0x7f35748e4840 (LWP 138679))] (gdb) bt #0 0x0000000000000000 in () #1 0x00007f35757e5a8a in g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x5623f12aa000, hash_table=0x5623f12cd810<error reading variable: Cannot access memory at address 0x4>) at ../glib/ghash.c:474 #2 g_hash_table_lookup (hash_table=0x5623f12cd810<error reading variable: Cannot access memory at address 0x4>, key=key@entry=0x5623f12aa000) at ../glib/ghash.c:1540 <...> (gdb) frame 1 #1 0x00007f35757e5a8a in g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x5623f12aa000, hash_table=0x5623f12cd810<error reading variable: Cannot access memory at address 0x4>) at ../glib/ghash.c:474 474 hash_value = hash_table->hash_func (key); I think the backtrace has information value and should be reported by abrt.
Created attachment 1935547 [details] backtrace
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.