TASEmulators / TASEmulators/BizHawk
[PSX] Using debugger on MainRAM throws readable but unhandled exception
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
When I try to set a breakpoint in debugger with (the only) PSX core on an address that is located in the MainRAM, an exception is thrown. It does says "MainRAM is not currently supported for callbacks", but it however says that the exception is unhandled; it is actually thrown via .NET unhandled exception dialog box. According to adelikat, it is not actually supposed to be unhandled exception. While the emulator will keep running if you press Continue, it would be better if the exception was handled and shown via cusom dialog box, mostly to avoid unexpected consequences.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the PSX debugger breakpoint path for addresses in MainRAM and the exception-handling flow around the "MainRAM is not currently supported for callbacks" message. Confirm that this case is routed to the intended custom dialog rather than the .NET unhandled-exception dialog, while the emulator can continue running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100