Parrot 6.6.0 "Parrothead" | parrot.org/ | Log: irclog.perlgeek.de/parrot | #parrotsketch meeting Tuesday 19:30 UTC
Set by moderator on 23 July 2014.
00:18 Psyche^ joined 01:10 FROGGS__ joined 02:54 steven_is_false joined
steven_is_false Hello. I wish to know if src/gc/malloc_trace.c is ever used in production. It has a very, very tiny security weakener and I was wondering if that is something that people should care about? src/gc/malloc_trace.c is only ever used in debug builds right? 02:56
03:04 steven_is_false left
Util stephen_is_false: I believe that it is the original intention, that malloc_trace.c is only ever used in debug builds. 03:16
However, I would like to include your concerns, and the details of the security weakener, in our docs, as a warning to packagers. 03:18
04:26 davidfetter joined 06:12 bighugedog joined 06:19 bighugedog joined 06:21 wagle joined 06:22 bighugedog joined 07:39 FROGGS joined 07:52 basiliscos joined 08:13 bighugedog joined 09:12 bighugedog joined 11:40 kid51 joined 12:29 rurban1 joined
rurban malloc_trace is entirely unused and is documented as such (src/gc/api.c) 12:35
both malloc files are just old upstream versions of standard glibc dlmalloc, not even ptmalloc2/3. they should be removed 12:40
14:45 Chirag joined
Chirag rurban: does, get_pointer, set_integer_native, unshift_integer, find_method, isa, invoke ----- are the only VTABLE methods left to be exported... I am directly calling all the others now. Maybe I can try exporting these as well 15:21
rurban didn't I exported all VTABLE methods already? 15:47
But maybe I left out some, where I found no users. If you find users, remove the static, and convert it sure.
Chirag will do.. do I even push callcontext.c ? 15:48
rurban as long as pmc2c is not changed we need to push the hand-edited sources, yes 15:53
Chirag i ll finish it soon and then change pmc2c if our tests look good 15:54
18:25 basiliscos joined 19:39 rurban1 joined 20:18 basiliscos joined 22:27 kid51 joined