abrt 1.0.4 detected a crash. architecture: i686 cmdline: compiz --ignore-desktop-hints glib gconf gnomecompat --replace component: compiz executable: /usr/bin/compiz kernel: 2.6.31.5-127.fc12.i686.PAE package: compiz-0.8.2-21.fc12 rating: 0 reason: Process was terminated by signal 11 release: Fedora release 12 (Constantine) backtrace ----- Cannot access memory at address 0x107 Thread 1 (Thread 4292): #0 0x008dd8a0 in ?? () No symbol table info available. #1 0x0037d408 in ?? () No symbol table info available. #2 0x00000000 in ?? () No symbol table info available. Cannot access memory at address 0x107 No symbol table is loaded. Use the "file" command.
Created attachment 388351 [details] File: backtrace
Cannot access memory at address 0x107 Thread 1 (Thread 4292): #0 0x008dd8a0 in ?? () No symbol table info available. #1 0x0037d408 in ?? () No symbol table info available. #2 0x00000000 in ?? () No symbol table info available. Cannot access memory at address 0x107 No symbol table is loaded. Use the "file" command. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This stack trace isn't very useful. (Must have come from a buggy abrt.) Can you reproduce the bug? If so, please do and attach a more complete stack trace. Otherwise, we will have to close this for INSUFFICIENT_DATA. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers