https://llvm.org/bugs/show_bug.cgi?id=27863
Todd Fiala changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=27864
Bug ID: 27864
Summary: TestTopLevelExprs.py
test_top_level_expressions_gmodules() fails on OS X
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
https://llvm.org/bugs/show_bug.cgi?id=27865
Bug ID: 27865
Summary: DeadStripTest.py test_gmodules() fails on Linux x86_64
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: nor
https://llvm.org/bugs/show_bug.cgi?id=27868
Bug ID: 27868
Summary: Evaluating JITed expressions on arm cannot handle hard
float ABI
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Statu
https://llvm.org/bugs/show_bug.cgi?id=27883
Bug ID: 27883
Summary: TestConstVariables.py fails on arm/aarch64 linux
targets failing frame variable type lookup
Product: lldb
Version: unspecified
Hardware: PC
https://llvm.org/bugs/show_bug.cgi?id=27935
Bug ID: 27935
Summary: Linking CXX executable lldb-argdumper and lldb-mi
fails
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
> On May 31, 2016, at 12:52 AM, Ravitheja Addepally via lldb-dev
> wrote:
>
> Hello,
> I posted this query a while ago, i still have no answers, I am
> currently working on Bug 27687 (PrintStackTraces), so the reason for the
> failure is the erroneous unwinding o
https://llvm.org/bugs/show_bug.cgi?id=27963
Bug ID: 27963
Summary: static variables are not listed with "(lldb) target
variable" when initialized in-place
Product: lldb
Version: 3.8
Hardware: PC
OS: Linux
Saleem Abdulrasool via llvm-dev writes:
> As long as a mechanism for bisecting across the repositories is worked
> out, definitely a +1 from me.
I have some git-subtree changes in the works (and used in production
here) that allows this quite naturally.
Not that I'm necessarily recommending git
Mehdi Amini via llvm-dev writes:
>> Personally, I’m hugely in favor of moving llvm’s source hosting to
>> github at some point, despite the fact that I continue to dislike
>> git as a tool and consider monotonicly increasing version numbers to
>> be hugely beneficial.
>
> Getting a monotonically
Tim Northover via cfe-dev writes:
> On 31 May 2016 at 13:45, Mehdi Amini via lldb-dev
> wrote:
>> Apparently I wasn't very clear: llvm and clang (and the others
>> projects) would be simple decoupled, individual git
>> repositories. You would be able to check the
Richard Smith via llvm-dev writes:
> How would you ensure that two dependent changes on different
> repositories get the same revision number?
>
> That is not the case today and isn't (in my opinion) a problem we need
> to solve with this migration. If there's a small (1-2 revision) windo
Florent Castelli via cfe-dev writes:
> For a linear history, you can have GitHub doing a rebase when merging
> the changes instead of a merge. I would recommend to do that to keep
> the history clean and have less "fixup" or "wip" commits in the
> history.
Non-linear history doesn't casue "fixu
Anton Korobeynikov via llvm-dev writes:
> I'm not sure we will benefit from having *all* the subprojects in the
> single repository. This might affect pull / clone time significantly.
> Think about having lld, lldb along with llvm + clang in the single
> main repo.
I have a personal setup just l
Piotr Padlewski via llvm-dev writes:
> I also find it bad idea to have it all in one repo. Right now when I
> develope clang-tidy, I don't have to recompile clang often because
> most of the commits in clang-estra doesn't require new clang fetures.
> This is pretty nice if work on 2 core machine
Matthias Braun via cfe-dev writes:
> 3. Make sure we have ala llvm-project-submodules setup in the official
> account. (Optional or necessary for the buildbots?)
> 7. Make sure bisecting with llvm-project-submodules is a good experience
I would like to have a fuller discussion about how to hand
Renato Golin via cfe-dev writes:
> * Sub-modules may help with a lot of the current relationship we have
> inside the SVN repo, but it also has some problems. Namely they:
>- require a modern version of git (1.7/1.9), but that's 2013 onward.
>- may need additional server side scripting,
Mehdi Amini via llvm-dev writes:
>> What exactly is the concrete benefit of monotonically increasing
>> revision numbers? It's completely foreign to git's architecture.
>
> I'm notified that bug is fixed in r12345, my binary says "clang -v" is
> r23456, if I observe the bug I know there is a pro
Mehdi Amini via llvm-dev writes:
>> How do you get monotonically increasing number with a history graph?
>
> I think what we're trying to get is a "pushed" revision number,
> i.e. tracking the state of the upstream repositories at a given time.
Ah, that is something else entirely. We use Stash/
via llvm-dev writes:
> Anton Korobeynikov via llvm-dev writes:
>
>> I'm not sure we will benefit from having *all* the subprojects in the
>> single repository. This might affect pull / clone time significantly.
>> Think about having lld, lldb along with llvm + clang in the single
>> main repo.
>
Mehdi Amini via cfe-dev writes:
> My opinion is that submodules or not is an implementation details. For
> the sake of this high-level discussion we should be able to keep it as
> "submodules" meaning "some system to integrate and manage different
> repositories coherently".
> We should evaluate
Mehdi Amini via cfe-dev writes:
>> Fair enough. It might be less confusing to use a term other that
>> "submodule" though. I've used "superproject/subproject" in the past,
>> for example, and also "host repository" and "project repository."
>
> It does not even represent the full set of possibi
https://llvm.org/bugs/show_bug.cgi?id=28016
Bug ID: 28016
Summary: Assertion failed: (false && "Unhandled quote
character")
Product: lldb
Version: 3.6
Hardware: Macintosh
OS: MacOS X
Status: NEW
https://llvm.org/bugs/show_bug.cgi?id=28017
Bug ID: 28017
Summary: error: failed to load objectfile for static-linking
archives?
Product: lldb
Version: 3.6
Hardware: Macintosh
OS: MacOS X
Status:
Chris Lattner writes:
>> On Jun 2, 2016, at 11:42 AM, via lldb-dev wrote:
>>
>> Yeah, I get that and I actually don't mind keeping a linear history.
>> But we definitely should branch for release. Given release branches,
>> there are a number of questions
https://llvm.org/bugs/show_bug.cgi?id=28019
Bug ID: 28019
Summary: Possibly insecure use of TCP sockets by LLDB
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=28026
Bug ID: 28026
Summary: LLDB-MI doesn't properly output CLI command response
using console-stream-output
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
ble the optimizer, and turn on all debugging. This means building your own version of GDB and/or LLVM -Duane.
Original Message ----
Subject: [lldb-dev] Structure variable names
From: Jiten Thakkar via lldb-dev <lldb-dev@lists.llvm.org>
Date: Tue, June 07, 2016 9:56 am
To: lldb-
https://llvm.org/bugs/show_bug.cgi?id=28041
Bug ID: 28041
Summary: Tab completion adds backslashes to function names,
which causes them not to match
Product: lldb
Version: 3.6
Hardware: Macintosh
OS: MacOS X
https://llvm.org/bugs/show_bug.cgi?id=27652
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=22252
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=17237
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=15989
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=24976
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=15039
lab...@google.com changed:
What|Removed |Added
Status|REOPENED|RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=18093
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=16582
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=26439
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=16172
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=16808
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=20406
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=23322
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=28055
Bug ID: 28055
Summary: continue in watchpoint commands disables the
watchpoint
Product: lldb
Version: unspecified
Hardware: All
OS: All
Status: NEW
https://llvm.org/bugs/show_bug.cgi?id=26139
lab...@google.com changed:
What|Removed |Added
CC||lab...@google.com
Assignee|lldb-de
https://llvm.org/bugs/show_bug.cgi?id=27510
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=28091
Bug ID: 28091
Summary: Build docs shouldn
Product: lldb
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P
https://llvm.org/bugs/show_bug.cgi?id=28092
Bug ID: 28092
Summary: Build docs shouldn't use relative paths
Product: lldb
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
https://llvm.org/bugs/show_bug.cgi?id=28092
Manish Goregaokar changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|lldb-dev@lists.
https://llvm.org/bugs/show_bug.cgi?id=28091
Eugene Zelenko changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=28127
Bug ID: 28127
Summary: lldb-server broken when LLVM_LINK_LLVM_DYLIB=ON
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=28156
Bug ID: 28156
Summary: TestWithModuleDebugging.py: failing on macOS
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=28156
Todd Fiala changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |apra...@apple.com
--- Comment #1 from Todd Fiala
https://llvm.org/bugs/show_bug.cgi?id=27416
Marius Trandafir changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|marius.tranda...@live
https://llvm.org/bugs/show_bug.cgi?id=28178
Bug ID: 28178
Summary: lldb segfault when debugging mysql in certain
functions
Product: lldb
Version: 3.8
Hardware: PC
OS: Linux
Status: NEW
https://llvm.org/bugs/show_bug.cgi?id=28253
Bug ID: 28253
Summary: lldb-mi Regression with LLDB_DISABLE_PYTHON=1
Product: lldb
Version: 3.8
Hardware: Macintosh
OS: MacOS X
Status: NEW
Severity: normal
Dear all
you know, in windbg there is a very useful command -- locks . it will tell
us who owned the special lock. in lldb, there is no such command. sometimes,
we have a deadlock. but we cannot find the mutex, whitch thread owned it , and
do not release!!
Thank you very much!
Dear all
you know, in windbg there is a very useful command -- locks . it will tell
us who owned the special lock. in lldb, there is no such command. sometimes,
we have a deadlock. but we cannot find the mutex, whitch thread owned it , and
do not release!!
Thank you very much!
https://llvm.org/bugs/show_bug.cgi?id=28293
Bug ID: 28293
Summary: LLDB can't find split debug info if the debuggee has
been moved form build directory
Product: lldb
Version: unspecified
Hardware: PC
OS: Lin
https://llvm.org/bugs/show_bug.cgi?id=28127
Sylvestre Ledru changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=28127
Sylvestre Ledru changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|DUPLICATE
https://llvm.org/bugs/show_bug.cgi?id=28353
Bug ID: 28353
Summary: TestTopLevelExprs.py fails with gcc-4.8
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
P
https://llvm.org/bugs/show_bug.cgi?id=28354
Bug ID: 28354
Summary: TestTemplateIntegerArgs.py fails with gcc
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=28354
lab...@google.com changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |clayb...@gmail.com
--- Comment #3 from lab..
https://llvm.org/bugs/show_bug.cgi?id=28392
Bug ID: 28392
Summary: Thread local variables are not working on Linux
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Hi All,
I am trying to simple "Hello World" program remotely on a MAC OS using
eclipse and lldb-mi. I followed the instructions available here: "
https://www.codeplay.com/portal/lldb-mi-driver---part-2-setting-up-the-driver";.
I am facing below issue. Any suggestions would be of great help.
It is
https://llvm.org/bugs/show_bug.cgi?id=28428
Bug ID: 28428
Summary: lldb.SBProcess.is_running and
lldb.SBProcess.is_stopped Python accessors
Product: lldb
Version: 3.8
Hardware: PC
OS: Windows NT
https://llvm.org/bugs/show_bug.cgi?id=28428
Greg Clayton changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=28455
Bug ID: 28455
Summary: Thread state not in sync with process state
Product: lldb
Version: 3.8
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=28455
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
6384"
314,273
=library-loaded,id="/usr/lib/system/libsystem_secinit.dylib",target-name="/usr/lib/system/li\
314,274 16-list-thread-groups --available
bsystem_secinit.dylib",host-name="/usr/lib/system/libsystem_secinit.dylib",symbols-loaded="0",loaded\
Thanks Greg. Attached is the file after sampling lldb-mi. Please let me
know if you can find some clue from it.
--
Have a nice day!
Regards,
Dipti
On Fri, Jul 8, 2016 at 5:49 AM, Greg Clayton wrote:
> It looks like we continue and then ask fore thread groups? I am not sure
> on the rules of M
Thanks Greg. But is it possible that for eclipse support some new wrapper
command is added ? [
https://www.codeplay.com/portal/lldb-mi-driver---part-4-how-to-add-a-command]
Not sure, just a thought. I am googling to see more details but not much
luck yet.
Attached is lldb-mi sample. Please let me
; --
>> Have a nice day!
>> Regards,
>> Dipti
>>
>>
>> On Mon, Jul 11, 2016 at 2:01 AM, Ilia K wrote:
>>
>>> Good point Greg! Eclipse turns on synchronous mode in lldb-mi but works
>>> as if it's in async. I faced with that prob
https://llvm.org/bugs/show_bug.cgi?id=26790
Luke Drummond changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=28548
Bug ID: 28548
Summary: NamespaceBreakpointTestCase fails with gcc
Product: lldb
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=19247
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=28549
Bug ID: 28549
Summary: TestStepNoDebug.py fails with gcc and top-of-tree
clang (3.9)
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status:
https://llvm.org/bugs/show_bug.cgi?id=28178
Jeff Davis changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://llvm.org/bugs/show_bug.cgi?id=24388
Bhushan Attarde changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=27634
ema...@freebsd.org changed:
What|Removed |Added
CC||ema...@freebsd.org
Assignee|lldb-
https://llvm.org/bugs/show_bug.cgi?id=28621
Bug ID: 28621
Summary: lldb-mi can't get variables of a frame (-stack-list-*
MI-commands) if the thread didn't cause the stop event
Product: lldb
Version: 3.9
Hardware: Macintosh
https://llvm.org/bugs/show_bug.cgi?id=28698
Bug ID: 28698
Summary: [lldb-mi] -break-insert with -f (pending flag)
requires additional parameter
Product: lldb
Version: 3.8
Hardware: Macintosh
OS: MacOS X
https://llvm.org/bugs/show_bug.cgi?id=28702
Bug ID: 28702
Summary: LLDB-MI: pending break point set with command
break-insert -f doesn't get resolved
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
https://llvm.org/bugs/show_bug.cgi?id=28703
Bug ID: 28703
Summary: LLDB-MI: break-insert command flag -d (disabled) has
no effect when combined with -f (pending)
Product: lldb
Version: unspecified
Hardware: PC
https://llvm.org/bugs/show_bug.cgi?id=28709
Bug ID: 28709
Summary: lldb-mi: break-insert not working when using absolute
paths
Product: lldb
Version: unspecified
Hardware: All
OS: All
Status: NEW
https://llvm.org/bugs/show_bug.cgi?id=28718
Bug ID: 28718
Summary: LLDB-MI: disassembly-flavor not supported by gdb-set
and gdb-show
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Stat
https://llvm.org/bugs/show_bug.cgi?id=28728
Bug ID: 28728
Summary: lldb python failed to enable watchpoint
Product: lldb
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Pr
https://llvm.org/bugs/show_bug.cgi?id=28729
Bug ID: 28729
Summary: lldb python failed to get watchpoint type
Product: lldb
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=28729
Greg Clayton changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=28728
Greg Clayton changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=28742
Bug ID: 28742
Summary: Make Process::StopForDestroyOrDetach handle
interrupting RunThreadPlan more robustly
Product: lldb
Version: unspecified
Hardware: PC
OS: All
https://llvm.org/bugs/show_bug.cgi?id=28709
Ilia changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=26947
dvlahov...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://llvm.org/bugs/show_bug.cgi?id=28826
Bug ID: 28826
Summary: "frame variable", "source list", etc. fail to produce
the expected output
Product: lldb
Version: 3.9
Hardware: All
OS: Linux
Sta
https://llvm.org/bugs/show_bug.cgi?id=28857
Bug ID: 28857
Summary: LLDB-MI: break-enable doesn't enable specified
breakpoints
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
https://llvm.org/bugs/show_bug.cgi?id=28858
Bug ID: 28858
Summary: LLDB-MI: no notification about process stopped if
attaching to a process
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
https://llvm.org/bugs/show_bug.cgi?id=28859
Bug ID: 28859
Summary: LLDB-MI: data-disassemble command doesn't accept "$pc"
as start and end address parameter
Product: lldb
Version: unspecified
Hardware: PC
OS
https://llvm.org/bugs/show_bug.cgi?id=28860
Bug ID: 28860
Summary: LLDB-MI: no breakpoint-modified notification when a
breakpoint is hit
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
https://llvm.org/bugs/show_bug.cgi?id=28898
Bug ID: 28898
Summary: LLDB_EDITLINE_USE_WCHAR should be enabled on Arch.
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
https://llvm.org/bugs/show_bug.cgi?id=28900
Bug ID: 28900
Summary: "ERROR: ld.so: object 'libfakeroot-sysv.so' from
LD_PRELOAD cannot be preloaded" in manpage
Product: lldb
Version: 3.8
Hardware: PC
OS:
201 - 300 of 9283 matches
Mail list logo
