Re: [mi] organize possible exec async mi oc command reasons

[Daniel Jacobowitz <drow@false.org>]

On Sat, May 28, 2005 at 10:53:49PM -0400, Bob Rossi wrote:
> The patch below should contain all of the changes. Thank you again for
> all your help. The more I do this, the more reliable my patches should
> become. At least as the GNU coding standard is concerned.
> 
> RCS file: /cvs/src/src/gdb/ChangeLog,v
> +	* Makefile.in (SUBDIR_MI_OBS, SUBDIR_MI_SRCS): Add mi-common.
> +	(gdb/mi/ headers): Add mi_common_h.
> +	(breakpoint.o, infrun.o): Add dependencies mi_common_h.
> +	* breakpoint.c (include): Add include 'mi/mi-common.h'.
> +	(print_it_typical): Use async_reason_lookup.
> +	(watchpoint_check): Ditto.
> +	* infrun.c (include): Add include 'mi/mi-common.h'.
> +	(print_stop_reason): Use async_reason_lookup.
> +	* mi/mi-common.h: New file.
> +	* mi/mi-common.c: Ditto.
> 
> RCS file: /cvs/src/src/gdb/doc/ChangeLog,v
> +	* gdb.texinfo (GDB/MI Out-of-band Records): Add bullet enumerating
> +	the possible reasons why an exec async record would be returned to FE.

These bits all look fine, but the new files are missing.

I really recommend using "cvs add" in your working trees, or cvsdo add
(from the cvsutils package), so that cvs diff -N can include new files. 
My $HOME/.cvsrc has this:

cvs -q
rdiff -u
diff -upN
co -P
update -P
log -N

Some of those options you probably don't want, they're specific to the
way I work - but the line for diff is very, very useful because it
means I rarely forget about new files.


-- 
Daniel Jacobowitz
CodeSourcery, LLC