Hi, Just wondering if anyone has any ideas.
I am using FPC 3.0 by the way.
Anyway, I am using a third party SFTP server lib and it creates a thread
inherited from tthread and in the create event of the tthread descendant it
does this:
(It uses this thread to read and write data on the socket)
FDa
Thanks Graeme.
To know what is sent to the linker, there is the -s parameter.
# fpc -XX -s test.pas
This will compile the object and create a script file for the linker.
Here the script with -XX parameter:
/usr/bin/ld -b elf32-i386-freebsd -m elf_i386_fbsd *--gc-sections* -s -L. -0
./test ./lin
El 13/10/2016 a las 15:07, Graeme Geldenhuys escribió:
> On 2016-10-13 13:48, Sven Barth wrote:
>> That won't help with Halt() however as that will "jump" directly to the
>> unit finalization, ignoring any and all exception handlers along the way.
>
> Wow, that's a bit harsh. Overriding the whole m
Hi.
> Anyway, I think that when the application is closed all the allocated
> memory is freed, memory leaks survive as long as the application is
> running. So wondering about what's in memory after a halt makes no
> sense, everything is freed.
I am not very familiar with internals of system pr
Hi.
> I would also rewrite that with a try..finally as in:
Thanks. This is what I am planning to do eventually but as for now I
am learning the ropes -- freepascal is kind of new to me and I am
slowly learning its new features. Last Pascal I've been programming in
was TP 6.0 with TurboVisi
Hi.
> Call Terminate and exit properly ?
> TCustomApplication has an exitcode property which will set the global exit
> code.
This feature either undocumented or I am just too stupid to find it. Mind if I
ask you to point me directly to the documentation?
I believe it would have to be something
Am 13.10.2016 15:07 schrieb "Graeme Geldenhuys" <
mailingli...@geldenhuys.co.uk>:
>
> On 2016-10-13 13:48, Sven Barth wrote:
> > That won't help with Halt() however as that will "jump" directly to the
> > unit finalization, ignoring any and all exception handlers along the
way.
>
>
> Wow, that's a
due to the fact that there is no fixed time between major releases ,
one can wait maybe 10 years to see a next major release , just like
gcc4 (2004-2014) , in the other hand gcc5 lives only 1 year .
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.
On 2016-10-13 13:48, Sven Barth wrote:
> That won't help with Halt() however as that will "jump" directly to the
> unit finalization, ignoring any and all exception handlers along the way.
Wow, that's a bit harsh. Overriding the whole meaning of the
try..finally language feature. Then I would rec
Am 13.10.2016 10:09 schrieb "Graeme Geldenhuys" <
mailingli...@geldenhuys.co.uk>:
>
> On 2016-10-12 20:37, grouchysmurf wrote:
> > Say, I have a code, where TH is a Class(TCustomApplication):
> >
> > ph := TH.Create(Nil);
> > ph.Initialize;
> > ph.ProcessOptions;
> > ph.Run;
> > ph.Free;
On 2016-10-07 14:38, fredvs wrote:
> FreeBSD has decided to stop FreeBSD 32 bit
I just saw the FreeBSD 11.0 release announcement. In the "Availability"
list, i386 is still mentioned.
https://www.freebsd.org/releases/11.0R/announce.html
Regards,
Graeme
__
Of course, fpc might skip version 4 altogether. There is precedent.
Winamp skipped version 4 with some lame excuse about not wanting to
market "Winamp 4" skins ;-)
On 13/10/16 10:56, Graeme Geldenhuys wrote:
On 2016-10-13 09:58, Bart wrote:
The danger in that is that he might get so excited
On 2016-10-13 09:58, Bart wrote:
> The danger in that is that he might get so excited by the prospect of
> seeing a 4.0 version of fpc, that he may die of cardiac arrest in the
> process.
Thankfully FPC comes with the following disclaimer. :-p
“
This program is distributed in the hope that i
El 13/10/2016 a las 10:09, Graeme Geldenhuys escribió:
> I would also rewrite that with a try..finally as in:
> ph := TH.Create(nil)
> try
> ph.Initialize;
> ph.ProcessOptions;
> ph.Run;
> finally
> ph.Free;
> end;
May be I'm wrong, but I think that Halt(n) is a nuclear bomb, it closes
the
On 10/13/16, Michael Van Canneyt wrote:
> Call Terminate and exit properly ?
> TCustomApplication has an exitcode property which will set the global exit
> code.
AFAICS not in fpc 3.0.0
(TATCApp = class(TCustomApplication)
procedure TATCApp.OnExcept(Sender: TObject; E: Exception);
begin
writ
On 10/13/16, Graeme Geldenhuys wrote:
> Well, you have the source code. Simply change the version number
> constant and rebuild it. ;-)
The danger in that is that he might get so excited by the prospect of
seeing a 4.0 version of fpc, that he may die of cardiac arrest in the
process.
Bart
_
On 2016-10-12 20:37, grouchysmurf wrote:
> Say, I have a code, where TH is a Class(TCustomApplication):
>
> ph := TH.Create(Nil);
> ph.Initialize;
> ph.ProcessOptions;
> ph.Run;
> ph.Free;
I would also rewrite that with a try..finally as in:
ph := TH.Create(nil)
try
ph.Initialize;
On Wed, 12 Oct 2016, grouchysmurf wrote:
Hi.
Is there a way to pre-maturely halt TCustomApplication without causing
memory leaks?
Say, I have a code, where TH is a Class(TCustomApplication):
ph := TH.Create(Nil);
ph.Initialize;
ph.ProcessOptions;
ph.Run;
ph.Free;
When options are pr
18 matches
Mail list logo
