From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] AT91SAM9G20-EK and aplay
Date: Fri, 24 May 2013 10:05:20 +0200 [thread overview]
Message-ID: <20130524100520.01c518fd@skate> (raw)
In-Reply-To: <519F186B.3060606@scen.it>
Dear Carlo Rajko,
On Fri, 24 May 2013 09:36:11 +0200, Carlo Rajko wrote:
> With buildroot-2013.02 use kernel 3.1.6 and use toolchain
> CODESOURCERY_ARM201203
>
> The kernel detects sound card, but when use prg aplay or use mpg123 to
> play a file, receive a "Segmentation fault"
>
> if I run the command "cat file.wav > /dev/dsp" the sound card works fine.
>
> With buildroot-2011.11 is all ok.
>
> Can you help me ?
Do you have a few more messages in the kernel logs that given more
details about the segmentation fault?
Otherwise, do "ulimit -c unlimited", run the crashing application, it
will generate a 'core' file. Transfer it to your development PC, and
run cross-gdb on it:
./output/host/usr/bin/arm-linux-gdb -c core ./output/target/usr/bin/aplay
and then see what's the reason of the segmentation fault.
Also, could you post on http://code.bulix.org your Buildroot .config
and give us the link? Just to check there isn't anything obviously
wrong in your configuration file.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-24 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 7:36 [Buildroot] AT91SAM9G20-EK and aplay Carlo Rajko
2013-05-24 8:05 ` Thomas Petazzoni [this message]
2013-05-24 9:03 ` Carlo Rajko
2013-05-24 9:23 ` Thomas Petazzoni
2013-05-24 10:47 ` Carlo Rajko
2013-05-24 12:50 ` Gustavo Zacarias
2013-05-27 8:03 ` Carlo Rajko
2013-05-27 9:16 ` Thomas Petazzoni
2013-05-27 10:28 ` Carlo Rajko
2013-05-28 17:02 ` Arnout Vandecappelle
2013-05-29 15:15 ` Carlo Rajko
2013-07-04 9:02 ` Aleksandar Zivkovic
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=20130524100520.01c518fd@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.