You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected to see the entire multiline preprocessor condition in the output of the .toString(), rather than just the first line - but when I went to file this bug, I realised this is not specified anywhere as correct behavior (as far as I can see), and so this may be expected behavior. However, if we ignore that maybe-issue, there is still a second issue - the location information appears to be incorrect, stating that the preprocessor condition ends at line 1 column 21, while it actually ends on line 2.
Finally - it may be that the CSV output is malformed, as the terminating quote is prefixed by a backslash.
Hope this is helpful! For your extra context, I found this while scanning the Linux kernel, so it seems this is a common code pattern, as opposed to an infrequently-seen corner case.
The text was updated successfully, but these errors were encountered:
Hi all. I'm seeing some unexpected behavior from CodeQL when I process C preprocessor branches that span multiple lines.
For example, if I scan the following C file:
with the following query:
I see the output:
I expected to see the entire multiline preprocessor condition in the output of the
.toString()
, rather than just the first line - but when I went to file this bug, I realised this is not specified anywhere as correct behavior (as far as I can see), and so this may be expected behavior. However, if we ignore that maybe-issue, there is still a second issue - the location information appears to be incorrect, stating that the preprocessor condition ends at line 1 column 21, while it actually ends on line 2.Finally - it may be that the CSV output is malformed, as the terminating quote is prefixed by a backslash.
Hope this is helpful! For your extra context, I found this while scanning the Linux kernel, so it seems this is a common code pattern, as opposed to an infrequently-seen corner case.
The text was updated successfully, but these errors were encountered: