Replies: 3 comments 6 replies
-
|
As far as I understand, the current
The biggest obstacle is |
Beta Was this translation helpful? Give feedback.
-
|
Hi Matz. Thanks for replying. Is there any appetite from you guys to implement the tracepoint api in debug build? If not I suppose its dead in the water. That would be a shame as it would be a killer feature for mruby. Why would |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
tracepoint is a huge API, so it would take time. |
Beta Was this translation helpful? Give feedback.
-
|
That's not a no. Could be worse 😀 I would love to see it but I know how busy you guys are. |
Beta Was this translation helpful? Give feedback.
-
|
The other challenge is memory. mruby is originally designed for embedding environment. Since tracepoint should be built in the core, it may consume more memory. It may be unacceptable. We'll see. |
Beta Was this translation helpful? Give feedback.
-
|
What if its debug build only and wrapped in config ifdefs? |
Beta Was this translation helpful? Give feedback.
-
|
Is it worth me opening a feature request issue? |
Beta Was this translation helpful? Give feedback.
-
|
We already have |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I've ported my codebase to use mruby, which I'm loving. However, I do badly miss the ruby debug gem running under vscode. I was thinking of making my codebase work with C ruby too just for this purpose but I really don't want to and feels really nasty. I was wondering, in principle, if its possible to port the gem to mruby, and if so how big a task that might be. I'm assuming the vscode extension could stay the same (I hope). I did mention this in the debug gem discussions but its not on their radar.
Thanks :)
Beta Was this translation helpful? Give feedback.
All reactions