José Fonseca writes:
>> Do you know why this is?
>
> No, I don't have a clear understanding.
OK. Thanks for letting me know.
>> I'd definitely be interested in making apitrace work more transparently
> here.
>
> Me too. But there are so many apps that only work well with
> LD_LIBRARY_PATH, that
On Sat, Jun 15, 2013 at 8:05 PM, Carl Worth wrote:
> José Fonseca writes:
> > FYI, with
> >
> https://github.com/apitrace/apitrace/commit/7700f74f294a28e57860487b917c8807156b3ad1
> > apitrace no longer crashes with Steam overlay.
>
> Thanks, José! This will be quite handy. And it's a fix I'd bee
José Fonseca writes:
> FYI, with
> https://github.com/apitrace/apitrace/commit/7700f74f294a28e57860487b917c8807156b3ad1
> apitrace no longer crashes with Steam overlay.
Thanks, José! This will be quite handy. And it's a fix I'd been hoping
to make for apitrace, but hadn't gotten around to.
It's
On Tue, Mar 5, 2013 at 9:11 AM, Alexander Monakov wrote:
>
>
> On Mon, 4 Mar 2013, Carl Worth wrote:
>
> > I don't think it should be too hard to get this to work, (though it
> > may require a source change to the Steam overlay). I'll do some more
> > experiments tomorrow and see if I can't make a
Alexander Monakov writes:
> 2) Specifically in order to work with the Steam overlay, the interposer
> *protects itself from dlsym interposition* by using
> real_dlsym = dlsym(dlopen("libdl.so.2"), "dlsym"). Similar protection against
> dlopen interposition would also make sense.
Thanks, Alexande
On Tue, 5 Mar 2013, Jose Fonseca wrote:
> $LIB is a neat idea. But does it work on debian/ubuntu systems, where
> mesa/NVIDIA libGL.so are put in different paths , which are then chosen via
> /etc/ld.so.conf*?
I think Debian installs a symlink to the active libGL in /usr/lib. Not sure
about Ub
On Tue, 5 Mar 2013, Jose Fonseca wrote:
> I expected that when one sets TRACE_LIBGL env var with the path for the true
> libGL.so.1, then apitrace wouldn't be picking up symbols the overlay -- it
> would be taking symbols only from the true libGL.so, there avoiding infinite
> recursion.
... unle
On Mon, 4 Mar 2013, Carl Worth wrote:
> I don't think it should be too hard to get this to work, (though it
> may require a source change to the Steam overlay). I'll do some more
> experiments tomorrow and see if I can't make a concrete recommendation
> to be able to give to Valve as a bug repor
- Original Message -
>
>
> On Mon, 4 Mar 2013, Carl Worth wrote:
>
> > I don't think it should be too hard to get this to work, (though it
> > may require a source change to the Steam overlay). I'll do some more
> > experiments tomorrow and see if I can't make a concrete recommendation
I expected that when one sets TRACE_LIBGL env var with the path for the true
libGL.so.1, then apitrace wouldn't be picking up symbols the overlay -- it
would be taking symbols only from the true libGL.so, there avoiding infinite
recursion.
Jose
- Original Message -
> Jose Fonseca writ
Jose Fonseca writes:
> I see. But one can use apitrace through LD_LIBRARY_PATH instead of
> LD_PRELOAD. Steam is not the first app to have issues with LD_PRELOAD.
I spend some time looking at this issue today.
First, things aren't as bad as I had first thought. I had
misunderstood the original
- Original Message -
> On Wed, Feb 27, 2013 at 1:21 AM, Jose Fonseca wrote:
> > - Original Message -
> >> Jordan Justen writes:
> >>
> >> > Motivated by wanting to see if GenTextures was called by an
> >> > application while debugging another Steam overlay issue.
> >>
> >> Making
Jose Fonseca writes:
> - Original Message -
>> Jordan Justen writes:
>>
>> > Motivated by wanting to see if GenTextures was called by an
>> > application while debugging another Steam overlay issue.
>>
>> Making a systematic MESA_DEBUG=api using dispatch tables and code
>> generation s
On Wed, Feb 27, 2013 at 1:21 AM, Jose Fonseca wrote:
> - Original Message -
>> Jordan Justen writes:
>>
>> > Motivated by wanting to see if GenTextures was called by an
>> > application while debugging another Steam overlay issue.
>>
>> Making a systematic MESA_DEBUG=api using dispatch ta
- Original Message -
> Jordan Justen writes:
>
> > Motivated by wanting to see if GenTextures was called by an
> > application while debugging another Steam overlay issue.
>
> Making a systematic MESA_DEBUG=api using dispatch tables and code
> generation seems like it would be nice inste
Jordan Justen writes:
> Motivated by wanting to see if GenTextures was called by an
> application while debugging another Steam overlay issue.
Making a systematic MESA_DEBUG=api using dispatch tables and code
generation seems like it would be nice instead of adding it ad-hoc. Not
something agai
On Mon, Feb 25, 2013 at 2:00 PM, Jordan Justen
wrote:
> Motivated by wanting to see if GenTextures was called by an
> application while debugging another Steam overlay issue.
>
> Signed-off-by: Jordan Justen
> ---
> src/mesa/main/texobj.c | 21 +
> 1 file changed, 21 insert
Motivated by wanting to see if GenTextures was called by an
application while debugging another Steam overlay issue.
Signed-off-by: Jordan Justen
---
src/mesa/main/texobj.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/src/mesa/main/texobj.c b/src/mesa/main/texobj.
18 matches
Mail list logo
