Obtaining stacktraces

[feral rover]

I was running GDB on a game recently and was getting the '???' trace results that are generally associated with a stripped library in use by the app.

I dual-booted into a different distro and ran without GDB. I was surprised to see not only a stacktrace appear on the terminal when the program died, but the debug symbols were suddenly there as well.

1. What gentoo component am I missing to get the trace on the terminal without using GDB?

2. how would the other distro print debug info when the lib in question appeared to be stripped when running in gentoo?

[true wind]

You'll need to provide more context. What is the game?

[feral rover]

I can’t provide very much detail. It is a testing build of xplane 12. Native linux.

[shell kindle]

Maybe glibc compiled with -O2, disabling lto (which provides the backtrace library)

[feral rover]

I'm already building everything with O2 and have never tried the lto option, so don't think that's creeping in anywhere.

[feral rover]

Thank you for the detailed response. I have a couple questions. That makes the lib and bin folders much bigger in size, correct?

How does that help when the library in question was shipped in the game? Not something I compiled locally without symbols?

[feral rover]

Yeah, the original problem is that I get a good stack trace when I run this game in an ubuntu terminal (without gdb) but only ??? when running with gdb in gentoo. I'm trying to figure out what I'm missing in gentoo build to get this automatic trace that also seems to have good debug info, without using gdb.

[feral rover]

Doesn't look like there's anything in there that would contribute to this.