Details
- 
    
Bug
 - 
    Resolution: Unresolved
 - 
    
Critical
 - 
    None
 - 
    None
 - 
    None
 
Description
0.4.15-dev-6789-g9360423 GCC8.4.0 built with RosBEWin2.2.2 in debug config.
I used ros in some scenario, and got an assert. The kind of the assert, and how I get there I will report in another ticket.
When I translated that logfile with the following command,
					log2lines -f -U -d C:\ros\reactos\output-MinGW-i386\bootcd.iso < D:\0.4.15-dev-6789-g9360423_fastfatAssert.log > D:\0.4.15-dev-6789-g9360423_fastfatAssert_translated.log
			 | 
		
 I found that the shell32 addresses were not translated properly for some reason,
 but the comctl32 and Win32SS were properly translated.
That did never happen to me before. I don't know when the regression started, I do assume within the last few months in 0.4.15-dev'ing.
I do attach both files here, so you can see the part in the assertions callstack clearly with the shell32.dll addresses by comparing those files directly with a compare-tool:
0.4.15-dev-6789-g9360423_fastfatAssert.log![]()
0.4.15-dev-6789-g9360423_fastfatAssert_translated.log![]()
Attachments
Issue Links
- relates to
 - 
                    
CORE-19267 reproducible assertion STATUS_FILE_CORRUPT_ERROR in NTOSKRNL iomgr when dealing with file-copying large files and the recycler
-         
 - Open
 
 -