03:44:20 <spicywolf> jbk, if you're okay with auto-assignment, the way I've gotten it to work is by using the "ips" field in the config.  It takes an array, and the dynamic options are "dhcp" for ipv4 and "addrconf" for ipv6, but you can drop a static v6 in there too iirc.  I've never tried it though.
13:58:07 <danmcd> fenix illumos#17575
13:58:08 <fenix> FEATURE 17575: Have pstack support "-k" to see kernel thread stacks (New)
13:58:08 <fenix> ↳ https://www.illumos.org/issues/17575
13:58:35 <danmcd> (Am I on crack or is folding the mdb one-liner into pstack(1) a good idea?)
14:14:30 <jbk> it seems useful enough... i think it'd be implied, but maybe good to reiterate the output would be 'not an interface' in case someone later wanted to be ambitious and maybe read /dev/kmem directly and format the output similar to the existing pstack output....
14:14:46 <jbk> vs. spawning mdb
14:17:39 <jbk> i mean, like 99% of the time some process is unkillable or is otherwise stuck in the kernel, that is the first thing I go to
18:44:34 <danmcd> @jbk -> only question I have is should -k only query kernel or should it be an additive to procfs user stack, and we have -K for only query kernel ?  Silly UI design decision...
19:12:06 <jbk> probably one of those things where seeing might help -- this is probably beyond the initial proposal, but as a 'future rainbows and ponies' behavior, showing the stack across the kernel boundary like it was one thing would be pretty neat
20:20:15 <richlowe> having the feature in pstack would be nice, implementing it that way seems off
21:10:28 <jclulow> Yeah I think we should probably implement it as code in pstack.  I feel like a lot of the actual stack walky bits are in some library anyway?
21:13:41 <jclulow> (I do think being able to show both the user and kernel stack as a unifed thing would be neat, also)
21:14:36 <jclulow> Also feels like it would be good if pstack had a flag for the aggregating behaviour of ::stacks haha
21:15:18 <richlowe> that logic is all in findstack, but isn't rough to commonize
21:17:13 <richlowe> the interesting thing is that if your thread is a /proc victim like this, you do already know it's stack
21:17:23 <richlowe> 'cos you stopped it for /proc