On Tue, Jun 18, 2019 at 5:04 PM Mark Wielaard wrote:
> My apologies if you tried to upstream this and I missed it. But I think
> the patch below is a more complete fix. If you could test it in your
> setup that would be great.
Hi Mark,
I'm not sure if we tried to upstream the patch. So no worrie
On Tue, Jul 2, 2019 at 4:15 PM Mark Wielaard wrote:
> I'll try to create a testcase to replicate the issue to see if I can
> debug where the offset value gets truncated.
Sounds good to me.
> Or do you happen to have the 5.4 GB binary named "chrome" create before
> splitting still around somewher
On Wed, Jul 3, 2019 at 7:53 AM Mark Wielaard wrote:
> Thanks for the file, it is indeed pretty big :)
> But I am not able to replicate the issue with elfutils from git trunk.
> commit 31c8b3f098b0654db8f573b2a15d5b6d07d4d3b0
>
> And both the produced chrome_elfutil_test.stripped and
> chrome_elfut
On Wed, Jul 3, 2019 at 8:34 AM Mark Wielaard wrote:
> Great. Thanks for testing on a real world binary.
> There aren't actually that many out there this big!
> Please do let me know if you still see issues (or discover others).
You are welcome. Thank you for fixing this issue in elfutils.
We wil
