No mention of KDevelop? ;__;
I like it because it is the pretty much only FOSS graphical IDE where the edit-compile-debug cycle works. I’m been using it for last 10y for C/C++/Python, and it recently gained LSP support. (ported from Kate)
I mean no harm.
No mention of KDevelop? ;__;
I like it because it is the pretty much only FOSS graphical IDE where the edit-compile-debug cycle works. I’m been using it for last 10y for C/C++/Python, and it recently gained LSP support. (ported from Kate)
I intended this an sarcastic example; I think it’s worse than putting the main outside of the branch because of the extra indent-level. It does have an upside that the main()
doesn’t exist if you try import this as an module.
Btw, ld.so
is a symlink to ld-linux-x86-64.so.2
at least on my system. It is an statically linked executable. The ld.so
is, in simpler words, an interpreter for the ELF format and you can run it:
ld.so --help
Entry point address: 0x1d780
Which seems to be contained in the only executable section segment of ld.so
LOAD 0x0000000000001000 0x0000000000001000 0x0000000000001000
0x0000000000028bb5 0x0000000000028bb5 R E 0x1000
Edit: My understanding of this quite shallow; the above is a segment that in this case contains the entirety of the .text
section.
I would put my code in a def main()
, so that the local names don’t escape into the module scope:
if __name__ == '__main__':
def main():
print('/s')
main()
(I didn’t see this one yet here.)
Holy hell, thats rough. :D
My favorite so far:
$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list
Thread 1 "gdb" received signal SIGABRT, Aborted.
I once wrote bind_front()
and move_only_function
likes in C++17. This nearly drove me mad because you cannot refer to a overload set by a name.
On the otherhand, I can now decipher the template error mess that the (g++) C++ compiler spews out.
what the actual fuck. 🤮
$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list
Thread 1 "gdb" received signal SIGABRT, Aborted.
Yeah, try debug that.
A kernel was released that changed how the hash value got computed for casefolded filenames. (used for better windows compatibility) That kernel then went into production. This unfortunately split some file-systems that supported this into two incompatible versions, breaking the kernel rule 1.
There might now exist file-systems were created/modified with this bug present that the old/fixed kernels can’t understand.
I was reluctant to take this project, knowing well I would end up deleting nearly all existing code I would have to touch, all while having just mediocre skill writing its successor, if it ever becomes one.
I can no longer escape from this project, nor do have I will to.
deleted by creator
The point when the AI hallucinations become useful is the point where I raise my eye brows. This not one of those.
I do this exact same expression when I’m forced to gain knowledge of something potentially personally catastrophic…
Python is just a pile of dicts/hashtables under the hood. Even the basic int
type is actually a dict of method names:
x = 1
print(dir(x))
['__abs__', '__add__', '__and__', '__bool__', '__ceil__', '__class__', '__delattr__', '__dir__', ... ]
PS: I will never get away from the fact that user-space memory addresses are also basically keys into the page table, so it is hashtables all the way down - you cannot escape them.
They could be very well using the earth’s orbit around the sun to get better resolution - two data points from opposite sides of the orbit. What I know is that the largest “virtual” radiotelescope is literally the size of earth. The data points are synced with atomic clocks (or better), and a container of harddrives gets shipped into a datacenter to be ingested. Thats hundreds of streams (one per antenna) of data to be just synced up, before the actual analysis even can begin. (I’m just guessing after this) At this point, you have those hundreds (basically .wav files) lined up at timepoints they were sampled (one sample, one timepoint column). So row by row, so you can begin to sort out signal phase differences between the source rows.
I.e to put it shortly: an image is not taken, it is inferred and computed. Not that you even could in the first place, it’s a blackhole after all.
Jokes on merge… when a rebase editing goes wrong after +15 commits and six hours, and git hits you with a leadpipe: “do it. Do it again, or reassemble your branch from the reflog.” I.e. you commited a change very early, went over bunch of commits resolving/fixing/improving them and at middle way forget if you should commit --amend
or rebase --continue
to move forward. Choose wrong, and two large change-sets get irreversilbly squashed together (that absolutely shouldn’t), with no way to undo. Cheers. 👍
I never finished reading my CMake book that weights about two kilos. It’s now outdated, except for the core concepts.
I didn’t even think what the questionnaire was about, and filled the entire thing. It’s a rare thing to see for a FOSS project to ask what I’m staring at this very moment, how to make it better. But yes, the questionnaire was a bit oddly structured.
I spent solid 10min writing an useful answer and then looked up. Now I want my 10mins back.
hint
Just wipe the screen clear from the goo, dummy.