Thank you, this revealed something that could be reason for the
FORTIFY error.
Marco Hoehle wrote:
> "most uncertain component of computer systems are humans !"
>
> First of all - my appoligies . Everything I said yesterday about the
> segfaults is not so critical as it seems to be.
>
> I found
Good news. thanks
Marco Hoehle wrote:
> "most uncertain component of computer systems are humans !"
>
> First of all - my appoligies . Everything I said yesterday about the
> segfaults is not so critical as it seems to be.
>
> I found out why I was not able to reproduce the segmentation faults
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"most uncertain component of computer systems are humans !"
First of all - my appoligies . Everything I said yesterday about the
segfaults is not so critical as it seems to be.
I found out why I was not able to reproduce the segmentation faults at
wo
You could also try running through Valgrind
M
Marco Hoehle wrote:
> Hello,
>
>
> running on CentOS 5.3 / RHEL5.3 32 and 64bit , cf3 trunk build 434.
> When compiling cf3 without special options the cf-agent binary is
> throwing a segfault after every run.
> When disabling FORTIFY_SOURCE with CF
Can you provide example code that fails?
Marco Hoehle wrote:
> Hello,
>
>
> running on CentOS 5.3 / RHEL5.3 32 and 64bit , cf3 trunk build 434.
> When compiling cf3 without special options the cf-agent binary is
> throwing a segfault after every run.
> When disabling FORTIFY_SOURCE with CFLAGS=
