similar to: ibm fstack protector

I've downloaded wine 0.9.1 recently, after having used the last pre-.9 CVS drop for about a month or so, but the 0.9 version won't compile on my system. It conks out with an error in the loader subdir (actual data below). The following is the output I get when I run make: ------------------------------------------------------------------------------------- bas@pairadocs

I got some problem with wine (since wine 1.1.13) on hardened-sources ... actually using ... kernel -> 2.6.28-hardened-r7 #1 SMP Mon Apr 6 17:41:50 CEST 2009 x86_64 gcc -> x86_64-pc-linux-gnu-3.4.6-hardened Code: __bb_init_func': preloader.c:(.text+0x4f): undefined reference to `__guard' preloader.c:(.text+0x70): undefined reference to `__stack_smash_handler' preloader.o: In

i get this error on dmesg: zaptel: Unknown symbol __stack_smash_handler zaptel: Unknown symbol __guard paradise dove

On 2 Oct 2012, at 03:26, Magee, Josh wrote: > 1) An address of a local variable is taken in such a way as to expose the > address of a stack location. > - Example: the address of a local on the RHS of an assignment, the > address of a local passed into function. This sounds like something that would be triggered for any function containing a block, even if the

Hi all. For a while, gcc has supported a stack protection mechanism (-fstack-protector and friends, available in gcc 4.1.2 and up). Can anyone think of a good reason not to enable it if the compiler supports it? A quick test here shows minimal difference in runtime over a full regress pass (~10sec over 8.5 minutes, and since the machine is not entirely idle that could be experimental error).

David Chisnall wrote: >On 2 Oct 2012, at 03:26, Magee, Josh wrote: > >> 1) An address of a local variable is taken in such a way as to expose the >> address of a stack location. >> - Example: the address of a local on the RHS of an assignment, the >> address of a local passed into function. > > It also sounds like it would be triggered for a

I tried building dovecot using : CPPFLAGS="-fstack-protector" LDFLAGS="-lssp" ./configure That would result in a proper build, yet the binary would complain once being run: dlopen(/usr/local/lib/dovecot/imap/lib10_quota_plugin.so) failed: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so: undefined symbol: __stack_chk_fail_local Error: imap dump-capability process returned

On Mon, Feb 22, 2016 at 3:32 PM Joerg Sonnenberger via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Mon, Jan 25, 2016 at 07:57:43PM +0000, Tim Shen via llvm-dev wrote: > > A cleaner solution could be adding an IR intrinsic llvm.get_tcb_address() > > and hard code the offset of stack_guard member, since they aren't > supposed > > to change. > > It

On Mon, Feb 22, 2016 at 5:00 PM Eric Christopher <echristo at gmail.com> wrote: > Yeah, for most of the architectures listed there it's not particularly > useful as they support direct access to TLS variables (as Joerg says > later). That grep isn't representative of how the data is actually > accessed. If the current address space way of specifying isn't doable on

----- Original Message ----- > From: "Eric Christopher" <echristo at gmail.com> > To: "Tim Shen" <timshen at google.com>, llvm-dev at lists.llvm.org, "Hal > Finkel" <hfinkel at anl.gov>, "Kit Barton" <kbarton at ca.ibm.com> > Sent: Wednesday, February 10, 2016 6:59:50 PM > Subject: Re: [llvm-dev] [PPC] Linker fails on

When -fstack-protector is turned on, linker fails to find the symbol "__stack_chk_guard" because at least for powerpc64le, glibc doesn't provide this symbol. Instead, they put the stack guard into TCB. x86 fixed this issue by injecting a special address space (which is later translated to TCB register access) and hard code the offset of stack_guard, but I don't see a easy way to

Hi, List, In checking the page fault problem when using pv-grub to start domU in opensuse12.3[1], found that the problem is caused by ''-fstack-protector'' flag which is introduced in rpm build: export EXTRA_CFLAGS_XEN_TOOLS="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_TRADITIONAL="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_XEN="$RPM_OPT_FLAGS" with

hi is there any way to build 4.8 release with this fstack protection? or atleast some ports is there any good info on this? the only page i found was that ibm page but it seemed outdated. //martin

Hello, Does the -fstack-protector option work on CLANG 3.1 and 3.2? There is thread on FreeBSD forums about the stack protector and ports and I'm wondering if it's possible to use the -fstack-protector option with CLANG. http://forums.freebsd.org/showthread.php?t=36927 -Kimmo

I'll come up with a address-space-based proof of concept. On Wed, Feb 10, 2016, 17:05 Eric Christopher <echristo at gmail.com> wrote: > On Wed, Feb 10, 2016 at 5:04 PM Hal Finkel <hfinkel at anl.gov> wrote: > >> >> ------------------------------ >> >> *From: *"Eric Christopher" <echristo at gmail.com> >> *To: *"Tim

On 10/1/12 9:26 PM, Magee, Josh wrote: > Hello, > > I plan to implement "Stack Smashing Protection - Strong" support in LLVM. > Below is a description of this feature and an overview of the implementation > plan. I have divided up the implementation into stages that can be delivered > incrementally. > > I'm looking for any feedback (suggestions, requests,

I found a bit weird to use address space for this, since the offset of getting stack_guard in TCB is, unfortunately, negative: https://github.com/gcc-mirror/gcc/blob/master/gcc/config/rs6000/linux64.h#L610 In my understanding an address space is referring to a segment register (-on powerpc 32bit; or SLB entry on powerpc 64bit?) with a non-negative offset value, so that it's actually accessing

On 2009-01-24 19:27, Ingo Molnar wrote: > * Török Edwin <edwintorok at gmail.com> wrote: > >> #define put_user(x, ptr) \ >> ({ \ >> - int __ret_pu; \ >> + __typeof__(*(ptr)) __ret_pu; \ >> > > This does not look right. We can sometimes have

Hello, I plan to implement "Stack Smashing Protection - Strong" support in LLVM. Below is a description of this feature and an overview of the implementation plan. I have divided up the implementation into stages that can be delivered incrementally. I'm looking for any feedback (suggestions, requests, etc) before I actually begin the work. Thank you! Josh

Hi List- I''m brand new to xen but an old hand with Linux. With a fresh, clean, Gentoo installation on this box, I''m attempting to install xen using the gentoo-standard: emerge xen but the process is failing with an error that''s very similar to one reported by another user (A Streetcar Named: see