public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>,
	Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Strange segfault on native Go binaries
Date: Tue, 15 Dec 2020 08:42:19 +0000	[thread overview]
Message-ID: <e764b980aaeff08300ca9b1cf2a7a7d5d817400f.camel@linuxfoundation.org> (raw)
In-Reply-To: <04ea4495-feba-652d-9b15-d09e23c7bc03@gmail.com>

On Mon, 2020-12-14 at 21:18 -0800, Khem Raj wrote:
> The problem seems to obscure editing of the glide binary which is 
> resulting in a single byte in ELF header being modified between 
> do_install and do_populate_sysroot
> 
> easy reproducer is
> 
> bitbake -cinstall glide-native
> 
> then make a copy of glide installed in image/ dir ( where do_install 
> puts it ) then run
> 
> bitbake -cpopulate_sysroot glide-native
> 
> % cmp 
> ../../image/mnt/b/yoe/master/build/tmp/work/x86_64-linux/glide-
> native/0.13.3-r0/recipe-sysroot-native/usr/bin/glide 
> glide
> 
> so they are identical.
> 
> and now compare the installed binary and the saved copy.
> 
> % cmp 
> ../../image/mnt/b/yoe/master/build/tmp/work/x86_64-linux/glide-
> native/0.13.3-r0/recipe-sysroot-native/usr/bin/glide 
> glide
> ../../image/mnt/b/yoe/master/build/tmp/work/x86_64-linux/glide-
> native/0.13.3-r0/recipe-sysroot-native/usr/bin/glide 
> glide differ: byte 57, line 1
> 
> it seems installed binary is fine until do_install but then gets
> edited 
> during populate_sysroot
> 
> I have shunted many functions, including patchelf operations and the 
> binary still gets modified in place
> 
> I wonder what other operations could be put under scanner here, Let
> me 
> know if anyone has ideas..

Is it from chrpath.bbclass? or the patchelf call in uninative.bbclass?

Cheers,

Richard


      reply	other threads:[~2020-12-15  8:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12 23:52 Strange segfault on native Go binaries Otavio Salvador
2020-12-13  2:29 ` [OE-core] " Khem Raj
2020-12-13 14:52   ` Otavio Salvador
2020-12-14  3:48     ` Khem Raj
2020-12-14 11:31       ` Otavio Salvador
2020-12-14 11:51         ` Konrad Weihmann
2020-12-14 14:03           ` Otavio Salvador
2020-12-14 14:05             ` Konrad Weihmann
2020-12-14 15:25               ` Otavio Salvador
2020-12-14 15:50                 ` Konrad Weihmann
2020-12-14 22:58 ` Khem Raj
2020-12-14 23:50   ` Otavio Salvador
2020-12-15  0:12     ` Khem Raj
2020-12-15  5:18       ` Khem Raj
2020-12-15  8:42         ` Richard Purdie [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e764b980aaeff08300ca9b1cf2a7a7d5d817400f.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=raj.khem@gmail.com \
    /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