Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <Openembedded-core@lists.openembedded.org>
Subject: Re: autom4te segfault in Dumper.so when configuring intltool
Date: Wed, 15 Apr 2015 12:08:50 +0200	[thread overview]
Message-ID: <20150415100850.GA2338@jama> (raw)
In-Reply-To: <CAJ86T=VMoW-hX-Y6xPy835Hfn4W3Wqbn_s+TCYWfHZ42Oc368w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2254 bytes --]

On Tue, Apr 14, 2015 at 07:05:35PM -0700, Andre McCurdy wrote:
> On Tue, Apr 14, 2015 at 4:39 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > Yes, I see it very often since this patch almost 3 years ago:
> > http://lists.openembedded.org/pipermail/openembedded-core/2012-August/066282.html
> 
> The problem seems to be that autom4te is getting executed by the host
> system's perl but loads Dumper.so from OE sysroot. If the host and OE
> versions of perl are sufficiently different then host perl crashes
> when it tries to execute OE sysroot Dumper.so
> 
> Manually hacking the first line of autom4te to replace "/usr/bin/perl"
> with the full path to the perl-native binary in OE sysroot makes the
> crashes stop.

Based on RP's reply in the old thread I assume you should rather try to
hack it to load Dumper.so from system, so that there is no dependency
between automake-native and perl-native.

> > On Tue, Apr 14, 2015 at 11:34 PM, Andre McCurdy <armccurdy@gmail.com> wrote:
> >>
> >> I'm seeing messages such as the following appear in syslog when
> >> building intltool or intltool-native from fido:
> >>
> >>   [1049484.121948] autom4te[16180]: segfault at 1 ip 00007fea41a7e7fe
> >> sp 00007fff3c666080 error 4 in Dumper.so[7fea41a77000+8000]
> >>   [1049567.199028] autom4te[17012]: segfault at 1 ip 00007f34acc007fe
> >> sp 00007fff5ed84db0 error 4 in Dumper.so[7f34acbf9000+8000]
> >>
> >> The segfault happens reproducibly when configuring intltool or
> >> intltool-native (one segfault every time I run or re-run the
> >> run.do_configure script).
> >>
> >> There are no obvious errors in config.log and the intltool build
> >> succeeds over-all.
> >>
> >> If I hack the intltool run.do_configure script so that the host
> >> machine's perl (v5.18.2) is found instead of perl-native from sysroot
> >> then the segfaults stop.
> >>
> >> Is anyone else seeing the same issue?
> >>
> >> Andre
> >> --
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> >

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-04-15 10:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 21:34 autom4te segfault in Dumper.so when configuring intltool Andre McCurdy
2015-04-14 23:39 ` Martin Jansa
2015-04-15  2:05   ` Andre McCurdy
2015-04-15 10:08     ` Martin Jansa [this message]
2015-04-15 21:37       ` Andre McCurdy
2015-04-17  2:09         ` Khem Raj
2015-04-17  7:15           ` Richard Purdie
2015-04-17 15:28             ` Khem Raj

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=20150415100850.GA2338@jama \
    --to=martin.jansa@gmail.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=armccurdy@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