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 88725 - gnome 2.0 crashes in FreeBSD 4.5-RELEASE
gnome 2.0 crashes in FreeBSD 4.5-RELEASE
Status: RESOLVED DUPLICATE of bug 84117
Product: gnome-session
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Scaffold Maintainers List
Scaffold Maintainers List
Depends on:
Blocks:
 
 
Reported: 2002-07-21 14:54 UTC by edulsa
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description edulsa 2002-07-21 14:55:08 UTC
Package: anjuta2
Severity: normal
Version: 1.5.19
Synopsis: gnome 2.0 crashes in FreeBSD 4.5-RELEASE
Bugzilla-Product: anjuta2
Bugzilla-Component: libanjuta
BugBuddy-GnomeVersion: 2.0 (1.117.0)

Description:
Description of Problem:


Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




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)...0x2897c7fc in _thread_sys_poll ()
   from /usr/lib/libc_r.so.4

Thread 1 (process 23780, 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-07-21 10:55 -------

The original reporter (edulsa@quimica.ufpr.br) 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, anjuta2-maint@bugzilla.gnome.org.

Comment 1 Luis Villa 2002-07-29 16:04:18 UTC

*** This bug has been marked as a duplicate of 84117 ***
Comment 2 Elijah Newren 2003-03-04 22:54:15 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."