[Bug 7371] tux leaves colored trails in ppracer

[<bug...@an...>]

Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=7371          
     




------- Additional Comments From j.w...@hh...  2006-06-30 13:18 -------
Created an attachment (id=6085)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=6085&action=view)
Backtrace of ppracer crashing when run under electricfence with mesa 6.5
snapshot

Hi,

I just ran ppracer under gdb in combination with electric fence (a malloc
debugger, which checks out of bound accesses) and I've just attached the
backtrace. Or atleast as much as I got of a backtrace before gdb crashed.

The problem is that currently I'm using the following to get electric fence
linked in:
export LD_PRELOAD=libefence.so

Neat trick, but I don't know how todo this with it also influencing gdb, which
then quickly runs out of virtual memory (each malloc causes 2 whole pages to be
allocated by electricfence).

When I've got the time I'll rebuild ppracer directly linked against efence and
investigate some more. I think we have something here.
          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.