SA-JDI tests have a problem on Linux during nightly testing

Here is the entry from my nightly analysis report:

New nsk.sajdi failures (from 2007.12.18)
* nsk/sajdi/jdb/options/connect/connect002
* nsk/sajdi/jdb/options/connect/connect004
* nsk/sajdi/SACoreAttachingConnector/attach/attach001
* nsk/sajdi/SACoreAttachingConnector/attach/attach002
* nsk/sajdi/SADebugServerAttachingConnector/attach/attach011
* nsk/sajdi/SADebugServerAttachingConnector/attach/attach012
        These tests failed due to "ERROR: Debuggee core file not found:
        core or core.NNNN" on Linux IA32 Client VM (machine brain) and
        Linux IA32 Server VM (machine colfax003). There are also
        warnings and errors about ulimiting core file size. I'm
        guessing this is some sort of Linux OS issue.

        Update: In the 2007.12.19 nightly, the failures reproduced on
            Linux IA32 Client VM (machine vm-v20z-24).

        Update: These failure first appeared in the 2007.12.13 nightly
            on Linux IA32 Client VM (machine vm-v20z-21) and Linux IA32
            Server VM (machine jck-win5).
These failures reproduced in the 2008.02.12 nightly:

New nsk.sajdi failures (from 2008.02.12)
* nsk/sajdi/jdb/options/connect/connect002
* nsk/sajdi/jdb/options/connect/connect004
* nsk/sajdi/SACoreAttachingConnector/attach/attach001
* nsk/sajdi/SACoreAttachingConnector/attach/attach002
* nsk/sajdi/SADebugServerAttachingConnector/attach/attach011
* nsk/sajdi/SADebugServerAttachingConnector/attach/attach012
        These tests failed due to "ERROR: Debuggee core file not found:
        core or core.NNNN" on Linux IA32 Client VM (machine dip) and
        Linux IA32 Server VM (machine jtg-linux17).

        These tests are covered by the following test bug:

            6644910 4/4 SA-JDI tests have a problem on Linux during
                        nightly testing

        which was closed as "not reproducible" on 2008.02.11. I
        reopened the bug because the analysis was not clear. Pavel
        updated the analysis and closed the bug again on 2008.02.12.

        I will add this entry to the bug and reopen it again.