Debugging with POSE 3.0a8, CW R6 (all patches), 3.5 colour debug ROMs.
I'd like some help deciphering this error. POSE reports:
********************************************************************************
21216.033 (144353): === ERROR: "YourApp" 1.8.9 reports "Blitter.c,
Line:468, Invalid Params". If this is the latest version of "YourApp",
please report this to the application author.
21216.033 (144353): === ERROR:
********************************************************************************
The CW stack looks like this:
PilotMain
EventLoop
0x10C697F8(FrmDispatchEvent)
0x10C65E64(PrvSendEventToForm)
MainFormViewHandleEvent
0x10C68C4C(FrmAlert)
0x10C69202(FrmCustomAlert)
0x10C66714(FrmDrawForm)
0x10C55662(WinSaveBits)
0x10C55E52(WinCopyRectangle)
0x10C4E0EC(BltCopyRectangle)
0x10C18382(ErrDisplayFileLineMsg)
10C4E0EC: 4FEF000A lea 10(a7),a7
10C4E0F0: 262A0036 move.l 54(a2),d3
10C4E0F4: 6716 beq.s *+24 ; 0x10c4e10c
10C4E0F6: 082C00060006 btst #6,6(a4)
10C4E0FC: 670E beq.s *+16 ; 0x10c4e10c
10C4E0FE: 4A6C0010 tst.w 16(a4)
10C4E102: 6708 beq.s *+10 ; 0x10c4e10c
10C4E104: 2F03 move.l d3,-(a7)
10C4E106: 4E4F trap #15
10C4E108: A012 sysTrapMemChunkFree
10C4E10A: 584F addq.w #4,a7
10C4E10C: 206EFFFC movea.l -4(a6),a0
10C4E110: 4A28041E tst.b 1054(a0)
10C4E114: 671E beq.s *+32 ; 0x10c4e134
10C4E116: 082B00030006 btst #3,6(a3)
10C4E11C: 6716 beq.s *+24 ; 0x10c4e134
10C4E11E: 3F2EFFF2 move.w -14(a6),-(a7)
10C4E122: 3F2EFFF4 move.w -12(a6),-(a7)
10C4E126: 3F2EFFF8 move.w -8(a6),-(a7)
10C4E12A: 3F2EFFF6 move.w -10(a6),-(a7)
10C4E12E: 4E4F trap #15
10C4E130: A0F1 sysTrapScrDrawNotify
10C4E132: 504F addq.w #8,a7
10C4E134: 082A00070034 btst #7,52(a2)
10C4E13A: 670E beq.s *+16 ; 0x10c4e14a
10C4E13C: 55AA0030 subq.l #2,48(a2)
10C4E140: 2F2A0030 move.l 48(a2),-(a7)
10C4E144: 4E4F trap #15
10C4E146: A012 sysTrapMemChunkFree
At the point of failure, the following code:
------
case AutoPushButton:
if ( auto )
{
fails here ------> button = FrmAlert( RepeatAlert );
auto = false;
}
else
{
bVisual = false;
}
bHandled = true;
break;
----------------
I don't really understand how to begin digging into this. It appears that
the call to FrmAlert / FrmCustomAlert is breaking down deep inside Blitter.c.
Can someone steer me right?
--
Andrew Ball
[EMAIL PROTECTED]
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
