Might skim the following, and see if it helps: ... https://apple.stackexchange.com/questions/384216/closing-terminal-window-does-not-kill-script-run-with-sudo

Add your own Python from /usr/local/bin into your PATH ahead of the system-provided Python, and see if that meets your requirements. I wouldn't suggest attempting to replace the version of Python installed by macOS. Apple is removing Python in a future version of macOS. Per Apple: Deprecations Scripting language runtimes such as Python, Ruby, and Perl are included in macOS for compatibility with legacy software. Future versions of macOS won’t include scripting language runtimes by default, and might require you to install additional packages. If your software depends on scripting languages, it’s recommended that you bundle the runtime within the app. (49764202)

Automatic reference-counting garbage collection schemes and manual reference count schemes and fully manual memory management whether via alloca or malloc or otherwise—and C and Objective C buffer overflows and exploits—are all related, but are distinct concepts. C will happily overwrite any memory that isn't otherwise write protected, when handed a rogue pointer. Some links to more info and background: https://developer.ibm.com/tutorials/l-memory/ https://stackoverflow.com/questions/6220212/buffer-overflow-in-c https://www.tallan.com/blog/2019/03/07/exploring-buffer-overflows-in-c-part-one-theory/ https://www.tallan.com/blog/2019/04/04/exploring-buffer-overflows-in-c-part-two-the-exploit/ As this question reads like a homework question, I'm including some introductory material around memory management foibles and C exploits in the above links.

See if implementing and connecting to and using the mitmproxy or similar TLS proxy tool might help figure out where the fault lurks.

Maybe purchase a commercial license for Ghostscript, or for Sanface txt2pdf, or some other existing tool that provides this?

I'd expect to see the following info returned for the foreseeable future: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.3 Safari/605.1.15 With tracking prevention, Apple is seeking to both make fingerprinting and user tracking more difficult, and to discourage website dependencies on the browser agent string while encouraging a shift to using capabilities-based interfaces, and what you're encountering here is all part of that. Per Apple:: Fingerprinting, or stateless tracking, is tracking based on the properties of the user’s behavior and computing environment, without the need for explicit client-side storage. This includes properties of user’s web browser and its configuration, the user’s device and its configuration, the user’s location, or the user’s network connection. Fingerprinting vectors include but are not limited to installed fonts, the user agent string, GPU details, CPU details, IP address, and TLS connection.

A panic has a snapshot of system state at the time of the crash, but not the history leading up to the crash; not how the Mac got tangled. Bad Mac hardware, bad cabling, flaky external hardware, broken kext, macOS bug, pretty much everything is in play here as a potential trigger for this panic. Probably best to ask this over in the Support Community for Big Sur too, as this question doesn't seem to involve app development. When re-posting this question, please also include the EtreCheck hardware and software configuration report as a text attachment to the posting.

Apple is focusing on Swift and Swift tooling for new app development, while much of the existing app development for Apple platforms has used Objective C. Assuming you have a Mac sufficiently capable, C and C++ app development works just fine in Xcode. And I prefer working in Swift and Objective C and C to working in C++, but that’s more about my preferences and experiences around C++. Among other details, the Xcode continuous compilation support is wonderful, and that works in C, C++, Objective C, and Swift. If you’re interested in learning Swift, consider starting with Playgrounds; a deceptively capable IDE. That lets you focus more on learning Swift and on your Swift code than in Xcode, which is bigger and more complex than Playgrounds. But the only thing that’s relevant to the questions here is whether Xcode works for you, and that’s something you’re going to have to try and to decide. You might well find a more familiar IDE to your preferences.

This would typically be included in the contract with you, and would be signed by both you and the rights-holder for the material. The contract would cover what you’re allowed to do and not allowed to do with the material from the textbook, and for how long, and with provisions for renewals, and with provisions describing expectations around app support and updates and related maintenance for the app, and whether you will hold rights to the source code you’re creating, or if the author expects that. This can include whether you’re setting up an Apple ID for the author for control over the app in the App Store, too. Your lawyer and their lawyer will then usually have some wording around “used by permission” or some such for inclusion in the documentation and app copyright statements. As for Apple, the App Store agreement has you responsible for infringements for the contents of the apps you publish.

Verify that your local DNS settings are correctly configured and operating for your particular local network (check with the network administrator, or with your ISP), and then contact Instagram app support for assistance with the Instagram app.

Third-party cookies? That's up to Apple, and log some feedback. But enabling third-party cookies seems increasingly unlikely. Alternatives to using third-party cookies include using first-party cookies (which are also time-limited now), or using Sign In With Apple, or migrating to token-based logins akin to Twitter or using the built-in authenticator, or waiting for the MFA app to figure out how to update their implementation to use first-party cookies.

This was recently asked elsewhere, and that IDE doesn't work very well if at all on any recent macOS, and macOS support appears to have been withdrawn. Among other discussions: https://discussions.apple.com/thread/253619481 Your choices here are to use Xcode and not the Code::Blocks as your IDE (which'll mean less or no support from the instructor), or boot and use Windows or another supported platform directly or as a guest and use Code::Blocks, or re-port and support Code::Blocks to macOS—that you found something that ~works may or may not be helpful, if there are issues found later. As for the H file with Xcode, add it to the project. Create a new file, of type C header file, and populate the header file accordingly. File > New > select macOS > C Header File. To reference a project local header file in C or C++, use double quotes around the filename, and not angle brackets. Here's a screenshot of the Xcode IDE just having added a bogus header file to another C++ example I've posted elsewhere, with the include visible in the project to the left column and with the #include highlighted in the displayed C++ source. (There's nothing in BogoHeader.h here, but it compiles.) There are various other Code::Blocks discussions around, but it's probably best to ask those questions over in the Code::Blocks forum.

You’re setting up symbolic links with the way you’re trying to copy files around, here to the installer, to the DMG disk image, and to the installation kit. (That’s the arrow shown in the lower left corner of the icons.) If you have enough room, load Xcode, and let that load the command-line tools. If you don’t, then double-click on the package (pkg) file to install the tools. Then clean up all those links. Control-click, and select move-to-trash. Some common shortcuts: https://support.apple.com/en-us/HT201236

“can’t find the site” seems rather more like a DNS error, or a site that doesn’t exist. Here, the specified mysupport-pilot.apple.com website also doesn’t seem to exist in DNS, a d there are very few references. Same issues when booted in Safe Mode? Do you have any VPN apps, add-on anti-malware apps, add-on cleaner apps, or similar, loaded onto this Mac? And check with whatever Apple service has you trying to access that site, and see if a login or some other setup is required.

If there are any add-on anti-malware apps installed, or add-on VPN apps, or add-on cleaner apps installed, or similar, remove all of those per the vendors’ instructions, restart, and try again.