|
From: Chris P. <jud...@gm...> - 2008-08-12 00:50:33
|
On closer inspection I don't think the current error I'm seeing is a threading problem. There is some process monitoring SW on our system that is used to start the app in question and expects a callback within a period of time, which with valgrind is well and truly exceeded and the app is started multiple times, causing my error. Now I just need to figure out where to extend that timeout... On Tue, Aug 12, 2008 at 11:59 AM, Chris Packham <jud...@gm...>wrote: > On Tue, Aug 12, 2008 at 11:45 AM, Tom Hughes <to...@co...> wrote: > >> Valgrind does not (these days) replace libpthread, nor does it alter >> the mapping between user and kernel threads. There is still one kernel >> thread for each pthread you create - the only change is the order in >> which they execute and how many may execute at once. > > > OK, I understand this now. > > If your program is reliant on the order in which threads execute or how >> many threads execute at once then it is, by definition, broken. > > > Yes its definitely not in a good state. I was just hoping not to have to > deal with the threading issues at this point. I guess I may just have to fix > those first. > |