In gdb, I can get stack traces from inside rust and from upcalls just fine. But when an assertion in LLVM is hit, gdb gets confused a nd just shows me the LLVM funtions on the stack, and then below that bogus addresses labeled with '???'. Doing 'ret' to get out of the LLVM functions doesn't help -- it'll enter the bogus addresses and get lost there.
Patrick mentioned that this works on his Mac set-up. Are other Linux users seeing a similar problem? Has anyone found a workaround? When working on trans, having to do acrobatics with log statements to narrow down the place where an assert is firing is completely fatal for productivity. _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
