|
From: Jenny L. <jli...@pi...> - 2003-07-31 14:34:48
|
I need to further break out the piece of my program that is causing this = behavior, then I should be able to provide a test case. -Jenny -----Original Message----- From: Julian Seward [mailto:js...@ac...] Sent: Thursday, July 31, 2003 1:45 AM To: Jenny Lighthart Cc: val...@li... Subject: Re: [Valgrind-users] valgrind running REALLY slow, then no output > > Could this be because my program is doing something not supported by > > valgrind? Any ideas for figuring out where it is getting hung up? Best of all, can you supply us with a test case to reproduce this with? Realistically that's the only way we can get to the bottom of this kind of problem. J |
|
From: Jenny L. <jli...@pi...> - 2003-07-31 21:01:47
|
The problem appeared to be with a call to pselect() being issued from a =
thread that was doing not much else because some lists had no values. =
Putting a cout statement in the run() method caused valgrind to get =
happy, as did replacing pselect() with select().
1. Psuedocode for what did not work:
mythread::run {
vector x<string *> list //In the test cases, list had no elements
for each item in my list:
do something
pselect(...yada yada)
}
2. Adding a cout made valgrind happy:
mythread::run {
vector x<string *> list //In the test cases, list had no elements
cout << "mythread::run" << endl;
for each item in my list:
do something
pselect(...yada yada)
}
3. Replacing pselect with select made valgrind happy without the cout
mythread::run {
vector x<string *> list //In the test cases, list had no elements
for each item in my list:
do something
select(...yada yada)
}
I can leave the select call in for now, but we'd really like to use the =
newer pselect because it is [supposed to be] reentrant. But, according =
to the man page there is no pselect system call on Linux so the pselect =
improvement is not there anyway.
So, I'm rolling along again. If anyone has any information regarding =
pselect(), select(), and valgrind I'd like to hear it.
-Jenny
-----Original Message-----
From: Julian Seward [mailto:js...@ac...]
Sent: Thursday, July 31, 2003 1:45 AM
To: Jenny Lighthart
Cc: val...@li...
Subject: Re: [Valgrind-users] valgrind running REALLY slow, then no
output
> > Could this be because my program is doing something not supported by
> > valgrind? Any ideas for figuring out where it is getting hung up?
Best of all, can you supply us with a test case to reproduce this with?
Realistically that's the only way we can get to the bottom of this
kind of problem.
J
|