Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40944 - [gc] build with --enable-redirect-malloc

Attached to Project: Arch Linux
Opened by Alexandre Kandalintsev (exe2) - Monday, 23 June 2014, 10:39 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 11 February 2015, 18:22 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

It is useful to build extra/gc with --enable-redirect-malloc
Without this it is impossible to write wrappers of malloc/free/etc functions
and call GC_* inside them.

What do you think?
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 11 February 2015, 18:22 GMT
Reason for closing:  Won't implement
Comment by Daniel Micay (thestinger) - Thursday, 10 July 2014, 15:31 GMT
I don't think this should be enabled. You *can* change the behaviour of the malloc family of functions by overriding the weak symbols and/or setting the glibc malloc hooks. It should be up to the program to do this if and only if it wants to do it.
Comment by Jan de Groot (JGC) - Friday, 23 January 2015, 11:55 GMT
From documentation:
You may be able to build the collector with --enable-redirect-malloc and set the LD_PRELOAD environment variable to point to the resulting library, thus replacing the standard malloc with its garbage-collected counterpart. This is rather platform dependent. See the leak detection documentation for some more details.

I don't see why our packaged version should have this. I don't know if this will affect running code in any way and so far no other distributions enable this.
Comment by Alexandre Kandalintsev (exe2) - Monday, 26 January 2015, 13:19 GMT
Thanks, Jan. I think we can close the bug.

Loading...