Eyal, Konstantin,
On Wednesday 14 November 2007 10:52, Konstantin Serebryany wrote:
> In my case I had to go down to 14. :(
> This is rather risky since we will be getting out of lock sets then.
>
> On Nov 12, 2007 3:41 PM, Eyal Lebedinsky <[EMAIL PROTECTED]> wrote:
> > 15 really did it (complete
In my case I had to go down to 14. :(
This is rather risky since we will be getting out of lock sets then.
On Nov 12, 2007 3:41 PM, Eyal Lebedinsky <[EMAIL PROTECTED]> wrote:
> 15 really did it (completed one servers test now).
>
--
> And to think that some call this computer "science"...
No, this is software "engineering" :-)
J
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log eve
15 really did it (completed one servers test now).
And to think that some call this computer "science"...
Thanks
Julian Seward wrote:
>>> In the meantime, at hg_main.c:902 reduce N_LSID_BITS from 17 to 16 and
>>> try again.
>
> change to 15 and try again.
>
> J
--
Eyal Lebedinsky ([EMAIL PRO
> > In the meantime, at hg_main.c:902 reduce N_LSID_BITS from 17 to 16 and
> > try again.
change to 15 and try again.
J
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? St
Sorry to say but this actually did not fix the problem. My first test
ran past where it failed before but it did fail later and I can now
see that the problem is not resolved.
Though the message is slightly different now (tset/lset):
Helgrind: Fatal internal error -- cannot continue.
Helgrind: mk
> I notice that I am getting race reports for situations where I
> am rather sure that the only active thread is the main thread.
It depends what you mean by the "only active thread". Are the
other threads still alive but blocked somehow? Or (as below)
have they really all exited?
> My program
Julian,
Thanks, this fixes it.
Can I ask a question then?
I notice that I am getting race reports for situations where I
am rather sure that the only active thread is the main thread.
My programs do not apply locks in these sections of the code,
for example during server shutdown after all threa
> Helgrind: Fatal internal error -- cannot continue.
> Helgrind: mk_SHVAL_ShR(tset=8192,lset=1): FAILED
> Helgrind: max allowed tset=8191, lset=131071
> Helgrind: program has too many thread sets or lock sets to track.
Yes. It's a problem I'm tracking. Really it is trying to squeeze
too much in
I am trying to use helgrind and so far I have a showstopper.
Simplified, my software is a number of servers and clients. The
clients execute a heartbeat connection to one server (1/sec).
Bringing up the servers and clients all looks fine but very soon
(90s after it actually starts running) one se
10 matches
Mail list logo
