![]() This changes the way the arguments are handled so it makes sense that it broke the redirection. * (handle_v_run): Just pass empty program argĪs such, since any further processing is now handled viaĬhange-Id: Ibf963fcd51415c948840fb463289516b3479b0c3 To get string representation which properly escapes (win32_process_target::create_inferior): UseĬonstruct_inferior_arguments instead of stringify_argv * (linux_process_target::create_inferior), Now properly handles "hello world" as a single arg, not two separate $ gdbserver localhost:50505 myprogram "hello world" This makes gdbserver properly handle program args containing specialĬharacters (like spaces), e.g. It redirects stdout and stderr using shell-like syntax (>stdout 2>stderr). 'construct_inferior_args' would preserve by adding The clion debugger support seems to rely on google-specific gdbserver behaviour. In 'construct_inferior_arguments' already (and insertingĪ "''" string in 'handle_v_run' would otherwiseĬause that one to be treated as a string literally In gdbserver/ to just insert an empty stringįor an empty arg, since that one is now properly handled (I could not test that case myself, though.)Īdapt handling of empty args in function 'handle_v_run' ("Fix quoting of special characters for the MinGW build.", Proper quoting for Windows shells in commit Since construct_inferior_args has been extended to do Using construct_inferior_arguments seems "natural", since itsĭocumentation also mentions that it "does the Special characters, while stringify_argv does not. To fork_inferior (linux-low, lyn-low), sinceĬonstruct_inferior_arguments properly takes care of Stringify_argv to construct a string from the programĪrguments in those places where that one is then passed ![]() Use the construct_inferior_arguments function instead of Use construct_inferior_arguments which handles special chars
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |