Tom Hughes a écrit : > In message <[EMAIL PROTECTED]> > Julian Seward <[EMAIL PROTECTED]> wrote: > > >> The business of tracking the bounds of each stack is a pain, and >> makes for fragility -- for example, does it now work correctly with >> user-defined stacks? >> > > Well it should do so long as they are registered with the > appropriate client request (oddly wine seems to register the > initial stack for each process but not those for any other > threads it creates). > it's mainly because we (wine project) create a specific stack for the first thread in a process (so the first thread of a process gets two stacks: the one allocated by the system, and the one wine creates) each other threads gets only one stack, and it's bound to the thread at thread creation time at the time I looked at this it wasn't necessary to add any instrumentation for this case as valgrind happily handled the one thread / one stack case A+
-- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
