public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "ago at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/21315] multiple misaligned address errors for Elf64_Shdr
Date: Mon, 03 Apr 2017 16:37:00 -0000	[thread overview]
Message-ID: <bug-21315-10460-sup25xyVaM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21315-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=21315

--- Comment #2 from Agostino Sarubbo <ago at gentoo dot org> ---
(In reply to Mark Wielaard from comment #1)
> Note that in some cases elfutils deliberately does unaligned accesses if it
> believes it is safe. See the following in lib/eu-config.h:
> 
> /* Define ALLOW_UNALIGNED if the architecture allows operations on
>    unaligned memory locations.  */
> #define SANITIZE_UNDEFINED 1
> #if (defined __i386__ || defined __x86_64__) && ! CHECK_UNDEFINED
> # define ALLOW_UNALIGNED        1
> #else
> # define ALLOW_UNALIGNED        0
> #endif
> 
> Note that it is to not allow unaligned accesses when configuring with
> --enable-sanitize-undefined (which adds -fsanitize=undefined
> -fno-sanitize-recover to CFLAGS and CXXFLAGS).
> 
> Are you configuring using --enable-sanitize-undefined? Or adding
> -fsanitize=undefined by hand? In the later case you should also add
> -DCHECK_UNDEFINED=1

It was added by hand..I need to test if I obtain those warning with
--enable-sanitize-undefined

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-04-03 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 12:07 [Bug libelf/21315] New: multiple misaligned address errors ago at gentoo dot org
2017-03-27 12:10 ` [Bug libelf/21315] multiple misaligned address errors for Elf64_Shdr ago at gentoo dot org
2017-04-03 15:07 ` mark at klomp dot org
2017-04-03 16:37 ` ago at gentoo dot org [this message]
2017-05-24 20:05 ` ago at gentoo dot org
2017-05-24 20:21 ` mark at klomp dot org

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-21315-10460-sup25xyVaM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).