user breakpoint 
Author Message
 user breakpoint

why in vc 6.0 do i get a USER CALLED BREAKPOINT FROM CODE AT ..... ?

i have NO breakpoints set at all, and F5 continues without grief.

is this some type of crash?



Wed, 19 Jan 2005 02:50:20 GMT  
 user breakpoint

Quote:
> why in vc 6.0 do i get a USER CALLED BREAKPOINT FROM CODE AT ..... ?

> i have NO breakpoints set at all, and F5 continues without grief.
> is this some type of crash?

Not necessarily.  See this KB article Q130667: "PRB: F12 Causes Hard-
Coded Breakpoint Exception When Debugging"

Also, this from "Troubleshooting Common Problems with Applications:
Debugging in the Real World
Mark Long
Microsoft Corporation

October 2000"
"When running under the de{*filter*}, you may sometimes get a message saying
that a user breakpoint has been hit, and the breakpoint seems to be in a
system function. This is normally a sign that something is not as it
should be. Look at the following code fragment:

   void * lpMem = malloc(8192);

   free(lpMem);
   free(lpMem);
The second call to free is invalid and generates an INT 3 exception:
user breakpoint hit. This exception is not normally fatal outside of the
de{*filter*} but is a signal that you have a bug in your code."



Wed, 19 Jan 2005 09:42:25 GMT  
 user breakpoint
Is there some artical that analysed this issuse cleanly and deeply???


Quote:

> > why in vc 6.0 do i get a USER CALLED BREAKPOINT FROM CODE AT ..... ?

> > i have NO breakpoints set at all, and F5 continues without grief.
> > is this some type of crash?

> Not necessarily.  See this KB article Q130667: "PRB: F12 Causes Hard-
> Coded Breakpoint Exception When Debugging"

> Also, this from "Troubleshooting Common Problems with Applications:
> Debugging in the Real World
> Mark Long
> Microsoft Corporation

> October 2000"
> "When running under the de{*filter*}, you may sometimes get a message saying
> that a user breakpoint has been hit, and the breakpoint seems to be in a
> system function. This is normally a sign that something is not as it
> should be. Look at the following code fragment:

>    void * lpMem = malloc(8192);

>    free(lpMem);
>    free(lpMem);
> The second call to free is invalid and generates an INT 3 exception:
> user breakpoint hit. This exception is not normally fatal outside of the
> de{*filter*} but is a signal that you have a bug in your code."



Sat, 22 Jan 2005 08:47:32 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. Unhandled Exception:User Breakpoint Message

2. User breakpoint called from code at 0x77fa018c

3. Mysterious user breakpoint?

4. User BreakPoint problem

5. User breakpoint from code ad 0x77f9f9df

6. user breakpoint

7. user breakpoint in DBGHEAP.c

8. User Breakpoint in WS2_32.DLL

9. user breakpoint

10. User breakpoint called from ...

11. Unexplicable User breakpoint called at 77F9EEA9 - exact error someone else had posted

12. User breakpoint

 

 
Powered by phpBB® Forum Software