Re: [tracecompass-dev] Call stack view not sorted correctly by depth

[Rocky Dunlap <rocky.dunlap@xxxxxxxx>]

Thanks for all the suggestions!  A simple restart looks like it has resolved the problem.  I'm going to keep testing a bit more just to be confident, but I hope it was perhaps due to a corrupt state system from using the debugger...

Rocky

On Tue, Oct 3, 2017 at 11:31 AM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:

Hi Rocky,

I had a similar problem a while ago due to problems in my event stream. I had warning messages I didn't see at first (of the form "Function exit name in event ({0}) different from the expected one ({1}). You may have lost events in your trace", message from CallStackStateProvider.eventHandle(ITmfEvent)). Is there a warning in your log along those lines? If so, you may need to look at your data source.

Jonah

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

On 3 October 2017 at 18:16, Patrick Tasse <patrick.tasse@xxxxxxxxx> wrote:

Hi Rocky,

As far as I can see from the source code, instances of CallStackEntry are assigned their stack level from an internal counter that is incremented as each new child is added to the parent (ThreadEntry in your case).

The children of ThreadEntry should never be rearranged by a sort, as the CallStackComparator always returns 0 when comparing CallStackEntry's.

Not sure this helps, but if you notice anything that appears incompatible with the above, let us know...

Patrick

On Tue, Oct 3, 2017 at 12:06 PM, Rocky Dunlap - NOAA Affiliate <rocky.dunlap@xxxxxxxx> wrote:

I have implemented a custom call stack analysis by extending CallStackStateProvider.  In one trace I have a call stack depth of 33.  When I view it in the call stack view, it is for some reason not sorted by depth.  Notice in the screenshot that the values in the depth column itself are correct, but the stack frame UI elements are not sorted visually by this depth.  There is some kind of interesting pattern that might shed light -- the even numbered depths are at the bottom (except for 1) and the odd depths are at the top.

Any ideas what could lead to this or what I might be doing wrong?

Thanks,

Rocky

_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev

_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev

_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev