User Details
- User Since
- Feb 28 2018, 12:11 PM (257 w, 3 d)
Aug 7 2018
Abandoned since suggested functionality is already done in https://reviews.llvm.org/D49739.
Jun 18 2018
As we discussed previously, it would be nice to have a class in SB API that will manipulate with SBTarget's properties.
I started to work on this and , as I expected, faced with a problem:
TargetProperties class doesn't have a property with image search paths while Target does. It means that we should have a pointer to Target to implement things like
SBTargetSettings::AppendImageSearchPath(const char *from, const char *to, SBError &error).
Jun 11 2018
Jun 9 2018
Removed unnecessary m_lldbResult attribute, updated python test to successfully process new error messages in exec-step command.
Jun 8 2018
Removed unnecessary m_lldbResult attribute.
Jun 7 2018
Updated because of commited -exec-next and -exec-step commands.
Changes for using thread ids in a gdb way. Also added case of specified thread into test case.
Changes for using thread ids in a gdb way. Also added case of specified thread into test case.
Jun 6 2018
I'm a little bit confused about situation with thread id. For example:
(gdb) thread list ~"Process 31642 stopped\n* thread #1: tid = 31642, 0x000000000041eed0 bash`main, name = 'bash', stop reason = breakpoint 1.1\n" ^done
Added some checks for invalid thread id.
Jun 5 2018
Jun 3 2018
Do you know another way of implementing AppendImageSearchPaths method?
Thank you.
Due to https://reviews.llvm.org/D47678 we can enable this test with a XFAIL directive for Windows.
Added the test.
Jun 2 2018
You are right. I think that the reason of exiting *normally is much deeper. I'll look at this, but for now I don't have any idea about what this may be caused by, do you have one?
I would really appreciate if you guys can check this test on Windows again.
A bit of refactoring.
These changes fix the hanging of the lldb-mi lit tests. For example:
-file-exec-and-symbols a.out
-exec-run
commands in test may cause a hanging if a.out is invalid name of binary.
I have got a few ideas about what may cause such a behavior. I'll check them out as soon as possible.
May 26 2018
May 25 2018
May 24 2018
May 23 2018
Removed underscore in the lldb-mi variable from lit.cfg.
May 21 2018
Moved the option parsing code down by the others.
May 19 2018
This version of commit uses the new lldb-mi option that I added to review https://reviews.llvm.org/D47110.
This option is needed by https://reviews.llvm.org/D46588.
May 17 2018
May 16 2018
I have all the patches I was sending. I will follow this topic until you decide what to do with lldb-mi testing.
May 15 2018
Also, I combined FileCheck commands and lldb-mi input in a single file.
Created separate directory for an lldb-mi tests.
May 14 2018
Added more comments about the test.
May 12 2018
Added comments describing which lldb-mi command's output is currently parsing.
Moved tests to lit.
May 10 2018
So, what do you think about the patch? There is no any decision about lldb-mi tests and I do not know what to do with this.
May 9 2018
Added testcase and updated revision.
May 8 2018
Mar 3 2018
Thanks for your time.
Added . to the end of sentences in comments.
Mar 2 2018
As we have current executable file in test, it would be better to use it in search pattern.