[Bug c++/21873] GDB Crashes when ^C pressed while debugging ARM-Cortex M4F

["ihkose at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=21873

--- Comment #5 from Ismail <ihkose at gmail dot com> ---
I downloaded gdb from the following read only repository and configure it with
your parameters and then built it. GDB 8


git clone git://sourceware.org/git/binutils-gdb.git

Here is the GDB version output

$ gdb/gdb --version                                                             
GNU gdb (GDB) 8.0.50.20170801-git
Copyright (C) 2017 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 "--host=x86_64-pc-linux-gnu --target=arm-none-eabi".
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".



I dont know if generated bin files has issues. I use the following gcc compiler
version. I sometimes see dwarf errors. But, the firmware itself works well.

arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.7.4 20130913
(release) [ARM/embedded-4_7-branch revision 202601]
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.



I am not sure how to debug the gdb itself. It seems little bit complicated. I
have to use openocd in order to run and debug the program on the target. 

I will have one GDB as runner and debugger, the second one that works in TUI
mode will connect to openocd and debug the firmware. 

I would be happy if you can give me some documents/guidance to debug it.

Thanks
Ismail

-- 
You are receiving this mail because:
You are on the CC list for the bug.