From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] AT91SAM9G20-EK and aplay
Date: Fri, 24 May 2013 11:23:55 +0200 [thread overview]
Message-ID: <20130524112355.70d1cc53@skate> (raw)
In-Reply-To: <519F2CDB.8080805@scen.it>
Dear Carlo Rajko,
On Fri, 24 May 2013 11:03:23 +0200, Carlo Rajko wrote:
> I do not have arm-linux-gdb but have arm-none-linux-gnueabi-gdb.
> But when use the command
> ./output/host/opt/ext-toolchain/bin/arm-none-linux-gnueabi-gdb -c core
> ./output/target/usr/bin/aplay and use command "run" the debugger show:
> Don't know how to run. Try "help target".
Don't use "run", "run" is to start the program. Here we want to do a
post-mortem analysis of the crash using the core file. Google "gdb core
file" to have more details about what a core file is.
Can you run the gdb command, and copy/paste what you see? Without
entering any command *inside* gdb, it should already tell you which
instruction has faulted, and for what reason.
> I think the problem is not in aply because I have the same problem with
> mpg123.
> Could be the library alsa?
It could. But at least gdb will tell us if it's an undefined
instruction, an invalid memory access, an unaligned access, or
something else.
> > 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.
>
> when I press buttom "PASTE" I have error "Antispam verification failed"
Right left to the "Paste" button there is a little box to train your
mental calculation. You should pay attention to it :-)
Thanks,
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 9:23 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
2013-05-24 9:03 ` Carlo Rajko
2013-05-24 9:23 ` Thomas Petazzoni [this message]
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=20130524112355.70d1cc53@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox