|
From: Nicholas N. <nj...@ca...> - 2003-05-04 12:45:21
|
On Mon, 28 Apr 2003, Adam Gundy wrote: > there are three places where if a thread switches stack, valgrind doesn't > keep its idea of the highest word in the stack in sync. This causes backtraces > with only one function in them, and sometimes causes valgrind to quit. > > The attached patch fixes all three cases. Do you have some small example programs which exhibit the bugs -- too-small backtraces and early quitting? Thanks. N |