Re: [linux-audio-dev] Re: [ardour-dev] which libc6

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] Re: [ardour-dev] which libc6
From: root (drh_AT_niptron.com)
Date: Tue Aug 14 2001 - 06:23:42 EEST


Ok heres some more info. If I hit the rec enable button on a channle
and then disable it. I get

Program received signal SIGSEGV, Segmentation fault.
0x401613b7 in memset_interleave (dst=0x40833024 "", val=0 '\000',
bytes=304,
unit_bytes=4, skip_bytes=40) at memops.cc:165

also after about 1 min recording time I start to get xruns about every 3-4
secs with
the frequency increasing as the recording continues. heres what I got from
gdb at the
segmentation fault

        switch (unit_bytes) {
        case 1:
                while (bytes--) {
                        *dst = val;
                        dst += skip_bytes;
                }
                break;
        case 2:
                while (bytes) {
                        *((short *) dst) = (short) val;
                        dst += skip_bytes;
                        bytes -= 2;
                }
                break;
        case 4:
> while (bytes) {
                        *((int *) dst) = (int) val;
                        dst += skip_bytes;
                        bytes -= 4;
                }
                break;
        }

(xxgdb) info stack
#0 0x401613b7 in memset_interleave (dst=0x40833024 "", val=0 '\000',
bytes=304, unit_bytes=4, skip_bytes=40) at memops.cc:165
#1 0x40164436 in ALSA::MultiChannelDevice::silence_on_channel
(this=0x806f698, chn=1, nframes=256) at audioengine/alsa_device.h:342
#2 0x4015d5cd in ALSA::MultiChannelDevice::io_loop (this=0x806f698) at
alsa_device.cc:813
#3 0x4015e3a9 in ALSA::MultiChannelDevice::do_work (this=0x806f698) at

and heres my link list

 ldd /usr/src/ardour/gtk_ardour/ardour
        libardour-0-201-1.so => /usr/local/lib/libardour-0-201-1.so
(0x40014000)
        libmidipp-1-5-0.so => /usr/local/lib/libmidipp-1-5-0.so
(0x400b6000)
        libasound.so.2 => /usr/lib/libasound.so.2 (0x400d6000)
        libaudioengine-1-4-1.so => /usr/local/lib/libaudioengine-1-4-1.so
(0x40148000)
        libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x40171000)
        libguileconfig-0-2-0.so => /usr/local/lib/libguileconfig-0-2-0.so
(0x40193000)
        libpbd-1-3-1.so => /usr/local/lib/libpbd-1-3-1.so (0x401a2000)
        libltdl.so.0 => /usr/lib/libltdl.so.0 (0x401b8000)
        libsigc-0.0.so.5 => /usr/lib/libsigc-0.0.so.5 (0x401bc000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x401c8000)
        libguile.so.6 => /usr/lib/libguile.so.6 (0x401db000)
        libsndfile.so.0 => /usr/lib/libsndfile.so.0 (0x4024d000)
        libgdbm.so.1 => /usr/lib/libgdbm.so.1 (0x40277000)
        libxml++.so.0 => /usr/lib/libxml++.so.0 (0x4027e000)
        libxml2.so.2 => /usr/lib/libxml2.so.2 (0x40292000)
        libgtkmmext-2-11-1.so => /usr/local/lib/libgtkmmext-2-11-1.so
(0x4031f000)
        libgtkmm-1.2.so.0 => /usr/lib/libgtkmm-1.2.so.0 (0x4038b000)
        libgdkmm-1.2.so.1 => /usr/lib/libgdkmm-1.2.so.1 (0x40487000)
        libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x404a2000)
        libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x405c5000)
        libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x405f6000)
        libdl.so.2 => /lib/libdl.so.2 (0x405f9000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x405fd000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40609000)
        libm.so.6 => /lib/libm.so.6 (0x406aa000)
        libstdc++-libc6.1-2.so.3 => /usr/lib/libstdc++-libc6.1-2.so.3
(0x406c8000)
        libc.so.6 => /lib/libc.so.6 (0x4070d000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

I thought I had linked in hoard. But it dosent seem to be.

Paul Davis wrote:

> Richard Furse wondered:
>
> >Hmmm I wonder if the LADSPA plugins are being unloaded before shutdown?
>
> they are. but the but doesn't come from within the LADSPA plugin code
> itself. it comes from within GTK+ and/or Gtk--, as well destroy the
> GUI that was automagically built for the plugin. its hard to identify
> the cause, since it never, ever happens on my system. whether this
> means there are some thread-related issues, i am not sure.
>
> --p


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Tue Aug 14 2001 - 05:25:47 EEST