| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 03489 | Misc. | Minor | Always | Oct 26, 2009, 23:56 | 24 days ago |
| Tester | Lord Nightmare | View Status | Public | Platform | |
| Assigned To | Resolution | Invalid report | OS | ||
| Status [?] | Closed | Driver | |||
| Version | 0.134u4 | Fixed in Version | Build | ||
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 03489: UNIDASM - tms32010 cpu (possibly others): Word issue in disassembled code | ||||
| Description |
When using the tms32010 architecture disassembles 0x800 bytes, despite the fact that the tms32010 cpu has an address space 0x400 long. I think it's a word since tms32010 is 0x400 WORDS long while it technically needs 0x800 BYTES to store that code. It probably affects several of the other disassemblers as well. An example rom is attached. |
||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | UNIDASM - tms32010 cpu (possibly others) | ||||
|
Attached Files
|
 dtc01_tms32010_int.zip (3,270 bytes) Oct 26, 2009, 23:56 | ||||
 No.22543
hap Developer
24 days ago
edited on: 24 days ago
|
Why should it stop at 0x400? I think it's a good thing that unidasm disassembles the whole file by default. Take for example a program ROM from a NES game with memory banks. If you want it to stop at 0x400, do -count 0x400 *edit* or did you mean that the disassembler was completely broken and disassembled 8-bit words instead of 16-bit words for this CPU? I don't see any issue like that (anymore). |
|---|---|
 No.22545
Lord Nightmare Developer
24 days ago
|
This is no longer valid and/or was fixed long ago. |