how to fix core dump?

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

how to fix core dump?

onazari
hi
when i start zekr a java application this error occured how to fix it?
******************************************************************
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f8b34f6aee1, pid=3042, tid=140237238118144
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build
1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode
linux-amd64 compressed oops)
# Problematic frame:
# C  [libsoup-2.4.so.1+0x70ee1]  soup_session_feature_detach+0x11
#
# Failed to write core dump. Core dumps have been disabled. To enable
core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/onazari/zekr/hs_err_pid3042.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
zekr.sh: line 18:  3042 Aborted                 "$JAVA_CMD" $VM_ARGS -cp
"$CLASS_PATH" $MAIN_CLASS $*
******************************************************************
ulimit not available in my pc!

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Per Jessen
om.bagh wrote:

> hi
> when i start zekr a java application this error occured how to fix it?
> ******************************************************************
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007f8b34f6aee1, pid=3042,
> #  tid=140237238118144
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build
> 1.7.0_45-b18)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # C  [libsoup-2.4.so.1+0x70ee1]  soup_session_feature_detach+0x11
> #
> # Failed to write core dump. Core dumps have been disabled. To enable
> core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /home/onazari/zekr/hs_err_pid3042.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.sun.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> zekr.sh: line 18:  3042 Aborted                 "$JAVA_CMD" $VM_ARGS
> -cp "$CLASS_PATH" $MAIN_CLASS $*
> ******************************************************************
> ulimit not available in my pc!


ulimit will only allow the core dump to be written, it will not
automagically fix it :-)  Regardless, 'ulimit' has to be available on
your system.  How did you determine that it is not?



--
Per Jessen, Zürich (-0.8°C)
http://www.hostsuisse.com/ - dedicated server rental in Switzerland.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Per Jessen
om.bagh wrote:

> On 12/12/2013 12:02 PM, Per Jessen wrote:
>> om.bagh wrote:
>>> On 12/12/2013 11:48 AM, Per Jessen wrote:
>>>> om.bagh wrote:
>>>>
>>>>> hi
>>>>> when i start zekr a java application this error occured how to fix it?
>>>>> ******************************************************************
>>>>> #
>>>>> # A fatal error has been detected by the Java Runtime Environment:
>>>>> #
>>>>> #  SIGSEGV (0xb) at pc=0x00007f8b34f6aee1, pid=3042,
>>>>> #  tid=140237238118144
>>>>> #
>>>>> # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build
>>>>> 1.7.0_45-b18)
>>>>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode
>>>>> linux-amd64 compressed oops)
>>>>> # Problematic frame:
>>>>> # C  [libsoup-2.4.so.1+0x70ee1] soup_session_feature_detach+0x11
>>>>> #
>>>>> # Failed to write core dump. Core dumps have been disabled. To enable
>>>>> core dumping, try "ulimit -c unlimited" before starting Java again
>>>>> #
>>>>> # An error report file with more information is saved as:
>>>>> # /home/onazari/zekr/hs_err_pid3042.log
>>>>> #
>>>>> # If you would like to submit a bug report, please visit:
>>>>> #   http://bugreport.sun.com/bugreport/crash.jsp
>>>>> # The crash happened outside the Java Virtual Machine in native code.
>>>>> # See problematic frame for where to report the bug.
>>>>> #
>>>>> zekr.sh: line 18:  3042 Aborted                 "$JAVA_CMD" $VM_ARGS
>>>>> -cp "$CLASS_PATH" $MAIN_CLASS $*
>>>>> ******************************************************************
>>>>> ulimit not available in my pc!
>>>>
>>>> ulimit will only allow the core dump to be written, it will not
>>>> automagically fix it :-)  Regardless, 'ulimit' has to be available on
>>>> your system.  How did you determine that it is not?
>>>>
>>>>
>>>>
>>> i determined by executing "cnf ulimit" commond,
>>> cnf ulimit output:
>>> ulimit: command not found
>>
>> All answers to the emailing list too, please.
>>
>> 'ulimit' is a shell builtin, what happens when you use 'ulimit -a' ?
>>
>>
>> /Per
> hi
> the ulimit -a output:

All answers to the emailing list too, please.

Okay, so you do have a 'ulimit' command.  If you want the core dump, use "ulimit
-c unlimited" to enable it.


/Per
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Carlos E. R.-2
On 2013-12-13 09:28, Per Jessen wrote:

> Okay, so you do have a 'ulimit' command.  If you want the core dump, use
> "ulimit -c unlimited" to enable it.

And call your program from the same terminal or equivalent.


--
Cheers / Saludos,

                Carlos E. R.
                (from 12.3 x86_64 "Dartmouth" at Telcontar)


signature.asc (271 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Per Jessen
Carlos E. R. wrote:

> On 2013-12-13 09:28, Per Jessen wrote:
>
>> Okay, so you do have a 'ulimit' command.  If you want the core dump,
>> use "ulimit -c unlimited" to enable it.
>
> And call your program from the same terminal or equivalent.

Good point, thanks.



--
Per Jessen, Zürich (-0.6°C)
http://www.hostsuisse.com/ - dedicated server rental in Switzerland.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

onazari
On 12/13/2013 05:50 PM, Per Jessen wrote:
> Carlos E. R. wrote:
>
>> On 2013-12-13 09:28, Per Jessen wrote:
>>
>>> Okay, so you do have a 'ulimit' command.  If you want the core dump,
>>> use "ulimit -c unlimited" to enable it.
>> And call your program from the same terminal or equivalent.
> Good point, thanks.
Hi,
i used this command "ulimit -c unlimited" then start the zekr ( a java
application to quran study ) in same terminal, the error ocurred:
*****
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f7307232ee1, pid=11664, tid=140133123618560
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build
1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode
linux-amd64 compressed oops)
# Problematic frame:
# C  [libsoup-2.4.so.1+0x70ee1] soup_session_feature_detach+0x11
#
# Core dump written. Default location: /home/onazari/SOFT/zekr1/core or
core.11664
#
# An error report file with more information is saved as:
# /home/onazari/SOFT/zekr1/hs_err_pid11664.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
zekr.sh: line 18: 11664 Aborted                 (core dumped)
"$JAVA_CMD" $VM_ARGS -cp "$CLASS_PATH" $MAIN_CLASS $*
********
"ulimit -a " output:
****
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 15693
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 15693
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
*******
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Carlos E. R.-2
On 2013-12-13 22:00, om.bagh wrote:
> On 12/13/2013 05:50 PM, Per Jessen wrote:
>> Carlos E. R. wrote:


> Hi,
> i used this command "ulimit -c unlimited" then start the zekr ( a java
> application to quran study ) in same terminal, the error ocurred:

What error? Is the core file created or not? If it is created, the rest
is irrelevant.

--
Cheers / Saludos,

                Carlos E. R.
                (from 12.3 x86_64 "Dartmouth" at Telcontar)


signature.asc (271 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

James Knott
Carlos E. R. wrote:
> What error?

Warp core breach.  ;-)

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Carlos E. R.-2
On 2013-12-13 22:34, James Knott wrote:
> Carlos E. R. wrote:
>> What error?
>
> Warp core breach.  ;-)

ROTFL!

(I barely can type with the tears)

--
Cheers / Saludos,

                Carlos E. R.
                (from 12.3 x86_64 "Dartmouth" at Telcontar)


signature.asc (271 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

onazari
On 12/14/2013 01:19 AM, Carlos E. R. wrote:
> On 2013-12-13 22:34, James Knott wrote:
>> Carlos E. R. wrote:
>>> What error?
>> Warp core breach.  ;-)
> ROTFL!
>
> (I barely can type with the tears)
>
Hi,sorry for delay reply
I download last version of swt.jar from here and replaced it in zekr lib
directory, then zekr work correctly.
but 2 problem occured that is new for me!
1. root directory fulled although I installed only kde on 18 GB brtfs
root partition. xdiskusage report  page attached.
2. /proc/kcore size is near 128TB! why?
best regards.

127.png (31K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Malcolm
On Sun 15 Dec 2013 08:52:16 PM CST, om.bagh wrote:

>On 12/14/2013 01:19 AM, Carlos E. R. wrote:
>> On 2013-12-13 22:34, James Knott wrote:
>>> Carlos E. R. wrote:
>>>> What error?
>>> Warp core breach.  ;-)
>> ROTFL!
>>
>> (I barely can type with the tears)
>>
>Hi,sorry for delay reply
>I download last version of swt.jar from here and replaced it in zekr
>lib directory, then zekr work correctly.
>but 2 problem occured that is new for me!
>1. root directory fulled although I installed only kde on 18 GB brtfs
>root partition. xdiskusage report  page attached.
>2. /proc/kcore size is near 128TB! why?
>best regards.
>
Hi
Have you configured snapper to remove old snapshots?

Look at /etc/snapper/configs/root and wind it back (I only keep 4
number and timelines...)

The following commands show disk usage;
[CODE]
btrfs filesystem show
btrfs filesystem df /
[/CODE]


--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLED 11 SP3 (x86_64) GNOME 2.28.0 Kernel 3.0.101-0.8-default
up 2 days 2:35, 4 users, load average: 0.52, 0.57, 0.62
CPU Intel® B840@1.9GHz | GPU Intel® Sandybridge Mobile


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Carlos E. R.-2
In reply to this post by onazari
On 2013-12-15 18:22, om.bagh wrote:
> 2. /proc/kcore size is near 128TB! why?

It is a virtual file, it does not really "exist".

--
Cheers / Saludos,

                Carlos E. R.
                (from 12.3 x86_64 "Dartmouth" at Telcontar)


signature.asc (271 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Rajko M.
On Sun, 15 Dec 2013 20:24:09 +0100
"Carlos E. R." <[hidden email]> wrote:

> On 2013-12-15 18:22, om.bagh wrote:
> > 2. /proc/kcore size is near 128TB! why?
>
> It is a virtual file, it does not really "exist".
>

Even if it does not exist, it can't be bigger then RAM.

(128TB is a biiig RAM.)

--
Regards, Rajko.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Martin Helm-2
Am 16.12.2013 06:32, schrieb Rajko:
> Even if it does not exist, it can't be bigger then RAM. (128TB is a
> biiig RAM.)

Off top of my head I think to remeber that 64-bit systems show 128TB of
kcore, because it is the limit the 64-bit
chipset can handle and kcore is set up to map the maximum memory not the
actual memory.

Maybe an expert knows more.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Martin Helm-2
Am 16.12.2013 11:11, schrieb Martin Helm:
> Off top of my head I think to remeber that 64-bit systems show 128TB
> of kcore, because it is the limit the 64-bit chipset can handle and
> kcore is set up to map the maximum memory not the actual memory. Maybe
> an expert knows more.

http://www.novell.com/support/kb/doc.php?id=7004153

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: how to fix core dump?

Rajko M.
On Mon, 16 Dec 2013 11:13:43 +0100
Martin Helm <[hidden email]> wrote:

> Am 16.12.2013 11:11, schrieb Martin Helm:
> > Off top of my head I think to remeber that 64-bit systems show 128TB
> > of kcore, because it is the limit the 64-bit chipset can handle and
> > kcore is set up to map the maximum memory not the actual memory.
> > Maybe an expert knows more.
>
> http://www.novell.com/support/kb/doc.php?id=7004153
>

Thanks Martin.

It is always nice to have correct picture of the world, even if it is
not what one expects.

--
Regards, Rajko.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]