Re: [hatari-devel] Is it me or the symbols prg option is broken ? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
Hi,
On sunnuntai 03 toukokuu 2015, Konador, Cyprian wrote:
> Thanks Eero,
> Now it seems to work fine and myprofile.txt is properly generated.
Thanks for testing!
Btw. I updated gst2ascii, hopefully it also works in next build. You need
it to provide ASCII format symbols for the callgraph etc. generation.
> Regarding "b all", in case of my simple script, profiler output looks the
> same with and without "b all".
You need to add multiple breakpoints in script before that to trigger the
issue (= add Pterm breakpoint as I suggested). But it's already fixed in
today's Hatari code & builds.
- Eero
>
> Regards
> Cyprian
>
> > -----Original Message-----
> > From: Eero Tamminen
> > Sent: 2 May 2015 18:33
> > To: hatari-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [hatari-devel] Is it me or the symbols prg option is
> > broken ?
> >
> > Hi,
> >
> > On assumption that issues is "r" vs. "rb", I commited a fix to this (I
> > don't see why Windows would fail with either, but latter works for
> > autostarting):
> > http://hg.tuxfamily.org/mercurialroot/hatari/hatari/rev/528947b85ee3
> >
> > Assuming the automated Windows builds still work, could you test the
> > change
> > after current version gets built?
> >
> > (If the fix helps, I'll change also gst2ascii.)
> >
> > On perjantai 01 toukokuu 2015, Konador, Cyprian wrote:
> > > > -----Original Message-----
> > > > From: Eero Tamminen
> > > >
> > > > Because in your case there's a crash before next VBL and program
> > > > terminates
> > >
> > > > before breakpoint for the VBL, there aren't anymore:
> > > I guess it crash due to lack of the BLiTTER (which is used here very
> > > intensively)
> >
> > Ah, it needs STE (and real TOS, not EmuTOS). With that it works, but I
> > found a bug in Hatari's conditional breakpoints code. It didn't expect
> > breakpoints to be removed during parsing of debugger files in chained
> > breakpoints.
> >
> > For now, I'd recommend removing "b all" from the debugger files that
> > are specified to be read when breakpoint is hit. I'll fix the issue
> > soon.
> >
> > - Eero
> >
> > > > Attached is graph of:
> > > > # get the profile
> > > > hatari --parse break.ini bt4pc_dx.prg
> > > >
> > > > # get symbols for profile post-processing
> > > > gst2ascii bt4pc_dx.prg > symbols.txt
> > > >
> > > > # post-process profile, output top-lists & callgraphs
> > > > hatari_profile.py -stpg -r symbols.txt --compact myprofile.txt
> > > >
> > > > # convert callgraph to SVG
> > > > dot -Tsvg myprofile-2.dot > myprofile-cycles.svg
> > > >
> > > > Attached SVG file can be viewed with Browser.
> > >
> > > That graph looks really cool. Thanks for that list of commands