From: Russ Cox <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ports update
Date: Fri, 26 Mar 2004 11:21:50 -0500 [thread overview]
Message-ID: <4064589E.9020304@swtch.com> (raw)
In-Reply-To: <200403261552.i2QFqlX27346@plg2.math.uwaterloo.ca>
Richard C Bilson wrote:
>>From: Russ Cox <rsc@swtch.com>
>>
>>I suspect it's a stack overflow problem, I just don't know
>>where to look or how. I'm not overflowing the stack on other
>>systems, and I've got 32kB stacks in the program in question,
>>which should be way more than enough. On Linux I can use
>>valgrind to check such things (well, sort of).
>>
>>
>
>For what it's worth, I haven't yet been able to get the ports working
>reliably under either Linux/x86 or SunOS. Strangely, they're quite
>sturdy when run over VNC, but not when I use my normal (Xfree86) X
>server.
>
>
I'm running quite reliably under Linux/x86 for all day-to-day work,
and I was using FreeBSD for a good while too. There was an important
bug fix to libregexp a couple weeks ago, but since then they've been solid.
Russ
next prev parent reply other threads:[~2004-03-26 16:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 15:52 Richard C Bilson
2004-03-26 16:07 ` Axel Belinfante
2004-03-26 16:21 ` Russ Cox [this message]
2004-03-26 16:26 ` Sam
-- strict thread matches above, loose matches on Subject: below --
2004-03-26 19:05 Richard C Bilson
2004-03-26 19:16 ` Russ Cox
2004-03-26 19:27 ` Axel Belinfante
2004-03-27 13:10 ` boyd, rounin
2004-03-27 13:09 ` boyd, rounin
2004-03-26 2:21 Russ Cox
2004-03-26 9:54 ` Douglas A. Gwyn
2004-03-26 12:32 ` Fco.J.Ballesteros
2004-03-26 15:41 ` Russ Cox
2004-03-26 15:48 ` Fco.J.Ballesteros
2004-03-26 17:39 ` Russ Cox
2004-03-27 13:07 ` boyd, rounin
2004-03-26 15:42 ` Russ Cox
2004-03-26 18:24 ` Scott Schwartz
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=4064589E.9020304@swtch.com \
--to=rsc@swtch.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).