Hello all,
Iam new to unix while executing java program which finely working in windows know iam testing with unix ,but in unix while executing iam getting core dump, my application is in client server environment and it is menu drivrn application on clicking options no problem but after some time it result in core dump and client terminaes, iam writing scripts to run them which follow like here:
At server side:
At client side
and iam running these scripts in
place please check this if u come across any solutions please tell me step by step
this is first time iam coming acorss core dump if u can help me it will be a great favour as u r the masters of unix.please help me.
My options take there path
<b>
for ex:
netscape=/user/bin/netscape
jot=/user/bin
clock=/user/bin/xclock
For sometime they work when i execute them repeatedly they result in coredump.please help me.</b>
I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start
but savecore failed to create the two files, that is vmcore.n and vmunix.n.
savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname
1)... (4 Replies)
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Hi All
I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Hi ,
I want to read core dump file on AIX5.3. While i am trying to use following commands, i am getting only few lines of information.
ux201p3:e46123> dbx capsWrkstnMgr core
Type 'help' for help.
reading symbolic information ...
Segmentation fault in malloc_common.extend_brk at... (1 Reply)
my progrme complaints 'Segmentation fault'.
How to let it print 'Segmentation fault(core dumped)' and generate core dump file?
$ulimit
unlimited (22 Replies)
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Hi guys,
just want to know which core file pattern is best to set for core dumps:
1) per-process file name pattern
or
2) global file name pattern.
I will really appreciate an explanation why the chosen one is better.
Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 Replies
LEARN ABOUT MOJAVE
javah
javah(1) General Commands Manual javah(1)NAME
javah - C header and stub file generator
SYNOPSIS
javah [ options ] fully-qualified-classname ...
javah_g [ options ] fully-qualified-classname ...
DESCRIPTION
The javah command generates C header and source files that are needed to implement native methods. The generated header and source files
are used by C programs to reference instance variables of an object from native source code. The .h file contains a structure definition
whose layout parallels that of the corresponding class. The fields in the structure correspond to instance variables in the class.
The name of the header file and the structure declared within it are derived from the name of the class. If the class passed to javah is
inside a package, the package name is prepended to both the header file name and the structure name. Underscores ( _ ) are used as name
delimiters.
By default, javah creates a header file for each class listed on the command line and puts the files in the current directory. Use the
-stubs option to create source files. Use the -o option to concatenate the results for all listed classes into a single file.
The new native method interface, Java Native Interface (JNI), does not require header information or stub files. The javah command can
still be used to generate native method function prototypes needed for JNI-style native methods. javah produces JNI-style output by
default, and places the result in the .h file.
The javah_g version is a non-optimized version of javah suitable for use with debuggers like jdb.
OPTIONS
The following options are supported:
-o outputfile Concatenates the resulting header or source files for all the classes listed on the command line into outputfile. Only the
-o or -d option may be used.
-bootclasspath path
Specifies path from which to load bootstrap classes. By default, the bootstrap classes are the classes implementing the
core Java 2 platform located in jre/lib/rt.jar and several other jar files.
-classpath path
Specifies the path javah uses to look up classes. Overrides the default of the CLASSPATH environment variable if it is set.
Directories are separated by colons. Thus the general format for path is:
.:<your_path>
For example:
.:/home/avh/classes:/usr/local/java/classes
-d directory Sets the directory where javah saves the header files or the stub files.
-force Specifies that output files should always be written.
-help Prints help message for javah usage.
-jni Causes javah to create an output file containing JNI-style native method function prototypes. This is the default output,
so use of -jni is optional.
-old Specifies the old JDK1.0-style header files should be generated.
-stubs Causes javah to generate C declarations from the Java object file.
-trace Tracing is no longer supported. Instead, use the -verbose:jni option of the virtual machine.
-verbose Indicates verbose output and causes javah to print a message to stdout concerning the status of the generated files.
-version Print out javah version information.
-Joption Pass option to the Java virtual machine, where option is one of the options described on the man page for the java applica-
tion launcher, java(1). For example, -J-Xms48m sets the startup memory to 48 megabytes. It is a common convention for -J to
pass options to the underlying virtual machine.
ENVIRONMENT VARIABLES
CLASSPATH Used to provide the system with a path to user-defined classes. Directories are separated by colons, for example,
.:/home/avh/classes:/usr/local/java/classes
SEE ALSO java(1), javac(1), javadoc(1), javap(1), jdb(1)
13 June 2000 javah(1)