From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12196] duma package
Date: Fri, 13 Dec 2019 22:34:30 +0000 [thread overview]
Message-ID: <bug-12196-163-IVQVj8jzR3@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 #6 from Arnout Vandecappelle <arnout@mind.be> ---
Really weird... This is the disassembly around the faulting instruction:
0xb6e04694 <+672>: b 0xb6e046dc <__gettextparse+744>
0xb6e04698 <+676>: b 0xb6e046dc <__gettextparse+744>
=> 0xb6e0469c <+680>: b 0xb6e04ab8 <__gettextparse+1732>
0xb6e046a0 <+684>: b 0xb6e04a94 <__gettextparse+1696>
0xb6e046a4 <+688>: b 0xb6e049fc <__gettextparse+1544>
0xb6e046a8 <+692>: b 0xb6e049e4 <__gettextparse+1520>
So it's in the middle of a switch table, simple relative branch instruction
0xea000105. The instructions that it jumps to all look pretty normal as well.
However, duma does do weird things with the code. It is possible that the real
fault is hidden by some exception handling within duma itself... gdb isn't able
to print a proper backtrace, so that could be an indication...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-12-13 22:34 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
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 [this message]
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-IVQVj8jzR3@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