freenode/#clasp - IRC Chatlog
Search
12:27:22
Colleen
Bike: drmeister said 7 hours, 1 minute ago: Use clasp/src/profiler/scripts/profile_throw <pid-of-clasp> and then run it to reproduce the error. If there are too many frames with 0x###### hex addresses run it through the symbolicator first. profile_throw will dump a backtrace everytime cxa_throw is invoked.
12:27:22
Colleen
Bike: drmeister said 7 hours, 1 minute ago: The last backtrace is probably the one you want. Or one of the last ones if there is a catch/rethrow in there.
12:28:06
Bike
karlosz: clasp closures have their vector within them directly - there's no indirection - so a "closure" that doesn't close over anything odesn't take up any extra memory for it
12:28:16
Bike
that said, we should reinstate the optimization where closures like that are allocated at load time
12:44:59
Bike
drmeister: tried the script. "dtrace: option requires an argument -- o". do i need more parameters.
14:13:58
Bike
why does boost not give me more information... file, line, the bad format string in question, SOMETHING
16:23:48
karlosz
Bike: also, an easy win is to just not call initialize-closure when the closure-size is zero.
16:41:04
karlosz
well, how segregate lexicals has always done it is to add 1 every time a new input to enclose is processed, that hasn't changed
16:42:40
karlosz
one could make it so that the insert-after-insturction is called only after the first lexical location that needs to be closed over is inserted, so shouldnt be too bad
16:43:35
karlosz
inlining is irrelevant wrt to closure-size, because its run before segregate-lexicals