I don't know why, but sometimes I will get this message when I have other
break points set. I usually just delete (D*) all other break points and then
set the new one.
HTH,
James
Hi all,
>>
>> Anyone see why I cannot set a breakpoint at line 60?
>>
>> SIS907: 59:IF BAL.LIST<1,A
VLIST the program and make sure source matches object
> Any include files that would confuse the debuggers line numbering?
>
> > Anyone see why I cannot set a breakpoint at line 60?
> >
> > SIS907: 59:IF BAL.LIST<1,ARI.PTR> # 0 THEN
> > SIS907: 60: ARI.ID =
has the source changed since it was last compiled ?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, July 28, 2005 11:21 AM
To: u2-Users
Subject: [U2] Bad Address for Breakpoint in Debugger
Hi all,
Anyone see why I cannot
Any include files that would confuse the debuggers line numbering?
Brian
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: 28 July 2005 16:21
> To: u2-Users
> Subject: [U2] Bad Address for Breakpoint in Debugger
>
> Hi
... because it's in the middle of a loop?
Pete Dick
Technology Support
www.epicor.com
Tel.: +44 (0)1344 468220
Fax: +44 (0)1344 468055
1 The Arena, Downshire Way, Bracknell, Berks, UK, RG12 1PU This e-mail
is for the use of the intended recipient(s) only. If you have received
this e-mail in
