Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 890708 - sys-devel/gdb-12.1-r3: Crash starting to debug steam
Summary: sys-devel/gdb-12.1-r3: Crash starting to debug steam
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-13 16:36 UTC by farmboy0
Modified: 2023-04-20 22:49 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description farmboy0 2023-01-13 16:36:51 UTC
When I try to run steam in gdb it crashes with thia double free error:

Error while reading shared library symbols for /usr/lib/liblzma.so.5:
`/usr/lib/debug/usr/lib/crti.o.debug': can't read symbols: file format not recognized.
free(): double free detected in tcache 2


Fatal signal: Aborted
----- Backtrace -----
0x560f33345aef ???
0x560f33454194 ???
0x7f9386c6038f ???
        /var/tmp/portage/sys-libs/glibc-2.36-r5/work/glibc-2.36/signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x7f9386cb02ec __pthread_kill_implementation
        /var/tmp/portage/sys-libs/glibc-2.36-r5/work/glibc-2.36/nptl/pthread_kill.c:44
0x7f9386c602e1 __GI_raise
        ../sysdeps/posix/raise.c:26
0x7f9386c4a471 __GI_abort
        /var/tmp/portage/sys-libs/glibc-2.36-r5/work/glibc-2.36/stdlib/abort.c:79
0x7f9386ca4337 __libc_message
        ../sysdeps/posix/libc_fatal.c:155
0x7f9386cba0f9 malloc_printerr
        /var/tmp/portage/sys-libs/glibc-2.36-r5/work/glibc-2.36/malloc/malloc.c:5660
0x7f9386cbc3fb _int_free
        /var/tmp/portage/sys-libs/glibc-2.36-r5/work/glibc-2.36/malloc/malloc.c:4469
0x7f9386cbe93e __GI___libc_free
        /var/tmp/portage/sys-libs/glibc-2.36-r5/work/glibc-2.36/malloc/malloc.c:3385
0x560f33733d31 ???
0x560f33576960 ???
0x560f335796f4 ???
0x560f3344bc47 ???
0x560f3372a072 ???
0x560f3372938c ???
0x560f336f0a0c ???
0x560f336f234e ???
0x560f336f256b ???
0x560f33336cc4 ???
0x560f334e44af ???
0x560f334e635a ???
0x560f334e7f8d ???
0x560f33c82ba5 ???
0x560f33c83196 ???
0x560f3353fc24 ???
0x560f335418d4 ???
0x560f332646c9 ???
0x7f9386c4b2c9 __libc_start_call_main
        ../sysdeps/nptl/libc_start_call_main.h:58
0x7f9386c4b384 __libc_start_main_impl
        ../csu/libc-start.c:381
0x560f33264590 ???
0xffffffffffffffff ???
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible.  GDB will now terminate.

This is a bug, please report it.  For instructions, see:
<https://bugs.gentoo.org/>.


Reproducible: Always

Steps to Reproduce:
1.Install steam and gdb
2.Run DEBUGGER=gdb steam in the cli
3.Watch it crash and burn
Actual Results:  
GDB crashes and terminates.

Expected Results:  
GDB can be used to debug steam.
Comment 1 farmboy0 2023-01-13 16:41:51 UTC
In gdb first press Return or c or q when it asks you to do so and then type r and return on the gdb command prompt to start steam within gdb.
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-02-04 18:26:06 UTC
Could you report this upstream at https://sourceware.org/bugzilla/ please and share the link here? Thanks.