Debug support in fiddle?
還沒有人認領這個 Issue。
評估
研究方向
先從主 README 和 issue 中描述的 Fiddle::Pointer 行為開始，然後將 Fiddle 呼叫可用的偵錯資訊與 Ruby 的 caller 和堆疊追蹤進行比較。確定可執行的結果是改進診斷，還是記錄偵錯指南；完成的標準是明確指定其中一條路徑，並由測試或 README 變更提供支援。
由索引模型根據 Issue 內容生成。
描述
kojix2 provides the fiddle-bindings for libui here:
https://github.com/kojix2/LibUI
Libui is very easy to use; I ported many of my ruby-gtk3 widgets already,
even though libui is quite limited compared to ruby-gtk3. Anyway, in my own
project i modify Fiddle::Pointer to fake-"simulate" OOP.
My biggest problem with fiddle so far is the debug-support. Due to doing
tons of mistakes I get lots of segfaults, and while it is fun to find out why,
in the long run I'd love to be able to more easily and quickly find the error
I did. But when things segfault, I don't seem to get good quality information.
If segfaults happen in ruby, then I often get the exact name, stack tracke
and call stack; and I can use caller(). With fiddle I do not seem to get the
same information or at the least not as much as I think may be useful.
Would it be possible to improve the debug support in fiddle in general?
Perhaps a better stack trace showing where errors happened, a bit
like how ruby does. Or perhaps I just don't know how to debug this,
in which case it would be nice if the main README could provide a
few helpful pointers. Please feel free to close this issue at any moment
in time - I understand that this may not be a trivial change but if anyone
finds some time in the future, keeping better debug-support would be
super-useful. Right now I seem to do random changes and hope for
the best. :D (See also kojix2' comment in regards to having to assign
to variables to avoid the GC terminate the program. Would be nice
if this could all become more transparent when working via ruby.)
- 主要語言
- Ruby
- 星號
- 195
- 分支
- 53
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
ruby/fiddle 的其他 Issue
-
難度 3/5 1-2 天 新手友好度 52/100
-
難度 3/5 1-2 天 新手友好度 68/100
-
難度 5/5 一週以上 新手友好度 30/100
-
難度 2/5 1-3 小時 新手友好度 45/100
-
難度 2/5 1-3 小時 新手友好度 52/100
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 76/100
lugassawan/swe-workbench#799 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
Homebrew/homebrew-core#317477 · 2 則留言 ·
維護者通常 1 天內回覆
-
bug help wanted
難度 2/5 1-3 小時 新手友好度 72/100
hanami/hanami-cli#453 ·
-
area/web interface
難度 2/5 1-3 小時 新手友好度 62/100
mastodon/mastodon#41009 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆