After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 389059 - crash in Sound: Ich habe System->Einstel...
crash in Sound: Ich habe System->Einstel...
Status: RESOLVED DUPLICATE of bug 363005
Product: gnome-control-center
Classification: Core
Component: Sound
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-23 23:02 UTC by gandalf
Modified: 2007-01-05 11:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
strace for gnome-sound-properties with optimizations causing the crash (132.72 KB, text/plain)
2006-12-24 20:28 UTC, gandalf
Details

Description gandalf 2006-12-23 23:02:51 UTC
Version: 2.16.1

What were you doing when the application crashed?
Ich habe System->Einstellungen-> Audio geöffnet.
--------------------
I opened  System->Settings->Audio.



Distribution: Gentoo Base System version 1.12.8
Gnome Release: 2.16.2 2006-12-22 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 25583616 vsize: 0 resident: 25583616 share: 0 rss: 12161024 rss_rlim: 0
CPU usage: start_time: 1166914778 rtime: 0 utime: 17 stime: 0 cutime:16 cstime: 0 timeout: 1 it_real_value: 0 frequency: 1

Backtrace was generated from '/usr/bin/gnome-sound-properties'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230129488 (LWP 1680)]
0xb7f5a410 in ?? ()

Thread 1 (Thread -1230129488 (LWP 1680))

  • #0 ??
  • #1 ??
  • #2 ??
  • #0 ??

Comment 1 Bruno Boaventura 2006-12-24 04:03:22 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 gandalf 2006-12-24 17:20:39 UTC
Hi,

I´m sorry, that I reported this. It seems to be connected to agressive CFLAGS. I was using:

CFLAGS="-march=pentium-m -mmmx -msse -msse2 -msse3 -pipe -O3 -mtune=pentium-m -mfpmath=sse -momit-leaf-frame-pointer -ftracer -fomit-frame-pointer -funroll-loops -fforce-addr -frename-registers -falign-functions=64"
LDFLAGS="-Wl,-O1,-z,now"

After adjusting CFLAGS to produce a stacktrace I was not able to reproduce the crash.Well, I have to try which CFLAG caused the problem.

Merry Christmas

Jürgen
Comment 3 gandalf 2006-12-24 20:28:53 UTC
Created attachment 78864 [details]
strace for gnome-sound-properties with optimizations causing the crash
Comment 4 gandalf 2006-12-24 20:29:45 UTC
This is strange, even only supplying -O2 causes the crash. Only leaving out the -Ox flag is not sufficient. It works with no CFLAGS, and even -march=pentium-m -mmmx -msse -msse2 -msse3  -pipe worked.Well, I was not able to get a stacktrace with the method described in the link. Perhaps it´s nessecary to recompile some dependant libs with debugging enabled. Perhaps you can tell me which ones are relevant, since I don´t want to recompile the whole system. At least I performed a strace. Possibly this is of some help, but really large. Maybe it´s not caused by control-center, but by some configuration problem or depandant package.

Greets Jürgen

Comment 5 André Klapper 2007-01-04 05:01:22 UTC
i guess that hald is not running and that this is a duplicate of bug 363005 - gandalf, is hald running?
Comment 6 gandalf 2007-01-04 17:06:00 UTC
Yes, you´re right. I didn´t have hald running. Well, perhaps there should be an error message instead of a crash.It is still interesting, that the problem only occurs when some combinations of CFLAGS are set. After reviewing the bug you mentioned, I agree with your guess, that this entry is a duplicate.

Thx

Jürgen
Comment 7 André Klapper 2007-01-05 11:09:47 UTC
yes, there definitely shouldn't be a crash.

marking as duplicate.

*** This bug has been marked as a duplicate of 363005 ***