[mmap, duplex]

when i'm reconfiguring pcm streams to use different frames/cycle 
settings, i'm getting strange segfaults at seemingly random points 
in time and memory. this happens with the awe as well as with the
ice. many if not most of the segfaults are around here:

#0  0x40009c6b in fixup () from /lib/ld-linux.so.2
#1  0x40009e00 in _dl_runtime_resolve () from /lib/ld-linux.so.2
#2  0x406f7429 in _nss_compat_initgroups () from /lib/libnss_compat.so.2
#3  0x4000a3d6 in _dl_fini () from /lib/ld-linux.so.2
#4  0x40311db5 in exit () from /lib/libc.so.6
#5  0x40309a58 in __libc_start_main () from /lib/libc.so.6

but sometimes i also get inexplicable corruption within ordinary 
dynamically allocated memory of the process before it exits.

i have spent considerable time on verifying that these are indeed
caused by changing the period_size, and not by my own code.

it does not help to close and reopen the streams; the symptoms are the
same. only a new process, it seems, is able to cleanly change the
period_size configuration.

it may be related or not: at one time i have got an area adress of 
0x4001b000 by mmap_begin after a change of period_size on the awe. 
(gdb) info sharedlibrary 
>From        To          Syms Read   Shared Object Library
0x4001b000  0x4001e08c  Yes         /lib/libdl.so.2

at another time, trying to read the first sample from the second
channel from the area returned by a reconfigured ice1712 triggered 
SIGSEGV.

i'm bewildered, please help.

tim



_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Reply via email to