Re: [lldb-dev] lldb versus visual studio

2021-03-25 Thread Zdenek Prikryl via lldb-dev 
LLVM-MI, that can be used in Eclipse, lives here [1] and it is still in 
use. Although more people working on it would be definitely better 
situation that it is at the moment :-)...


[1] https://github.com/lldb-tools/lldb-mi

*Zdenek Prikryl* | /CTO/ | +420 541 141 475 | www.codasip.com 




On 3/22/21 10:31 PM, Franz Fehringer via lldb-dev wrote:

Thx again


Am 22.03.2021 um 21:55 schrieb Ted Woodward:

There was. Almost nobody used it. Nobody maintained it.


-Original Message-
From: lldb-dev  On Behalf Of Franz
Fehringer via lldb-dev
Sent: Monday, March 22, 2021 2:28 PM
To: lldb-dev@lists.llvm.org
Subject: [EXT] Re: [lldb-dev] lldb versus visual studio

Thank you very much, this essentially meets my expectations (no eclipse
debugging with Windows/VC++), i am a little surprised that there is no
working lldb integration for eclipse, is this really the whole truth 
(or did i

misunderstand)?


Am 22.03.2021 um 19:28 schrieb Greg Clayton:

On Mar 20, 2021, at 8:57 AM, Franz Fehringer via lldb-dev 
d...@lists.llvm.org> wrote:

Dear lldb-dev community,

First a disclaimer: If my question is inappropriate for this 
(developer) list
please ignore or guide me to a more appropriate list (it is possibly 
more of an

end user question).

Is it possible to debug Visual Studio generated (with pdb debug info)

executables (2017 or 2019, C++ only)  with lldb?

LLDB does have PDB parsing abilities, though I am unsure how well they
work out of the box with no extra configuration. There are two PDB 
parsers
in LLDB at the moment, one that uses a DLL from Visual Studio that 
knows
how to parse a PDB file, and one that tries to parse the PDB file 
manually. So
if you are natively on windows, I believe you might need to set run 
the batch
file that sets up environment variables for finding these DLLs. The 
native PDB
parser should work, but I am not sure if the native version always 
takes

precedence when running on the Windows OS.

Maybe someone that did the PDB integration could chime in?


And if so is there a full integration into eclipse so i can debug 
Visual Studio

generated executable with eclipse?
The only integration that I am aware of was one that used lldb-mi, 
or the
GDB remote machine interface. But the lldb-mi was dropped from the 
top of

tree LLDB a while ago because it was not tested and was bit rotting.

We do have a lldb-vscode binary that implements the Microsoft Visual
Studio Code DAP (Debug Adaptor Protocol). If there are any Eclipse 
plug-ins
that integrated with the VS Code DAP plug-ins, that would be the 
option I
would suggest looking into. Is using Visual Studio Code an option, 
or only

Eclipse?

The platform in question is Microsoft Windows 10 (recent versions).

Thx in advance

Franz

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

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


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

[lldb-dev] Bugzilla / GitHub migration: username request

2021-03-25 Thread Anton Korobeynikov via lldb-dev 
Dear All,

As you might know, LLVM Foundation is working on migrating the data
that is currently residing in Bugzilla at http://bugs.llvm.org into
LLVM GitHub project repository. The ultimate goal is to shut down the
Bugzilla instance and allow the use of GitHub issues and pull requests
across LLVM repositories. We hope that this will lower the bar for
newer contributors and allow much smoother user experience than we're
having now.

Unfortunately, this is not an easy task and several valid (legal)
concerns with respect to the procedure, process and content were
raised in the past. The LLVM Foundation together with lawyers is
working on resolving them and now it's time for the next step of this
migration: the username mapping. Bugzilla uses email addresses as
usernames and GitHub operates solely via github usernames. There is no
way to associate an email with github username in automatic way, so we
are asking you to fill in the survey above:

https://forms.gle/tNg86K6T7y2YfsBx9

I would appreciate if this from will be filled by April, 30

Q&A:

Q: How will this data be used?
A: This email - username mapping will be used by the LLVM Foundation
solely for the purposes of the Bugzilla migration process and will be
deleted as soon as migration will finish.

Q: What will happen if I will not provide email - username mapping?
A: All data produced by unidentified users will be anonymized during
the migration, so there will be no way to attribute data to a
particular github username

Q: What if I cannot use the form above for some reason?
A: Please email LLVM Foundation Board your bugzilla username (email)
and your github username. By receiving this data it will be assumed
that you will be giving permission to the LLVM Foundation to migrate
all the data created by you in LLVM Bugzilla database under the
account(s) you sent to the Github issues in the LLVM project
repository.

Thanks,

On behalf of the LLVM Foundation,
Anton Korobeynikov
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev