tatyana-krasnukha (Tatyana Krasnukha)
User

Projects

User does not belong to any projects.

User Details

User Since
Apr 28 2017, 8:23 AM (25 w, 2 d)

Recent Activity

Thu, Oct 12

tatyana-krasnukha updated the diff for D37983: Add instruction subset for the ARC backend.

Corrupted it by merging...

Thu, Oct 12, 9:57 AM
tatyana-krasnukha updated the diff for D37983: Add instruction subset for the ARC backend.

Thanks for comment, Pete!

Thu, Oct 12, 9:22 AM

Fri, Oct 6

tatyana-krasnukha updated the diff for D37983: Add instruction subset for the ARC backend.

Forgot to change decoder method name.

Fri, Oct 6, 9:19 AM

Sep 22 2017

tatyana-krasnukha updated the diff for D37983: Add instruction subset for the ARC backend.

Applied fixes from 2nd comment.

Sep 22 2017, 10:39 AM
tatyana-krasnukha added inline comments to D37983: Add instruction subset for the ARC backend.
Sep 22 2017, 10:37 AM
tatyana-krasnukha updated the diff for D37983: Add instruction subset for the ARC backend.

Added tests, fixed ARCDisassembler.cpp according suggestions.

Sep 22 2017, 10:15 AM

Sep 19 2017

tatyana-krasnukha added a comment to D37983: Add instruction subset for the ARC backend.

Hi Pete, thank you for review!

Sep 19 2017, 6:35 AM

Sep 18 2017

tatyana-krasnukha created D37983: Add instruction subset for the ARC backend.
Sep 18 2017, 10:42 AM
tatyana-krasnukha added a comment to D37934: Fix compatibility with OpenOCD debug stub..

This obvious solution works well for me and seems safe.

Sep 18 2017, 10:22 AM · Restricted Project

Jul 3 2017

tatyana-krasnukha retitled D34942: [PYTHON] Fix crash with "Fatal Python error: Python memory allocator called without holding the GIL" from [PYTHON][Windows] Fix crash with "Fatal Python error: Python memory allocator called without holding the GIL" to [PYTHON] Fix crash with "Fatal Python error: Python memory allocator called without holding the GIL".
Jul 3 2017, 8:40 AM
tatyana-krasnukha updated the summary of D34942: [PYTHON] Fix crash with "Fatal Python error: Python memory allocator called without holding the GIL".
Jul 3 2017, 8:40 AM
tatyana-krasnukha created D34942: [PYTHON] Fix crash with "Fatal Python error: Python memory allocator called without holding the GIL".
Jul 3 2017, 7:34 AM

Jun 30 2017

tatyana-krasnukha added a comment to D4672: For expression evaluation, a new ThreadPlanCallFunctionGDB for executing a function call on target via register manipulation..
Jun 30 2017, 7:37 AM

Jun 27 2017

tatyana-krasnukha added a comment to D34681: [DWARFCallFrameInfo] Add Type enum to differentiate eh/debug_frame sections.

Saying about clear intent, it would be even much more better if class name doesn't start with DWARF ;)

Jun 27 2017, 12:53 PM

Jun 26 2017

tatyana-krasnukha added a comment to D34613: Add debug_frame section support.

Works well for me. Thank you a lot for bringing it up to scratch!

Jun 26 2017, 7:36 AM

Jun 7 2017

tatyana-krasnukha updated the diff for D33504: Fix FDE indexing while scan debug_info section.

Removed non-printable characters from DWARFCallFrameInfo::GetFDEIndex and redundant version checks from UnwindTable::Initialize.

Jun 7 2017, 6:06 AM

Jun 5 2017

tatyana-krasnukha added inline comments to D33504: Fix FDE indexing while scan debug_info section.
Jun 5 2017, 9:59 AM

Jun 2 2017

tatyana-krasnukha updated the diff for D33504: Fix FDE indexing while scan debug_info section.

Added support of DWARF <= 5. For unsupported versions GetUnwindPlan will return false and next behavior should be like without debug_frame at all. Checked it on binaries with v.2 and v.4 on x86-linux target, but have not a chance to run tests for arm-android and other. I'd appreciate it if someone, who has adjusted environment, would check it.

Jun 2 2017, 9:46 AM

May 25 2017

tatyana-krasnukha added a comment to D33504: Fix FDE indexing while scan debug_info section.

Yes, give those binaries, please.

May 25 2017, 6:40 AM

May 24 2017

tatyana-krasnukha created D33504: Fix FDE indexing while scan debug_info section.
May 24 2017, 9:48 AM

May 23 2017

tatyana-krasnukha added a comment to D32366: Set "success" status correctly.

It can make sense to add

assert(eReturnStatusStarted != result);

after cmd_obj->Execute() invocation at CommandInterpreter::HandleCommand, do you think?

May 23 2017, 1:19 PM · Restricted Project
tatyana-krasnukha added a comment to D31275: Fix lldb build on musl.

Looks reasonable, limits.h really is not included by any of these system headers in musl.

May 23 2017, 12:45 PM · Restricted Project