[lsb-discuss] question on __longjmp_chk

Petrie, Glen glen.petrie at eitc.epson.com
Thu Aug 23 20:38:26 UTC 2012


Thanks, I will have to disable FORTIFY SOURCE


-----Original Message-----
From: Carlos O'Donell [mailto:carlos_odonell at mentor.com] 
Sent: Thursday, August 23, 2012 1:25 PM
To: Petrie, Glen
Cc: Wichmann, Mats D; lsb-discuss at lists.linux-foundation.org
Subject: Re: [lsb-discuss] question on __longjmp_chk

On 8/23/2012 4:13 PM, Wichmann, Mats D wrote:
> What's not mentioned here is that __longjmp_chk is a new-ish symbol,
> in LSB terms, it's tagged GLIBC_2.11 which is newer than anything
> included in LSB at thing point (will change as of LSB 5.0, but that's
> a different story).

I would also point out that the code in question doesn't use
__longjmp_chk directly either, the compiler does it for you as part of
a runtime check enabled with FORTIFY SOURCE (-D_FORTIFY_SOURCE=n).

Thus if you *really* need to build this application you could do so by
disabling FORTIFY SOURCE for your build of the application using CFLAGS.

Cheers,
Carlos.
-- 
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell at mentor.com
carlos at codesourcery.com
+1 (613) 963 1026


More information about the lsb-discuss mailing list