Jason points out this was gdb writing out a binary form of gdb's psymtabs to be a cheap accelerator table. Anyway, having the data representation of debug information depend on the internal state of either the compiler or debugger is a fragile thing...
Jim > On Jan 26, 2018, at 6:16 PM, Jim Ingham <jing...@apple.com> wrote: > > Note, I think the jury's still out on whether it was a great idea to have the > swift type representation be the swift compiler's internal state. It has > proven more than a little fragile. I'm not sure I would suggest that route. > I vaguely remember back in the day there was a -g flag in gcc that produced a > compiler state dump that gdb was supposed to read. But IIRC that ended up > being more trouble than it was worth. > _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
