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 85731 - Segmentation Fault at startup on FreeBSD v4.6-Stable
Segmentation Fault at startup on FreeBSD v4.6-Stable
Status: RESOLVED DUPLICATE of bug 84117
Product: gnome-session
Classification: Core
Component: gnome-session
unspecified
Other other
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-06-18 01:05 UTC by eldoraan
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description eldoraan 2002-06-18 01:01:52 UTC
Package: gnome-session
Severity: blocker
Version: 2.0.0
Synopsis: Segmentation Fault at startup on FreeBSD v4.6-Stable
Bugzilla-Product: gnome-session
Bugzilla-Component: gnome-session
BugBuddy-GnomeVersion: 2.0 (2.0.1)

Description:
Description of Problem:

Upon starting gnome-session, receive segmentation fault and application
quits. Cannot successfully run Gnome2RC1.

Steps to reproduce the problem:
1. Start X with "exec gnome-session" in .xinitrc
2. X starts up and gnome-session immediately segfaults.

Actual Results: Segmentation Fault and program quit


Expected Results: Gnome Session startup


How often does this happen? Every time


Additional Information:

Clean build from FreeBSD Ports system update via CVS as of ~ 8:00pm EST
6/16/02.



Debugging Information:

Backtrace was generated from '/usr/X11R6/bin/gnome-session'

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x189c4370 in _thread_sys_poll ()
    from /usr/lib/libc_r.so.4

Thread 1 (process 94474, thread 1)

  • #0 _thread_sys_poll
    from /usr/lib/libc_r.so.4
  • #1 _thread_kern_sched_state_unlock
    from /usr/lib/libc_r.so.4
  • #2 _thread_kern_scheduler
    from /usr/lib/libc_r.so.4
#3  0x0 in ?? ()
No symbol table info available.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-17 21:01 -------

The original reporter (eldoraan@earthlink.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-session-maint@bugzilla.gnome.org.

Comment 1 Luis Villa 2002-06-18 18:07:54 UTC

*** This bug has been marked as a duplicate of 84117 ***
Comment 2 Elijah Newren 2003-03-04 22:55:33 UTC
I apologize for the spam, but in talking to David Kennedy on #bugs we decided
that it might be useful for me to add a comment to a lot of bugs that have
nearly identical stack traces that aren't very useful.  (It took me a while
because I gave up on several bugzilla queries that simply hung).  Anyway, I may
have caught some bugs with this query that aren't relevant, so I apologize again
if this bug is one of those.  If not:

The following comment from 100709 may be relevant: "It turns out this was an
accidental FreeBSD ABI change during the import of gcc-3.2.1. div(), a structure
returning function, was the culprit."