Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 10011 - Segmentation Faults and Core Dump from X
Segmentation Faults and Core Dump from X
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Depends On:
  Show dependency treegraph
Reported: 2000-03-06 10:22 EST by wasquith
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-05-30 15:01:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description wasquith 2000-03-06 10:22:24 EST
Installation support told me to report this as a bug.
While running some small Perl/Tk apps, I am getting repeated Segmentation
Faults and Core Dumps.  These apps do not have problems on Irix,
Solaris, or Win98.  Though the crash is sort of random, I can get it to
repeat easy.  The /var/log/messages is reported the following snippet about
the exact same time as the seg fault:

modprobe: can't locate module block-major-22
          last message repeated 29 times

modprobe: can't locate module char-major-108
          last message repeated 19 times

The 'last ... times' repeats again and again with a different repeat count.
Running 6.1, on Dell Latitude CPi.  Everything else is working fine, except
the GNOME desktop which core dumps a lot so I switched to KDE several weeks
ago.  Thanks for the help.
Comment 1 Trond Eivind Glomsrxd 2000-05-30 15:01:59 EDT
The first is a complaint about /dev/hdc (caused by magicdev or automount,
perhaps, looking for disks to mount), the second message is a PPP thing. Neither
of these are relevant. What is dumping core - your apps or X? My guess is bugs
in either perl/Tk and/or your apps.
Comment 2 Trond Eivind Glomsrxd 2000-08-08 14:42:24 EDT
Closed - I assume it works in the current release. Reopen if not.

Note You need to log in before you can comment on or make changes to this bug.