[Bug gdb/15730] New: problem in debugging with gdb

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

http://sourceware.org/bugzilla/show_bug.cgi?id=15730

            Bug ID: 15730
           Summary: problem in  debugging with gdb
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: critical
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: manishbaing2789 at gmail dot com

Hello I am Manish .I am doing ARM cortex M4 Programming with STM32F4 discovery
,code flashes properly but it having problem when debgging with GDB.Following
result i have found.please guide me how to slove that.



manish@manish-Inspiron-1501:~/my-wow-adc$ arm-none-eabi-gdb
obj/STM32F4_Test.elf
GNU gdb (Sourcery CodeBench Lite 2013.05-23) 7.4.50.20120716-cvs
Copyright  2012 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=i686-pc-linux-gnu --target=arm-none-eabi".
For bug reporting instructions, please see:
<https://sourcery.men...m/GNUToolchain/>...
Reading symbols from /home/manish/my-wow-adc/obj/STM32F4_Test.elf...done.
(gdb) target extended-remote localhost:4242
Remote debugging using localhost:4242
0x080077fc in Reset_Handler ()
(gdb) monitor reset init
(gdb) load
Loading section .isr_vector, size 0x188 lma 0x8000000
Loading section .text, size 0x7e34 lma 0x8000188
Loading section .ARM, size 0x8 lma 0x8007fbc
Loading section .init_array, size 0x4 lma 0x8007fc4
Loading section .fini_array, size 0x4 lma 0x8007fc8
Loading section .data, size 0x5b0 lma 0x8007fcc
Start address 0x80077fc, load size 34172
Transfer rate: 6 KB/sec, 4881 bytes/write.
(gdb) b main
Breakpoint 1 at 0x80073f2: file src/main_temp.c, line 4.
(gdb) c
Continuing.
Note: automatically using hardware breakpoints for read-only addresses.

then program halts

I am not getting why

Note: automatically using hardware breakpoints for read-only addresses.

above line prints and how to caime from that. :huh:

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