From: "Michel Dänzer" <michel@daenzer.net>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: alsa-lib & oss 1.0.3rc1
Date: Thu, 26 Feb 2004 18:56:12 +0100 [thread overview]
Message-ID: <1077818171.2680.123.camel@thor.asgaard.local> (raw)
In-Reply-To: <20040226155548.GC21451@master.mivlgu.local>
On Thu, 2004-02-26 at 16:55, Sergey Vlasov wrote:
>
> $ gdb mpg123
> (gdb) set args xxx.mp3
Or gdb --args mpg123 xxx.mp3 ;)
> (gdb) set env LD_PRELOAD /home/user/src/alsa-cvs/alsa-oss/alsa/.libs/libaoss.so
> (gdb) run
>
> This way LD_PRELOAD will be set only for the debugged process, and not for
> the debugger itself - hopefully the debugger will not crash and will
> provide some useful info.
Indeed, thanks. I've actually used something like this before, but I was
in such a hurry that I didn't think of it.
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
next prev parent reply other threads:[~2004-02-26 17:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 22:05 alsa-lib & oss 1.0.3rc1 Jaroslav Kysela
2004-02-24 16:59 ` Will
2004-02-25 11:05 ` Jaroslav Kysela
2004-02-25 13:40 ` Will
2004-02-26 0:06 ` Michel Dänzer
2004-02-26 10:30 ` Jaroslav Kysela
2004-02-26 14:13 ` Michel Dänzer
2004-02-26 14:10 ` Jaroslav Kysela
2004-02-26 14:30 ` Michel Dänzer
2004-02-26 14:33 ` Jaroslav Kysela
2004-02-26 17:53 ` Michel Dänzer
2004-02-26 18:38 ` Jaroslav Kysela
2004-02-27 12:38 ` Michel Dänzer
2004-02-27 13:49 ` Adam Tla/lka
2004-02-27 14:18 ` Adam Tla/lka
2004-02-26 15:55 ` Sergey Vlasov
2004-02-26 17:56 ` Michel Dänzer [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 21:43 Pawel Rozanski
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=1077818171.2680.123.camel@thor.asgaard.local \
--to=michel@daenzer.net \
--cc=alsa-devel@alsa-project.org \
--cc=vsu@altlinux.ru \
/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