[lldb-dev] [Bug 45011] New: lldb can swallow some of the output when doing `p SM.dump(SourceLoc)`, or similar

[via lldb-dev]

https://bugs.llvm.org/show_bug.cgi?id=45011

Bug ID: 45011
   Summary: lldb can swallow some of the output when doing `p
SM.dump(SourceLoc)`, or similar
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: v...@apple.com
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org

While debugging clang or llvm and calling 'dump' on various objects, lldb
sometimes swallows part of the output. E.g.:

```
(lldb) p BV.dump()
(lldb)1]}
```

or

```
(lldb) p SM.dump(SourceLoc)
(lldb)ile.cpp:30:10
```

Why does that happen? These dump methods are writing to dbgs(), which should
just be stderr.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] Odd behavior with Python on Windows (loading 2 copies of liblldb.dll/_lldb.pyd)

[Pavel Labath via lldb-dev]

On 21/02/2020 23:32, Ted Woodward via lldb-dev wrote:
> Looking into differences, I’m using swig 3.0.12 and the bot is using
> swig 3.0.2. I’m building with 3.0.2 on my machine right now, but it will
> take a while to finish!

I think this could very likely be the cause. We use a different
mechanism
()
for importing the lldb module starting with swig-3.0.11. This could very
well be one of the side effects.

pl
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev