Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2 RFC] workaround for debugedit segv
Date: Mon, 25 Mar 2013 17:47:52 +0000	[thread overview]
Message-ID: <1364233672.3097.64.camel@ted> (raw)
In-Reply-To: <1364231993-31670-1-git-send-email-mark.hatle@windriver.com>

On Mon, 2013-03-25 at 12:19 -0500, Mark Hatle wrote:
> [ YOCTO #4089 ]
> 
> This is an attempt at a workaround for the debugedit segv.
> 
> The problem is that during the creation of the build-id hash, the
> system iterates over the various ELF sections passing a point to the
> loaded data and size of each section to a hash function.
> 
> When it gets to the hash for the .plt and .bss section, the size is
> non-zero, while the data is point to 0.  This immediately causes a
> segfault on access of data at address 0.
> 
> See the bug and patch comments for more diagnostic information.

I really want to figure out how widespread issues are so I merged the
workaround and my version of the error handling patch so we start seeing
where the remaining problems are (if any).

I'm hoping to test this out on the autobuilder, see how we stand.

If further improvements are found to the workaround we can merge those
on top of the existing tree.

Cheers,

Richard






      parent reply	other threads:[~2013-03-25 18:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 17:19 [PATCH 0/2 RFC] workaround for debugedit segv Mark Hatle
2013-03-25 17:19 ` [PATCH 1/2 RFC] rpm: Add workaround for debugedit-segv Mark Hatle
2013-03-25 17:02   ` Phil Blundell
2013-03-25 17:10     ` Mark Hatle
2013-03-25 17:45       ` Phil Blundell
2013-03-25 19:32         ` Mark Hatle
2013-03-25 21:47           ` Mark Hatle
2013-03-26 10:38             ` Phil Blundell
2013-03-26 12:20               ` Mark Hatle
2013-03-25 17:19 ` [PATCH 2/2 RFC] package.bbclass: Trigger a bb.error if split/strip fails Mark Hatle
2013-03-25 17:47 ` 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=1364233672.3097.64.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=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