From: Manuel Reimer <manuel.reimer@gmx.de>
To: qemu-devel@nongnu.org
Subject: [Bug 1869073] [NEW] qemu-arm-static crashes "segmentation fault" when running "git clone -s"
Date: Wed, 25 Mar 2020 19:52:40 -0000 [thread overview]
Message-ID: <158516596046.18657.8423350120096244746.malonedeb@chaenomeles.canonical.com> (raw)
Public bug reported:
I want to use qemu-arm-static to cross-compile software. The compiler
itself is a native cross-compiler connected via "distcc".
The problem is that a script tries to do some stuff with "git" and with
a "git clone -s" command the whole story reproducibly stops with a
"segmentation fault".
I don't know how to properly debug the issue but it happens 100% of the
time that I get the "crash" or git just hangs forever with 100% CPU
usage.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869073
Title:
qemu-arm-static crashes "segmentation fault" when running "git clone
-s"
Status in QEMU:
New
Bug description:
I want to use qemu-arm-static to cross-compile software. The compiler
itself is a native cross-compiler connected via "distcc".
The problem is that a script tries to do some stuff with "git" and
with a "git clone -s" command the whole story reproducibly stops with
a "segmentation fault".
I don't know how to properly debug the issue but it happens 100% of
the time that I get the "crash" or git just hangs forever with 100%
CPU usage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869073/+subscriptions
next reply other threads:[~2020-03-25 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 19:52 Manuel Reimer [this message]
2020-03-26 6:57 ` [Bug 1869073] Re: qemu-arm-static crashes "segmentation fault" when running "git clone -s" Laurent Vivier
2020-03-26 17:49 ` Manuel Reimer
2020-03-26 20:09 ` Peter Maydell
2020-08-08 9:50 ` Thomas Huth
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=158516596046.18657.8423350120096244746.malonedeb@chaenomeles.canonical.com \
--to=manuel.reimer@gmx.de \
--cc=1869073@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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.
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 NNTP newsgroup(s).