undefined -21 ... Speicherzugriffsfehler

FolkertM · #1 20th June 2012, 01:45 PM

Please read first complete what my problem is!

I had a clean, stabil fedora 14 system in the past. When I read in the news support for fedora14 was quitted by the managemend, I made the update to fedora15.

I spend much time on the machine fedoraXX and I haven't virtualised everything.

I observed fedora15 was coming with problems over the Internet during the update process.

Actually, I observed the misbehavoir of evince:

Quote:

[technican@fedoraXX ~]$ evince /media/6138-3061/innoQ/System\ Development\ Life\ Cycle.ps
undefined -21
undefined -21

(evince:7388): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:7388): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:7388): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:7388): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:7388): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:7388): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:7388): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:7388): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:7388): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:7388): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:7388): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:7388): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:7388): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:7388): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:7388): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:7388): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:7388): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:7388): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Speicherzugriffsfehler

And this is only the head of the long worm

evince crashed everytime I open .ps extension files.
I searched the forum, but haven't found any hint/solution.

Kind regards, FolkertM

---------- Post added at 02:41 PM ---------- Previous post was at 01:28 PM ----------

Then I tried to debug the disbehavoir:

Quote:

[technican@fedoraXX ~]$ gdb evince
GNU gdb (GDB) Fedora (7.3.1-48.fc15)
Copyright (C) 2011 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 "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<...://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/evince...Reading symbols from /usr/lib/debug/usr/bin/evince.debug...done.
done.
(gdb) run
Starting program: /usr/bin/evince
[Thread debugging using libthread_db enabled]
[New Thread 0xb7bffb70 (LWP 8486)]
[New Thread 0xb71ffb70 (LWP 8487)]
[New Thread 0xb69feb70 (LWP 8488)]
[New Thread 0xb0485b70 (LWP 8489)]

(evince:8483): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:8483): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:8483): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:8483): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:8483): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:8483): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:8483): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:8483): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:8483): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:8483): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:8483): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:8483): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:8483): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:8483): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:8483): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(evince:8483): Gtk-CRITICAL **: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed

(evince:8483): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(evince:8483): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
[Thread 0xb71ffb70 (LWP 8487) exited]
[New Thread 0xb71ffb70 (LWP 8495)]
undefined -21
undefined -21

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb71ffb70 (LWP 8495)]
0x016a9099 in _cmsMalloc (size=2142) at base/gsicc_lcms.c:492
492 return gs_alloc_bytes(gs_lib_ctx_get_non_gc_memory_t(), size, "lcms");
Missing separate debuginfos, use: debuginfo-install krb5-libs-1.9.3-1.fc15.i686
(gdb)

---------- Post added at 02:45 PM ---------- Previous post was at 02:41 PM ----------

And the missing debuginfo package wasn't possible to install:

Quote:

[technican@fedoraXX ~]$ sudo debuginfo-install krb5-libs-1.9.3-1.fc15.i686
[sudo] password for Techniker:
Geladene Plugins: auto-update-debuginfo, langpacks, presto, refresh-packagekit
enabling fedora-debuginfo
enabling rpmfusion-free-updates-debuginfo
enabling rpmfusion-free-debuginfo
enabling updates-debuginfo
Could not find debuginfo for main pkg: krb5-libs-1.9.3-1.fc15.i686
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket e2fsprogs-debuginfo-1.41.14-2.fc15.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Paket keyutils-debuginfo-1.2-7.fc15.i686 ist bereits in der neusten Version installiert.
Paket keyutils-debuginfo-1.2-7.fc15.i686 ist bereits in der neusten Version installiert.
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Could not find debuginfo pkg for dependency package krb5-libs-1.9.3-1.fc15.i686
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket glibc-debuginfo-2.14.1-6.i686 ist bereits in der neusten Version installiert.
Paket libselinux-debuginfo-2.0.99-4.fc15.i686 ist bereits in der neusten Version installiert.
No debuginfo packages available to install

FolkertM · #2 20th June 2012, 02:00 PM

It was a problem with malloc.c

Code:

(gdb) info threads
  Id   Target Id         Frame 
* 5    Thread 0xb01ffb70 (LWP 8741) "evince" 0x016a907c in _cmsMalloc (size=2142) at base/gsicc_lcms.c:492
  4    Thread 0xb0b44b70 (LWP 8740) "evince" 0x00131416 in __kernel_vsyscall ()
  3    Thread 0xb71ffb70 (LWP 8735) "evince" 0x00131416 in __kernel_vsyscall ()
  2    Thread 0xb7bffb70 (LWP 8734) "evince" 0x00131416 in __kernel_vsyscall ()
  1    Thread 0xb7fdaa60 (LWP 8731) "evince" _int_free (av=0x10043e0, p=0x832e308, have_lock=0) at malloc.c:4780
(gdb)

It came near to the thread: https://bugzilla.redhat.com/show_bug...iple&id=752731

tashirosgt · #3 20th June 2012, 03:22 PM

When evince crashes, do you get a core dump directory in the /var/spool/abrt directory?

FolkertM · #4 20th June 2012, 04:19 PM

it didn't crash

stevea · #5 20th June 2012, 04:41 PM

Yes - bugzilla is a good resource for identifying bugs.
I've never seen any similar behavior and I use evince extensively.

I suggest you document the revision of the kernel, evince and relates libraries and create a new bugzilla report.

F15 is nearly EOL (EOL date is June 26, 6 days away) so no one will look at a new F15 bug.
You'll need to reproduce this and document on F16 or F17.

p.s. my opinion i that F15 was a fairly scruffy release. You may have a better experience w/ F16 or F17, aside from the desktop changes.

george_toolan · #6 20th June 2012, 04:43 PM

Sure it did. What else is it supposed to do after a "Speicherzugriffsfehler"?

Quote:

Program received signal SIGSEGV, Segmentation fault.

Looks like core dumps are disabled though.

FolkertM · #7 20th June 2012, 10:11 PM

Quote:

Originally Posted by stevea

Yes - bugzilla is a good resource for identifying bugs.
I've never seen any similar behavior and I use evince extensively.

I suggest you document the revision of the kernel, evince and relates libraries and create a new bugzilla report.

F15 is nearly EOL (EOL date is June 26, 6 days away) so no one will look at a new F15 bug.
You'll need to reproduce this and document on F16 or F17.

p.s. my opinion i that F15 was a fairly scruffy release. You may have a better experience w/ F16 or F17, aside from the desktop changes.

I did the update to fedora16, the misbehavoir continues too.
It's a long worms head.

---------- Post added at 10:39 PM ---------- Previous post was at 10:37 PM ----------

Quote:

Originally Posted by george_toolan

Sure it did. What else is it supposed to do after a "Speicherzugriffsfehler"?

Looks like core dumps are disabled though.

Where can I search alternative for the core dumps?

---------- Post added at 11:11 PM ---------- Previous post was at 10:39 PM ----------

Quote:

Originally Posted by stevea

Yes - bugzilla is a good resource for identifying bugs.
I've never seen any similar behavior and I use evince extensively.

I suggest you document the revision of the kernel, evince and relates libraries and create a new bugzilla report.

F15 is nearly EOL (EOL date is June 26, 6 days away) so no one will look at a new F15 bug.
You'll need to reproduce this and document on F16 or F17.

p.s. my opinion i that F15 was a fairly scruffy release. You may have a better experience w/ F16 or F17, aside from the desktop changes.

I did Bug 678500 - undefined -21 ... Speicherzugriffsfehler