From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0000455]: segfault when trying to connect dmix->plug
Date: Thu, 19 Aug 2004 10:21:54 +0200 (CEST) [thread overview]
Message-ID: <20040819082154.3872C1102F@server.perex-int.cz> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000455
======================================================================
Reported By: stsp
Assigned To:
======================================================================
Project: ALSA - lib
Bug ID: 455
Category: pcm - digital audio
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-18-2004 20:20 CEST
Last Modified: 08-19-2004 10:21 CEST
======================================================================
Summary: segfault when trying to connect dmix->plug
Description:
Hi.
With the attached configuration I get
segmentation fault:
---
$ ogg123 mise02-ulicka.ogg
ALSA lib pcm_dmix.c:873:(snd_pcm_dmix_open) dmix plugin can be only
connected to hw plugin
Segmentation fault
---
Here is the problematic place:
---
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1078196992 (LWP 30505)]
snd_pcm_plug_open (pcmp=0xbffff7c0, name=0x43653b13 "default",
sformat=1131543104, schannels=1131543104, srate=1131543104,
route_policy=1131543104, ttable=0x4371fa40, tt_ssize=1131543104,
tt_cused=1131543104, tt_sused=1131543104, slave=0x428c6fdc,
close_slave=1131543104) at pcm_plug.c:1034
1034 pcm->fast_ops = slave->fast_ops;
(gdb) p pcm->fast_ops
$1 = (snd_pcm_fast_ops_t *) 0x0
---
So it is trying to assign to NULL.
======================================================================
----------------------------------------------------------------------
stsp - 08-19-2004 10:21 CEST
----------------------------------------------------------------------
> $1 = (snd_pcm_fast_ops_t *) 0x0
> So it is trying to assign to NULL.
OK, never mind, of course that assignment is valid.
Nothing wrong with the slave->fast_fops either.
But it segfaults here only when some memory debugger
is used (njamd, efence), otherwise it segfaults much
later. Might be some memory corruption.
Attached are backtraces at a crash points: log1 - with
memory debugger; log2 - without. Both looks pretty
useless...
Bug History
Date Modified Username Field Change
======================================================================
08-18-04 20:20 stsp New Bug
08-18-04 20:20 stsp File Added: asound.conf
08-19-04 10:21 stsp Bugnote Added: 0001589
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next reply other threads:[~2004-08-19 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 8:21 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-09 15:32 [ALSA - lib 0000455]: segfault when trying to connect dmix->plug bugtrack
2004-09-15 18:44 bugtrack
2004-09-13 16:36 bugtrack
2004-08-22 15:58 bugtrack
2004-08-18 18:20 bugtrack
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=20040819082154.3872C1102F@server.perex-int.cz \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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.