<html>
<head>
<base href="http://llvm.org/bugs/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:dblaikie@gmail.com" title="David Blaikie <dblaikie@gmail.com>"> <span class="fn">David Blaikie</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - default debug level does not play well with libstdc++"
href="http://llvm.org/bugs/show_bug.cgi?id=20741">bug 20741</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>INVALID
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - default debug level does not play well with libstdc++"
href="http://llvm.org/bugs/show_bug.cgi?id=20741#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - default debug level does not play well with libstdc++"
href="http://llvm.org/bugs/show_bug.cgi?id=20741">bug 20741</a>
from <span class="vcard"><a class="email" href="mailto:dblaikie@gmail.com" title="David Blaikie <dblaikie@gmail.com>"> <span class="fn">David Blaikie</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=20741#c3">comment #3</a>)
<span class="quote">> In my opinion it is better to make the setting that provides the expected
> functionality for all users the default and let users concerned about file
> size hunt the manpage for an option to reduce it rather than the other way
> round. </span >
FWIW, GCC has the same default (and the same/similar optimizations (the
std::string one is different - but try hello world in GCC and observe that GCC
produces only a declaration for std::fstream):
DW_TAG_class_type [30] *
DW_AT_name [DW_FORM_strp] ( .debug_str[0x00000283] =
"basic_ostream<char, std::char_traits<char> >")
DW_AT_declaration [DW_FORM_flag_present] (true)
More than just the same default, -g1, -g2, -g3 have no affect on this. The only
way to produce the definition of basic_ostream<char..> from hello world is:
-femit-class-debug-always
Instead of emitting debugging information for a C++ class in only one object
file, emit it in all object files using the class. This option should be used
only with debuggers that are unable to handle the way GCC normally emits
debugging information for classes because using this option increases the size
of debugging information by as much as a factor of two.
<a href="https://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html#Debugging-Options">https://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html#Debugging-Options</a>
Though just because they did it doesn't /necessarily/ mean we should. But
there's no argument from compatibility (except maybe to provide a flag alias)
with -gN flags.
<span class="quote">> -fno-standalone-debug really only works for a project when every
> single C++ library is also compiled with debug info. On platforms where this
> statement is likely to be false (3rd-party libraries, etc), the default
> should be -fstandalone-debug.</span >
3rd party libraries don't necessarily make this statement false - they can/do
provide debug builds of those libraries.
If you don't have debug builds of your libraries it's not hard to get into a
situation where you don't have enough type information (pimpls would be a
common example - the headers just won't have the type information you might
want to inspect the state of the objects you're interacting with).
But, yes, -fstandalone-debug should get you to a point where any expression you
wrote in the source, you can also write successfully in your debugger
expression evaluator, give or take a few things.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>