02:20:32 <antranigv> dtrace: failed to compile script unixso.d: line 1: useless declaration
02:20:40 <antranigv> any idea how can I find the useless declaration?
03:10:19 <sommerfeld> I'd start by looking at the first line of unixso.d
03:12:41 <sommerfeld> Error comes frmo here: https://code.illumos.org/c/illumos-gate/+/3208
03:12:49 <fenix> → CODE REVIEW 3208: 16149 intrd leaks memory (NEW) | https://www.illumos.org/issues/16149
03:13:55 <sommerfeld> oh, oops, not there.
03:13:57 <sommerfeld> try here:
03:14:09 <sommerfeld> https://github.com/illumos/illumos-gate/blob/master/usr/src/lib/libdtrace/common/dt_parser.c#L1437-L1452
03:23:58 <antranigv> sommerfeld I'm stuck at a simpler place now
03:24:06 <antranigv> basically
03:24:07 <antranigv>         sockaddrv = (struct sockaddr_un *)arg2;
03:24:07 <antranigv>         trace(sockaddrv->sun_path);
03:24:24 <antranigv> I cannot get the path. I know I have to use copyinstr
03:24:33 <antranigv> but I'm having a hard time understanding where
04:31:26 <jbk> what are you tracing?
04:32:09 <jbk> userland program? or a kernel function?
06:33:10 <tsoome> -18C. nice.
08:39:35 <antranigv> jbk a userland application
14:20:44 <jbk> then maybe trace(copyinstr(sockaddrv->sun_path))
14:38:11 <jbk> tsoome: sounds like a midwest winter :)
17:38:27 <tomww> n/win 23
21:55:28 <josephholsten> if you were wanting driver code to read to complement reading the STEAMS Programming guide, is there a driver that's conceptually simple I should start with?
21:58:42 <josephholsten> I know I'm totally out of my depth trying to understand how to contribute ath, or port a more recent wifi driver. If there's the equivalent of a wading pool, I should probably start there.
22:02:29 <richlowe> If you're wanting wifi drivers, think about STREAMS as little as you can, look into the gldv3 drivers
22:02:55 <richlowe> I haven't looked at the Sun version, but I wrote a version of atu(4D) for myself years ago, and that's a super simple device to learn how to get yourself into the network stack etc.
22:03:57 <josephholsten> are the virtio drivers worth learning? I was imagining they might be interestingly trivial.
22:04:41 <richlowe> they could be, I didn't think of that, but I haven't looked at them really either.
22:15:05 <josephholsten> so just all of uts/common/io/mac, right?
22:16:54 <josephholsten> oh, _provider first I see
22:20:36 <jbk> they're i think simpler than many drivers since they don't have to worry as much about hw variants, other bits that might be relevant for physical hardware, etc
22:21:09 <jbk> but not sure if that means they're 'simple'
22:30:34 <richlowe> yeah, that was my logic with atu too, it's a very pair of usb pipes, as best as I remember
23:30:55 <jbk> the extent of my experience writing STREAMS drivers is writing a keyboard driver for hyper-v
23:31:00 <jbk> which wasn't tooo bad
23:31:12 <jbk> more of the issues weren't really STREAMS related
23:31:38 <jbk> but more all the undocumented assumptions about what things you have to implement
23:32:00 <jbk> as well as how we deal with keyboards as the console input device
23:32:52 <jbk> where we (almost certainly for legacy, and probably even pre-ACPI legacy reasons) bake in certain assumptions
23:47:18 <jbk> it wouldn't surprise me if we could simplify a lot of that
23:52:50 <josephholsten> anything I should keep my eyes open for? I'm likely to assume complexity is necessary until I have a lot more reading under my belt.
23:58:32 <gitomat> [illumos-gate] 16146 webrev.sh and flg.flp.sh need some style updates -- Bill Sommerfeld <sommerfeld⊙ho>