Sponsored Content
Top Forums Shell Programming and Scripting Segmentation Fault(Core Dump) Error Post 302442048 by jim mcnamara on Tuesday 3rd of August 2010 06:59:56 AM
Old 08-03-2010
There is not really enough here to make good suggestions. Have your tried to run a debugger (jdi, jdb, etc.) on the class code to see where it is crashing? You need to see what incoming data is like just before the segfault, and where in the code it is crashing.

Segfaulting is usually the result of trying to store XXX data into a memory location, where only X memory is allocated.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Segmentation fault (core dumped)

Hello To All! Now anfd then I receive a message on my console: Segmentation fault (core dumped) What does it mean? Or more precisely what are the implications? :confused: (1 Reply)
Discussion started by: Ivo
1 Replies

2. Programming

Segmentation Fault (core dumped)

what r the situations to receive an error msg like the one below Segmentation Fault (core dumped) (2 Replies)
Discussion started by: bankpro
2 Replies

3. Solaris

Segmentation Fault (core dumped)

i am getting Segmentation Fault (core dumped) on solaris, but when i run the same program with same input on linux it runs successfully. How can i trace the fault in program on solaris. (6 Replies)
Discussion started by: junaid.nehvi
6 Replies

4. HP-UX

memory fault(core dump)

i am getting memory fault (core dump) in a C program i want to know which statement execution caused it. i tried following things $ gdb generalised_tapinread_mod HP gdb 5.4.0 for HP Itanium (32 or 64 bit) and target HP-UX 11.2x. Copyright 1986 - 2001 Free Software Foundation, Inc.... (2 Replies)
Discussion started by: junaid.nehvi
2 Replies

5. UNIX for Advanced & Expert Users

Segmentation Fault and Core dump

Hi All, I have this dbt since long ... What is the difference between Segmentation Fault and Core Dump ? As far as I know Seg fault is due to memory leakage or memory which cannot be accessed. Please let me know if I am wrong. Can some one tell me what is the diff between Segmentation... (1 Reply)
Discussion started by: shubhranshu
1 Replies

6. Solaris

segmentation fault core dumped

i am getting segmentation fault (core dumped) i tried following things but couldn't understand what is wrong with my prog and where the problem is.... i have only adb debugger available on solaris.... so plz help bash-3.00$ pstack core core 'core' of 765: ./mod_generalised_tapinread... (4 Replies)
Discussion started by: junaid.nehvi
4 Replies

7. Red Hat

Segmentation fault (core dumped)

Hi All, I am getting "Segmentation fault (core dumped)" error in the runtime. I am new this please can you tell me why is that i am getting this error and I am not sure of my compilation : gcc -c avc_test.c gcc -c md5.c gcc avc_test.o md5.o -shared -Llibcoreavc_sdk.so -o proj ... (1 Reply)
Discussion started by: fido.genial
1 Replies

8. Programming

getting Segmentation Fault (core dumped) error but Program runs fine.

i am executing following program int main() { char str; FILE * fp; int i=0; ... (4 Replies)
Discussion started by: bhavesh.sapra
4 Replies

9. UNIX for Advanced & Expert Users

Segmentation Fault/ core dumped in metadb

When I was trying to mirror in my v880 server after OS up gradation from 8 to 10 metadb -afc 3 /dev/dsk/c1t1d0s7 I got an error metadb: Segmentation Fault Segmentation Fault (core dumped) Then I logged a case to Oracle/sun team they suggest "Please could you try metadb -ac 3... (0 Replies)
Discussion started by: taherahmed
0 Replies

10. UNIX and Linux Applications

Tilda Segmentation fault (core dumped)

Can anyone tell me why I keep getting a Segmentation fault when I try to run tilda? $ tilda Segmentation fault (core dumped) It seemed to run after I deleted my tilda directory like this thread said to do. Unfortunately it wouldn't let me set my keybinding with anything I tried. ... (0 Replies)
Discussion started by: cokedude
0 Replies
java(5) 							File Formats Manual							   java(5)

NAME
java, javac, jre, jdb, javah, javap, javadoc, appletviewer, rmic, rmiregistry, serialver, native2ascii, jar, javakey - The Java Develop- ment Kit tools SYNOPSIS
java [ options ] classname <args> java_g [ options ] classname <args> DESCRIPTION
This reference page describes the java command only. The Java Development Kit (JDK) is part of the Java Virtual Machine (VM). If the JDK documentation was installed on your Tru64 UNIX system, you can view documentation on all of the JDK tools, and other Java reference mate- rial, at the following location: /usr/share/doclib/java/index.html The java command invokes an interpreter that executes Java bytecodes. It executes Java class files created by a Java compiler, for instance, javac. NOTES
Any arguments that appear after classname on the command line are passed to the main method of the class. The java command expects the binary representation of the class to be in a file called classname.class, which is generated by compiling the corresponding source file with javac. All Java class files end with the filename extension .class which the compiler automatically adds when the class is compiled. classname must contain a main method defined as follows: class Aclass { public static void main(String argv[]){ . . . } } java executes the main method and then exits unless main creates one or more threads. If any threads are created by main then java doesn't exit until the last thread exits. Ordinarily, you compile source files with javac then run the program using java. However, java can be used to compile and run programs when the -cs option is used. As each class file is loaded its modification date is compared to the modification date of the class source file. If the source has been modified more recently, it is recompiled and the new class file is loaded. java repeats this procedure until all the classes are correctly compiled and loaded. The interpreter can determine whether a class is legitimate through the mechanism of verification. Verification ensures prior to their exe- cution that class files do not violate any language constraints. java_g is a non-optimized version of java suitable for use with debuggers like jdb. EXAMPLES
The classname argument is the name of the class to be executed. classname must be fully qualified by including its package in the name, for example: % java java.lang.String When you define your own classes you need to specify their location. Use CLASSPATH to do this. CLASSPATH consists of a colon separated list of directories that specifies the path. For example: .:/home/xyz/classes The system always appends the location of the system classes onto the end of the class path unless you use the -classpath option to specify a path. OPTIONS
Allows the Java debugger, jdb, to attach itself to this java session. When -debug is specified on the command line, java displays a pass- word which must be used when starting the debugging session. When a compiled class is loaded, this option causes the modification time of the class bytecode file to be compared to that of the class source file. If the source has been modified more recently, it is recompiled and the new class file is loaded. Specifies the path java uses to look up classes. Overrides the default or 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/xyz/classes:/usr/local/java/classes Sets the maximum size of the memory allocation pool (the garbage collected heap) to x. The default is 16 megabytes of memory. x must be greater than or equal to 1000 bytes. By default, x is measured in bytes. You can specify x in either kilobytes or megabytes by appending the letter k for kilobytes or the letter m for megabytes. Sets the startup size of the memory allocation pool (the garbage collected heap) to x. The default is 1 megabyte of memory. x must be > 1000 bytes. By default, x is measured in bytes. You can specify x in either kilobytes or megabytes by appending the letter k for kilobytes or the letter m for megabytes. Turns off asynchronous garbage collection. When activated no garbage collection takes place unless it is explicitly called or the program runs out of memory. Normally garbage collection runs as an asynchronous thread in parallel with other threads. Turns off garbage collection of Java classes. By default, the Java interpreter reclaims space for unused Java classes during garbage collection. Prints the build version information. Prints a usage message. Each Java thread has two stacks: one for Java code and one for C code. The -ss option sets the maximum stack size that can be used by C code in a thread to x. Every thread that is spawned during the execution of the program passed to java has x as its C stack size. The default units for x are bytes. The value of x must be greater than or equal to 1000 bytes. You can modify the meaning of x by appending either the letter k for kilobytes or the letter m for megabytes. The default stack size is 128 kilobytes (-ss 128k). Each Java thread has two stacks: one for Java code and one for C code. The -oss option sets the maximum stack size that can be used by Java code in a thread to x. Every thread that is spawned during the execution of the program passed to java has x as its Java stack size. The default units for x are bytes. The value of x must be greater than or equal to 1000 bytes. You can modify the meaning of x by appending either the letter k for kilobytes or the letter m for megabytes. The default stack size is 400 kilobytes (-oss 400k). Prints a trace of the instructions executed (java_g only). Causes java to print a message to stdout each time a class file is loaded. Runs the verifier on all code. Runs the verifier on all code that is loaded into the sys- tem via a classloader. verifyremote is the default for the interpreter. Turns verification off. Causes the garbage collector to print out messages whenever it frees memory. Redefines a property value. propertyName is the name of the property whose value you want to change and newValue is the value to change it to. For example, this command line % java -Dawt.button.color=green ... sets the value of the property awt.button.color to "green". java accepts any number of -D options on the command line. ENVIRONMENT VARIABLES
Used to provide the system a path to user-defined classes. Directories are separated by colons, for example, .:/home/xyz/classes:/usr/local/java/classes SEE ALSO
If the JDK documentation was installed on your Tru64 UNIX system, you can view it at the following location: /usr/share/doclib/java/index.html delim off java(5)
All times are GMT -4. The time now is 11:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy