Hey Ryan,
> There's enough of those appearing that I suspect it's increasing dtrace's
> probe effect. I'm tempted to just throw a -q at it, that would only mask the
> symptoms. Is there something else I should do to prevent the errors from
> occurring at all?
It's hard to say why you might be hitting that. You could investigate by doing
something like this:
ERROR
{
stop();
printf("stopped %d due to an error", pid);
exit();
}
Then you can use gcore <pid> to grab a core dump and prun <pid> to set the
process running again. From that core we should be able to figure out why the
stack backtrace failed.
> I'm on Solaris 10/sparcv9, and the app being traced is heavily threaded, in
> case that makes any difference.
Threading should not be a contributing factor to this issue.
Adam
On Jul 10, 2010, at 12:52 AM, Ryan Johnson wrote:
> Hi all,
>
> I'm trying to use the following profile probe to grab stack traces at regular
> intervals:
>> profile-$FREQ /pid==$PID/ {
>> @profile[ustack()]=count;
>> }
>
> and am getting quite a few errors like the following:
>> dtrace: error on enabled probe ID 4 (ID 60477: profile:::profile-7777us):
>> invalid address (0x100000) in action #2
>> dtrace: error on enabled probe ID 4 (ID 60477: profile:::profile-7777us):
>> invalid address (0x100000) in action #2
>> dtrace: error on enabled probe ID 4 (ID 60477: profile:::profile-7777us):
>> invalid address (0x100000) in action #2
>> dtrace: error on enabled probe ID 4 (ID 60477: profile:::profile-7777us):
>> invalid address (0x17f3fa000) in action #2
>> dtrace: error on enabled probe ID 4 (ID 60477: profile:::profile-7777us):
>> invalid address (0x100000) in action #2
>> dtrace: error on enabled probe ID 4 (ID 60477: profile:::profile-7777us):
>> invalid address (0x0) in action #2
>> dtrace: error on enabled probe ID 4 (ID 60477: profile:::profile-7777us):
>> invalid address (0x100000) in action #2
>
> There's enough of those appearing that I suspect it's increasing dtrace's
> probe effect. I'm tempted to just throw a -q at it, that would only mask the
> symptoms. Is there something else I should do to prevent the errors from
> occurring at all?
>
> I'm on Solaris 10/sparcv9, and the app being traced is heavily threaded, in
> case that makes any difference.
>
> Thanks!
> Ryan
>
> _______________________________________________
> dtrace-discuss mailing list
> [email protected]
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
_______________________________________________
dtrace-discuss mailing list
[email protected]
