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
The LINES section in the PDB shows that this function begins on line 36. All other functions so far have "started" on the line with the curly brace (37), and this is what we expect when parsing. The curly brace is always on its own line because we enforce Allman-style indenting via clang-format.
You may ask: What is special about this function that causes MSVC to behave differently? I don't think this is worth pursuing (except for one's own curiosity) because other compilers can do as they please (re: line-to-address reporting) and reccmp has to work with the data it gets.
I think the short term solution is to match any of the lines between the end of the marker comments and the curly brace. This is prone to problems if you edit the file without recompiling (and updating the PDB), but this is already a limitation of the parser.
The text was updated successfully, but these errors were encountered:
See isledecomp/isle#1309. We want to annotate a function like this (line numbers added):
The
LINES
section in the PDB shows that this function begins on line 36. All other functions so far have "started" on the line with the curly brace (37), and this is what we expect when parsing. The curly brace is always on its own line because we enforce Allman-style indenting viaclang-format
.You may ask: What is special about this function that causes MSVC to behave differently? I don't think this is worth pursuing (except for one's own curiosity) because other compilers can do as they please (re: line-to-address reporting) and
reccmp
has to work with the data it gets.I think the short term solution is to match any of the lines between the end of the marker comments and the curly brace. This is prone to problems if you edit the file without recompiling (and updating the PDB), but this is already a limitation of the parser.
The text was updated successfully, but these errors were encountered: