Re: linux native async mode support

[Nick Roberts <nickrob@snap.net.nz>]

 > It's really a timing issue, and that's why I can't reproduce -- it is
 > timing/host sensitive.  So this means this problem isn't related to my
 > patch, but it's a general async issue, that may be visible too in "target
 > async" connected to a gdbserver for example.  Although since we're running
 > over a slower link there, nobody was probably seeing it.  I don't know
 > enough MI to say if this is according to the spec or not, but it feels like
 > a testsuite deficiency, is it not?

I don't think it's a testsuite deficiency but, coincidentally, Vladimir has
just been talking about removing the "(gdb) \n" after ^running.  This may be
a good reason to do it.

The patch below fixes the fails that I was seeing in mi-var-child-f.exp.

-- 
Nick                                           http://www.inet.net.nz/~nickrob



*** inf-loop.c	15 Mar 2008 22:34:07 +1300	1.11
--- inf-loop.c	20 Mar 2008 13:55:12 +1200	
*************** inferior_event_handler (enum inferior_ev
*** 91,98 ****
        was_sync = sync_execution;
        async_enable_stdin ();
  
-       do_all_continuations ();
- 
        if (current_language != expected_language)
  	{
  	  if (language_mode == language_mode_auto)
--- 91,96 ----
*************** inferior_event_handler (enum inferior_ev
*** 101,106 ****
--- 99,106 ----
  	    }
  	}
  
+       do_all_continuations ();
+ 
        /* If the continuation did not start the target again,
  	 prepare for interation with the user.  */
        if (!target_executing)