I can't remember whether NT 4.0 had that feature - quite
possibly. Look in the de{*filter*} output window and the
cryptic message there will tell you _why_ a user
breakpoint was called.
Quote:
> Hi
> I use NT 4.0. Is it the same as with W2k?
> Oli
> >Look in the de{*filter*} output window (type Alt+2 to open it).
> >There will be a cryptic message from the memory allocation
> >system telling you about memory corruption or some other
> >problem. The breakpoint is to make sure you see the
> >message.
> >It's not a project settings problem - it's a memory problem.
> >It doesn't happen when you run it with Ctrl+F5 because
> >Win2K only checks for memory corruption when you run
> >under the de{*filter*}. The problem still exists with Ctrl+F5
> >(it's probably corrupting some of your data) it just isn't
> >detected/reported.
> >> Hi
> >> If I start my console application with Ctrl-F5 everything works allright.
> If
> >> I start it with F5, I get the following message: "User breakpoint called
> >> from code ....". This call was DbgBreakPoint.
> >> Can anybody help me? Perhaps a project settings problem.
> >> Thanks a lot
> >> Oli
> >--
> >.Bruce Dawson, Humongous Entertainment (we're hiring).
> > http://www.*-*-*.com/
> >Send job applications by e-mail, post technical questions
> >to the newsgroups please. Thanks.
--
.Bruce Dawson, Humongous Entertainment (we're hiring).
http://www.*-*-*.com/
Send job applications by e-mail, post technical questions
to the newsgroups please. Thanks.
DbgBreakPoint