| WinUAEScanner by The Deadliners [web] | ||||||||
|---|---|---|---|---|---|---|---|---|
|
|
|||||||
|
popularity : 57% |
|||||||
alltime top: #11705 |
|
|||||||
|
||||||||
added on the 2021-03-11 12:18:30 by Soundy  |
||||||||
popularity helper
comments
Not coding against emulators and not using windows, but take my thumb anyway. :-)
I use more FS-UAE than WinUAE lately (I am more of a Linux user). Anyway, you got my thumb. :]
What ham said. Also docu-link: http://deadliners.net/WinUAEScanner_Documentation.pdf
Interesting stuff, thx for sharing it with us.
Great! Need to try this at once!
Another useful tool from the deadliners!
My workflow is on FS UAE, but considering I have huge trouble with Amiga-Assembly debugger, I may config WinUAE and use this one instead ^^
Demotools for the masses
Link to the application seems broken.
Real shame as I have a nice debugging problem that would really help solve it.
Real shame as I have a nice debugging problem that would really help solve it.
Do not cry for me Amigaaaaaa.
mcgeezer can you describe the problem? I tried clicking on the link with 3 different devices, and I always get the .zip file.
Sorry t doesn't work for you
Sorry t doesn't work for you
Quote:
mcgeezer can you describe the problem? I tried clicking on the link with 3 different devices, and I always get the .zip file.
Sorry t doesn't work for you
Just tried again Soundy and now this is working.
Thanks for sorting this, I have a problem that this will help me fix quickly!
Uploaded a new version fixing some cases when tags were not found, and improved the doc a bit. Cheers.
Looks cool
tool thumbs :)
Tried it and seems useful, doesn't fully appear to work for me though.
When clicking on the " View Vars" button, I get an unhandled exception which in turn causes the tool to lose its main functionality.
Also, the offset to the area to be debugged should be a long as otherwise it's not possible to watch data in a large buffer, limitation to a word doesn't make sense for me.
When clicking on the " View Vars" button, I get an unhandled exception which in turn causes the tool to lose its main functionality.
Also, the offset to the area to be debugged should be a long as otherwise it's not possible to watch data in a large buffer, limitation to a word doesn't make sense for me.
Thank you StingRay for the very constructive feedback. Updated the tool with long offsets as you suggested. Also added more exception catching code and error messages. Feel free to send me your ADF through FaceBook, I'll try to find out why it crashes in your case.
Thanks for the quick update, Soundy. The exception is now caught ("Variable type not identified at offset: $xxxx"). I'll do some more tests and will send you a message on FB if I can't figure out the reason for the exception on my own.
submit changes
if this prod is a fake, some info is false or the download link is broken,
do not post about it in the comments, it will get lost.
instead, click here !
code when using WinUAE. The trick consists in reading the memory pages from
WinUAE's application process and searching for data to watch. This is a very
simple hack, no rocket science at all, yet helped me to quickly spot errors.
Doc: WinUAEScanner_Documentation.pdf