Re: [commit] fix for "info threads" printing multiple headers

[Michael Snyder <msnyder@vmware.com>]

Tom Tromey wrote:
>>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:
> 
> Michael> -  if (argc == 1)
> Michael> -    thread = atoi (argv[0]);
> Michael> -
> Michael> -  print_thread_info (uiout, thread, -1);
> Michael> +  print_thread_info (uiout, argv[0], -1);
> 
> Tom> This changes the arguments accepted by the MI command.
> 
> Tom> Maybe it isn't a big deal; but I thought it was at least worth pointing
> Tom> out.  I'm not sure how much argument checking MI does -- by the looks of
> Tom> the pre-patch source, not much.
> 
> Michael> Hmmm?  My intention was to change only what was passed to
> Michael> print_thread_info.  How does it change the syntax of the command?
> 
> The command is documented to accept a thread number, but now it also
> accepts a range.

Oooohhh, I hadn't thought of that.