On 10/6/22 3:39 AM, Bram Moolenaar wrote:
Ernie Rael wrote:
I built ASAN with 9.0.669,
Since I was setup, I did a "make" in testdir. There was one asan problem
and some test failures that didn't seem too troubling:
For an ASAN log to be useful, I need a way to reproduce it. Ideally a
short script. Or, when it is from running tests, which test. I then
still have to binary search for the cause (commenting out parts of the
testa), which can take time.
Is there a way to associate an asan.### file with a particular test? I
tried doing "ls -lt" and occasionally you can see a some_test.res file
interspersed with the asan files. Something like a timestamp (optional?)
column in messages would do the trick. That would narrow things down to
a few tests.
-ernie
On CI there is also a run with ASAN, thus normally things are caught
there.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/fba4c791-d167-a4ca-a355-a7e934cf4ff9%40raelity.com.
