From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: vnc-list@realvnc.com
Subject: 3.1-rc9: Xvnc segmentation fault/coredump
Date: Mon, 10 Oct 2011 06:02:29 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1110100545540.16362@p34.internal.lan> (raw)
Hello,
Summary: vncserver crashes with 3.1-rc9 when launching
thunderbird and chrome (usually reproducible)
Problem: With 3.1-rc9 -- vncserver (both vnc-4_1_3-x86_linux) and the
package in Debian: 4.1.1+X4.3.0-37 both core dump under 3.1-rc9 when I
launch a couple of applications, thunderbird and chrome, these
applications were also upgraded around the time I went to 3.1-rc9 so I
cannot be certain which is causing the crashes. I cannot change the
kernel for a while, machine is in production now; however, I have been
following the 3.1-rc's for awhile and all were OK (ran -rc8) for
the longest until -rc9. There appears to be no quick/fast
debug package available for vncserver; however, I will show/describe it as
best as I can.
1. Start vnc: vncserver -geometry 1920x1200 :1 -depth 24
2. Launch latest thunderbird, then chrome, then Xvnc crashes, dumps core.
Core with Debian's 4.1.1+X4.3.0-37
-rw------- 1 bob users 60551168 Oct 10 05:01 core.Xvnc4.7121
Core with realvnc's latest VNC on website (4.1.3):
-rw------- 1 bob users 67252224 Oct 10 05:11 core.Xvnc.9631
Obviously without a debug version, the output is not meaningful, however,
I was curious if ayone had seen anything like this with 3.1-rc9?
Core was generated by `Xvnc4 :1 -desktop p34:1 (bob) -auth /home/bob/.Xauthority -geometry 1920x1200 -'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000000004cbed4 in ?? ()
(gdb) bt full
#0 0x00000000004cbed4 in ?? ()
No symbol table info available.
#1 0x00000000004dd577 in ?? ()
No symbol table info available.
#2 0x00000000005832a2 in ?? ()
No symbol table info available.
#3 0x00000000005834ff in ?? ()
No symbol table info available.
#4 0x0000000000426d90 in ?? ()
No symbol table info available.
#5 0x000000000040be86 in ?? ()
No symbol table info available.
#6 0x00007f78bc27eead in __libc_start_main ()
from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#7 0x0000000000409259 in ?? ()
No symbol table info available.
#8 0x00007fff81ea1f58 in ?? ()
No symbol table info available.
#9 0x000000000000001c in ?? ()
No symbol table info available.
#10 0x0000000000000015 in ?? ()
No symbol table info available.
---Type <return> to continue, or q <return> to quit---
#11 0x00007fff81ea2cbc in ?? ()
No symbol table info available.
#12 0x00007fff81ea2cc2 in ?? ()
No symbol table info available.
#13 0x00007fff81ea2cc5 in ?? ()
No symbol table info available.
#14 0x00007fff81ea2cce in ?? ()
No symbol table info available.
#15 0x00007fff81ea2cda in ?? ()
No symbol table info available.
#16 0x00007fff81ea2ce0 in ?? ()
No symbol table info available.
#17 0x00007fff81ea2cf6 in ?? ()
No symbol table info available.
#18 0x00007fff81ea2d00 in ?? ()
No symbol table info available.
#19 0x00007fff81ea2d0a in ?? ()
No symbol table info available.
#20 0x00007fff81ea2d11 in ?? ()
No symbol table info available.
#21 0x00007fff81ea2d14 in ?? ()
No symbol table info available.
#22 0x00007fff81ea2d1d in ?? ()
---Type <return> to continue, or q <return> to quit---
No symbol table info available.
#23 0x00007fff81ea2d23 in ?? ()
No symbol table info available.
#24 0x00007fff81ea2d2c in ?? ()
No symbol table info available.
#25 0x00007fff81ea2d42 in ?? ()
No symbol table info available.
#26 0x00007fff81ea2d4b in ?? ()
No symbol table info available.
#27 0x00007fff81ea2d50 in ?? ()
No symbol table info available.
#28 0x00007fff81ea2d54 in ?? ()
No symbol table info available.
#29 0x00007fff81ea2d58 in ?? ()
No symbol table info available.
#30 0x00007fff81ea2e68 in ?? ()
No symbol table info available.
#31 0x00007fff81ea2e6c in ?? ()
No symbol table info available.
#32 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)
Justin.
reply other threads:[~2011-10-10 10:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1110100545540.16362@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vnc-list@realvnc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®