daily bread allegations
| pronouns | she/her |
| main project | https://mermaid.industries |
| on bsky | https://bsky.app/profile/dryad.technology |
| avatar by | Dana |
@mcc
- 34.8K Followers
- 607 Following
- 81.9K Posts
glitch girl
To be clear one thing creating difficulty here is the process has both the .NET standard library and *the entirety of Chrome* loaded into it, which means the output of such things as ldd, LD_DEBUG, etc is… noisy. Enough it's hard for me to tell which of the signals I ought to be paying attention to.
How do I tell, in the LD_DEBUG=libs output, which error is the one that caused the dll to "not load"? I'm seeing "symbol lookup error"s as diverse as DLLMain (not so surprising, dotnet is in the mix), u_strlen in libicuuc, "_Z7ssgInitv", and seemingly every single symbol in seemingly every X11 library (libX11.so, libXext.so, libXcursor.so, etc). It's *very likely* libVendorTrash.so assumes I'm on some specific Linux distro, "Vendor" considers Linux a 4th-class platform. But DLLMain surprises me.
It's sinking in, at this moment, that I don't "know" how to use LD_DEBUG. I've often *used* it before, but always I just randomly run LD_DEBUG=libs or LD_DEBUG=all and sorta just click around the output until I see an Obvious Error and then I fix an Obvious Error and it's fixed. At this moment I'm not seeing an Obvious Error and I'm realizing I need to actually learn to use the tool.
Running with LD_DEBUG=libs results in 1,114 lines of diagnostic output. 408 of these contain the word "error".
Okay. May I ask for help here?
Imagine this happens. I am writing a program for Linux. At runtime, it dynamically loads libMyTrash.so. ld fails, announcing "I can't find libMyTrash.so!". libMyTrash.so is on the disk. I conclude: libMyTrash.so is loading libVendorTrash.so, and libVendorTrash is probably linked against the wrong libc for the Linux I'm running, or against some .so I don't have. I need to use LD_DEBUG to get it to print the "real" error.
How? How do I use LD_DEBUG systematically?
Thom, Itanium™ influencerBREAKING: GNOME and KDE agree to remove letter X from desktop Linu
vacuumbeefI made a new version of the Snake game in #Orca
I used to draw each body segment with it's own X operator, but suddenly I realized that I need only 2 - X for printing the char and X for erasing it. The tip of the tail receives the coordinates of the head with a delay, and this delay = the length of the snake.
Using enough Q operators I can make the maximum length of the snake as long as I want without worrying that Orca can only count to 35, it feels like cheating.
Ami AngelwingsSure they're called humans but you never see them hume, except for that one guy