This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] gdb: improve usage strings


> From: Mike Frysinger <vapier@gentoo.org>
> Date: Sat, 11 Aug 2012 13:36:40 -0400
> Cc: gdb-patches@sourceware.org
> 
> static void
> finish_command (char *arg, int from_tty) 
> {
>   ...
> 
>   /* Find out whether we must run in the background.  */
>   if (arg != NULL)
>     async_exec = strip_bg_char (&arg);
> 
>   /* If we must run in the background, but the target can't do it,
>      error out.  */
>   if (async_exec && !target_can_async_p ())
>     error (_("Asynchronous execution not supported on this target."));
> 
>   /* If we are not asked to run in the bg, then prepare to run in the
>      foreground, synchronously.  */
>   if (!async_exec && target_can_async_p ())
>     {
>       /* Simulate synchronous execution.  */
>       async_disable_stdin ();
>     }
> 
>   if (arg)
>     error (_("The \"finish\" command does not take any arguments."));
>  ...
> 
> so it seems like finish *does* secretly accept options, but in this case it's 
> trying to be secret about it rather than someone just didn't fully document 
> it.  or i read the "arg" parsing logic above incorrectly.

Isn't that the case of "finish &" ?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]