Closed Quuxplusone closed 10 years ago
Quuxplusone
commented
10 years ago | Bugzilla Link | PR18785 |
| Status | RESOLVED INVALID |
| Importance | P normal |
| Reported by | amol (amol.deshpande@gazillion.com) |
| Reported on | 2014-02-09 09:55:14 -0800 |
| Last modified on | 2014-02-22 14:55:10 -0800 |
| Version | unspecified |
| Hardware | PC Linux |
| CC | dgregor@apple.com, jonathan.sauer@gmx.de, llvm-bugs@lists.llvm.org, rnk@google.com |
| Fixed by commit(s) | |
| Attachments | |
| Blocks | |
| Blocked by | |
| See also |
Quuxplusone
commented
10 years ago diagnostic log was too big to attach.
Quuxplusone
commented
10 years ago While I understand that you cannot attach the offending source code due to license restrictions, unfortunately without a test case or at least a diagnostic log it's difficult, if not impossible, to determine what went wrong.
Could you compress the log and attach it?
The clang version you are using is very old (3.0, current is 3.4). Would it be possible for you check a newer version to see if the bug has been fixed in the meantime?
Quuxplusone
commented
10 years ago unfortunately, even the compressed diagnostic log was too large. I will see if
I can put it up somewhere and post a link.
This has only happend to me once so far, so I'm not sure upgrading clang will
fix it. I'll investigate that option if it's compatible with the software we're
using.
thanks.After hitting this (or similar) errors 3-4 more times, I upgraded to clang 3.3
(which is what is available with apt-get in my version of Ubuntu, and I did not
want to mess with downloading it myself).
Have not seen the error yet, but I will update this bug if it does happen.
Unfortunately, the code in question is proprietary 3rd party, so I am not sure
I can post it anywhere publicly.
thanks.I haven't seen this bug since I upgraded to clang 3.3. Please feel free to close it out.