[cfe-users] Should clang++ -g produce debugging info for all types?

2019-07-25 Thread Bob Eastbrook via cfe-users
On Fedora 30, "clang++ -g main.cc" does not emit debugging information for types such as std::string. I can only get complete debugging information by including "-fno-limit-debug-info". On Ubuntu 19.04, "clang++ -g" emits debugging info for std::string as expected. Which behavior of "-g" is corr

Re: [cfe-users] Should clang++ -g produce debugging info for all types?

2019-07-30 Thread Bob Eastbrook via cfe-users
On Thu, Jul 25, 2019 at 8:35 PM David Blaikie wrote: > No, it shouldn't - clang attempts to avoid emitting duplicate debug info > across the program (it assumes you built the whole program and all libraries > with debug info), gcc assumes the same thing though in slightly > different/fewer way

Re: [cfe-users] Should clang++ -g produce debugging info for all types?

2019-08-09 Thread Bob Eastbrook via cfe-users
On Mon, Aug 5, 2019 at 1:36 PM David Blaikie wrote: > Does it work with gdb? It works with gdb. More info: g++ & gdb -- works, even without debuginfo for libstdc++ clang++ & gdb -- works g++ & lldb -- works clang++ & lldb -- fails I now notice these warnings in lldb after installing the debug