Does core dump analysis require program arguments?
 

I was analysing a core dump using KDevelop/GDB. I specified the executable name in Project Options. My program requires some arguments at launch. But I realised that I need not specify the program arguments during coredump analysis. When I load the core file, the program doesn't launch. So, I removed the environment variable settings also from Project Options. I want to confirm if my findings are correct?
I work on C++ and JNI but these observations are common for both.

Thanks

KDevelop/GDB is just a little GUI wrapper around GDB. Effectively, it *IS* GDB.

With the same behavior you asked about in previous links:

http://www.linuxquestions.org/questi...m-name-821216/

http://www.linuxquestions.org/questi...alysis-821217/

PS:
If you're working with JNI, I strong (strongly!) urge you to:

1. Keep your JNI layer as thin as possible (do as LITTLE as possible OUTSIDE of Java)
2. Use C (rather than C++)

Thanks paulsm4 for your reply. Yes, the diff posts relate to gdb. But since these are different, I preferred to put them separately.

At one time, I was passing program arguments but later found that the analysis work even without them and without environment variable setting. This would be because it doesn't run the program. But I just wanted to confirm it over here.

Thanks.