Getting useful stuff from HISE debug version

[Lindon]

OK so I'm getting a lot of crashes using the AudioWaveform - but I cant reproduce it in a simple project so I'm running the debug version of HISE - well I'm trying to - so I assume I run HISE inside VS2017 - and get to my crash point - then what - how do I extract the useful info. from the debug crash, such that i can pass it along to CH?

currently the output is telling me:

The thread 0x1158 has exited with code 0 (0x0).
The thread 0x920 has exited with code 0 (0x0).
The thread 0x2aac has exited with code 0 (0x0).
The thread 0x2ab0 has exited with code 0 (0x0).
The thread 0xa94 has exited with code 0 (0x0).
The thread 0x1720 has exited with code 0 (0x0).
The thread 0x26e8 has exited with code 0 (0x0).
The thread 0x1c48 has exited with code 0 (0x0).
The thread 0x27b4 has exited with code 0 (0x0).
The thread 0x103c has exited with code 0 (0x0).
The thread 0x30f4 has exited with code 0 (0x0).
The thread 0x127c has exited with code 0 (0x0).
JUCE Assertion failure in juce_mathsfunctions.h:266
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in samplebuffer.cpp:437
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in samplebuffer.cpp:437
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in samplebuffer.cpp:437
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in samplebuffer.cpp:437
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in samplebuffer.cpp:437
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in samplebuffer.cpp:437
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in samplebuffer.cpp:437
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in samplebuffer.cpp:437
HISE Debug.exe has triggered a breakpoint.

Exception thrown at 0x00007FF6D0876DEE in HISE Debug.exe: 0xC0000005: Access violation writing location 0x0000020E41C82000.

Unhandled exception at 0x00007FF6D0876DEE in HISE Debug.exe: 0xC0000005: Access violation writing location 0x0000020E41C82000.

The program '[9336] HISE Debug.exe' has exited with code 0 (0x0).

[d.healey]

how do I extract the useful info.

Look at the stack trace (I don't know where that is in Visual Studio) and follow it back until you get to a point that looks suspicious, then start adding break points and watching variables. If you know the area that is causing the issue then you can skip the stack trace part and just go straight to the breakpoints.

Do things that you know should trigger specific reactions or populate variables with certain values and see if what you think should happen is what actually happens. If the result matches then the problem is likely somewhere else, if it doesn't match then you need to work backwards to find the cause.

[Lindon]

@d-healey well huh, theres a metric tonne of jasserts - which seem to be not the problem, they are in HiseSample Buffer -so I'm assuming its loading the sample(s), then we get a massive problem

Unhandled exception at 0x00007FF68ED46DEE in HISE Debug.exe: 0xC0000005: Access violation writing location 0x000001CB46903000.

which according to the call stack comes from:

memcpy_repmoves() line 114

which turns out to be this line:

        rep     movsb                   ; copy source to destination buffer

so I'm figuring this is WAAAY above my pay grade.

I am trying to use 32 samplers by the way - but in this instance I have only 10 samplers un-Bypassed - but I'm trying to get these samplers to change their sample maps in a loop, so I may be pushing too hard here...but I cant think of an alternative...

[d.healey]

@Lindon

which turns out to be this line:

That looks like assembly code to me, so I'm not sure what to suggest.

[d.healey]

but I'm trying to get these samplers to change their sample maps in a loop,

Assuming one iteration of the loop per sampler I don't think that should be an issue - also assuming you're not doing this on a realtime thread.

[Lindon]

@d-healey no its deferred...

[d.healey]

@Lindon Then I think it should be fine, I'm doing the same thing with 6 samplers.

[Dan Korneff]

I've been down this road before.
https://forum.hise.audio/topic/5110/debugging-access-violation-reading-location?_=1647887538765

[ustk]

@dustbro @Lindon seeing the cure and that it's never been fixed, we definitely need an issue report