Determining Part of Loading Process of Installation From Debug Logs

All development related issues welcome

Moderator: Moderator Team

Post Reply
berylliumquestion
Posts: 10
Joined: Sun Sep 01, 2019 12:59 am

Determining Part of Loading Process of Installation From Debug Logs

Post by berylliumquestion »

So, on one of my machines I try to install Reactos (I posted to Jira CORE-16362) it stalls out. I'd like to know how I can determine what part of the process it has stalled out at. For instance, the normal debug logs from Qemu look a little like this (This isn't where the problem is, it's just a hypothethical):

(drivers/storage/port/storport/storport.c:963) HwStartIo: FCF05091
(drivers/storage/port/storport/storport.c:964) HwInterrupt: FCF0366A
(drivers/storage/port/storport/storport.c:965) HwFindAdapter: FCF05430
(drivers/storage/port/storport/storport.c:966) HwResetBus: FCF025B3

But right after that something, anything goes wrong, stops and backtrace won't work because it couldn't access memory at 0x%08x, 0x%lx, or 0x%p. How do I determine where in the process it's at? Is there some sort of control diagram I could look at? Where's a good place to start?

EDIT:
I just noticed that there was a very inconspicuous file named notes.txt in the freeldr folder. Is everything up to date in that file?

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest