<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">That subtraction diagnostic doesn’t generate a stack trace, does it? I don’t see one on Darwin, anyway. Perhaps a platform difference?<div><br></div><div>The top level report_fatal_error() function has a parameter for whether to consider the failure a crasher or not, but doesn’t look like this is going through that path.</div><div><br></div><div>-Jim</div><div><br><div><div>On Jan 30, 2014, at 10:54 AM, Reid Kleckner <<a href="mailto:rnk@google.com">rnk@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">I'd leave the stack trace alone for now. That's what all other MC errors do. If somebody wants to fix that, they can do it later.<div><br></div><div>For the wording, IMO it'd be more consistent to say that this was an "undefined symbol". It's not clear what "couldn't resolve" means, and "undefined" feels more precise. Also, we should mention .secidx.</div>
<div><br></div><div>We have other errors like:</div><div><div> Twine("symbol '") + B->getName() +</div><div> "' can not be undefined in a subtraction expression");</div>
</div><div><br></div><div>So we could do something like:</div><div><span style="font-family:arial,sans-serif;font-size:13px">Cannot get section of undefined symbol 'bar' in .secidx directive</span></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Jan 30, 2014 at 10:46 AM, Timur Iskhodzhanov <span dir="ltr"><<a href="mailto:timurrrr@google.com" target="_blank">timurrrr@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">What's the recommended way to get rid of the stacktrace?<br><br></div>
</blockquote></div><br></div>
</blockquote></div><br></div></body></html>