FS#44048 - [gdb]Crashes while casting a variable as (char [][])
Attached to Project:
Arch Linux
Opened by Vibhav Pant (vibhavp) - Wednesday, 04 March 2015, 20:11 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 05:33 GMT
Opened by Vibhav Pant (vibhavp) - Wednesday, 04 March 2015, 20:11 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 05:33 GMT
|
Details
Description: GDB crashes when a variable is casted as a char
[][] type.
GDB Version: gdb 7.9-1 (on a 64 bit system). Steps to reproduce: 1. gdb ./a.out 2. print (char []][])<variable or constant> 3. GDB Crashes. Example LOG: zsh/4 1019 % gdb ./a.out GNU gdb (GDB) 7.9 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./a.out...done. (gdb) set logging on Copying output to gdb.txt. (gdb) print (char [][])123 $1 = gdbtypes.c:4215: internal-error: copy_type: Assertion `TYPE_OBJFILE_OWNED (type)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: <http://www.gnu.org/software/gdb/bugs/>. gdbtypes.c:4215: internal-error: copy_type: Assertion `TYPE_OBJFILE_OWNED (type)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y zsh: abort (core dumped) gdb ./a.out |
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 29 May 2023, 05:33 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please report upstream.
Monday, 29 May 2023, 05:33 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please report upstream.
Comment by Vibhav Pant (vibhavp) -
Wednesday, 04 March 2015, 20:13 GMT
Comment by
Anatol Pomozov (anatolik) -
Thursday, 05 March 2015, 03:49 GMT
Comment by
Jelle van der Waa (jelly) - Sunday,
22 October 2017, 17:32 GMT
It seems as if the crash happens independent of the binary
compiled.
It sounds like an upstream issue. Please report it upstream
buganizer.
Can you provide a sample reproducer or check if it's still
reproducible with the latest gdb?