bugGNUstep - Bugs: bug #8827, gdnc thread problems on NetBSD

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #8827: gdnc thread problems on NetBSD

Submitted by:  None
Submitted on:  Thu 06 May 2004 10:37:27 PM UTC  
 
Category: Base/FoundationSeverity: 3 - Normal
Item Group: BugStatus: Duplicate
Privacy: PublicAssigned to: None
Open/Closed: Closed

Sun 21 Nov 2004 11:27:11 PM UTC, comment #2:

When closing bugs as duplicates, I suggest referring to the other bug like so: bug #10967. savannah will turn that into a clickable link which makes it easy for users to move to the real bug.

Alexander Malmberg <alexm>
Project Member
Sun 21 Nov 2004 08:33:22 AM UTC, comment #1:

Closed because this and #10967 are duplicates, and there is more/better info in #10967

Richard Frith-Macdonald <CaS>
Project Member
Thu 06 May 2004 10:37:27 PM UTC, original submission:

Both on NetBSD/68K (1.6.2) and on NetBSD/ppc (2.0 pre) launching programs gives troubles with gdnc, it doesn't get autolaunched, so it seems.

On NetBSD/ppc I tried to trace the problem and it seems that gdnc dies.

I started gdnc with -f and get:
gimli: {14} gdnc -f
*Pth* SCHEDULER INTERNAL ERROR: no more thread(s) available to schedule!?!?
gdnc killed by signal 6

pth on that box is 2.0.0 prom the ports

Anonymous

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Sun 21 Nov 2004 08:33:22 AM UTCCaSStatusNone=>Duplicate
  Open/ClosedOpen=>Closed

Back to the top


Powered by Savane 3.1-cleanup1