Quote from: mm0359 on August 19, 2016, 02:33:43 AM
Windows
ADM_setCrashHook [libADM_core6.dll]
ADM_backTrack [libADM_core6.dll]
TsIndexer::runH264(char const*, ADM_TS_TRACK*) [libADM_dm_ts.dll]
...
Quote from: Jan Gruuthuse on August 21, 2016, 05:38:41 AM
Linux
TsIndexer::decodeSEI(unsigned int, unsigned char*, unsigned int*, pictureStructure*)
TsIndexer::runH264(char const*, ADM_TS_TRACK*)
...
Is it expected that the "TsIndexer::decodeSEI(...)" line is not reported on Windows?
Quote from: mm0359 on August 23, 2016, 08:01:33 AM
Is it expected that the "TsIndexer::decodeSEI(...)" line is not reported on Windows?
Ftr,
"v2.6.11 + usp10.dll" on WinXP,
displays an Info dialog, without the expected line:
same as assert stack in v2.6.12/v2.6.13.
"v2.6.11 (160210_f4e7b7ff081) Debug + usp10.dll" on WinXP,
displays an Info dialog, with the expected line:
Crash
ADM_setCrashHook [libADM_core6.dll]
ADM_backTrack [libADM_core6.dll]
TsIndexer::decodeSEI(unsigned int, unsigned char*, unsigned int*, pictureStructure*) [libADM_dm_ts.dll]
TsIndexer::runH264(char const*, ADM_TS_TRACK*) [libADM_dm_ts.dll]
...
Likely cause: decodeSEI(...) is "inlined/forgotten" in non-debug?
(Or is it an "issue" with the reporting code?)