Subject: Re: [PATCH/RFC] *BSD kernel debugging
To: Mark Kettenis <kettenis@chello.nl>
From: Andrew Cagney <cagney@gnu.org>
List: tech-toolchain
Date: 05/17/2004 15:48:59
> +void
> +_initialize_bsd_kvm (void)
> +{
> + bsd_kvm_ops.to_shortname = "kvm";
> + bsd_kvm_ops.to_longname = "Kernel memory interface";
> + bsd_kvm_ops.to_doc = "XXX";
> + bsd_kvm_ops.to_open = bsd_kvm_open;
> + bsd_kvm_ops.to_close = bsd_kvm_close;
> + bsd_kvm_ops.to_fetch_registers = bsd_kvm_fetch_registers;
> + bsd_kvm_ops.to_xfer_memory = bsd_kvm_xfer_memory;
> + bsd_kvm_ops.to_stratum = process_stratum;
> + bsd_kvm_ops.to_has_memory = 1;
> + bsd_kvm_ops.to_has_stack = 1;
> + bsd_kvm_ops.to_has_registers = 1;
> + bsd_kvm_ops.to_magic = OPS_MAGIC;
> +
> + add_target (&bsd_kvm_ops);
> +}
Can the deck chairs be re-arange a little here? Instead of having:
bsd_kvm_supply_pcb
picked up by accident, add an _initialize to the *-nat.c files where
they can do something more explicit vis:
_initialize_foobsd_nat ()
{
add_bsd_kvm_target (foobsd_kvm_supply_pcb);
}
Andrew