-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow use of lldb for corral run target #82
Comments
ok, got this working. What I did was added another command ("exec") and all it does is execve() without forking, thus leaving all of the stdin/stdout/stderr in place for lldb to run. Not sure what kind of processing corral needs to after running the command (nothing I assume?). Snippet from the apply() in CmdRun:
|
@cquinn do you have any feedback? |
one more noodle I missed.
By the time it gets to that @execve() mentioned above, the second "--" needed by lldb has been dropped from the args list. Looking as to why... |
for the second (and any more) "--" being ignored corral is not at fault. The answer lies in command_parser.pony, _parse_command()
The above code eats all "--" option stops in the command line. I am unsure of the standard behind "--", but it seems logical to me that it should only swallow the first option stop and then leave the rest of the arguments unaltered.
The above patch works for the issue described here. |
This sounds good to me. |
@cquinn i did not make a PR. Would you like me to (both for the corral change and the ponyc/command_parser change)? |
@KittyMac can you open a PR for these changes? it would be greatly appreciated. |
With stable it was possible for me to debug ponyc while invoking it from the stable env.
With corral this doesn't seem to be possible:
I don't know if there is a work-around I am missing? If not, I will probably dig into fixing this tomorrow as this is a showstopper for me.
The text was updated successfully, but these errors were encountered: