Chris,
This is the only thing I see from gdb:
r...@tomcat_liv:/# gdb -c core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-slackware-linux".
(no debugging symbols found)
Core was generated by
`/usr/local/java/bin/java -Djava.util.logging.config.file=/usr/local/tomcat/conf'.
Program terminated with signal 11, Segmentation fault.
[New process 3824]
[New process 4182]
[New process 3811]
[New process 3823]
[New process 3825]
[New process 4325]
[New process 3849]
[New process 3364]
[New process 3850]
[New process 3393]
[New process 3851]
[New process 3395]
[New process 3852]
[New process 3399]
[New process 3401]
[New process 3853]
[New process 3406]
[New process 3859]
[New process 3860]
[New process 3861]
[New process 3862]
[New process 3863]
[New process 3410]
[New process 3864]
[New process 3880]
[New process 3416]
[New process 3939]
[New process 3940]
[New process 3775]
[New process 3986]
[New process 3780]
[New process 3987]
[New process 3388]
[New process 4291]
[New process 3387]
[New process 3403]
[New process 3383]
[New process 3389]
[New process 3396]
[New process 3398]
[New process 3407]
[New process 3408]
[New process 3409]
[New process 3411]
[New process 3412]
[New process 3413]
[New process 3414]
[New process 3415]
[New process 3776]
[New process 3782]
[New process 3818]
[New process 3820]
#0 0x00007fe01f9d359d in ?? ()
I have thought the reason I am seeing nothing beyond the JVM is that the JVM
has no debugging symbols. Did I miss something?
Thanks,
Carl
----- Original Message -----
From: "Christopher Schultz" <ch...@christopherschultz.net>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Friday, February 12, 2010 5:27 PM
Subject: Re: Tomcat dies suddenly
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Carl,
On 2/12/2010 4:59 PM, Carl wrote:
Darn, I thought we were onto something here but, as you suspected, the
line contains a lot of parameters and was truncated. So, now, I think
we know the JVM is seg faulting, we just don't know where or why. I'm
guessing we have to somehow get a stack trace at the point of failure...
any idea how I can get one? Or, is there a better way?
I believe you can do roughly this with gdb (from memory):
$ gdb core-file
gdb) where
(boom: your stack trace goes here)
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkt11bwACgkQ9CaO5/Lv0PBUCgCfbR2f2IXwFq7ile8biFNjsXOH
opEAnj7gYfb2jfQDtwIcl5atUpyYG8au
=im6P
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
