From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 30107@debbugs.gnu.org
Subject: bug#30107: How I got the core dump
Date: Sat, 3 Feb 2018 09:36:26 +0100 [thread overview]
Message-ID: <20180203093626.6c927477@alma-ubu> (raw)
In-Reply-To: <87o9lxapul.fsf@gmail.com>
On request, I'm writing here how I got to that coredump:
My first step was to investigate the build.sh, and I just patched it to
output the full command, stripping of the rest:
diff --git a/bootstrap.sh b/bootstrap.x.sh
index bc54db4..f8c0720 100755
--- a/bootstrap.sh
+++ b/bootstrap.x.sh
@@ -151,18 +151,7 @@ cp src/script/antRun bin
chmod +x bin/antRun
echo ... Building Ant Distribution
-
-"${JAVACMD}" -classpath "${CLASSPATH}" -Dant.home=. $ANT_OPTS
org.apache.tools.ant.Main -emacs "$@" bootstrap -ret=$?
-if [ $ret != 0 ]; then
- echo ... Failed Building Ant Distribution !
- exit $ret
-fi
-
-
-echo ... Cleaning Up Build Directories
-
-rm -rf ${CLASSDIR}
-rm -rf bin
+echo I would do:
+echo "${JAVACMD}" -classpath "${CLASSPATH}" -Dant.home=. $ANT_OPTS
org.apache.tools.ant.Main -emacs "$@" bootstrap echo ... Done
Bootstrapping Ant Distribution
I added the patch into the package definition.
As I have learned yesterday, I could just repack the sources and use
guix --with-source=modified-ant.tar.gz ...
Anyway, I found out it calls:
/gnu/store/088bg6n5llvqn9j7d2740hhhilbqai4a-sablevm-1.13/bin/java-sablevm
-classpath build/classes:src/main:lib/xercesImpl.jar:lib/xml-apis.jar:
-Dant.home=. -Dbuild.compiler=jikes org.apache.tools.ant.Main -emacs
-Ddist.dir=/gnu/store/dxdsdsj4nz7fig92b2xjb7jf7swm5rni-ant-bootstrap-1.7.1
bootstrap
Next, I realized that my Ubuntu+Guix-on-top is eating up my core dumps:
$> cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c %d %P
So instead I went into my QEMU machine and continued there.
Set ulimit to unlimited:
ulimit -c unlimited
In sablevm, we need to get debugging infos into it:
Add to it's package definition's #arguments this one:
#:strip-binaries? #f
Rebuild it:
./pre-inst-env guix build -e '(@@ (gnu packages java) sablevm)'
--no-grafts --no-substitutes -K > sablevm.log 2>&1
Remove your failed builds /tmp/guix-build-* directories, if you have
any.
Then I looped through with this little bash script:
#!/bin/sh
ROUNDS=100
for i in `seq -w 0 $ROUNDS`; do
# DATE=${date}
# echo $DATE
echo -n $i..
./pre-inst-env guix build -e '(@@ (gnu packages java)
ant-bootstrap)' --no-grafts --no-substitutes --check -k -K >log-$i.log
2>&1
done;
echo
Then search in the logs:
grep Segementation log-*.log
Hopefully it finds one. Otherwise, repeat step above.
Check that it not onle Segfaults,but also has a "(core dumped)" behind
it. Otherwise, check your ulimit and corefile settings.
The coredump is in the /tmp/guix-build-ant..-n, where n coresponds to
your log-file number.
Finally, exporting the stack trace:
set logging on
set logging file backtrace.log
show logging
bt
info reg
quit
That's it.
Björn
prev parent reply other threads:[~2018-02-03 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 6:58 bug#30107: ant-bootstrap@1.7.1 sometimes fails to build on core-updates Chris Marusich
2018-01-14 9:32 ` Gábor Boskovits
2018-01-18 9:02 ` bug#30107: Another kind of failure Gábor Boskovits
2018-01-26 10:30 ` bug#30107: Backtrace Björn Höfling
2018-02-03 8:36 ` Björn Höfling [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180203093626.6c927477@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=30107@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).