Bug 13204 – gnomemeeting 0.94.1 segfaulting

• Product: Gentoo Linux
• Status: RESOLVED WORKSFORME

[Description FieldySnuts 2003-01-03 21:21:26 UTC]

I have only tested this while 'talking' to an MS Netmeeting user. I am not sure
if this happens with other gnomemeeting 0.94.1 users, as I was unable to find
anyone to help me test this out.

gnomemeeting 0.94.1 segfaults after a few minutes of talking. We tried this at
least a dozen times, and there was not one session that was not ended by a
segfault after about 2 or 3 minutes.

See the attached strace log. It is bzip2 compressed, since I don't feel like
sending 1.3 MB over dial up.

I am looking for other gnomemeeting 0.94.1 users to test this out with.

[Comment 1 FieldySnuts 2003-01-03 21:23:05 UTC]

Created attachment 6937 [details]
output of running strace gnomemeeting 2> gnomemeeting.strace.log (bzip2 compressed)

[Comment 2 FieldySnuts 2003-01-03 21:25:01 UTC]

Blah, forgot emerge info:

Portage 2.0.46-r2 (default-1.0, gcc-2.95.3, glibc-2.2.5-r2,2.2.5-r6)
=================================================================
System uname: 2.4.19-ipv6 i686 AuthenticAMD
USE="x86 oss apm avi crypt cups jpeg libg++ mikmod mpeg ncurses qtmt quicktime
spell xml2 xv berkdb esd gdbm gif gnome-libs gpm guile imlib java ldap libwww
motif mozilla nls opengl pam png python qt readline scanner sdl slang ssl svga
tcpd tetex tiff X gtk gtk2 gnome -alsa -arts 3dnow cdr encode kde mmx oggvorbis
pdflib perl sse truetype xmms ipv6"
ARCH="x86"
COMPILER=""
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=i686 -mcpu=i686 -O3 -pipe"
CXXFLAGS="-march=i686 -mcpu=i686 -O3 -pipe"
ACCEPT_KEYWORDS="x86 ~x86"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config
/usr/kde/3.1/share/config:/usr/kde/3/share/config:/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
MAKEOPTS="-j3"
JDK_HOME="/opt/blackdown-jdk-1.3.1"
JAVA_HOME="/opt/blackdown-jdk-1.3.1"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo"

[Comment 3 foser (RETIRED) 2003-01-07 09:08:16 UTC]

firs of all, try lowering your optimizations.

[Comment 4 FieldySnuts 2003-01-07 18:25:34 UTC]

Okay, any suggestions on what to shave off?

[Comment 5 Spider (RETIRED) 2003-01-07 19:19:00 UTC]

make -O3 be -O2 instead.

[Comment 6 FieldySnuts 2003-01-07 20:31:40 UTC]

Okay, I tried the following with the same person who is using Netmeeting from
before:

replaced -O3 with -O2 . Result: Segfaults 1min 30sec in , three times in a row
replaced -O2 with -O0 . Result: Segfaults 1min 30 sec in, three times in a row

I'm no developer, but that repeated time pattern is.. odd to say the least.

What would you like me to try next? I'm still curious if this will happen with
another gnomemeeting user. Perhaps we could try it if you have the time.

[Comment 7 foser (RETIRED) 2003-01-08 05:32:20 UTC]

i dont have a webcam and stuff :/

Anyway, can you debugbuild it and give a backtrace (easiest way is to add
'inherit debug' at the top of the gnomemeeting ebuild) ?

[Comment 8 FieldySnuts 2003-01-08 19:08:58 UTC]

Okay, so I add "inherit debug" at the top of the ebuild, and by backtrace do you
mean an strace log? Appolgies for my lack of a clue, and thanks for the patience.

[Comment 9 foser (RETIRED) 2003-01-11 11:29:09 UTC]

No, when it crashes it comes up with a dialog like 'close this app or file a bug
report'. Choose the file a bugreport one. The first dialog in bug-buddy
generates a backtrace (heap of debugger related output), we would like to see
that. And then cancel bug-byddy, dont file a bugreport trough it just yet.

[Comment 10 FieldySnuts 2003-01-12 22:38:17 UTC]

Created attachment 7246 [details]
gnomemeeting backtrace 1

[Comment 11 foser (RETIRED) 2003-01-31 12:38:12 UTC]

how is this problem with the new gnomemeeting 0.96 ?

[Comment 12 FieldySnuts 2003-01-31 12:46:40 UTC]

I hadn't noticed it was out, I will give it a shot when the other person comes on line.

I'll try building it 'normally' at first.

[Comment 13 foser (RETIRED) 2003-04-03 17:11:22 UTC]

closing, reopen if the problem still exists with 0.96

[Comment 14 Alastair Tse (RETIRED) 2003-09-28 13:51:59 UTC]

reclosing