[PATCH]: Clean-up of procfs debug trace.
Fri May 5 14:23:00 GMT 2000
Date: Fri, 5 May 2000 13:55:47 -0700 (PDT)
This cleans up a little private debugging API that I use for
working with /proc, and adds a little more diagnostics.
All of the ugliness is now hidden in proc-api.c and
I was wondering who was adding those block comments with *'s in front
of them. Looks like I caught you red-handed :-)
>From the GDB Internals Manual:
The standard GNU requirements on comments must be followed strictly.
Block comments must appear in the following form, with no `/*'- or
'*/'-only lines, and no leading `*':
/* Wait for control to return from inferior to debugger. If inferior
gets a signal, we may decide to start it up again instead of
returning. That is why there is a loop in this function. When
this function actually returns it means the inferior should be left
stopped and GDB should read more commands. */
So if you can break the habit ...
More information about the Gdb-patches