Home/ Questions/Q 337741
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T10:21:51+00:00

My Java (Eclipse) application is spawning a child process, monitoring its stdout stream and

  • 0

My Java (Eclipse) application is spawning a child process, monitoring its stdout stream and exit value. When the child process is crashing with SIGABRT, there is no core dump file created. If I start the child process manually and kill it, the core dump is there alright.

I couldn’t find any info about whether the JVM prepares somehow the child process (for example setting the core dump file size to 0).

Does anybody know what might be going on and what settings to change so that the core dumps are created?

This is on Suse 10 and Ubuntu 9.04, with Java 5 and 6, if it makes any difference.

best regards,
Vlad

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Normally, the (non-)creation of core files is controlled by the ulimit command (specifically ulimit -c). See help ulimit (in bash) for details.

    This setting should be inherited from shell to subshell, so Java should use the setting in the shell it was started from. Java might mess with ulimit, but I’ve never heard of it doing this.

    Try setting ulimit in a shell, then starting your Java process from there. If that does not help, you could invoke a wrapper script from Java which sets ulimit, then starts your program.

    • 0