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

[Jose Fonseca]

Is this the i915 gallium or classic driver? What does glxinfo show?

Jose 


________________________________________
From: mesa-dev <mesa-dev-bounces at lists.freedesktop.org> on behalf of Steven Stewart-Gallus <sstewartgallus00 at mylangara.bc.ca>
Sent: 11 November 2014 23:45
To: Kenneth Graunke
Cc: mesa-dev at lists.freedesktop.org
Subject: Re: [Mesa-dev] How difficult would it be to have debugging information for Jitted code show up?

I'm hoping that it would be possible to have symbol names for Jitted code to
show up for profiling tools. For example, with software rendering and examining
my code using perf utils 70% of my code is just a mysterious callstack inside
the i915 shared library that has no symbols and no source information as the
JITted code has no debug information.

Thank you,
Steven Stewart-Gallus
_______________________________________________
mesa-dev mailing list
mesa-dev at lists.freedesktop.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_mesa-2Ddev&d=AAIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=zfmBZnnVGHeYde45pMKNnVyzeaZbdIqVLprmZCM2zzE&m=5-qyNgNTfbll239LRSjQLKJuiUBT0u_c9rBpLMXBFgA&s=xDSlgkTlh6J3y4qx789edpfnRxZPgS7OSx3twMfza0o&e=