amosnew achievement unlocked: use a syscall valgrind hasn't implemented
I think I need to call the linux kernel hotline, anyone know the number
god I hate reading C code. dude passes `&foo` to a function - is it reading from it? is it writing to it? who knows.
remember to remove binutils from your production systems so the exploits won't run, yeesh
infosec is at that rare skill intersection where the red team writes python code, but in C
whoa, `println!("{:016x}")` writes every 0 with a single write, no buffering involved - presumably to avoid allocations.
maybe that only applies to stderr but... that can't be efficient 🤔
it's called a man page because it won't shut up about stuff you already know and doesn't actually have the answer to your question
systemd-jaded.timer@fasterthanlime i can't recall if you've been in today's lucky 10000 about this one yet, but here's a truly maddening fact: almost no GNU software has a complete man page.
gcc, gdb, and many others have the complete docs as info pages (which can be built to pdf or html, no need to use the mess that is info(1); such things can be acquired from https://www.gnu.org/manual/manual.html or https://docs.jade.fyi)
lj·rk@leftpaddotpy @fasterthanlime Yep, GNU tools are really horrible there. I long for the great SunOS man pages for which @alanc is currently still doing a lot of work. Outside of Solaris systems I mostly use the publicly available POSIX man pages which are *shorter* yet more to the point as they're concise and well-written:
https://pubs.opengroup.org/onlinepubs/9699919799/
Of course they may not document GNU extensions but it works for *most* of what I need just fine.
https://pubs.opengroup.org/onlinepubs/9699919799/
Of course they may not document GNU extensions but it works for *most* of what I need just fine.
@ljrk @fasterthanlime @alanc i personally find man pages to be a seriously outmoded format: they predate "hyperlinks" and hooo boy do you ever need hyperlinks in docs. if you're just looking up function docs it's more ok, but man pages kind of suck. (also no fun to author)
my belief in hypertext led to making docs.jade.fyi
git docs and systemd docs both have canonical online versions that have working hyperlinks but are otherwise identical to their man pages.
Alan Coopersmith@leftpaddotpy @ljrk @fasterthanlime
yeah - back in the 90's the Solaris man pages were converted to DocBook so that they could have hyperlinks, and a "Phase 2" project was promised to provide a man page viewer that could follow links. But Phase 2 never arrived, and the only links included were to other pages (which you can see in the HTML output), but not inter-page links that would be useful.
The man pages ended up as cumbersome reference manuals to search, but not good modern documentation.
@alanc @ljrk @fasterthanlime ah. what I've done to docbook stuff I've had to work with (notably the postgres manual) is to treat it like texinfo: build a single giant page and let the browser deal with it with hyperlinks and search. it mostly works but i want a sidebar. one day i might implement that.
@leftpaddotpy
Yeah, we did similar with Docbook at X.Org, but that was mainly for protocol & API specifications, not general purpose docs. Still, adding lots of internal links seemed to really help there.
Yeah, we did similar with Docbook at X.Org, but that was mainly for protocol & API specifications, not general purpose docs. Still, adding lots of internal links seemed to really help there.