Re: [hatari-devel] breakpoint : once problem ?

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

This issue should now be fixed.  Change to test code
was larger than to debugger code, as the cause for
this bug was stuff that only the test code required.

	- Eero

On 01/07/2016 01:28 AM, Eero Tamminen wrote:
> Hi,
>
> On 01/07/2016 12:24 AM, Laurent Sallafranque wrote:
> > I've migrated tonight to the latest Hatari source code + SDL2.
> >
> > I'm trying the command : 'b pc=text : once'
> >
> > I get the following into the console :
> >
> >  > b pc=text:once
> > CPU condition breakpoint 1 with 1 condition(s) added:
> >      pc = text
> > -> Once, delete after breaking.
> >  > c
> > Returning to emulation...
> > 1. CPU breakpoint condition(s) matched 1 times.
> >      pc = text :once
> > Removed CPU breakpoint 1:
> >      pc = text :once
> >
> > But hatari doesn't break and the program continue.
> > Is it a bug or did I make somerthing wrong ?
>
> It's a bug.  I broke it when I fixed access to already
> deleted breakpoints with chained breakpoints / debugger
> parse files.
>
> I'll need to think how to fix it properly.  In the meanwhile,
> you can work it around by setting some dummy breakpoint
> (e.g. with "a 0") before specifying the real breakpoints.
>
>
>      - Eero