From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] alsa-lib crashes with current OSELAS.Tollchain-2011.11.0 toolchain (arm-v4t-linux-gnueabi)
Date: Tue, 27 Dec 2011 19:31:53 +0100 [thread overview]
Message-ID: <201112271931.53676.jbe@pengutronix.de> (raw)
Hi,
someone here who has tried to run something alsa-lib related with our current
OSELAS.Tollchain-2011.11.0?
Here all programs are crashing with a "Segmentation fault" if they are using
the 'libasound.so' at run-time. There are reports about issues with alsa-libs
and glibc-2.14 [1].
All I can say is, the same alsa-lib release runs without a problem on a system
build with the OSELAS.Tollchain-2011.03.0 (and so with the older glibc-2.13).
I tried with 'catchseg' but the output is very 'strange' and not helpfull:
root@mini2440:/ catchsegv aplay /mnt/music.wav
Segmentation fault
*** Segmentation fault
Register dump:
R0: bee43768 R1: 04698ec3 R2: bee43480 R3: 00000000
R4: 00000000 R5: 01b6b164 R6: 8d31d86a R7: 00000007
R8: 00000000 R9: bee43768 SL: 40114dc8 FP: 40115000
IP: 400bc6a4 SP: bee43388 LR: 400f818c PC: 400f7a00
CPSR: 20000010
Trap: 0000000e Error: 00000017 OldMask: 00000000
Addr: 00000014
Backtrace:
Memory map:
00008000-00016000 r-xp 00000000 00:0e 33729737 /usr/bin/aplay
0001d000-0001e000 rwxp 0000d000 00:0e 33729737 /usr/bin/aplay
01b67000-01b8c000 rwxp 00000000 00:00 0 [heap]
40010000-40012000 r-xp 00000000 00:0e 33671138 /lib/libdl-2.14.1.so
40012000-40019000 ---p 00002000 00:0e 33671138 /lib/libdl-2.14.1.so
40019000-4001a000 r-xp 00001000 00:0e 33671138 /lib/libdl-2.14.1.so
4001a000-4001b000 rwxp 00002000 00:0e 33671138 /lib/libdl-2.14.1.so
4006b000-40071000 r-xp 00000000 00:0e 33671132 /lib/librt-2.14.1.so
40071000-40078000 ---p 00006000 00:0e 33671132 /lib/librt-2.14.1.so
40078000-40079000 r-xp 00005000 00:0e 33671132 /lib/librt-2.14.1.so
40079000-4007a000 rwxp 00006000 00:0e 33671132 /lib/librt-2.14.1.so
400bc000-400bd000 rwxp 00000000 00:00 0
400ca000-400cb000 rwxp 00000000 00:00 0
400ea000-400eb000 rwxp 00000000 00:00 0
400ee000-4010c000 r-xp 00000000 00:0e 33671102 /lib/ld-2.14.1.so
40114000-40115000 r-xp 0001e000 00:0e 33671102 /lib/ld-2.14.1.so
40115000-40116000 rwxp 0001f000 00:0e 33671102 /lib/ld-2.14.1.so
40116000-4012a000 r-xp 00000000 00:0e 33671115 /lib/libpthread-2.14.1.so
4012a000-40132000 ---p 00014000 00:0e 33671115 /lib/libpthread-2.14.1.so
40132000-40133000 r-xp 00014000 00:0e 33671115 /lib/libpthread-2.14.1.so
40133000-40134000 rwxp 00015000 00:0e 33671115 /lib/libpthread-2.14.1.so
40134000-40136000 rwxp 00000000 00:00 0
4014b000-4014d000 r-xp 00000000 00:0e 10031903 /lib/libSegFault.so
4014d000-40154000 ---p 00002000 00:0e 10031903 /lib/libSegFault.so
40154000-40155000 r-xp 00001000 00:0e 10031903 /lib/libSegFault.so
40155000-40156000 rwxp 00002000 00:0e 10031903 /lib/libSegFault.so
40156000-4024b000 r-xp 00000000 00:0e 33677413 /usr/lib/libasound.so.2.0.0
4024b000-40252000 ---p 000f5000 00:0e 33677413 /usr/lib/libasound.so.2.0.0
40252000-40255000 rwxp 000f4000 00:0e 33677413 /usr/lib/libasound.so.2.0.0
40255000-402f4000 r-xp 00000000 00:0e 33671168 /lib/libm-2.14.1.so
402f4000-402fb000 ---p 0009f000 00:0e 33671168 /lib/libm-2.14.1.so
402fb000-402fc000 r-xp 0009e000 00:0e 33671168 /lib/libm-2.14.1.so
402fc000-402fd000 rwxp 0009f000 00:0e 33671168 /lib/libm-2.14.1.so
402fd000-40308000 r-xp 00000000 00:0e 33733303 /lib/libgcc_s.so.1
40308000-4030f000 ---p 0000b000 00:0e 33733303 /lib/libgcc_s.so.1
4030f000-40310000 rwxp 0000a000 00:0e 33733303 /lib/libgcc_s.so.1
40310000-40433000 r-xp 00000000 00:0e 33671109 /lib/libc-2.14.1.so
40433000-4043a000 ---p 00123000 00:0e 33671109 /lib/libc-2.14.1.so
4043a000-4043c000 r-xp 00122000 00:0e 33671109 /lib/libc-2.14.1.so
4043c000-4043d000 rwxp 00124000 00:0e 33671109 /lib/libc-2.14.1.so
4043d000-40440000 rwxp 00000000 00:00 0
bee23000-bee44000 rw-p 00000000 00:00 0 [stack]
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors
Any idea how to debug a toolchain/glibc issue like this?
Regards,
Juergen
[1]
http://www.linuxquestions.org/questions/linux-from-scratch-13/segfault-in-ld-2-14-so-running-alsa-utils-893812/
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2011-12-27 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201112271931.53676.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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