All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glenn Maynard <glenn@zewt.org>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Removal of assert() in alsa-lib
Date: Fri, 10 Dec 2004 00:46:08 -0500	[thread overview]
Message-ID: <20041210054607.GX14919@zewt.org> (raw)
In-Reply-To: <s5hzn0n8mqd.wl@alsa2.suse.de>

On Thu, Dec 09, 2004 at 05:23:06PM +0100, Takashi Iwai wrote:
> +void snd_err_msg(const char *file, int line, const char *function, int err, const char *fmt, ...) __attribute__ ((format (printf, 5, 6)));

Can this be a weak symbol, so it can be overridden by user code?

If my application causes errors on some version of ALSA, having diagnostic
information going to stderr is inconvenient: I centralize all diagnostics
for bug reporting in a single file, so I don't have to pull teeth from users
to have them copy bits of information from other places.

As long as snd_err_msg() is only called on "unexpected" errors (eg. what
used to be assertion failures), and made a weak symbol, I can redirect it
to my logs.

I currently do this with __assert_fail() and __assert_perror_fail(), and I'd
like to continue to be able to catch all important diagnostic output
automatically.

-- 
Glenn Maynard


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-10  5:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 16:31 Removal of assert() in alsa-lib Takashi Iwai
2004-12-01 17:51 ` Jaroslav Kysela
2004-12-01 18:01   ` Takashi Iwai
2004-12-02 12:03     ` Takashi Iwai
2004-12-09 16:23       ` Takashi Iwai
2004-12-10  5:46         ` Glenn Maynard [this message]
2004-12-10  7:49           ` Jaroslav Kysela
2004-12-10 11:03             ` Takashi Iwai

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=20041210054607.GX14919@zewt.org \
    --to=glenn@zewt.org \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.