On 2013-11-23 7:22 AM, ISHIKAWA,chiaki wrote:
(2013/11/23 1:41), Ehsan Akhgari wrote:
On 2013-11-21 1:12 PM, ISHIKAWA,chiaki wrote:
(2013/11/22 2:17), Ehsan Akhgari wrote:
FWIW if this proves to be common, it's a huge problem since it would
affect our crash stats etc... :(
Well, if the problem is related to the symptom
that I observed with the use of -gsplit-dwarf option
with ccache, then we may be in for a big surprise.
But in that case, the debug information had a file name that
was produced by the initial CPP invocation (*.i), and despite the
#file, #line information, the invocation of gcc using this intermediate
file as input produced gdb debug information using "*.i" file name, and
thus later gdb could not locate source files at all.
Here we are NOT producing such a strange intermediate file, correct?
Hmm, but I think I see some trouble coming up on the horizon :-(
(A few tweaks to the front end of compilers affected may be necessary.)
Hmm to the best of my knowledge, we don't generate the *.i files unless
if you explicitly request them. Is that what you did in that build?
No, the build　in question is from automated periodic test.
(So I have no control over how it is compiled, etc. It should be using
the standard OSX build toolchain with default setting, etc.)
It's hard to say exactly what's going on here without knowing more about
how this build is produced. It would be really great if you could file
a bug about this with more details on how to reproduce this broken build.
Thanks!
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
