9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bengt Kleberg <bengt.kleberg@ericsson.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] any success with current plan9port on sunos5.8?
Date: Fri, 18 Jun 2004 09:06:16 +0000	[thread overview]
Message-ID: <catv0l$9lq$1@newstree.wise.edt.ericsson.se> (raw)
In-Reply-To: <200406172135.i5HLZQQ18405@zamenhof.cs.utwente.nl>

Axel Belinfante wrote:
>>Give up on _EXTENSIONS_ whatever that means.
>>Yield is a function provided by a system library.
>>The right fix is to rename the one the Plan 9 libraries
>>are calling.  #defining random things to make yield
>>disappear from view only makes the compiler think
>>there is no problem; it does not fix the problem.
> 
> 
> right. well put. thanks!
> done that, and seems things are ok again.
> that means, there are still a few things that fail,
> but they failed with a previous ports version in
> the same way.
> I'm sorry, but I simply do not see why or how they
> are failing, (maybe that's just because I don't know
> much about multi-threading?) so I'm posting this
> followup also to ask if someone has an explanation?
> Any insight would be appreciated.
> 
> Axel.
> 
> Details:
> 
> 
> the sort command called by ps sometimes gives me
> 'sort: note: sys: child'  followed by  Abort
> where does a SIGCHILD come from in this case? 
> (I mean, I don't see a fork; is this from some
>  thread related 'magic'?)
> 
> 
> when I do 'ls -lrt' I often get a bus error.
> it seems to be caused by an array bound read error
> in qsort (that's what purify and dbx tell me)
> but I miss to see how it is caused.
> 
> 
> In case it helps someone to understand (or explain)
> I'm including some purify output for the ls failure.
> Note: to avoid a name clash I slightly changed ls.c
> so line numbers will be off.

i have not experienced any name clash. i have not changed ''dirbuf''. i 
do not get any bus error from ''ls''.

an hypotetical reason for the bus error as described by you would be 
that the real size of dirbuf is smaller than the ''book keeping size'' 
(ndir). despite the attempt to make this possible (dirbuf gets it size 
changes independent of the changes to ndir), there is no place in the 
code where ndir can be bigger than the real size. as far as i can see.


bengt


  reply	other threads:[~2004-06-18  9:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17  2:33 Richard C Bilson
2004-06-17  7:53 ` Axel Belinfante
2004-06-17 16:11   ` Russ Cox
2004-06-17 21:35     ` Axel Belinfante
2004-06-18  9:06       ` Bengt Kleberg [this message]
2004-06-18 10:09         ` Axel Belinfante
2004-06-18  9:05     ` Bengt Kleberg
2004-06-17 17:08   ` Lyndon Nerenberg
2004-06-17 17:36     ` Russ Cox
2004-06-18  9:05       ` Bengt Kleberg
2004-06-18 13:02         ` Axel Belinfante
2004-06-18  9:06   ` Bengt Kleberg
2004-06-18  9:33     ` William Josephson
2004-06-18  9:47     ` Axel Belinfante
  -- strict thread matches above, loose matches on Subject: below --
2004-06-14 19:37 Richard C Bilson
2004-06-14 19:08 Richard C Bilson
2004-06-14 19:14 ` Charles Forsyth
2004-06-16  8:48 ` Bengt Kleberg
2004-06-16 23:50   ` Axel Belinfante
2004-06-17  9:05     ` Bengt Kleberg
2004-06-14 14:12 Richard C Bilson
2004-06-14 13:39 Richard C Bilson
2004-06-14 13:52 ` Axel Belinfante
2004-06-11 14:18 Richard C Bilson
2004-06-11 13:51 Richard C Bilson
2004-06-11 14:02 ` C H Forsyth
2004-06-11 13:58   ` William Josephson
2004-06-11 14:18     ` Russ Cox
2004-06-11 15:05 ` Axel Belinfante
2004-06-14 10:05 ` Bengt Kleberg
2004-06-14 11:30   ` Axel Belinfante
2004-06-16  8:48     ` Bengt Kleberg
2004-06-11 12:19 Axel Belinfante

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='catv0l$9lq$1@newstree.wise.edt.ericsson.se' \
    --to=bengt.kleberg@ericsson.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).