By default in RDOTNET on unix, R will catch an exception before the CLR can, leading to strange behavior and error messages. For example, consider this, normally handled, null reference exception in C#.
```
try{
string v=null;
var t=v.ToString()
}
catch()
{ //some other logic }
```
Instead of this try/catch executing, the R library tries to handle the exception and prints this message:
>
*** caught segfault ***
address (nil), cause 'memory not mapped'
Possible actions:
1: abort (with core dump, if enabled)
2: normal R exit
3: exit R without saving workspace
4: exit R saving workspace
Segmentation fault
I cannot seem to avoid this behavior on nullreferenceexceptions (this occurs only on CentOS from what I can tell
Comments: Fix included in codebase on branch 'jperraud', as of Revision: 237 Changeset: 8375124a9341c72faaba1bd8a8f31a34d8663b5c [8375124a9341] Pending a bit more testing (including unit test coming at rev 238), issue will be closed.
```
try{
string v=null;
var t=v.ToString()
}
catch()
{ //some other logic }
```
Instead of this try/catch executing, the R library tries to handle the exception and prints this message:
>
*** caught segfault ***
address (nil), cause 'memory not mapped'
Possible actions:
1: abort (with core dump, if enabled)
2: normal R exit
3: exit R without saving workspace
4: exit R saving workspace
Segmentation fault
I cannot seem to avoid this behavior on nullreferenceexceptions (this occurs only on CentOS from what I can tell
Comments: Fix included in codebase on branch 'jperraud', as of Revision: 237 Changeset: 8375124a9341c72faaba1bd8a8f31a34d8663b5c [8375124a9341] Pending a bit more testing (including unit test coming at rev 238), issue will be closed.