rust - How to debug differences between Cargo's debug and release builds? - Stack Overflow

I'm working with a fairly old (7-8 years) app that relies upon a fairly unmaintained OpenGL wrappe

I'm working with a fairly old (7-8 years) app that relies upon a fairly unmaintained OpenGL wrapper & an associated lib for adding text inside said wrapper (glium & glium_text). I'm currently trying to get the app working again before getting libs updated and/or rewriting it in more maintained tools. I'm struggling to do so however, and this issue can be reproduced using the examples from the glium_text repository.

Using cargo run (cargo run --example hello_world), the app/example works as expected and shows the intended text. However, upon using the --release flag (cargo run --example hello_world --release), the text no longer shows up at all. It disappears entirely, though the app/example does compile just fine and no errors are reported.

I haven't been able to find much in the way of information for why this could be, or how to go about debugging it (much less the actual underlying cause and solution). My understanding was that debug builds just contain debug information but this is a rather big divergence in actual behavior (in that the library as a whole doesn't work).

What do I do here? What are the steps for tracking down the reasons this could occur?

发布者:admin,转转请注明出处:http://www.yc00.com/questions/1743866709a4520689.html

相关推荐

发表回复

评论列表(0条)

  • 暂无评论

联系我们

400-800-8888

在线咨询: QQ交谈

邮件:admin@example.com

工作时间:周一至周五,9:30-18:30,节假日休息

关注微信