 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
José
Guest
|
 Posted: Tue May 15, 2007 5:07 pm Post subject: Unexpected interrupt break in program |
 |
|
When I test my program, it sometimes stops and shows a bit of assembly
with:
ntdll:DlgBreakPoint:
INT 3
When I hit F9, the program continues.
Did I so something wrong?
--
José |
|
| Back to top |
|
 |
dhoke
Guest
|
| Posted: Tue May 15, 2007 6:56 pm Post subject: Re: Unexpected interrupt break in program |
|
|
1)Is the item actually labeled ntdll:DbgBreakPoint: (D'b'g instead of
D'l'g)?
2)As a guess, seems like your code, or code in some dll your using, is
probably calling the API DebugBreak()... if I'm right, you'll have to
decide whether that is wrong. I sometimes code such calls in an affort to
force a program dump (generally via drwtsn) in code paths that
ShouldNotOccur - maybe something your using has done similarly.
"José" <jose (AT) 127 (DOT) 0.0.1> wrote in message
news:sh8j43l3vod80dhqgufsha5g6qe3lg3pu8 (AT) 4ax (DOT) com...
| Quote: | When I test my program, it sometimes stops and shows a bit of assembly
with:
ntdll:DlgBreakPoint:
INT 3
When I hit F9, the program continues.
Did I so something wrong?
--
José |
|
|
| Back to top |
|
|
José
Guest
|
| Posted: Tue May 15, 2007 7:46 pm Post subject: Re: Unexpected interrupt break in program |
|
|
On Tue, 15 May 2007 09:56:15 -0400, "dhoke"
<dhoke.nojunk@east-shore.com> wrote in borland.public.cppbuilder.ide:
| Quote: | 1)Is the item actually labeled ntdll:DbgBreakPoint: (D'b'g instead of
D'l'g)?
|
Yes, Dbg as in DeBuG
| Quote: | 2)As a guess, seems like your code, or code in some dll your using, is
probably calling the API DebugBreak()...
|
Anyhow, there is no self made DLL.
When I singlestep my program (with F the interrupt occurs when an
event procedure is completed.
I removed some things from the event procedure, which also removed the
interrupt. Eventually I discovered an error: I had declared a function
with a wchar_t parameter and I called it with a WideString. The
compiler did not rebuke me for that, and the program worked perfectly
when it wasn't being debugged.
--
José |
|
| Back to top |
|
|
Dennis Jones
Guest
|
| Posted: Thu May 17, 2007 1:04 am Post subject: Re: Unexpected interrupt break in program |
|
|
"José" <jose (AT) 127 (DOT) 0.0.1> wrote in message
news:b2hj439j8uhu1jjkq1k82ae3gaa71n4hbp (AT) 4ax (DOT) com...
| Quote: | When I singlestep my program (with F the interrupt occurs when an
event procedure is completed.
I removed some things from the event procedure, which also removed the
interrupt. Eventually I discovered an error: I had declared a function
with a wchar_t parameter and I called it with a WideString. The
compiler did not rebuke me for that, and the program worked perfectly
when it wasn't being debugged.
|
I have encountered this problem before too. I don't remember the details,
but if I recall correctly, there are some functions in Microsoft's DLL's in
which they failed to remove debug interrupts (apparently used when debugging
the OS). Thus, when debugging your application, you may encounter these
debug interrupts if your code calls (either directly or indirectly) into one
of the affected functions. If I am correct about this, the problem is not a
bug in your code nor in Borland's debugger, and is safe to ignore because it
will not affect your application when it is executed outside of a debugger.
- Dennis |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
