freenode/#clasp - IRC Chatlog
Search
22:12:27
drmeister
They aren't in any predictable order - so if you need a particular order, tell me and I'll set something up.
23:47:22
frgo
drmeister: If I enable line 125 -> https://github.com/dg1sbg/clasp/blob/ext-rti-dds/extensions/rti_dds/src/rti_dds.cc#L125 then I get compile errors. ../../extensions/rti_dds/src/rti_dds.cc:125:9: error: expected ']'
23:47:22
frgo
, class_< dds::core::cond::StatusCondition, dds::core::cond::Condition>>( "StatusCondition", no_default_constructor )
23:52:10
frgo
Sure - in "my" include file: https://github.com/dg1sbg/clasp/blob/ext-rti-dds/extensions/rti_dds/include/rti_dds.h#L49
23:55:43
drmeister
This line has two close angle brackets >> class_< dds::core::cond::StatusCondition, dds::core::cond::Condition>>( "StatusCondition", no_default_constructor )
23:56:01
drmeister
class_< dds::core::cond::StatusCondition, dds::core::cond::Condition>> !!!!!!!!!!! ( "StatusCondition", no_default_constructor )
0:00:17
frgo
Yep, works (of course) - Thanks again. Thank God I don't have to count how many times I already asked for help ...
0:03:20
drmeister
I added an extern "C" declared function HitAllocationNumberThreshold() - it gets called whenever N allocations have been carried out.
0:03:42
drmeister
I'm trying to trigger a probe every time HitAllocationNumberThreshold() is entered.
0:04:36
drmeister
dtrace: invalid probe specifier :HitAllocationNumberThreshold:entry /pid == 18943 && arg1 / { @[ustack()] = count(); } tick-30s { exit(0); }: probe description ::HitAllocationNumberThreshold:entry does not match any probes
0:24:11
drmeister
sudo dtrace -p $PID -x ustackframes=${FRAMES} -n "pid$PID::*HitAllocationNumberThreshold*:entry { @[ustack()] = count(); } tick-$TIME { exit(0); }" -o /tmp/out-$1.user_stacks
0:24:33
drmeister
But it's segfaulting dtrace because iclasp-boehm compiled with thinlto segfaults dtrace
0:54:08
drmeister
This is profiling the interpreter as it builds aclasp - lots of allocations involved in macroexpansion
3:51:27
beach
drmeister: It looked like it was just a stupid mistake in the code for checking the feature expression. I attempted to fix it, but haven't tested it.
3:53:22
beach
So, if you have time, could you please check that you can read the unmodified source with the #+(and close (not clasp)) in it?
3:56:28
beach
I am a bit unhappy with this code-and-fix state of affairs. But I guess it has its explanation in that we don't do this full time, and we are constantly overworked.
4:38:14
drmeister
I had to declare some constants that were being invoked by #. - I did that for about a dozen constants and then gave up - I think it will be fine.,
4:54:31
drmeister
I keep getting errors that look like this: #<SICL-READER:UNKNOWN-CHARACTER-NAME> [Condition of type SICL-READER:UNKNOWN-CHARACTER-NAME]
6:20:57
beach
drmeister: I think I fixed it. It had to do with the feature expression being read while *READ-SUPPRESS* was true.
8:15:27
beach
drmeister: I also fixed another bug in the read-time conditional expression that (apparently) hasn't been visible to you (yet).