<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1">It seems that "</font><font size="-1">mdadm
--assemble --scan --auto=yes --symlink=no" </font><small>is the
faulty invocation.</small><br>
<font size="-1"><br>
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:<br>
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<br>
<br>
and now I can get the folowing:<br>
<br>
# gdb --args mdadm --assemble --scan --auto=yes --symlink=no<br>
GNU gdb (GDB) 7.0.1-debian<br>
Copyright (C) 2009 Free Software Foundation, Inc.<br>
License GPLv3+: GNU GPL version 3 or later
<a class="moz-txt-link-rfc2396E" href="http://gnu.org/licenses/gpl.html"><http://gnu.org/licenses/gpl.html></a><br>
This is free software: you are free to change and redistribute it.<br>
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"<br>
and "show warranty" for details.<br>
This GDB was configured as "arm-linux-gnueabi".<br>
For bug reporting instructions, please see:<br>
<a class="moz-txt-link-rfc2396E" href="http://www.gnu.org/software/gdb/bugs/"><http://www.gnu.org/software/gdb/bugs/></a>...<br>
Reading symbols from /usr/src/archive/mdadm-3.1.4/mdadm...done.<br>
(gdb) run<br>
Starting program: /usr/src/archive/mdadm-3.1.4/mdadm --assemble
--scan --auto=yes --symlink=no<br>
*** glibc detected *** /usr/src/archive/mdadm-3.1.4/mdadm:
munmap_chunk(): invalid pointer: 0x000a9800 ***<br>
*** glibc detected *** /usr/src/archive/mdadm-3.1.4/mdadm:
malloc(): memory corruption: 0x000a9660 ***<br>
<br>
Program received signal SIGABRT, Aborted.<br>
0x40065c88 in raise () from /lib/libc.so.6<br>
(gdb) bt<br>
#0 0x40065c88 in raise () from /lib/libc.so.6<br>
#1 0x40069c24 in abort () from /lib/libc.so.6<br>
#2 0x40069c24 in abort () from /lib/libc.so.6<br>
#3 0x40069c24 in abort () from /lib/libc.so.6<br>
#4 0x40069c24 in abort () from /lib/libc.so.6<br>
#5 0x40069c24 in abort () from /lib/libc.so.6<br>
#6 0x40069c24 in abort () from /lib/libc.so.6<br>
#7 0x40069c24 in abort () from /lib/libc.so.6<br>
#8 0x40069c24 in abort () from /lib/libc.so.6<br>
#9 0x40069c24 in abort () from /lib/libc.so.6<br>
#10 0x40069c24 in abort () from /lib/libc.so.6<br>
....<br>
<br>
Is it interesting?<br>
<br>
Thanks,<br>
<br>
Arnaud<br>
<br>
</font><br>
<br>
Le 09/04/2011 09:30, martin f krafft a écrit :
<blockquote
cite="mid:20110409073044.GA18550@fishbowl.rw.madduck.net"
type="cite">
<pre wrap="">also sprach Arnaud Desmier <a class="moz-txt-link-rfc2396E" href="mailto:arnaud.desmier@googlemail.com"><arnaud.desmier@googlemail.com></a> [2011.04.09.0923 +0200]:
</pre>
<blockquote type="cite">
<pre wrap="">How can I get the stack trace as you requested?
</pre>
</blockquote>
<pre wrap="">
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'.
</pre>
</blockquote>
</body>
</html>