Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2018-07

Re: Why/how does the compiler have anon-trivialnumberofmemory leaks after over two decades of development?

2 messages · 2 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

J. Gareth Moreton

Apologies if these things seem trivial. I probably need to read the documentation cover to cover to learn about these global state variables.

I am a bit surprised that hitting out of memory exceptions causes incorrect error messages to appear though.

Gareth aka. Kit

On Mon 30/07/18 22:10 , Sven Barth via fpc-devel
sent:
Am 30.07.2018 um 19:49 schrieb J. Gareth Moreton:
The trouble is, these allocation failures are designed for C programs, where "malloc" returns NULL if memory isn't allocated.  Free Pascal's GetMem raises an exception instead.  Granted, it shouldn't be too much of a struggle to implement a custom memory manager for testing and to cause random (or deterministic) allocation failures to see how cleanly the situation is handled.  It could be a fun test suite! The default heap of FPC's RTL respects the value of ReturnNilIfGrowHeapFails (which by default is False).

Regards,
Sven

Reply by email

Sven Barth
to J. Gareth Moreton

J. Gareth Moreton schrieb am Mo., 30. Juli
2018, 23:20:

Show quoted text 6 lines
Apologies if these things seem trivial. I probably need to read the documentation cover to cover to learn about these global state variables. I am a bit surprised that hitting out of memory exceptions causes incorrect error messages to appear though.

Well, going out of memory is a bit of a nasty situation and normally not really checked for anyway.

Regards,
Sven

Reply by email