The strings this test is using seem to consistently fail to match against the expected values when built & run targeting Windows amd64. This PR updates them to the expected values. To fix the test and avoid over-specifying for a specific platform, use `assertIn(<target-substring>,...)` to see if we've got the correct target label instead of comparing the demangler output for an exact string match. --------- Co-authored-by: kendal <kendal@thebrowser.company>
12 lines
213 B
C++
12 lines
213 B
C++
|
|
int foo(int val, int extra) { return val + extra; }
|
|
|
|
int funcA() { return 22; }
|
|
|
|
int funcB() { return 54; }
|
|
|
|
int main(int argc, char const *argv[]) {
|
|
foo(funcA(), funcB()); // set breakpoint here
|
|
return 0;
|
|
}
|