Jonathan Adams writes:
> How's this?
That works.
I sort of liked meem's suggestion for resolving ambiguity: if you
really want to specify a type when the type is already known, then
give it a module qualifier with "`". (Where the same type
[unfortunately] appears in multiple modules, I can alrea
Hi Jonathon,
Jonathan Adams wrote:
> On Mon, Mar 09, 2009 at 09:08:51AM +0100, max at bruningsystems.com wrote:
>
>>
>>> ::walk kmem -n kmem_alloc_8192
>>>
>
> My proposed walker doesn't actually have a '-n' argument; it seems redundant
> given the "::walk kmem_alloc_8192" walker.
>
>
On Mon, Mar 09, 2009 at 12:05:37PM -0400, James Carlson wrote:
> Perhaps what's needed is a new summary for ::print -- the command line
> in the documentation (though oddly not the ::help text) says this:
>
> [address] ::print [-aCdiLptx] [-c lim] [-l lim] [type [member|offset ... ]]
>
> ... but
On Mon, Mar 09, 2009 at 08:56:43PM +0100, max at bruningsystems.com wrote:
> Hi Jonathon,
>
> Jonathan Adams wrote:
> >On Mon, Mar 09, 2009 at 09:08:51AM +0100, max at bruningsystems.com wrote:
> >
> >>
> >>>::walk kmem -n kmem_alloc_8192
> >>>
> >
> >My proposed walker doesn't actually ha
On Mon, Mar 09, 2009 at 03:00:23PM -0700, Dan Price wrote:
> On Mon 09 Mar 2009 at 02:35PM, Jonathan Adams wrote:
> > I've gone back and forth on this, and those were the other options I saw.
> > Maybe doing an incompatible change is the right answer:
> >
> > ::walk [-v var] [args]
> >
> > T
On Mon, Mar 09, 2009 at 02:43:27PM -0700, Peter Memishian wrote:
>
> > > I've gone through the materials, and I have one question about the new
> > > behavior for ::print: how does it disambiguate the command line?
> > >
> > > For example, if I do this:
> > >
> > > > ::walk foo | ::print
> > I've gone through the materials, and I have one question about the new
> > behavior for ::print: how does it disambiguate the command line?
> >
> > For example, if I do this:
> >
> >> ::walk foo | ::print bar
> >
> > is "bar" a member of whatever sort of structure the "foo" list
On Mon, Mar 09, 2009 at 01:26:41PM -0700, Dan Price wrote:
> On Mon 09 Mar 2009 at 12:21PM, Jonathan Adams wrote:
> > The main effect of the currently proposed kmem walker is to unify the
> > 6 kmem walkers: "kmem", "bufctl", "free", "freectl", "free_constructed",
> > "freectl_constructed" into a
On Mon, Mar 09, 2009 at 12:05:37PM -0400, James Carlson wrote:
> I've gone through the materials, and I have one question about the new
> behavior for ::print: how does it disambiguate the command line?
>
> For example, if I do this:
>
> > ::walk foo | ::print bar
>
> is "bar" a member of
On Mon, Mar 09, 2009 at 09:08:51AM +0100, max at bruningsystems.com wrote:
> Hi Jonathon,
>
> Jonathan Adams wrote:
> >On Sun, Mar 08, 2009 at 05:37:32PM -0700, Jonathan Adams wrote:
> >
> >>Hi everyone,
> >>
> >>I've been working on a wad started by Eric Schrock a couple years ago to
> >>add ty
Jonathan Adams writes:
> > ::walk thread | ::print kthread_t t_procp
>
> it should be possible to shorten this to:
>
> > ::walk thread | ::print t_procp
This is very cool to see (and it seems like we were just discussing
this somewhere recently ...).
I've gone through the
Hi Jonathon,
Jonathan Adams wrote:
> On Sun, Mar 08, 2009 at 05:37:32PM -0700, Jonathan Adams wrote:
>
>> Hi everyone,
>>
>> I've been working on a wad started by Eric Schrock a couple years ago to
>> add type information to MDB pipelines. It has blossomed into a fairly big
>> modification of
12 matches
Mail list logo
