Consequences of failures of UDF in non-protected Mode

Extensibility
Enthusiast

Consequences of failures of UDF in non-protected Mode

As I qualified in a previous post, I'm a Teradata newbie (migrating from Oracle).   Just started writing UDF's.  I see the following Warning in the UDF Programming manual and wanted to understand this in more detail.  There are also some additional comments in the same doc section referring to core dumps, and where they are stored. 

Warning: If the ALTER FUNCTION statement specifies EXECUTE NOT PROTECTED,

and the function fails during execution, the Teradata Database software will

probably restart.

I've got the following questions:

1)Does "function fail" mean anything that would generate a core dump?  Signals SIGBUS, SIGSEGV, etc?  Other conditions?  Could the UDF C code ignore or trap/handle all signals and thereby prevent such a restart?

2)What exactly does it mean when they say the "Database software" will restart?  Does that mean just the application process that encountered the error?  Or will more users/apps or the entire database availability be affected?  I'm trying to gauge the risk when using UDF's.

Thanks much!