On Sat, 2004-04-24 at 15:49, Brian Paul wrote:
> When a program segfaults in free(), it's usually because of a memory
> error (writing out of bounds, bouble-freeing a block, etc.).
>
> valgrind will easily find such errors. Once you have it
> built/installed, just run 'valgrind myApplication' a
On Sat, 2004-04-24 at 15:49, Brian Paul wrote:
> When a program segfaults in free(), it's usually because of a memory
> error (writing out of bounds, bouble-freeing a block, etc.).
>
> valgrind will easily find such errors. Once you have it
> built/installed, just run 'valgrind myApplication' a
Tilman,
I'm copying this patch to the dri-devel list. I'd like to get some
confirmation of the patch before I apply it. (I applied the other
three). Can someone take a look at this?
In the future DRI-related patches should probably be sent to the
dri-devel list.
-Brian
Tilman Sauerbeck wr
On Sat, 2004-04-24 at 02:02, Adam Jackson wrote:
> On Wednesday 21 April 2004 19:49, Michel DÃnzer wrote:
> > On Wed, 2004-04-21 at 04:17, Adam Jackson wrote:
> > > I tend to agree. I don't think there's any list of requested modules
> > > maintained anywhere. tdfx does xf86LoaderCheckSymbol("DRI
