Throwing exception in Autocad dialog kill Acad session

[majklha]

I have a ARX application with dialog. If I throw and subsequently catch exception in ARX code, program will return to AutoCAD. It is expected behavior.

But, If I throw exception in dialog code (for example in OnBnClickedButton function) , Autocad fell. 

I tested it on easy application generated by ARX Wizard. 

Example 1 (works properly) - called from command:

void Pokus()
{
try
{
throw std::exception("Pokus");
}
catch (std::exception& except)
{
acutPrintf(L"\nExcept: %s", except.what());

}
}

example 2 (kill Acad):

void Pokus()
{
try
{
CPokDialog dlg;
dlg.DoModal();
}

catch (std::exception& except)
{
acutPrintf(L"\nExcept: %s", except.what());

}
}



void CPokDialog::OnBnClickedButton1()
{
throw std::exception("throw");
}

[Alexander.Rivilis]

What behavior did you expect? This is a very bad practice to leave an unhandled exception.

[majklha]

It is maybe bad understanding. 

I am not leaving unhandled exception. The problem, I have, is that I handle exception (I have there catch block) and after it I return to ACAD (eg. acedRetNil()). And normal behavior is that Acad continue normally, user function was interrupted. It is first example.

But if i am in dialog - second example, the Autocad fell, although exception was handled....

Showing code was only part, of course. 

Thanks,

M.

[Alexander.Rivilis · Accepted solution]

If you not catch exception within CPokDialog::OnBnClickedButton1 method - this exception will be passed to AutoCAD message loop and will be unhandled as far as AutoCAD do not know that you will try to catch it after dialog will be closed. So you have to catch this exception within CPokDialog::OnBnClickedButton1