Hello,
I see that most of the ELF on my system, contain a signature like so:
ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked
(uses shared libs), for GNU/Linux 2.6.32,
BuildID[sha1]=0x39645af26ea483eaae81df45bf34701580506115, stripped
There are two very interesting
On 28 May 2012, at 14:09, ik wrote:
The second part is more interesting for this subject: It signs a checksum
of the ELF file, so any change to it will break the checksum.
It helps you to discover for example root-kits.
Is it a compiler based signature, or something from the build itself ?
Hello all,
I'm compiling the program at the end of this message in x86 and x64 mode
using the following command lines:
ppc386 -MDelphi -CfSSE3 testFPU.dpr
ppcrossx64 -MDelphi -CfSSE3 testFPU.dpr
while I get an exe file and no error in x64 mode, I get the following
error message with ppc386:
Is it possible to cross-compile a Linux/x86_64 target on a Linux/i386
host? AFAICT it should be possible and I've almost got it working (using
Debian's gcc-4.4-multilib for start-up code) but the linker looks for
x86_64 libraries that aren't available on a i386 system.
I'm guessing that libraries
On 28 May 2012, at 14:56, Bruce Tulloch wrote:
Am I correct to assume that if I drag in the x86_64 libraries I need
from another x86_64 system, put them in a local directory and then
reference then using the -XR option I can make this setup work?
-XR is for pointing the compiler/linker to
Excellent, thanks Jonas.
On 05/28/12 23:02, Jonas Maebe wrote:
On 28 May 2012, at 14:56, Bruce Tulloch wrote:
Am I correct to assume that if I drag in the x86_64 libraries I need
from another x86_64 system, put them in a local directory and then
reference then using the -XR option I can
On 28 May 2012, at 14:41, OBones wrote:
I'm compiling the program at the end of this message
The program is missing.
I really need to have the same instruction set used for floating point maths,
hence the use of SSE3 in both cases.
If your x86-64 target is Win64, using -CfSSE2/-CfSSE3
On 28 May 2012, at 15:19, OBones wrote:
Bugger, why does this keep happening to me???
Anyway, this time it is at the end.
I cannot reproduce the problem with 2.6.0/2.7.1 on Mac OS X/i386, nor with
2.7.1 on Linux/i386. I even don't see any comis* instructions in the code, the
comparison is
This is a pure fpc project, no LCL. If I have understood it correctly
then I have to call the CallAction() method for every connection I
have created but this seems to totally contradict what it claims to be
able to do: namely using some sophisticated event-mechanism that can
watch multiple
Jonas Maebe wrote:
On 28 May 2012, at 15:19, OBones wrote:
Bugger, why does this keep happening to me???
Anyway, this time it is at the end.
I cannot reproduce the problem with 2.6.0/2.7.1 on Mac OS X/i386, nor with
2.7.1 on Linux/i386. I even don't see any comis* instructions in the code,
Am Sunday 27 May 2012 17:44:41 schrieb Sven Barth:
On 27.05.2012 14:32, Rainer Stratmann wrote:
How to get debug information?
There is an error, but only adresses are shown.
I put on debugger Information in Lazarus (-g) but can get no further
infos when an error occurs (except the
On 27/05/2012 13:32, Rainer Stratmann wrote:
How to get debug information?
There is an error, but only adresses are shown.
How/ Where are the addresses shown?
Does your program has code of it's own, that dumps the stacktrace?
(normally added using with -gl)
Or do you run in a debugger
Am Monday 28 May 2012 21:12:30 schrieb Martin:
On 27/05/2012 13:32, Rainer Stratmann wrote:
How to get debug information?
There is an error, but only adresses are shown.
How/ Where are the addresses shown?
The addresses were shown in the output window (console).
Runtime error 207 at
On Mon, May 28, 2012 at 3:34 PM, Jonas Maebe jonas.ma...@elis.ugent.bewrote:
On 28 May 2012, at 14:09, ik wrote:
The second part is more interesting for this subject: It signs a checksum
of the ELF file, so any change to it will break the checksum.
It helps you to discover for example
On 28/05/2012 20:35, Rainer Stratmann wrote:
Am Monday 28 May 2012 21:12:30 schrieb Martin:
On 27/05/2012 13:32, Rainer Stratmann wrote:
How to get debug information?
There is an error, but only adresses are shown.
How/ Where are the addresses shown?
The addresses were shown in the output
Am Monday 28 May 2012 22:09:21 schrieb Martin:
On 28/05/2012 20:35, Rainer Stratmann wrote:
Am Monday 28 May 2012 21:12:30 schrieb Martin:
On 27/05/2012 13:32, Rainer Stratmann wrote:
How to get debug information?
There is an error, but only adresses are shown.
How/ Where are the
On 28/05/2012 21:19, Rainer Stratmann wrote:
Am Monday 28 May 2012 22:09:21 schrieb Martin:
On 28/05/2012 20:35, Rainer Stratmann wrote:
Am Monday 28 May 2012 21:12:30 schrieb Martin:
On 27/05/2012 13:32, Rainer Stratmann wrote:
How to get debug information?
There is an error, but only
Am Monday 28 May 2012 22:25:47 schrieb Martin:
Check that you have not accidentally set any options that will block
-gl, such as -Xs or maybe (may work but I do not know for sure) -Xg
After changing options, change Build or Build all from run menu.
All done, same effect (only addresses
On 28/05/2012 23:53, Rainer Stratmann wrote:
Am Monday 28 May 2012 22:25:47 schrieb Martin:
Check that you have not accidentally set any options that will block
-gl, such as -Xs or maybe (may work but I do not know for sure) -Xg
After changing options, change Build or Build all from run menu.
Can you create a generic that is based on a class that can stream
itself using rtti regardles of its structure ?
Something like
Type
TFundamentalClass = Class(TObject)
Public
Function GetProperty(Propertyname : String): Variant;
Procedure SetProperty(PropertyName : String; Value : Variant);
20 matches
Mail list logo
