Breakpoints not working properly

Breakpoints not working properly

[Marcel Wust]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]

Hi,
 
I was using Insight (x compiled for target ARM on 
host Windows NT) for some time without any problems until I set a 
breakpoint for example at _main . GDB crashes (exception)  and produces a 
stackdump (see below). Occasionally it is working alright. What's causing this problem ?
 
 
Regards,
Marcel
 
 
     96    1132 
[main] arm-elf-gdbi 1000 exception: trapped!  4082    
5214 [main] arm-elf-gdbi 1000 exception: code 0xC0000005 at 
0x4E5BE2  1943    7157 [main] arm-elf-gdbi 1000 
exception: ax 0x0 bx 0x1 cx 0xA17ADEC dx 
0x299DDF4  1831    8988 [main] arm-elf-gdbi 1000 
exception: si 0x1 di 0x299E008 bp 0x0 sp 0x299DDE0  3953   
12941 [main] arm-elf-gdbi 1000 exception: exception is: 
STATUS_ACCESS_VIOLATION  1810   14751 [main] arm-elf-gdbi 1000 
stack: Stack trace:  1848   16599 [main] arm-elf-gdbi 1000 
stack: frame 0: sp = 0x299DC04, pc = 0x6100AE63  1915   18514 
[main] arm-elf-gdbi 1000 stack: frame 1: sp = 0x299DC30, pc = 
0x77F96666  3374   21888 [main] arm-elf-gdbi 1000 stack: frame 
2: sp = 0x299DC54, pc = 0x77F8912B  1968   23856 [main] 
arm-elf-gdbi 1000 stack: frame 3: sp = 0x299DCE0, pc = 
0x77F763BA  1921   25777 [main] arm-elf-gdbi 1000 
handle_exceptions: Exception: STATUS_ACCESS_VIOLATION  1962   
27739 [main] arm-elf-gdbi 1000 handle_exceptions: Error while dumping state 
(probably corrupted stack)

Re: Breakpoints not working properly

[Fernando Nasser]

Hi Marcel,

Have you changed te cygwin1.dll by any chance? 

Please give me all the details: which gdb, got from where, same for
cygwin etc.

Also, if you can generate a small sample case that causes the problem it
would help... 

Fernando

> Marcel Wust wrote:
> 
> Hi,
> 
> I was using Insight (x compiled for target ARM on host Windows NT) for
> some time without any problems until I set a breakpoint for example at
> _main . GDB crashes (exception) and produces a stackdump (see below).
> Occasionally it is working alright. What's causing this problem ?
> 
> 
> Regards,
> Marcel
> 
> 
>      96    1132 [main] arm-elf-gdbi 1000 exception: trapped!
>  4082    5214 [main] arm-elf-gdbi 1000 exception: code 0xC0000005 at
> 0x4E5BE2
>  1943    7157 [main] arm-elf-gdbi 1000 exception: ax 0x0 bx 0x1 cx
> 0xA17ADEC dx 0x299DDF4
>  1831    8988 [main] arm-elf-gdbi 1000 exception: si 0x1 di 0x299E008
> bp 0x0 sp 0x299DDE0
>  3953   12941 [main] arm-elf-gdbi 1000 exception: exception is:
> STATUS_ACCESS_VIOLATION
>  1810   14751 [main] arm-elf-gdbi 1000 stack: Stack trace:
>  1848   16599 [main] arm-elf-gdbi 1000 stack: frame 0: sp = 0x299DC04,
> pc = 0x6100AE63
>  1915   18514 [main] arm-elf-gdbi 1000 stack: frame 1: sp = 0x299DC30,
> pc = 0x77F96666
>  3374   21888 [main] arm-elf-gdbi 1000 stack: frame 2: sp = 0x299DC54,
> pc = 0x77F8912B
>  1968   23856 [main] arm-elf-gdbi 1000 stack: frame 3: sp = 0x299DCE0,
> pc = 0x77F763BA
>  1921   25777 [main] arm-elf-gdbi 1000 handle_exceptions: Exception:
> STATUS_ACCESS_VIOLATION
>  1962   27739 [main] arm-elf-gdbi 1000 handle_exceptions: Error while
> dumping state (probably corrupted stack)

-- 
Fernando Nasser
Red Hat, Inc. - Toronto                 E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299