Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings
Discussion options

suetanvil
Nov 8, 2021

What are the negatives to setting conf.enable_debug in my build_config.rb?

Specifically, if I use an mruby build with debugging enabled but I don't use debugging features (i.e. I've run mrbc without -g), does this impose any efficiency costs?
You must be logged in to vote
Answered by matz Nov 9, 2021

enable_debug cost you:

  • memory for keeping debug information (especially symbols and line numbers)
  • code size (by enabling assertion checks)

But efficiency cost is small.

View full answer

Replies: 1 comment · 1 reply

Comment options

matz
Nov 9, 2021
Maintainer

enable_debug cost you:

  • memory for keeping debug information (especially symbols and line numbers)
  • code size (by enabling assertion checks)

But efficiency cost is small.
You must be logged in to vote
1 reply
@suetanvil
Comment options

suetanvil Nov 9, 2021
Author

Thanks. My use case is creating a binary distribution of the mruby tools. It seems like including mrdb is worth the overhead.
Answer selected by suetanvil
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Q&A
Labels
None yet
2 participants
@suetanvil @matz
Morty Proxy This is a proxified and sanitized view of the page, visit original site.