Monday, December 19, 2005

user breakpoint - Breakpoint exceptions from the heap

New programmers sometimes ask why the debugger stopped at a ‘userbreakpoint’ exception in their program. The exception dialog will comeup and say something like:

Unhandled exception at 0x77f75a58 in CoruptHeap.exe: User breakpoint.

The callstack might be something like:


Or if you have symbols:

ntdll.dll!RtlpBreakPointHeap(void *)
ntdll.dll!RtlpValidateHeapEntry(_HEAP *, _HEAP_ENTRY *, char *)
ntdll.dll!RtlDebugFreeHeap(void *, unsigned long, void *)
ntdll.dll!RtlFreeHeapSlowly(void *, unsigned long, void *)
ntdll.dll!RtlFreeHeap(void *, unsigned long, void *)

The problem is that your program has corrupted the heap. Thisusually happens when writing to freed memory, or when writing past theend of a buffer. Use pageheap to try and figure out where your program went wrong.

the above text was taken from the following page:
btw ; great c++ developer blog.

you entar in the mySql command line client and enter the following command SET PASSWORD FOR 'user'@'host' = OLD_PASSWORD('password');

my user: is peter, my password: something and my host: localhost

the command will be:

Here is a document on debugging linux aps.

electric fence - debug tool for linux: here and here
Lately is known as duma

No comments: