Re: [lldb-dev] [cfe-dev] Should we stop supporting building with Visual Studio?

[Csaba Raduly via lldb-dev]

On Sun, Oct 7, 2018 at 10:51 PM Zachary Turner via cfe-dev
 wrote:

> 1) Run CMake twice, generating to separate output directories.  Once using -G 
> "Visual Studio 15 2017" and once using -G Ninja, each to different 
> directories.
>
> 2) Open the VS one.  You have full IDE support.
>
> 3) Instead of hitting Ctrl+Shift+B to build, have a command prompt window 
> open and type ninja.  Wait for it to complete.

If there were errors, eyeball-grep the console output and manually
navigate to the affected file/line. No thanks.

> If you want to you can make a custom tool command in Visual Studio so that 
> you can access this from a keyboard shortcut.
>
> 4) When you want to debug, set your startup project (as you normally would), 
> right click and hit properties, go to Debugging, change Command from 
> $(TargetPath) to  to debug>.
>

Make some changes in the source, hit build, and wonder why the changes
don't appear in the debuggee. (because they got compiled into the VS
dir, not the ninja dir).

Csaba
-- 
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] Should we stop supporting building with Visual Studio?

[Zachary Turner via lldb-dev]

On Tue, Oct 9, 2018 at 12:49 AM Csaba Raduly  wrote:

> On Sun, Oct 7, 2018 at 10:51 PM Zachary Turner via cfe-dev
>  wrote:
>
> > 1) Run CMake twice, generating to separate output directories.  Once
> using -G "Visual Studio 15 2017" and once using -G Ninja, each to different
> directories.
> >
> > 2) Open the VS one.  You have full IDE support.
> >
> > 3) Instead of hitting Ctrl+Shift+B to build, have a command prompt
> window open and type ninja.  Wait for it to complete.
>
> If there were errors, eyeball-grep the console output and manually
> navigate to the affected file/line. No thanks.

I don’t find this to be a problem in practice.  You have to eyeball grep
the output anyway to figure out which  line to double click in the build
output window.  Usually it’s a file you have open in which case you don’t
have to manually navigate to it.  If it’s not then yes you have to manually
open the file, but you don’t have to manually navigate to the line.  You
can hit Ctrl+F7 to compile just that file in VS and then double click.
Since the ninja build is faster anyway though, the whole process doesn’t
actually end up taking that much more time.  Note that if you were to add a
custom tool command to do your build for you and output to the VS console
window, you could still double click lines there and it would be exactly
the same as if you built from inside VS


>
> > If you want to you can make a custom tool command in Visual Studio so
> that you can access this from a keyboard shortcut.
> >
> > 4) When you want to debug, set your startup project (as you normally
> would), right click and hit properties, go to Debugging, change Command
> from $(TargetPath) to  want to debug>.
> >
>
> Make some changes in the source, hit build, and wonder why the changes
> don't appear in the debuggee. (because they got compiled into the VS
> dir, not the ninja dir).


This will never happen.  An incremental build takes about 10-20 seconds,
compared to 5-10 minutes for a full build.  If you hit Build in VS you will
notice because you probably don’t want to sit around for 5-10 minutes.
Moreover, this is just muscle memory which would cause you to accidentally
hit build in VS.  I’ve probably only done this 3-4 times in as many years.

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

Re: [lldb-dev] Proposal for bi-endian code debugging support for lldb.

[Chirag Patel via lldb-dev]

Ping!

Chirag Patel| Software Engineer
RAINCODE Mainframe to .NET
Tel : +91 080 41159811 | Mob : +91 90493 36744
www.raincodelabs.com

From: lldb-dev  On Behalf Of Chirag Patel via 
lldb-dev
Sent: 04 October 2018 11:34
To: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Proposal for bi-endian code debugging support for lldb.

For the moment I am planning to add it for clang typesystem.


Chirag Patel| Software Engineer
RAINCODE Mainframe to .NET
Tel : +91 080 41159811 | Mob : +91 90493 36744
www.raincodelabs.com

From: lldb-dev 
mailto:lldb-dev-boun...@lists.llvm.org>> On 
Behalf Of Chirag Patel via lldb-dev
Sent: 04 October 2018 11:15
To: lldb-dev@lists.llvm.org
Subject: [lldb-dev] Proposal for bi-endian code debugging support for lldb.

Hello,

Kindly correct me if I am wrong.

Now llvm has the interface to set endianity on base_types, I am looking into 
the support for lldb to debug bi-endian code (with attribute DW_AT_endianity).
Currently I am planning to record the endianity/byte-order in CompilerType 
object with context and type(inclue/lldb/Symbol/ConpilerType.h) and pass it 
along to the parent(struct/union) and while reading/wrinting data using 
data-extractor setting the byte order on that.
Any suggestions are welcomed.

Regards,

Chirag Patel| Software Engineer
RAINCODE Mainframe to .NET
Tel : +91 080 41159811 | Mob : +91 90493 36744
www.raincodelabs.com

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

[lldb-dev] [LLDB]{Proposal} Adding new typesystem to support language like PLI/COBOL to lldb

[Chirag Patel via lldb-dev]

Hello all,

I am looking into adding the new typesystem support for languages like 
PLI/COBOL.
Is anybody actively working/looking on this?

Regards,

Chirag Patel| Software Engineer
RAINCODE Mainframe to .NET
Tel : +91 080 41159811 | Mob : +91 90493 36744
www.raincodelabs.com

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

Re: [lldb-dev] [cfe-dev] Should we stop supporting building with Visual Studio?

[Greg Bedwell via lldb-dev]

>
>
> Sadly that's part of the problem.  Very few people actually use the Visual
> Studio generator for building, so a lot of times when we get people with
> issues, nobody knows how to help (or the person that does know doesn't see
> the thread).  So they get a response like "hmm, not many people actually
> use that workflow, can you try this instead?"
>



I do wonder how many of these issues could be alleviated if we had a bot
doing builds with the VS generator.  It would, at least, shift the onus
onto person who broke the workflow to figure it out rather than the next
person to come along and try it.



>> If there were errors, eyeball-grep the console output and manually
>> navigate to the affected file/line. No thanks.
>
> I don’t find this to be a problem in practice.  You have to eyeball grep
> the output anyway to figure out which  line to double click in the build
> output window.  Usually it’s a file you have open in which case you don’t
> have to manually navigate to it.  If it’s not then yes you have to manually
> open the file, but you don’t have to manually navigate to the line.  You
> can hit Ctrl+F7 to compile just that file in VS and then double click.
> Since the ninja build is faster anyway though, the whole process doesn’t
> actually end up taking that much more time.  Note that if you were to add a
> custom tool command to do your build for you and output to the VS console
> window, you could still double click lines there and it would be exactly
> the same as if you built from inside VS
>

As long as errors are in MSVC format, the Error List window (which I
imagine a lot of people use extensively) saves having to actually directly
look at build output most of the time.  I've yet to try to the proposed
workflow to see how much of an issue it really is for me in practice
personally.

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

Re: [lldb-dev] [LLDB]{Proposal} Adding new typesystem to support language like PLI/COBOL to lldb

[Davide Italiano via lldb-dev]

On Tue, Oct 9, 2018 at 3:56 AM Chirag Patel via lldb-dev
 wrote:
>
> Hello all,
>
>
>
> I am looking into adding the new typesystem support for languages like 
> PLI/COBOL.
>
> Is anybody actively working/looking on this?
>
>
>
> Regards,
>
>
Not I'm aware of.

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