José Fonseca wrote: > On Thu, 2009-02-12 at 08:47 -0800, Brian Paul wrote: >> José Fonseca wrote: >>> Hi, >>> >>> I'd like to fix the naming collisions for the memory allocation utility >>> macros/functions between gallium & mesa, especially the MALLOC, CALLOC, >>> CALLOC_STRUCT, FREE, and REALLOC macros in u_memory.[ch]. >>> >>> The main motivation is to be able to use the memory debugging functions >>> debug_malloc, etc instead of the standard library's ones. The mesa >>> based state tracker sometimes frees mesa structures (allocated with >>> malloc), with debug_free, and probably vice versa. >> The simplest thing for now might be to go through >> src/mesa/state_tracker/ and use the _mesa_malloc(), _mesa_free(), etc >> wrappers everywhere. >> >> Would that do the trick, or do you need the macro wrappers for Windows >> in that area too? >> >> I don't think we need to use any of the gallium memory functions in >> the >> Mesa state tracker. > > Yeah, that would be a good start. The mesa statetracker can be debugged > on linux (and is already very stable to start with), so using the memory > debugging on the remaining pieces would cover most of the cases I'm > interested in.
Ok, I've committed some clean-ups. Let me know if that helps. -Brian ------------------------------------------------------------------------------ _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
