Hey I could use some help. I use cum, https://github.com/Ha

>I use cum to download and keep track of my manga.

I can't help you but thanks for giving me a right sensible chuckle

>>269555
This, I kek'd well. Good luck anon.

When I get this sort of error when coding, it is usually caused by a missing ";" or similar, which messes up following lines.
No idea how to fix that in your case though, and I could be completely wrong. Maybe ask the dev directly?

>>269550
Something is wrong in your config file. Can you show me the contents?

>>269550
Shove an issue on their tracker.

The JSON parser is throwing an exception, and they're not catching it, which is why they're getting killed.

>>270680
catching it in this situation would mostly just be a convenience thing for the user to tell them their config file is fucked up more clearly, but the fundamental problem here isn't the lack of an exception handler but the fact that the config file is not valid JSON.

Don't worry man I got this, just wondering whether OP is still here.

>>270673
Just got up and not to sound like a retard, which config file do you want?

>>270741
Should be in %APPDATA%/cum/config.json, or something like that.

>>270742
There's not a whole lot in it, just username and password data for batoto and madokami

http://pastebin.com/uyXBLbs3

>>270743
okay, it seems to be choking on the line with your madokami password. Since you probably don't want to show this to us (lol) here's a few things to make sure:

1. the password is surrounded by quotes (either 'like this' or "like this")
2. the password doesn't contain a lone \, especially near the quotes

>>270744
Tried both of your suggestions and it'st still throwing the same error

>>270746
can you try to change it to
"password": "",
"username": "anon",
and see if it then works? with anon replaced by your actual username of course, but with the quotes intact.
cum should prompt you for your madokami password and write it to the config after you enter it.

>>270748
Didn't work. Thanks for the help by the way.

I should probably just make an issue on github

>>270750
Please do, and include as much info as you can. This might be some strange bug that we haven't caught so far.

>>270752
Hey, just to give some closure to this, I decided to delete the config file and reenter all the info through cum and that fixed everything. The only issue in this whole thing was me

>>270771
Glad to hear you've got it working.
I've written up a bit of code just now to be clearer about these sorts of config file issues with a more readable error message, and I'll try to get it into the next release as soon as I've added some unit tests for it.

File: patrick sabber.jpg (174KB, 1280x800px) Image search: [Google]

174KB, 1280x800px

>>270776
I can't even read the damn github page without giggling like a child, this name man...

"the latest release of cum"

>>270778
Just wait until the pre-release versions are called pre-cum.

>>270692
Not getting killed by the language's assertion catcher isn't just "a convenience", it's a basic thing expected of any application, just like taking your shoes off before getting in the shower.

"Not validating input" makes up an entire family of security vulnerabilities.

You, the user, should never see a stack trace like this, because it's not amateur hour, and we should be catching parser errors before they become remote exploits.

>>270792
congrats on not knowing anything about the application.

1. the config is only ever written by the application itself
2. it is a local config, there is no "remote exploitation"
3. this is a memory safe language, so ACE is out of the question
4. it's a fucking JSON config file local to the computer that is only ever edited by either the tool itself or a user with a text editor that knows how to JSON.
5. uncaught exceptions have no side-effect other than terminating the application with a backtrace, there is no room for "exploitation" here because the builtin routine that terminates the application after showing a backtrace is already the fallback exception handler - it's simply an ugly one mostly useful for development.

Please shut the fuck up if you know jack shit. Your "not validating input" babbling makes me think you're a PHP-babby, and your knowledge about programming sure seems to imply this.

File: laughing_girl.jpg (35KB, 489x670px) Image search: [Google]

35KB, 489x670px

>>270781

>pre-cum