[quote user="edg"]My default system debugger is configured to be Visual Studio (even though I have WinDbg installed as well). When the exception occurred in Pegasus, the Exception dialog gives the option to open it in my Debugger without any intermediate DMP file saving involved. If this or any other exception occurs again, I'll see if I can investigate a better way to capture the dump file itself.[/quote]

I assume it works more or less like WinDbg, so there might be a similar approach for exporting a dump file.

Unfortunately, I did not have the Pegasus Crash handler installed..

 The error message dialog was "Unhandled Exception at 0x006cac22 in winpm-32.exe: 0XC0000005: Access violation reading location 0x00000000.

Not sure if there is enough info here, but I opened the exception in my VS debugger, and the call stack looks as follows:

>    winpm-32.exe!006cac22()    
     [Frames below may be incorrect and/or missing, no symbols loaded for winpm-32.exe]   
     winpm-32.exe!006c7b32()    
     user32.dll!_InternalCallWinProc@20()  + 0x23 bytes   
     user32.dll!_UserCallWinProcCheckWow@32()  + 0xb7 bytes   
     user32.dll!_DispatchMessageWorker@8()  + 0xed bytes   
     user32.dll!_DispatchMessageA@4()  + 0xf bytes   
     winpm-32.exe!00582a42()    
     winpm-32.exe!00583d86()    
     winpm-32.exe!007deed6()    
     winpm-32.exe!007ded5f()    
     kernel32.dll!@BaseThreadInitThunk@12()  + 0x12 bytes   
     ntdll.dll!___RtlUserThreadStart@8()  + 0x27 bytes   
     ntdll.dll!__RtlUserThreadStart@8()  + 0x1b bytes   
 

[quote user="edg"]Not sure if there is enough info here, but I opened the exception in my VS debugger, and the call stack looks as follows:[/quote]

Do you have the dump file? If so please forward it to "beta-reports [at] pmail.gen.nz" so we can use it along with the symbol file.

[quote user="idw"]

Do you have the dump file? If so please forward it to "beta-reports [at] pmail.gen.nz" so we can use it along with the symbol file.

[/quote]

Unfortunately, I don't have a dump file as I loaded the exception directly into my debugger to generate the above info. Can you turn that it into a dump file from there (I've never done that before)? Next time, I'll probably just generate a Dump file from the Task manager (or Process Explorer) on the process at the time the exception dialog shows.

More relevant, something went bad in my DNS  right around the same time... but I didn't find out about it until later.  I am thinking that this may have been the underlying issue that caused the crash.  If it occurs again, I will report it (hopefully) with a dump file.

[quote user="edg"]Unfortunately, I don't have a dump file as I loaded the exception directly into my debugger to generate the above info. Can you turn that it into a dump file from there (I've never done that before)? Next time, I'll probably just generate a Dump file from the Task manager (or Process Explorer) on the process at the time the exception dialog shows.[/quote]

I don't know how VS works with regard to this since I'm not using it (well, only the "Express" version in some very rare cases, I'm mainly using Delphi), but the information displayed can only come from a dump (file?) unless you're running Pegasus Mail from within your debugger to begin with. Or are you talking about WinDbg? If so, yes, you can make it write a dump file, just check its help index for an entry named ".dump" (without quotes but including the leading DOT): .dump /mF "FileName" would probably be the most useful command, some more details about using WinDbg can be found here. But if you're preparing for future exceptions you may as well just install the MiniDump extension ...

[quote user="idw"]

I don't know how VS works with regard to this since I'm not using it (well, only the "Express" version in some very rare cases, I'm mainly using Delphi), but the information displayed can only come from a dump (file?) unless you're running Pegasus Mail from within your debugger to begin with. Or are you talking about WinDbg? If so, yes, you can make it write a dump file, just check its help index for an entry named ".dump" (without quotes but including the leading DOT): .dump /mF "FileName" would probably be the most useful command, some more details about using WinDbg can be found here. But if you're preparing for future exceptions you may as well just install the MiniDump extension ...[/quote]

My default system debugger is configured to be Visual Studio (even though I have WinDbg installed as well). When the exception occurred in Pegasus, the Exception dialog gives the option to open it in my Debugger without any intermediate DMP file saving involved. If this or any other exception occurs again, I'll see if I can investigate a better way to capture the dump file itself.