This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] runtime/unwind: Allow to increase MAX_CFI

From: Torsten Polle <Torsten dot Polle at gmx dot de>
To: Mark Wielaard <mark at klomp dot org>
Cc: systemtap at sourceware dot org
Date: Thu, 29 Nov 2018 22:12:40 +0100
Subject: Re: [PATCH] runtime/unwind: Allow to increase MAX_CFI
References: <C4E12EE3-D556-4F60-B8B0-C06978ED9D0B@gmx.de> <20181129180615.GL31795@wildebeest.org>

Hi Mark,

> Am 29.11.2018 um 19:06 schrieb Mark Wielaard <mark@klomp.org>:
> 
> Hi Torsten,
> 
> On Tue, Nov 27, 2018 at 10:37:08PM +0100, Torsten Polle wrote:
>> As discussed this patch allows to define the limit of CFIs to a higher value in case the limit is too low.
> 
> Thanks, applied to git master.

Thanks.

> I am still curious what program/library defines more than 512 CFI
> instructions. If you could post some example of eu-readelf --debug-dump=frame
> that would be interesting. I assume it must be some really big
> functions that haven't been split up?

I’m working on it. But it’s not that trivial. I included tons of libraries with the '-d' option and have to identify the one(s) that is (are) causing the warnings.

> Cheers,
> Mark

Regards,
Torsten

References:
- [PATCH] runtime/unwind: Allow to increase MAX_CFI
  - From: Torsten Polle
- Re: [PATCH] runtime/unwind: Allow to increase MAX_CFI
  - From: Mark Wielaard

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]