[Mesa-dev] How difficult would it be to have debugging information for Jitted code show up?

[Jose Fonseca]

> However, all I really want are symbol names.  

You should have them when running inside perf.

>  Also for some reason I can't seem to view the assembly of the JITted code.  

Did you follow the instructions on http://mesa3d.org/llvmpipe.html and use bin/perf-annotate-jit script ?

Jose

________________________________________
From: Steven Stewart-Gallus <sstewartgallus00 at mylangara.bc.ca>
Sent: 14 November 2014 23:50
To: Jose Fonseca
Cc: Emil Velikov; ML mesa-dev
Subject: Re: RE: [Mesa-dev] How difficult would it be to have debugging information for Jitted code show up?

Hello,

This would be a tough task then. However, all I really want are symbol
names.  Having source level debugging would be really cool but not
something I would actually use that much.  Even just having a basic
outline of the code would be nice.  In fact, I'd imagine it'd be
easiest and best if simply the fixed function code was labelled with a
few symbol names that would let me understand the broad strokes of the
code.  Also for some reason I can't seem to view the assembly of the
JITted code.  Maybe I'm missing a special option for perf to record
JITted code, or it just lacks the functionality or maybe something has
to be done to notify profilers about it (similar to how Valgrind and
such need to be notified about JITted code.)

Thank you,
Steven Stewart-Gallus