Bug#621786: mdadm: invalid pointer or memory corruption on armel system

[Arnaud Desmier]

It seems that "mdadm --assemble --scan --auto=yes --symlink=no" is the 
faulty invocation.

I've run gdb using package mdadm but it couldn't find any debug 
symbol... So I run the following command as Makefile displays when 
compiling package:
gcc  -o mdadm mdadm.o config.o mdstat.o  ReadMe.o util.o Manage.o 
Assemble.o Build.o Create.o Detail.o Examine.o Grow.o Monitor.o dlink.o 
Kill.o Query.o Incremental.o mdopen.o super0.o super1.o super-ddf.o 
super-intel.o bitmap.o restripe.o sysfs.o sha1.o mapfile.o crc32.o 
sg_io.o msg.o platform-intel.o probe_roms.o

and now I can get the folowing:

# gdb --args mdadm --assemble --scan --auto=yes --symlink=no
GNU gdb (GDB) 7.0.1-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
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 "arm-linux-gnueabi".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/src/archive/mdadm-3.1.4/mdadm...done.
(gdb) run
Starting program: /usr/src/archive/mdadm-3.1.4/mdadm --assemble --scan 
--auto=yes --symlink=no
*** glibc detected *** /usr/src/archive/mdadm-3.1.4/mdadm: 
munmap_chunk(): invalid pointer: 0x000a9800 ***
*** glibc detected *** /usr/src/archive/mdadm-3.1.4/mdadm: malloc(): 
memory corruption: 0x000a9660 ***

Program received signal SIGABRT, Aborted.
0x40065c88 in raise () from /lib/libc.so.6
(gdb) bt
#0  0x40065c88 in raise () from /lib/libc.so.6
#1  0x40069c24 in abort () from /lib/libc.so.6
#2  0x40069c24 in abort () from /lib/libc.so.6
#3  0x40069c24 in abort () from /lib/libc.so.6
#4  0x40069c24 in abort () from /lib/libc.so.6
#5  0x40069c24 in abort () from /lib/libc.so.6
#6  0x40069c24 in abort () from /lib/libc.so.6
#7  0x40069c24 in abort () from /lib/libc.so.6
#8  0x40069c24 in abort () from /lib/libc.so.6
#9  0x40069c24 in abort () from /lib/libc.so.6
#10 0x40069c24 in abort () from /lib/libc.so.6
....

Is it interesting?

Thanks,

Arnaud



Le 09/04/2011 09:30, martin f krafft a écrit :
> also sprach Arnaud Desmier<arnaud.desmier at googlemail.com>  [2011.04.09.0923 +0200]:
>> How can I get the stack trace as you requested?
> Find the exact invocation of mdadm that produces the problem and run
> it under gdb until it crashes. The stacktrace you can then get with
> 'bt'.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20110409/39c27eb8/attachment-0001.htm>