Login
Username:

Password:

Remember me



Lost Password?

Register now!
Sections
Who's Online
91 user(s) are online (83 user(s) are browsing Forums)

Members: 0
Guests: 91

more...
Support us!
Recent OS4 Files
OS4Depot.net
Report message:*
 

Re: The MiniGL thread

Subject: Re: The MiniGL thread
by Hans on 2019/3/17 13:20:46

@kas1e
Quote:

As you can see ABADCAFE in DAR , which mean we have accessed uninitialized memory.

Correct. The program has somehow ended up using uninitialized memory.

Quote:
Stack trace point out in end of all on Warp3DNova, but that can be and SDL itself which cause that, and MiniGL, and Nova itself..

Actually, that's clearly MiniGL + Warp3D (the old one). Try not to get the old Warp3D and Warp3D Nova mixed up.

@Capehill

Quote:
I hope also Hans would take a look at the crash. I will try to reproduce it again but if it has to be a some kind of stress test, it will be hard and time-consuming.


Based on the stack trace, the driver is calling IExec->AllocItemPool() but the pointer to the item pool is obviously wrong. Possible reasons why that could happen:
- Random memory trashing has corrupted the RadeonHD_RM.resource context (or not so random memory trashing, like an app/lib writing beyond the end of an array
- The pointer to said context itself has been corrupted
- The RadeonHD_RM.resource context was destroyed, but it's still being used

No idea why any of the above would suddenly happen.

Hans

Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project