- --
Viewing Issue Advanced Details
| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 04158 | Debugger | Minor | Always | Dec 29, 2010, 12:50 | Aug 7, 2013, 10:01 |
| Tester | Pugsy | View Status | Public | Platform | MAME (Self-compiled) |
| Assigned To | Resolution | Fixed | OS | ||
| Status [?] | Resolved | Driver | |||
| Version | 0.139u2 | Fixed in Version | Build | 64-bit | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 04158: wjammers: Disassembly incorrect when watchpoints used | ||||
| Description | In wjammers (neogeo) if you place a read watchpoint on 100096 when it hits the watchpoint the disassembly is incorrect. It works properly prior to 0.139u2. | ||||
| Steps To Reproduce |
As soon as the debugger opens type:- wp 100096,1,r,pc==42e0 press F12 and start a game - the watchpoint will hit just prior to starting play. Note pc==42e0 is surplus really.. wp 100096,1,r is enough to show the bug - it just makes things neater to demonstrate the bug that's all. |
||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | 0.139u2 | ||||
| Affected Sets / Systems | wjammers | ||||
|
Attached Files
|
|||||
Relationships
| There are no relationship linked to this issue. |
Notes
5
|
No.06992
Kale Developer
Jan 2, 2011, 15:06
|
Yes, it more or less happens in several 68k games as per now. |
|---|---|
|
No.06994
AWJ Developer
Jan 2, 2011, 16:52
|
In the lower screenshot, it looks like the disassembler is reading every word byteswapped... both above and below the watchpoint. |
|
No.06996
Kale Developer
Jan 2, 2011, 18:33
|
Yeah, good catch. Something is fucking with the endianess somehow ... |
|
No.09707
AWJ Developer
Aug 7, 2013, 00:29
|
Does this bug still exist in the Windows debugger? It doesn't in the new Qt one, I just checked. |
|
No.09709
Robbbert Moderator
Aug 7, 2013, 10:01
|
Checked current svn of 32-bit debug build (0.149u1+), bug is not there. Checked old 64-bit non-debug (0.148u2) bug is not there either. So, seems to be fixed. |