Re: [hatari-devel] trace output format

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On sunnuntai 11 elokuu 2013, Nicolas Pomarède wrote:
> On 11/08/2013 00:58, Eero Tamminen wrote:
> > With today's GB sized disks, I don't think the small space increase
> > is a problem.  I've never had problems with the space the traces
> > take, just with finding the relevant data from them.
> 
> the problem is not the space on disk, the problem is when you want to
> open the full trace file under 'vi' for example, which I often need to
> do to trace complex issues that require several seconds of traces.

I think you're now referring to CPU disassembly tracing.  I wasn't
suggesting changing that [1], it already contains fixed sized PC address
field.

[1] Except maybe making some part(s) of it optional...


> In that case you need to deal with 2Go or more text file, and it will be
> slowwww to open in text editor, so every byte counts.

I've had that problem with Linux trace files, so I can symphatize.

For my purposes profiler, CPU symbols tracing, CPU execution history etc
make the need for CPU disassembly tracing non-existing.

From profiler output I can see all the executed instructions, how
many times they were executed, from symbols trace (enough of) in which
order they were executed, and with incremental approach to (automated)
breakpoints, I can typically whittle the problematic part small enough
that it's visible in the CPU execution history, or that the CPU disassembly
is of reasonable size.


But I guess it can be a bit different when one is looking at tricky
interrupt, video etc timings.  Just remember that adding symbols to
interrupt handlers, profiler can provide you list of where they were
called from and how many times.


Douglas, how much you have nowadays need for CPU disassembly tracing
when you're debugging bugs in Bad Mood sound, DSP etc interactions?


> > I'm not convinced, but if you really want to change it, go ahead. :-)
> 
> Will have a look later ; my working copy has pending changes I can't
> commit at the moment.


	- Eero