seemingly out of place errors?

[Josh Stone]

On 09/28/2012 10:51 AM, Nicholas Murphy wrote:
> Hmm...interesting.  Yes, one is in a read.return and the other is in
> an open.return probe.  Your second theory seems the most likely.  Is
> there any way to verify that's what's going on, and is there any fix
> other than to try increasing MAXMAPENTRIES?

Well, you could track it in parallel yourself to confirm that there are
too many calls without returns, something like:

global count
probe YOURPROBE.call { ++count }
probe YOURPROBE.return { --count }
probe error { printf("script error with %d active calls\n", count) }

Once confirmed, there are a lot of possibilities to figure out why this
is happening.  Maybe start by adding printfs with pid(),tid(),etc. to
the call/return probes above to trace where these are happening.

Josh