From: Takashi Iwai <tiwai@suse.de>
To: thewade <pdman@aproximation.org>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Alsa and hdspmixer segfault
Date: Fri, 01 Oct 2004 20:11:37 +0200 [thread overview]
Message-ID: <s5hu0tez4ti.wl@alsa2.suse.de> (raw)
In-Reply-To: <200410011754.i91HsYrn001612@sanctuary.aproximation.org>
At Fri, 1 Oct 2004 11:54:34 -0600,
thewade wrote:
>
> I downloaded the newest cvs (last night really, for me here in -6 MST),
> and built it ust now. alsa-lib built fine but hdspmixer in alsa-tools
> fails:
>
> make in hdspmixer:
> make[1]: Entering directory `/usr/local/src/alsa-tools/hdspmixer/src\'
> if g++ -DPACKAGE_NAME=\\\"\\\" -DPACKAGE_TARNAME=\\\"\\\" -DPACKAGE_VERSION=\\\"\\\" -DPACKAGE_STRING=\\\"\\\" -DPACKAGE_BUGREPORT=\\\"\\\" -DPACKAGE=\\\"hdspmixer\\\" -DVERSION=\\\"1.6\\\" -DSTDC_HEADERS=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -I/usr/local/include -I/usr/X11R6/include -fno-exceptions -MT HDSPMixerOutputs.o -MD -MP -MF \".deps/HDSPMixerOutputs.Tpo\" -c -o HDSPMixerOutputs.o HDSPMixerOutputs.cxx; \\
> then mv -f \".deps/HDSPMixerOutputs.Tpo\" \".deps/HDSPMixerOutputs.Po\"; else rm -f \".deps/HDSPMixerOutputs.Tpo\"; exit 1; fi
> In file included from HDSPMixerOutput.h:28,
> from HDSPMixerOutputs.h:26,
> from HDSPMixerOutputs.cxx:22:
> /usr/include/alsa/sound/hdsp.h:35: error: `u_int32_t\' does not name a type
> /usr/include/alsa/sound/hdsp.h:36: error: `u_int32_t\' does not name a type
> /usr/include/alsa/sound/hdsp.h:37: error: `u_int32_t\' does not name a type
> /usr/include/alsa/sound/hdsp.h:38: error: `u_int64_t\' does not name a type
> /usr/include/alsa/sound/hdsp.h:39: error: `u_int64_t\' does not name a type
> /usr/include/alsa/sound/hdsp.h:41: error: `u_int64_t\' does not name a type
> make[1]: *** [HDSPMixerOutputs.o] Error 1
> make[1]: Leaving directory `/usr/local/src/alsa-tools/hdspmixer/src\'
> make: *** [all-recursive] Error 1
Oh I forgot that it was fixed today.
It takes some time until anon cvs is sync'ed.
Wait until tomorrow, or change u_int32_t to uint32_t, and u_int64_t to
uin64_t. Also, add
#include <stdint.h>
at the beginnig of hdsp.h.
> It turns out that gdb says its a libfltk thing I think, at least with the
> current version of hdspmixer I have (Oct 1):
> Starting program: /usr/local/bin/hdspmixer
> [Thread debugging using libthread_db enabled]
> [New Thread 182894123680 (LWP 1231)]
>
> HDSPMixer 1.6 - Copyright (C) 2003 Thomas Charbonnel <thomas@undata.org>
> This program comes with ABSOLUTELY NO WARRANTY
> HDSPMixer is free software, see the file COPYING for details
>
> Looking for HDSP cards :
> Card 0 : SiS SI7012 at 0xe800, irq 169
> Card 1 : RME Hammerfall DSP + Multiface at 0x40800000, irq 209
> Multiface found !
> 1 Hammerfall DSP card found.
> Initializing default presets
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 182894123680 (LWP 1231)]
> 0x0000003092b6d075 in cb2 () from /usr/lib64/libfltk.so.1.1
>
> Should I rebuild fltk?
Not always, but what shows the stack trace?
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-01 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 17:54 Alsa and hdspmixer segfault thewade
2004-10-01 18:11 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-03 4:44 thewade
2005-02-05 0:37 ` thomas charbonnel
2005-02-08 19:25 ` Takashi Iwai
2004-10-01 23:03 thewade
2004-10-01 18:33 thewade
2004-10-01 19:31 ` Lee Revell
2004-10-01 18:19 thewade
2004-10-01 18:14 thewade
2004-10-01 18:08 thewade
2004-10-01 18:16 ` Lee Revell
2004-10-01 15:26 thewade
2004-10-01 17:23 ` Takashi Iwai
2004-10-01 17:49 ` Lee Revell
2004-10-01 17:55 ` Lee Revell
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=s5hu0tez4ti.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pdman@aproximation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox