From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: debugedit: canonicalization unexpectedly shrank by one character
Date: Thu, 25 Apr 2013 16:07:33 -0500 [thread overview]
Message-ID: <51799B15.2050600@windriver.com> (raw)
In-Reply-To: <B57A220D1EE1644685BA9AD5C790D20526BE5531DF@SOUTHSIDE.devonintlgroup.com>
On 4/25/13 3:43 PM, Ian Geiser wrote:
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> Martin Jansa
>> Sent: Wednesday, April 24, 2013 3:20 AM
>> To: openembedded-core@lists.openembedded.org
>> Subject: [OE-core] debugedit: canonicalization unexpectedly shrank by
>> one character
>>
>> Hi,
>>
>> with debugedit errors now catched and shown after:
>> commit 262a69ffd33e9d001a7a15fc73671a015e3b5dd1
>> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
>> Date: Mon Mar 25 16:52:07 2013 +0000
>>
>> package.bbclass: Handle subprocess errors correctly
>>
>> If an error occurs in subprocess.call() we currently don't catch
>> it. In particular
>> we have issues where debugedit is segfaulting unnoticed. This fixes
>> up
>> various code paths to catch the errors.
>>
>> I get couple of recipes failing with errors like:
> [...]
>> This leads to
>> https://bugzilla.redhat.com/show_bug.cgi?id=304121
>> https://bugs.launchpad.net/rpm/+bug/638633
>> https://qa.mandriva.com/show_bug.cgi?id=62391
>>
>> but no clear solution (it would be nice to show which path triggered
>> that message as suggested in redhat bugzilla)
>>
>> I can INHIBIT_PACKAGE_DEBUG_SPLIT in failing recipes or adding slash to
>> -d '/usr/src/debug/' works in this case too..
> I tried set PACKAGE_DEBUG_SPLIT_STYLE = "debug-without-src" in the package and that seemed to work around the problem. In my package that was offending was because there was an -rpath that had a trailing /. It seems debugedit is very sensitive to rogue path separators. Are there ways to make this more robust?
Source for debugedit is part of RPM. I don't see any reason why we wouldn't
accept patches for something like this. (However, it does seem like the rpath
may be wrong as well. Fixing the rpath should probably be done as well.)
--Mark
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2013-04-25 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 7:20 debugedit: canonicalization unexpectedly shrank by one character Martin Jansa
2013-04-25 20:43 ` Ian Geiser
2013-04-25 21:07 ` Mark Hatle [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=51799B15.2050600@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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