>>>>> Alexis <[email protected]> writes:
> Note that using smaller values than 10 work, even though it
> seems to have no effect on the trace level as suggested by the manpage.
> % for trace in {1..9}; do ./ledger -f test/input/sample.dat test--trace
> ${trace} 2>/tmp/ledger_trace_${trace}.txt >/dev/null; done
> Any helpful hints what needs to be changed?
I'm not sure what's causing the segmentation fault, but there are no trace
messages above level 9, so I'm not sure what type of information you'd be
looking for.
The whole tracing mechanism was pretty much subsumed by the advanced --debug
class mechanism which got added later. That one is regular expression based,
so that I can target exactly which debug messages I'm interested in seeing.
John
--
---
You received this message because you are subscribed to the Google Groups
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
