Hello,
If you are targeting Windows, there is a special area in the PE
structure for a DLL that contains addresses that will be jumped to
whenever a thread gets created/destroyed. This has been used by
libtcmalloc from gperftools:
https://github.com/gperftools/gperftools/blob/master/src/windo
The Lazarus team is glad to announce the release of Lazarus 2.0.0.
This release was built with FPC 3.0.4.
The previous release Lazarus 1.8.4 was built with FPC 3.0.4 as well.
Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes
h
On Mon, 2019-02-04 at 15:59 -0700, conlin664 via fpc-pascal wrote:
> THANKS GUYS.
>
> This is now working. The 'fix' was to actually install fpc 3.0.4 on this
> machine.
> My trusty 2.4.4 still compiled just fine what I use it for here at my day
> job.
>
> But it seems 2.4.4 was not really pulling
On 04/02/2019 14:49, Michael Schnell wrote:
Are threadvar variables being freed like regular managed vars
Threadvars are not freed at all. They are like global vars, only that each
running thread automatically has its own copy.
Yes, I know this. (did my google).
Even managed vars are not rele
Marc,
Hmmm. Okay, I just switched it to be stdcall
and had to slightly alter the name, but it compiled and ran.
So my example is now with "cpp" names, so my HelloC is now:
procedure HelloC; stdcall; external name '__Z6HelloCv';
vs
procedure HelloC; cdecl; external name '_Z6HelloCv';
both lin
