From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [Patch] libsensors: Introduce error string -
Date: Thu, 29 Jan 2009 12:28:19 +0000 [thread overview]
Message-ID: <20090129132819.465327e7@hyperion.delvare> (raw)
In-Reply-To: <20090129090945.GB4410@ubuntu>
On Thu, 29 Jan 2009 12:12:28 +0100, Andre Prendel wrote:
> On Thu, Jan 29, 2009 at 10:57:03AM +0100, Jean Delvare wrote:
> > Hi Andre,
> >
> > On Thu, 29 Jan 2009 10:09:45 +0100, Andre Prendel wrote:
> > > sensors_error() returns NULL if errnum is not valid. Returning
> > > "Unknown error" in this case, makes output clearer than:
> > >
> > > foo: (null)
> > >
> > > and prevents error output/logging from segmentation faults.
> > >
> > > What do you think?
> > >
> > > Andre
> > >
> > > Signed-off-by: Andre Prendel <andre_prendel@gmx.de>
> > > ---
> > >
> > > --- lm-sensors-dev/lib/error.c 2009-01-26 17:43:43.000000000 +0100
> > > +++ my-lm-sensors/lib/error.c 2009-01-28 22:49:53.000000000 +0100
> > > @@ -33,7 +33,7 @@ void (*sensors_fatal_error) (const char
> > > sensors_default_fatal_error;
> > >
> > > static const char *errorlist[] = {
> > > - /* Invalid error code */ NULL,
> > > + /* Invalid error code */ "Unknown error",
> > > /* SENSORS_ERR_WILDCARDS */ "Wildcard found in chip name",
> > > /* SENSORS_ERR_NO_ENTRY */ "No such subfeature known",
> > > /* SENSORS_ERR_ACCESS_R */ "Can't read",
> >
> > Out of curiosity: did you actually hit this problem in real life?
>
> No, I didn't. It's just theoretical.
>
> > I was about to say that the caller was supposed to check for NULL, but
> > apparently neither sensors nor sensord nor even libsensors does, so...
>
> IMO error reporting should be very stable. If the caller checks
> return value carefully it's fine too. Fprintf() isn't a problem. But I
> don't know what about vsnprintf(), syslog().
>
> > I guess you're right, having an error string instead of NULL would be
> > better. Actually that's what libsensors 2.x did, I can't remember why I
> > changed that in 3.x:
> > http://www.lm-sensors.org/changeset/4854
> >
> > Probably I thought it was not supposed to happen, but I guess it may
> > actually happen if mixing a recent application with an older version of
> > libsensors.
> >
> > So I am pretty much inclined to apply your patch.
>
> Vous avez le choix. :)
Sicherlich :)
Patch applied, thanks. If you intend to contribute to the lm-sensors
project again on a regular basis, please let me know, we can create an
account for you.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-01-29 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 9:09 [lm-sensors] [Patch] libsensors: Introduce error string - Unknown Andre Prendel
2009-01-29 9:57 ` [lm-sensors] [Patch] libsensors: Introduce error string - Jean Delvare
2009-01-29 11:12 ` [lm-sensors] [Patch] libsensors: Introduce error string Andre Prendel
2009-01-29 12:28 ` Jean Delvare [this message]
2009-01-30 9:01 ` Andre Prendel
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=20090129132819.465327e7@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.