06:27:19 ya, fortunately fusion has gdb stub and we can inspect the machine:) 15:14:19 [illumos-gate] 16820 Ignore library/libxml2/32 during package lint -- Marcel Telka 15:58:56 ho 16:59:14 [illumos-gate] 16670 libshare: issubdir() error: strcpy() 'dir1' too large for 'childdir' -- Toomas Soome 18:46:40 tsoome_: if you're using source debugging that way, have you seen arm64-gate's .gdbinit? 18:47:13 it's not perfect (we don't have a way to find the .bss again for it, and it doesn't care about alignment), but it works like, many times out of 10 18:47:29 unfortunately, the one time it doesn't will really confuse you :\ 18:49:44 anyway, that's what I did before I ported kmdb, and now I often use both at the same time (because I ported kmdb and don't trust it fully yet) 19:39:57 I usually do not use source debugging with gdb stub, I have done this just few times:) but it is good to know, thanks 19:57:28 tsoome_: you're gonna hate and/or love https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3356.htm 20:06:34 well, as it correctly stated, if we can declare variable in for statement, then why stop there -- it does make sense 20:10:46 I was just remembering how you dislike if ((foo = bar()) == NULL) 20:11:04 which isn't that different from if (foo = bar; foo != NULL) 20:11:17 which seems allowed here regardless of whether the LHS is a declaration 20:11:41 when I say "isn't that different", you're meant to ignore I reversed the condition like an absolute crumpet 20:12:18 well, I still dislike excessive use of assignment statement in if:D but if you add variable declaration to it, that is different;) 20:24:06 I could grow to like that. I'm always trying to scope things down as tightly as possible. 20:32:00 My preference for assignment in if is definitely at odds with my preference for scope minimisation in C haha 20:32:06 Hard to reconcile sometimes 20:38:31 I just dont like _statements_, really. 21:23:49 I certainly like (declaration; value check) better than combining them into a single ((foo = bar()) == NULL) style combo value-setting+check