TASEmulators / TASEmulators/BizHawk
How to enable trace options for Sega Genesis/Mega Drive II case?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Now it is grey color and not allow to select this item in menu. How to enable it? It is first part of question, other is: that trace is write trace logs correct? Before i use Gens and it work fine... until i get some problem. It write trace.log file as txt file with list of cpu commands and parametres, and A-D registers valuer per each line... but it missed strings, when interrupt happen. It write interrupt code, but main tread is not. So trace no have few strings of data. For example i write trace and ram dump file same time. Then start read trace file and recreate memory image by commands from this trace file. So i found some place, where should be cycle and dump for emulator - shows memory with "1" for each of cycle iteration. But trace file not have this last 4 iterations of cycle, because same time interrupt happen and trace file write data from it, and not write main thread with this cycle. I hope my bad language is enough to explain problem. So my question is - how to enable trace for BizHawk with Sega Genesis/Mega Drive II and it write this... "hyper treating" case? Will it save both threads of code same time? I need to get accurate trace.log file for my work.
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 reproducing the Sega Genesis/Mega Drive II case through BizHawk's trace menu, capturing trace.log and the RAM dump while the interrupt occurs. Compare the missing main-thread instructions with the interrupt entries and document whether the trace option can be enabled and whether both execution paths are recorded accurately.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100