|
From: Jeremy F. <je...@go...> - 2005-02-22 17:02:46
|
Eyal Lebedinsky wrote:
> I think that this is not a simple memory shortage, but rather
> a shortage of some other resource.
>
> - Any VG resource I can set higher?
> - A linux kernel limit I should raise?
I'm sure you know the routine by now:
Please file a bug containing:
* (ideally) a test program which lets us reproduce the problem, but
failing that
* the full, complete, unedited output of "valgrind <your options> -v
<your program>"
* and (in this case) --trace-syscalls=yes
Please include everything you've already mentioned in mail about this
bug so that its all in one place.
I really appreciate that you're testing Valgrind and finding some
interesting bugs, but it would be easier if you just file a bug report
up front for each issue, containing as much detail as you can. Your
system seems pretty complex, so I understand its hard to work out
exactly what the issue is, so include too much info - its much easier to
work with than not enough.
J
|