0

I am writing code for an animation program and I have a problem. I need to set up core dumping. NetBeans is saying this: Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

What do I do to start core dumping? Is there anything in terminal or at the string args[]?

Note: The program fails to run completely, so I do not know what is occurring.

jps
  • 15,760
  • 14
  • 59
  • 71
I have too many problems
  • 1
  • 1
  • 3
  • 2
    Read the error message... it tells you EXACTLY what to do. – Marc B May 04 '13 at 00:25
  • Also, unless you are debugging Java itself or maybe writing native code, you normally don't need to inspect core dumps. – Thilo May 04 '13 at 00:29
  • Maybe helpful: http://stackoverflow.com/questions/9386683/how-do-i-get-a-core-dump-on-os-x-lion?rq=1 , http://stackoverflow.com/questions/9412156/how-to-generate-core-dumps-in-mac-os-x?rq=1 and http://stackoverflow.com/questions/13212000/how-to-generate-core-files-on-a-mac?rq=1 – Thilo May 04 '13 at 00:30
  • 3
    Marc B - I would not have posted a question if I read what it said and it worked, I am not completely incompetent. – I have too many problems May 04 '13 at 00:31
  • @Ihavetoomanyproblems: sorry about that, then. You should have mentioned what you tried, though. A lot of people on Stackoverflow would not have bothered to follow those instructions in the error message. Core dumps on OS X seem to be a bit involved, I hope the linked questions help. – Thilo May 04 '13 at 00:33
  • Thanks a lot for your help, thilo. I apologize for my appalling behavior, I was unaware that people actually did that. Also, those links did help narrow down what wasn't my problem. Thanks again – I have too many problems May 04 '13 at 00:35
  • You're going to have to be a little more detailed with what's happening, or specify that nothing else happens. I think, though, that if you try and run a program and it fails, your JVM is probably crashing on start. –  May 04 '13 at 00:40
  • Nothing happens, it is behaving exactly like there is a syntax error in the code except there isn't a syntax error, it is not running. – I have too many problems May 04 '13 at 00:49
  • Define "not running". – Thorbjørn Ravn Andersen May 04 '13 at 00:57

2 Answers2

2

Open a terminal and execute the command 

$ ulimit -c unlimited

In this terminal, now launch your IDE Eclipse by command line

$ /Path/To/Eclipse/Eclipse.app/Contents/MacOS/eclipse

But this is not a solution for your error when your program is running.

Jeff
  • 21
  • 3
0

Q: You're going to have to be a little more detailed with what's happening, or specify that nothing else happens. I think, though, that if you try and run a program and it fails, your JVM is probably crashing on start.

A: Nothing happens, it is behaving exactly like there is a syntax error in the code except there isn't a syntax error, it is not running.

Q: Define "not running".

A: It will not compile.

So lets get this straight.

  • You have a Java program that is crashing NetBeans when you try to compile it.

  • When NetBeans crashes it says "Failed to write core dump ..." etcetera.

I suggest you ignore the issue with writing the core dump for now. (A dump won't tell you much anyway ... unless you are good at reading dumps. The thread stacktraces might give some hints though. They could be in the "hs_err_<...>" file ... is one is created.)

Instead try to identify what is causing the problem.

Start by compiling your program from the command line; e.g. using the javac command and setting the classpath etc to be equivalent to what it is when you are compiling in NetBeans. (If you have an Ant or Maven build recipe, run those from the command line ...)

  • If it works, then there is a compiler bug in the version of NetBeans you are using.

  • If it gives compilation errors, fix them and try again until your code compiles ... from the command line. Once you've got the fixed program to compile, try it in NetBeans again. If that works, the diagnosis is that there is a bug in NetBeans that is triggered by that particular error in your source code. But you've worked around it.

  • If you get compiler crashes from the command line, there is something in your code that is triggering compiler bugs on both platforms. This could be tricky. You'll need to progressively cut bits out of your code to try to identify the cause.

If you need more help, post the code that is causing the problems ... preferably after cutting out the bits that DON'T seem to matter.

Stephen C
  • 669,072
  • 92
  • 771
  • 1,162
  • I'm sorry, I haven't done any of this before. How do I enter in the path? The path to any .java class or the whole folder? May I have an example? – I have too many problems May 04 '13 at 02:27
  • Read the Java Tutorial for instructions on how to run the Java tools from the command line; e.g. http://docs.oracle.com/javase/tutorial/getStarted/cupojava/index.html – Stephen C May 04 '13 at 07:16