Thanks!
At this point, that same benchmark has about 1 empty stack trace per 300
samples, which should be good enough.
Vincent
At Mon, 12 Aug 2013 17:25:38 -0600,
Matthew Flatt wrote:
>
> I've pushed a repair for the main problem on x86_64 Linux (and other
> platforms that use DWARF-based stac
I've pushed a repair for the main problem on x86_64 Linux (and other
platforms that use DWARF-based stack unwind).
A related symptom I had noticed was that building without gcc
optimization used disabled stack traces; that's now fixed.
There are still ways to end up with an empty stack trace, but
I'm profiling one of the contract benchmarks[1], and I noticed that
sometimes (about 10 out of 300 samples), `continuation-mark-set->context'
would return an empty stack trace. This number is cut down by about half
if I disable the JIT. These samples seem to be spread out throughout
execution (i.e
3 matches
Mail list logo