Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[fuzz, binary] Assertion `StartColNo <= EndColNo && "Trying to highlight whitespace??"' failed. #22329

Closed
llvmbot opened this issue Dec 18, 2014 · 3 comments
Closed

[fuzz, binary] Assertion `StartColNo <= EndColNo && "Trying to highlight whitespace??"' failed. #22329

llvmbot opened this issue Dec 18, 2014 · 3 comments
Labels
bugzilla Issues migrated from bugzilla clang:diagnostics New/improved warning or error message in Clang, but not in clang-tidy or static analyzer crash-on-invalid worksforme Resolved as "works for me"

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Dec 18, 2014

Bugzilla Link 21955
Version trunk
OS Linux
Blocks #23431
Attachments test case
Reporter LLVM Bugzilla Contributor

Extended Description

Fuzzing discovered that the attached test case, which contains a null byte, when given as input to

clang -fno-crash-diagnostics -std=c++11 -xc++ -c -emit-llvm

causes this assertion failure:

clang-3.6: tools/clang/lib/Frontend/TextDiagnostic.cpp:969: void highlightRange(const clang::CharSourceRange&, unsigned int, clang::FileID, const {anonymous}::SourceColumnMap&, std::string&, const clang::SourceManager&, const clang::LangOptions&): Assertion `StartColNo <= EndColNo && "Trying to highlight whitespace??"' failed.
@kcc
Copy link
Contributor

kcc commented Nov 26, 2021

mentioned in issue #23431

@kcc kcc mentioned this issue Mar 28, 2015
Open
@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 9, 2021
@AaronBallman AaronBallman added the worksforme Resolved as "works for me" label Jun 12, 2023
@AaronBallman
Copy link
Collaborator

The source has a null character in it immediately before the <C>, which surprised me. However, I cannot reproduce (with or without the null character), so closing as works for me.

@AaronBallman AaronBallman closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2023
@EugeneZelenko EugeneZelenko added clang:diagnostics New/improved warning or error message in Clang, but not in clang-tidy or static analyzer and removed clang Clang issues not falling into any other category labels Jun 12, 2023
@Endilll
Copy link
Contributor

Endilll commented Jun 17, 2023 •
edited

It doesn't reproduce even on assertions builds: https://godbolt.org/z/6coo3rK5q

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla clang:diagnostics New/improved warning or error message in Clang, but not in clang-tidy or static analyzer crash-on-invalid worksforme Resolved as "works for me"
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kcc @AaronBallman @EugeneZelenko @Endilll @llvmbot