[Lldb-commits] [PATCH] D17724: Replace getopt with llvm::cl in lldb driver

[Zachary Turner via lldb-commits]

long and short options are supported, but the one I'm not sure about is the
case where you use a short option with no space.  Your example "-ax86_64"
might not work.  It might, just that it should be tested.  I'm 99%
confident the rest of them all work.

Also not sure about this example: "% lldb /bin/ls --arch=x86_64 -- -lAF"

If I understand correctly, this runs LLDB with the --arch=x86_64 argument,
and specifies the program to debug as "/bin/ls -IAF"?

Seems like a confusing syntax to me, is there any other way to specify this
currently?  like:

% lldb "/bin/ls -IAF" --arch=x86_64
% lldb /bin/ls --arch-x86_64 --args=-IAF

Or something along those lines?

On Mon, Feb 29, 2016 at 10:46 AM Greg Clayton <clayborg at gmail.com> wrote:

> clayborg added a comment.
>
> As long as both long and short options are still supported? Can you still
> type any of:
>
> - --arch=x86_64
> - --arch x86_64
> - -arch=x86_64
> - -arch x86_64
> - -ax86_64
> - -a x86_64
>
> Are we able to track which options can be used with other options with the
> llvm solution? I didn't look too close. There were bits in the old option
> definitions which defined with options could be specified with which other
> options. The other thing that might throw people for a loop is if llvm
> doesn't support this style:
>
> % lldb /bin/ls --arch=x86_64 -- -lAF
>
> getopt_long allowed you to have arguments mixed in between the options so
> the arguments would have bee "/bin/ls" and "-lAF". Options would have been
> "--arch=x86_64".
>
>
> http://reviews.llvm.org/D17724
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20160229/af3a467e/attachment-0001.html>