cvs commit: src/sys/ddb db_command.c db_output.c

[Robert Watson]

On Mon, 3 Oct 2005, Mark Linimon wrote:

> On Mon, Oct 03, 2005 at 07:03:23PM +0200, Poul-Henning Kamp wrote:
>> There are pro etc con for both methods.  Once a dump has been sitting
>> in a PR for a year, very few people tend to have compatible info
>> tools available.
>
> The counterpoint would be that after a dump has been sitting in a PR for 
> a year, the source base will often have drifted so much that any prior 
> investigative work needs to be re-run.
>
> I'm hardly arguing against either solution here -- anything that we can 
> do to cut out one email round-trip on e.g. the i386/kern PRs can only 
> help us.

After the PR has been sitting there for a year or two, trying to decide if 
it's the same bug can be quite difficult if the submitter didn't know 
which of a dozen DDB commands to type, or know how to try to extract 
kernel debug information using gdb.  I'm not saying this is a substitute 
for a full dump, but that in many situations, I would get more rather than 
less information as a result of what we're talking about.

Robert N M Watson