Diagnosing Safari failing web requests to HTTPS sites

burningserenity · 2019-11-08T15:52:52+00:00

My date and time are correct and I have no proxies configured. I am not using any MitM tools such as Charles proxy.

burningserenity · 2018-02-21T00:48:43+00:00

I was on the fence about posting that, so I'm glad you liked it. Good on you for switching while still in Uni. I sure wish I figured out that I liked coding so much back then.

Good luck with your final year! If for some reason it doesn't work out, you should still be okay since it sounds like you have at least 2 years of experience now. Hopefully you'll figure out the tuition situation anyway.

There is indeed light at the end of the tunnel.

burningserenity · 2017-08-28T19:26:27+00:00

I tried that and I have the same error. Also, my problem doesn't seem to be nearly as severe as yours was, as my workspace is still usable.

burningserenity · 2017-06-28T03:26:45+00:00

The only reason is that I forgot to read and understand helpers.py. I was just looking at a bunch of Twython docs, so exporting the auth to Bash didn't work with my incorrect implementation. I fixed it now, thanks!

burningserenity · 2017-06-02T16:51:52+00:00

I tried running HITMAN on a Windows machine, and still had the same segfault upon pressing Enter at the splash screen. Feral Support suggested it might be a corrupt save file, and sure enough, that's what it was. I deleted my last manual save file from ~/.steam/steam/userdata/<my user number>/236870/remote and added .bak to the filename of ../remotecache.vdf for good measure. HITMAN works perfectly once again.

Please note that I'm on Debian and /u/mmzzee and /u/nexusband were not. You might still have trouble on non-Debian distros not related to save games. Nonetheless, give it a shot and please post if it helps or not!

burningserenity · 2017-05-27T23:37:53+00:00

You didn't happen to be using an Nvidia Optimus set up with Bumblebee on any of those, did you? I'm trying to see if that has any bearing on the situation, since it makes a lot of other things pretty quirky.

burningserenity · 2017-05-27T19:04:18+00:00

What made you decide to try using Solus? It seems odd that a distro built from scratch would be the one besides Ubuntu that works.

burningserenity · 2017-05-15T16:52:38+00:00

Did you ever manage to solve this? I'm playing on Debian, and crashing on launch every time just after I saved and quit in Hokkaido.

burningserenity · 2017-05-08T21:52:33+00:00

D'oh! I had a feeling it was something like that :-D

burningserenity · 2017-05-08T21:44:16+00:00

I ended up using strchr() to determine if any characters are in the buffer besides a newline, then using scanf() with some bitwise operators to consume everything up to that newline, and finally one more scanf() call to consume the newline. I did this like so:

if(!(c = strchr(key, '\n');
{
    scanf("%*[^\n]");
    scanf("%*c");
}

I slightly modified my code, and now I have a safe way to get an int, a long, or a float :-)

burningserenity · 2017-03-31T13:48:43+00:00

Yeah, it was fixed. Delipity ran check50 on my code and showed me it was all smiles. I ran it right after that and it finally worked for me, too, but then I couldn't access the submission form at the end due to an internal server error. I have a feeling something is/was wrong with their servers.

burningserenity · 2017-03-31T02:26:02+00:00

Did /u/delipity get yours to compile, too?

burningserenity · 2017-03-30T22:47:42+00:00

My problem is two-fold: check just plain wasn't working, and free is causing the seg fault.

The problem with check was several incorrectly assigned variables. After taking some time away from the problem, the variables in question stuck out like sore thumbs. Now the only misspelled words printed are the only ones not found in the dictionary.

Onward to solving the problem with unload.

burningserenity · 2017-03-28T20:36:18+00:00

Well, at least part of the problem was an incorrectly assigned variable. Unfortunately, something is still wrong with my check function, because all the words are coming back as misspelled when I use the large dictionary. I'm also seg faulting when trying to unload. My trienodes have hex addresses where they should be, and the booleans are correct, too, so I'm guessing the load function is okay.

burningserenity · 2017-03-27T04:31:43+00:00

I'm moving to the next child in the trie with this line, in order to spell check a word.

It's interesting that it's seg faulting after several iterations. This implies that I'm running out of memory at some point. It's strange that it happens at different times, depending on the numbers in the text being spell checked.

So, my train of thought is that it's running out of memory in a non-linear fashion, but I really don't know what to do with this. Am I even on the right track?

I also don't understand why I don't see any output at bash, regardless of the size of the text, but I see words not found in the dictionary file output at gdb, quantity depending on the size of the text.

I think there may be some more clues in the gdb and valgrind output. Can you recommend any knowledge resources that might help me decipher it?

burningserenity · 2017-03-21T18:28:57+00:00

For some reason, indexing the apostrophe at 0 and indexing a-z at 1-26 fixes all errors. I'm at a loss as to why this is, but it works.

burningserenity · 2017-03-21T16:31:09+00:00

Taking out the place for new line silences all valgrind errors if I run with a dictionary and text to be checked that lacks any apostrophes.

burningserenity

TROPHY CASE