visual studio .net debugging: I have a problem. My application hangs when disposing the main form while
exiting it. The call stack is:
kernel32.dll!_IsBadReadPtr@8() + 0x11 bytes
PavSHook.dll!502875b2()
[Los marcos siguientes pueden no ser correctos o faltar, no se han cargado
símbolos para PavSHook.dll]
user32.dll!_DefWindowProcW@16() + 0x90 bytes
[Transición de administrado a nativo]
System.Windows.Forms.dll!System.Windows.Forms.Control.SetAcceptDrops(bool
accept = false) + 0xe6 bytes

System.Windows.Forms.dll!System.Windows.Forms.Control.OnHandleDestroyed(System.EventArgs e) + 0xc9 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WmDestroy(ref
System.Windows.Forms.Message m = {System.Windows.Forms.Message}) + 0x47 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WndProc(ref
System.Windows.Forms.Message m) + 0x42c bytes

System.Windows.Forms.dll!System.Windows.Forms.ScrollableControl.WndProc(ref
System.Windows.Forms.Message m) + 0x45 bytes
System.Windows.Forms.dll!System.Windows.Forms.ContainerControl.WndProc(ref
System.Windows.Forms.Message m) + 0x13 bytes
System.Windows.Forms.dll!System.Windows.Forms.UserControl.WndProc(ref
System.Windows.Forms.Message m) + 0x11 bytes

System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.OnMessage(ref System.Windows.Forms.Message m) + 0xd bytes

System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.WndProc(ref System.Windows.Forms.Message m) + 0xd6 bytes

System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DebuggableCallback(System.IntPtr
hWnd, int msg = 2, System.IntPtr wparam, System.IntPtr lparam) + 0x75 bytes
[Transacción de nativo a administrado]
user32.dll!_InternalCallWinProc@20() + 0x28 bytes
user32.dll!_UserCallWinProcCheckWow@32() + 0xb7 bytes
user32.dll!_DispatchClientMessage@20() + 0x4d bytes
user32.dll!___fnDWORD@4() + 0x24 bytes
[quoted text, click to view]
[Transición de administrado a nativo]

System.Windows.Forms.dll!System.Windows.Forms.UnsafeNativeMethods.DestroyWindow(System.Runtime.InteropServices.HandleRef hWnd) + 0xe bytes
System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DestroyHandle()
+ 0x74 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.DestroyHandle() +
0x26c bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.Dispose(bool
disposing = true) + 0xfe bytes
System.Windows.Forms.dll!System.Windows.Forms.Form.Dispose(bool disposing)
+ 0x1fb bytes
APRISA V.exe!APRISAV.APRISAMainForm.Dispose(bool disposing = true) Línea
20 + 0xf bytes C#
System.dll!System.ComponentModel.Component.Dispose() + 0xf bytes

System.Windows.Forms.dll!System.Windows.Forms.ApplicationContext.Dispose(bool disposing) + 0x26 bytes

System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.DisposeThreadWindows() + 0x25 bytes

System.Windows.Forms.dll!System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(int dwComponentID, int reason, int pvLoopData) + 0x2af bytes

System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(int
reason = -1, System.Windows.Forms.ApplicationContext context =
{System.Windows.Forms.ApplicationContext}) + 0x17d bytes

System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoop(int
reason, System.Windows.Forms.ApplicationContext context) + 0x53 bytes

System.Windows.Forms.dll!System.Windows.Forms.Application.Run(System.Windows.Forms.Form mainForm) + 0x2e bytes
APRISA V.exe!APRISAV.GraphicInterface.Exec(APRISAV.ExecArgument argument =
null) Línea 110 + 0x8 bytes C#
APRISA V.exe!APRISAV.ProyectoApp.Run() Línea 143 + 0xb bytes C#
APRISA V.exe!APRISAV.ProyectoApp.Main() Línea 94 + 0x9 bytes C#
mscoree.dll!__CorExeMain@0() + 0x34 bytes
kernel32.dll!_BaseProcessStart@4() + 0x23 bytes

[quoted text, click to view]

I guess it enters an infinite loop, with high CPU utilization, right?
If so, try to determine which function is responsible for the infinite loop -
try to do a series of Debug | Step Out commands and see which of the functions
does not return control to the previous function on the call stack.
(If Debug | Step Out loses track while stepping out of some frames,
an alternative is to set breakpoints on preceding stack frames by r-clicking them
in Call Stack window and choosing "Insert breakpoint")

Regards,
Oleg
[VC++ MVP http://www.debuginfo.com/]

Hi. I have found the problem. The problem is in Panda Antivirus. I have
posted also a problem on which i said thet the debugger hangs when trying to
open a serial port, the problem is also in panda antivirus. If you look at
the call stack you will see a dll named PavSHook.dll. Everytime my
application hangs a call to this libvrary has been made. When i close panda
antivirus i get no more hangs. The problem is that i dont know how to solve
this. IM completely lost.

[quoted text, click to view]