VA 8.5: Fatal Application Error exit dialog

[Marten Feldtmann]

According to the documentation:

" User error codes from 9000 through 9099 will suppress the display of the Fatal Application Error dialog box."

if this is true, how is this possible ? And another question: how can I get rid of this ?

[Marten Feldtmann]

I forgot the dialog

[Marten Feldtmann]

On the other hand: why does esvio.exe at all gives such GUI interaction - its a headless application.

[Marten Feldtmann]

Any idea about this ?

[Louis LaBrunda]

Hi Marten,

I have used "System exit: 9001 withObject: nil" from a VAST 8.0.3 NT service image without a problem or dialog?

Lou

[jtu...@objektfabrik.de]

Lou, Marten,

same here: I use 9001 to signal a failed automated build to hudson, and there's never any dialog or anything. The image gets called by a batch file. But I start abt.exe, not esvio.exe.

So maybe this is a specialty of esvio.exe...?

[Marten Feldtmann]

"System exit: 9001 withObject: nil" under abt.exe works here also. I had to use "System primitiveExit: 9001 withObject: nil" under esvio.exe, because "System exit: 9001 withObject: nil" does not fully work under esvio.exe: it seems to kill lots of stuff within the image (Seaside is not working/serving any more), but it does NOT exit the application.

[jtu...@objektfabrik.de]

okay...

so here's the question for Instantiations: what is the difference between exit:withObject: and primitiveExit:withObject: and which is intended for what?

And while somebody is digging in the docs: maybe some info on the 9001 and up range for the value would also be helpful.

Thanks

Joachim

[Marten Feldtmann]

It's documented under "VA Smalltalk Virtual Machine API : Primitive error codes":

"Users can add new error codes with values above EsPrimErrMinUserError. User error codes from 9000 through 9099 will suppress the display of the Fatal Application Error dialog box."