mirror of
https://github.com/wolfpld/tracy
synced 2025-04-29 12:23:53 +00:00
Ignore kernel-only stacks.
It is common to receive duplicate stack traces for the same timestamp (and thread), one containing proper user-space stack, and the second one containing only kernel frames. Discard the second one, as there's no documentation how this should be interpreted and the kernel stack is mostly useless.
This commit is contained in:
parent
59e859e59a
commit
6c0c508280
@ -141,7 +141,7 @@ void WINAPI EventRecordCallback( PEVENT_RECORD record )
|
||||
if( hdr.EventDescriptor.Opcode == 32 )
|
||||
{
|
||||
const auto sw = (const StackWalkEvent*)record->UserData;
|
||||
if( sw->stackProcess == s_pid )
|
||||
if( sw->stackProcess == s_pid && ( sw->stack[0] & 0x8000000000000000 ) == 0 )
|
||||
{
|
||||
const uint64_t sz = ( record->UserDataLength - 16 ) / 8;
|
||||
auto trace = (uint64_t*)tracy_malloc( ( 1 + sz ) * sizeof( uint64_t ) );
|
||||
|
Loading…
x
Reference in New Issue
Block a user