From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlo Rajko Date: Fri, 24 May 2013 12:47:09 +0200 Subject: [Buildroot] AT91SAM9G20-EK and aplay In-Reply-To: <20130524112355.70d1cc53@skate> References: <519F186B.3060606@scen.it> <20130524100520.01c518fd@skate> <519F2CDB.8080805@scen.it> <20130524112355.70d1cc53@skate> Message-ID: <519F452D.4070505@scen.it> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Il 24/05/2013 11:23, Thomas Petazzoni ha scritto: > 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. > OK. GNU gdb (Sourcery CodeBench Lite 2012.03-57) 7.2.50.20100908-cvs Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi". For bug reporting instructions, please see: ... Reading symbols from /home/carlo/debug/aplay...(no debugging symbols found)...done. warning: exec file is newer than core file. [New LWP 524] Reading symbols from /home/carlo/debug/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /home/carlo/debug/librt.so.1 Reading symbols from /home/carlo/debug/libasound.so.2...(no debugging symbols found)...done. Loaded symbols for /home/carlo/debug/libasound.so.2 Reading symbols from /home/carlo/debug/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /home/carlo/debug/libm.so.6 Reading symbols from /home/carlo/debug/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /home/carlo/debug/libdl.so.2 Reading symbols from /home/carlo/debug/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /home/carlo/debug/libpthread.so.0 Reading symbols from /home/carlo/debug/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /home/carlo/debug/libgcc_s.so.1 Reading symbols from /home/carlo/debug/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /home/carlo/debug/libc.so.6 Reading symbols from /home/carlo/debug/ld-linux.so.3...(no debugging symbols found)...done. Loaded symbols for /home/carlo/debug/ld-linux.so.3 Core was generated by `/mnt/2/sox/aplay'. Program terminated with signal 11, Segmentation fault. #0 0x400f31cc in ?? () from /home/carlo/debug/ld-linux.so.3 (gdb) >> 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 :-) OK, sorry. http://code.bulix.org/bazvmv-83592?raw Best regards, Carlo