On Thu, Dec 14, 2017 at 5:06 AM, LtColRDSChauhan <rdsc1964@...> wrote:

On Thu, Dec 14, 2017 at 3:34 AM, hvlad@... [firebird-support] <firebird-support@yahoogroups. com> wrote:

 

  Looks like there was no crash of Firebird or WER doesn't catch it.

  You may easy check if Firebird really crashed: just look at its PID before and after
run test application (and got exception).

1. The PID remains same: 4212, before and after the exception is caught. 

2. After the exception is caught, connection to the database is lost. Subsequently, any action on my .NET application throws unhandled exception- "Object reference not set to an instance of object". Connection is possible only after re-start of my .NET application.

1. At this point (after the subsequent unhandled exception- "Object reference not set to an instance of object"), there was a crash dump created for my .NET Application. Same is available at:

https://drive.google.com/file/d/1XEqfqjJ66X_I6q-ezHqbmbXU5RZl4fxk/view?usp=sharing

2. Dump Summary as follows:

Dump Summary
------------
Dump File: Inventory.exe.8296.dmp : C:\Users\rdsc1\DumpFolder\Inventory.exe.8296.dmp
Last Write Time: 14-12-2017 05:15:02
Process Name: Inventory.exe : D:\HMS\AppHMS\Program\Inventory.exe
Process Architecture: x64
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information: Not Present

Regards,
Vlad