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.

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

Detect stopped due to assert correctly on Windows #22167

Open
llvmbot opened this issue Dec 9, 2014 · 0 comments
Open

Detect stopped due to assert correctly on Windows #22167

llvmbot opened this issue Dec 9, 2014 · 0 comments
Labels
bugzilla Issues migrated from bugzilla lldb

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Dec 9, 2014

Bugzilla Link 21793
Version unspecified
OS Windows NT
Blocks #22140
Reporter LLVM Bugzilla Contributor

Extended Description

Repro command line:

d:\src\llvm\build\ninja>D:\python_src\Python-2.7.8\PCbuild\python_d.exe D:\src\llvm\tools\lldb\test/dotest.py -q --arch=i686 --executable D:/src/llvm/build/ninja/bin/lldb.exe -s D:/src/llvm/build/ninja/lldb-test-traces -u CXXFLAGS -u CFLAGS -C D:\src\llvm\build\ninja\bin\clang.exe -p TestInferiorAssert.py D:\src\llvm\tools\lldb\test\functionalities\inferior-assert

Description:

TestInferiorAssert.py attempts to detect that, after hitting an assert, the reason the inferior stopped was actually due to the assert, and not some other reason. It does this by looking for the string "stop reason = signal SIGABRT" in the backtrace. This is a non-portable string, and we should verify this differently on Windows. One possibility might be to modify StopInfo and create StopInfo::CreateStopInfoForAssertion() or StopInfo::CreateStopInfoForAbort(), then have the test check the stop reason directly, instead of searching the backtrace output for this string.

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from bugzilla lldb
Projects
None yet
Development

No branches or pull requests

1 participant