Does profiler work with stack-switching instructions?

[ezrakilty]

This may be just a question: Should I expect the profiler to work with suspend/resume, or is it completely not implemented? I'm running a program that takes about 3sec to run but the profiler gives 0.001778s as the top-line "nested" value. I don't know if that should be considered a bug or just unexplored territory.

[titzer]

I think it's not properly accounting for nesting with stack switching.

[ezrakilty]

Do you want to close this out as a non-bug then? I'm happy with that.

[titzer]

It's something that needs to be fixed in the monitor. I have to think this through a little more, but I think basically means that suspend "stops the clock" for the current stack and then resume "restarts the clock" so that nested time is calculated properly. I think that can be done by having a per-stack "suspension time" that is subtracted from every clock sample and increased upon resume.