From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12196] duma package
Date: Tue, 17 Sep 2019 08:32:41 +0000 [thread overview]
Message-ID: <bug-12196-163-qmdRnxtvkd@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12196-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12196
--- Comment #2 from Aleksey <ioctl@ya.ru> ---
Its a specific debug tool, that works on low level, so, I think, author of the
duma has a reason to use -O0 in original GNUmakefile.
However, we can try to understand this reason.
Unfortunately I was unable to get core dump in buildroot environment. How can I
do it?
As for the CPU, its a Marvell SOC. I have the following options in the
configuration:
BR2_ARCH="arm"
BR2_ENDIAN="LITTLE"
BR2_GCC_TARGET_ABI="aapcs-linux"
BR2_GCC_TARGET_CPU="marvell-pj4"
BR2_GCC_TARGET_FPU="vfpv3-d16"
BR2_GCC_TARGET_FLOAT_ABI="softfp"
BR2_GCC_TARGET_MODE="arm"
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-09-17 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 8:31 [Buildroot] [Bug 12196] New: duma package bugzilla at busybox.net
2019-09-11 13:30 ` [Buildroot] [Bug 12196] " bugzilla at busybox.net
2019-09-17 8:32 ` bugzilla at busybox.net [this message]
2019-11-27 20:40 ` bugzilla at busybox.net
2019-12-09 10:53 ` bugzilla at busybox.net
2019-12-09 10:55 ` bugzilla at busybox.net
2019-12-09 10:55 ` bugzilla at busybox.net
2019-12-13 22:34 ` bugzilla at busybox.net
2020-05-20 14:38 ` [Buildroot] [Bug 12196] Illegal instruction in "duma" when built with -O2 bugzilla at busybox.net
2024-06-15 14:50 ` bugzilla
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=bug-12196-163-qmdRnxtvkd@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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