02 May 2022, 00:45 | #1 |
This cat is no more
Join Date: Dec 2004
Location: FRANCE
Age: 52
Posts: 8,442
|
memory watch not working properly
I'm using memory watches for a while now it's been working perfect and saved me a lot of time.
Today I notice that it's failing me (latest winuae) Code:
D0 00000052 D1 00000320 D2 0002FFFF D3 00000002 D4 00000007 D5 FFFFFFFF D6 00000000 D7 FFFF013F A0 000780B0 A1 00051156 A2 001837CC A3 00004F00 A4 00005300 A5 00002A64 A6 00005400 A7 47FDEFE0 USP 001FFC00 ISP 47FDEFE0 SFC 00000005 DFC 00000005 CACR 80008000 TC 00008000 ITT0 00000000 ITT1 00000000 DTT0 00000000 DTT1 00000000 VBR 47FCF000 MSP 001FF800 MMUS 00000000 URP 47FDCE00 SRP 47FDCE00 T=00 S=1 M=0 X=0 N=0 Z=0 V=0 C=0 IMASK=1 STP=0 0: 7FFF-7FFFFFFF-FFFFF800 +nan 7FFF-7FFFFFFF-FFFFF800 +nan 2: 7FFF-7FFFFFFF-FFFFF800 +nan 7FFF-7FFFFFFF-FFFFF800 +nan 4: 7FFF-7FFFFFFF-FFFFF800 +nan 7FFF-7FFFFFFF-FFFFF800 +nan 6: 7FFF-7FFFFFFF-FFFFF800 +nan 7FFF-7FFFFFFF-FFFFF800 +nan FPSR: 00000000 FPCR: 00000000 FPIAR: 00000000 N=0 Z=0 I=0 NAN=0 Prefetch Chip latch 0000FFFE 001831f8 3419 move.w (a1)+ [cccc],d2 Next PC: 001831fa >w 0 $8000 $520c8-$8000 0: 00008000 - 000520C7 (303304) RWI CPU >g Memwatch 0: break at 00008000.L R 00000000 PC=47FC533E CPUDR (000) D0 CCCCCCCC D1 00032000 D2 80008000 D3 00000032 D4 00DFF000 D5 FFFFFF00 D6 47FC4C5E D7 FFFF027F A0 47FC530E A1 00DFF000 A2 47FD52F8 A3 47FD544C A4 47FCE000 A5 00008000 A6 4095B7F8 A7 40943E5C USP 40943E58 ISP 40943E5C SFC 00000000 DFC 00000000 CACR 00008000 TC 00000000 ITT0 00000000 ITT1 00000000 DTT0 00000000 DTT1 00000000 VBR 40073330 MSP 00000000 MMUS 00000000 URP 40075000 SRP 40075000 T=00 S=1 M=0 X=0 N=1 Z=0 V=0 C=0 IMASK=7 STP=0 0: 7FFF-7FFFFFFF-FFFFF800 +nan 7FFF-7FFFFFFF-FFFFF800 +nan 2: 7FFF-7FFFFFFF-FFFFF800 +nan 7FFF-7FFFFFFF-FFFFF800 +nan 4: 7FFF-7FFFFFFF-FFFFF800 +nan 7FFF-7FFFFFFF-FFFFF800 +nan 6: 7FFF-7FFFFFFF-FFFFF800 +nan 7FFF-7FFFFFFF-FFFFF800 +nan FPSR: 00000000 FPCR: 00000000 FPIAR: 00000000 N=0 Z=0 I=0 NAN=0 Prefetch Chip latch 0000012C 47fc533e 2015 move.l (a5) [cccccccc],d0 47fc5340 2ad6 move.l (a6) [00000000],(a5)+ [cccccccc] Next PC: 47fc5342 A1 = 00051156 watchpoint on memory range: 0: 00008000 - 000520C7 (303304) RWI CPU 001831f8 3419 move.w (a1)+ [cccc],d2 does not trigger watchpoint !!!!! (the bogus data is cccc it's located in the zone where the watchpoint is) After that, quitting game (whdload) triggers watchpoint when whdload restores memory first at $8000 so it works. But not at the "high" address. I used that watchpoint successfully for all day. What's the issue? (JIT is off of course). Is there a silent size limit? |
02 May 2022, 21:20 | #2 |
German Translator
Join Date: Aug 2018
Location: Drübeck / Germany
Age: 50
Posts: 214
|
w <num> <address> <length> [other options]
this $520c8-$8000 for length could be wrong? what is the range for the watchpoint? start: $8000 and end: ? try this: >w 0 8000 4a0c8 0: 00008000 - 000520C7 (303304) RWI CPU > |
02 May 2022, 21:32 | #3 |
This cat is no more
Join Date: Dec 2004
Location: FRANCE
Age: 52
Posts: 8,442
|
nope, this is broken
Code:
>w 0 $8000 $520c8-$8000 0: 00008000 - 000520C7 (303304) RWI CPU I can confirm that it doesn't work. Using whdload protect_read (which uses MMU to detect reads) in the same area detects reads. At least I have a workaround. |
04 May 2022, 19:36 | #4 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,609
|
Fixed. Memwatch regions that crossed 64k "bank" (or were larger than 64k) didn't map last bank if it was only partially required.
(This can be seen easily by using "dm" to see which parts of memory map is remapped to debug [D] banks) |
04 May 2022, 19:52 | #5 |
This cat is no more
Join Date: Dec 2004
Location: FRANCE
Age: 52
Posts: 8,442
|
thanks!
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Memory watch point on blitter writing to memory? | mcgeezer | support.WinUAE | 12 | 26 June 2019 22:12 |
Largest memory module for Apollo 1260 that fits properly | DJ Mike | support.Hardware | 9 | 11 October 2013 10:46 |
Apidya not working properly... | Predabot | support.Games | 61 | 03 February 2009 02:02 |
PPC not working properly | Gavilan | support.Hardware | 7 | 05 November 2008 19:03 |
STRICQ not working properly | Unregistered | support.WinUAE | 4 | 10 December 2001 23:32 |
|
|