9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] panic(?) and error(?)
Date: Sun, 25 Aug 2002 17:14:16 +0200	[thread overview]
Message-ID: <20020825171415.C29921@cackle.proxima.alt.za> (raw)
In-Reply-To: <7195f13865b12345b616627c0edf7651@plan9.bell-labs.com>; from presotto@plan9.bell-labs.com on Sun, Aug 25, 2002 at 10:43:27AM -0400

On Sun, Aug 25, 2002 at 10:43:27AM -0400, presotto@plan9.bell-labs.com wrote:
>
> Error() in upas/fs.c just exits the process after printing a message.
> I didn't use sysfatal() because I want to kill off the entire process
> group on error and sysfatal doesn't.  If I'ld used the thread package
> I wouldn't have needed to do it that way.
>
Did I perhaps miss a definition of error() local to upas/fs?  I could
easily have.

> It is totally unrelated to the error() in the kernel nor
> error() in 9660srv.  They implements an exception
> stack so that they can cleanly back out of errors without
> crashing.
>
9660srv uses panic() - again, I didn't think of looking for a local
definition - which takes a first argument that resembles an fd that
ought to be redirected to /dev/null.  That bit of logic baffles me.

> The similarity in name implies nothing about similarity in
> function.

I would make myself very unpopular if I mentioned that in studying
9p(2) and colleagues, I came to the conclusion that it would be
clearer in C++.  So I'll keep such thoughts to myself.  :-)  :-)

Namespace pollution caught me here, I'll go and do some additional
snooping.  Thanks for the clarification.

++L


  reply	other threads:[~2002-08-25 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 14:43 presotto
2002-08-25 15:14 ` Lucio De Re [this message]
2002-08-25 15:27 ` Lucio De Re
  -- strict thread matches above, loose matches on Subject: below --
2002-08-25 15:31 presotto
2002-08-25 15:47 ` Lucio De Re
2002-08-25 14:22 Lucio De Re

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=20020825171415.C29921@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).