Re: [avr-gcc-list] Re: Can avr-gdb + avarice work perfectly ?

[Sean D'Epagnier]

The reason is there are limited number of hardware breakpoints, and
software breakpoints normally can only be used when executing out of
ram.

So for example, gdb requires 1 hardware breakpoint to implement single
stepping, so if you only have 2 total hardware breakpoints, you can
only set 1 in the debugger.

But.. there are probably other actual bugs you are encountering.

I usually compile my code to run on multiple platforms, so I don't
really ever need to debug on the avr.

Sean

On Fri, Mar 6, 2009 at 4:43 PM, Gene Smith <address@hidden> wrote:
> Tristan Gingold wrote:
>>
>> On Feb 8, 2009, at 3:09 PM, Lin Nan wrote:
>>
>>> Hello, everyone.
>>>
>>> I have been working on a project for AVR ATmega128 for quite a long time
>>> and I found it hard to debug programs with avr-gdb and avarice. For
>>> example, I can not use command 'n' to step over a line of code, since
>>> avr-gdb always step into it.
>>
>> Yes this is a know issue.
>> We (=AdaCore) have a patch to fix it and we plan to submit it within a few
>> weeks.
>>
>> Tristan.
>
> I have a similar problem with ARM. But only if I set more than one
> breakpoint. If I have zero or one breakpoint only then can I step over
> functions; otherwise, always steps into them.
>
> Curious what gets patched. GDB? GCC? All the above?
>
> -gene
>
>
>
> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
>