Re: Strange exception, please help
nospam_at_cristalink.com
Date: 11/02/04
- Previous message: Leroy Casterline: "Re: Strange exception, please help"
- In reply to: Leroy Casterline: "Re: Strange exception, please help"
- Next in thread: Leroy Casterline: "Re: Strange exception, please help"
- Reply: Leroy Casterline: "Re: Strange exception, please help"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 3 Nov 2004 10:15:18 +1300
CC is INT 3 being the breakpoint instruction. You have a breakpoint in the
middle of an instruction. Try to delete all your breakpoints. Or delete the
workspace and rebuild the project.
-- http://www.cristalink.com "Leroy Casterline" <spamfreeme@nospam.com> wrote in message news:qfqfo057o17g7dfn3peh9jlla2p0kid0ac@4ax.com... > >You should have included the crash dump analysis produced by > >"!analyze -v". >>Are you sure that the instruction code was the same at the time of the >>crash? > > This is happening in an application rather than in a driver. The code is > written in BCB 6, so I'm using Borland's debugger rather than WinDbg. > > Yes, the instruction code is identical between crashing and non-crashing > runs. The only difference is the location of the instruction in virtual > memory. Commenting/uncommenting a line of code in my app shifts the > location of the failing instruction by 20 bytes. The failure is > absolutely repeatable. > > Baring a hardware problem, do you know of any way that an instruction > could write to an address other than its target address? Perhaps a > problem with virtual memory mapping or some such?
- Previous message: Leroy Casterline: "Re: Strange exception, please help"
- In reply to: Leroy Casterline: "Re: Strange exception, please help"
- Next in thread: Leroy Casterline: "Re: Strange exception, please help"
- Reply: Leroy Casterline: "Re: Strange exception, please help"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|