The wall of text was the error message.
I just prefer using the parsed outputs from IDEs which also take you to the line of code on click.
Disclaimer: I don’t represent KDE in any interaction with this account. I am just freeloading off of the kde.social server.
The wall of text was the error message.
I just prefer using the parsed outputs from IDEs which also take you to the line of code on click.
Doesn’t even startup on my box,
It needs to startup and then go to that point (after you select the projection) to cause the crash.
It definitely caused something other than the application to get into an invalid state. Which is why I am apprehensive about trying it out again to answer your comment. Probably was the display driver, which is why it didn’t just turn off after that.
deleted by creator
There’s this game “HyperRougue”. Run it on Arch.
hyperrogue-git version 13.0d.r60.g27fb2d92-1
Go to settings -> 3D configuration -> projection -> projection type ->
. Cycle through the projection types. One of them causes something good enough to call a crash.
I don’t remember anymore if it was just a display driver crash or a kernel crash and I haven’t updated to a newer version (which might have fixed it).
What language were you using?
Python maybe? I don’t know of any other interpreted language, that you may be calling system commands from, without saving to disk
I use C and C++ and my IDEs save to disk before compiling. Makes sense to not try compiling when there are potentially 2 versions (one on RAM or /tmp
and one on Disk) and the build system might be running multiple commands, which the IDE may/may not know of, in my case.
Guy is wrong. Went to 0th table. She asked for 1st table.
How come you know my IP !?
I installed a buzzer on it
Definitely want to do that on all keyboards at work
P.S. I’m guessing OP doesn’t actually have a CA and is just using simple self signed certificates without any private CA that has signed them.
You’re right. I’m talking about making a certificate using gpg
and storing it on your system. Then adding it to the root CA list and signing all your Local SSH stuff with it.
My router doesn’t have an HTTPS control page.
Sometimes frustrating.
For the certificate errors, just add a root CA of your own making.
Disabling auto-https, no idea. Maybe fix the source?
body with the power to actually do anything
Their response: “Another less opposer. Noice”
When the world is built upon forgiveness…
I was making a shared library at work and was recently asked to start throwing exceptions, because the users wouldn’t care to check my returned error and just continue with the empty returned data.
Well, now they will most probably have an empty catch block and continue doing what they did before.
Nothing can fix a lazy worker.
Next Up
Windows Server license on MS Windows Activation server has expired…
What if they got hashed by that cobalt system :P
Don’t worry. Give it half a millenium and we all will have been racist against dogs.
And more de-obf:
#include <stdio.h>
const char addarr1[]
= { 0x40, 0x40, 0x0, 0x40, 0x40, 0x40, 0x40, 0x0, 0x40, 0x40, 0x40, 0x40,
0x0, 0x40, 0x40, 0x40, 0x40, 0x40, 0x40, 0x0, 0x40, 0x40, 0x40, 0x0,
0x40, 0x0, 0x40, 0x40, 0x40, 0x40, 0x40, 0x0, 0x40, 0x40, 0x0, 0x40,
0x40, 0x40, 0x0, 0x40, 0x40, 0x40, 0x40, 0x0, 0x40, 0x40, 0x0, 0x40,
0x40, 0x40, 0x40, 0x40, 0x40, 0x0, 0x40, 0x40, 0x40, 0x40, 0x40, 0x40,
0x40, 0x40, 0x40, 0x40, 0x0, 0x40, 0x0, 0x0, 0x40, 0x40, 0x0, 0x40,
0x40, 0x0, 0x40, 0x40, 0x40, 0x40, 0x40, 0x40, 0x0, 0x40, 0x0, 0x40,
0x40, 0x40, 0x40, 0x0, 0x40, 0x40, 0x40, 0x40, 0x40, 0x40, 0x0, 0x0,
0x40, 0x0, 0x40, 0x40, 0x40, 0x0, 0x40, 0x0, 0x40, 0x40, 0x40, 0x40,
0x0, 0x0, 0x40, 0x40, 0x40, 0x0, 0x40, 0x40, 0x40, 0x40, 0x0, 0x40,
0x0, 0x40, 0x40, 0x0, 0x40, 0x40, 0x40, 0x40, 0x0, 0x40, 0x40, 0x0,
0x40, 0x40, 0x40, 0x40, 0x0, 0x40, 0x0, 0x40, 0x40, 0x40, 0x40, 0x0,
0x40, 0x40, 0x40, 0x0, 0x0, 0x0, 0x0, 0x0 };
const char addarr2[]
= { 0x9, 0x26, 0x20, 0x39, 0x2f, 0x35, 0x32, 0x20, 0x2c, 0x2f, 0x36, 0x25,
0x20, 0x2c, 0x25, 0x34, 0x34, 0x25, 0x32, 0x20, 0x29, 0x33, 0x2e, 0x27,
0x34, 0x20, 0x27, 0x29, 0x36, 0x25, 0x2e, 0x20, 0x29, 0x2e, 0x20, 0x34,
0x28, 0x25, 0x20, 0x26, 0x2f, 0x32, 0x2d, 0x20, 0x2f, 0x26, 0x20, 0x28,
0x29, 0x27, 0x28, 0x2c, 0x39, 0x20, 0x2f, 0x22, 0x26, 0x35, 0x33, 0x23,
0x21, 0x34, 0x25, 0x24, 0x20, 0x3, 0x2c, 0x20, 0x29, 0x33, 0x20, 0x29,
0x34, 0x20, 0x32, 0x25, 0x21, 0x2c, 0x2c, 0x39, 0x20, 0x21, 0x20, 0x2c,
0x2f, 0x36, 0x25, 0x20, 0x2c, 0x25, 0x34, 0x34, 0x25, 0x32, 0x3f, 0xa,
0x9, 0x20, 0x24, 0x2f, 0x2e, 0x27, 0x34, 0x20, 0x2b, 0x2e, 0x2f, 0x37,
0x2c, 0x20, 0x22, 0x35, 0x34, 0x20, 0x37, 0x28, 0x21, 0x34, 0x20, 0x9,
0x20, 0x24, 0x2f, 0x20, 0x2b, 0x2e, 0x2f, 0x37, 0x20, 0x29, 0x33, 0x20,
0x34, 0x28, 0x21, 0x34, 0x20, 0x9, 0x20, 0x2c, 0x2f, 0x36, 0x25, 0x20,
0x39, 0x2f, 0x35, 0x21, 0x20, 0x3c, 0x33, 0xa };
int main ()
{
for (int i = 0; i < 152; i++)
{
char adder1 = addarr1[i];
char adder2 = addarr2[i];
char to_print = (char)adder1 + adder2;
printf ("%c", to_print);
}
return 63;
}
I guess I should have kept the recursion and straightened it out in the next step, but now that it’s done…
The next step will just have an array of the characters that would be printed, so I’ll leave it here.
Here’s it with some amount of de-obfuscation:
#include <stdio.h>
short i = 0;
const long b[]
= { 0xd60, 0x3200, 0x1ca8, 0x74e2, 0x9c, 0x66e8, 0x5100, 0x14500,
0x63b8, 0x49c6, 0xe0, 0x6200, 0x75e8, 0x57a6, 0xe8, 0x4300,
0x4500, 0x63b8, 0x49ea, 0xc6, 0x548e, 0x22, 0x75e8, 0x57a6,
0xc6, 0x2fae, 0x7486, 0x8a, 0xd72, 0x4f9c, 0x63c6, 0x4ea2,
0x809c, 0x66e8, 0x5100, 0x5c00, 0x71a2, 0x51b8, 0x4e9e, 0xc6,
0x6200, 0x70c4, 0x8022, 0x7d00, 0x439c, 0x63b8, 0x6ae0, 0x54c0,
0x47e8, 0xe2, 0x5192, 0x6fc4, 0x4900, 0x60e8, 0x100ca, 0x14fe8,
0x6000, 0x44e92, 0x6300, 0x57c4, 0xae, 0x4ecc, 0x62de, 0xc6,
0xafae, 0x70c4, 0x9e, 0x4ec6, 0x639c, 0x5100, 0x4ecc, 0x74a2,
0x9e, 0x54e8, 0x7100, 0x608a };
const long n = 9147811012615426336;
long
main ()
{
if (i < 152)
{
char shifter;
if (i % 2 == 0)
{
shifter = 8;
}
else
{
shifter = 1;
}
char adder1 = (b[i >> 1] >> shifter) & 64;
char adder2 = (n >> (b[i >> 1] >> shifter)) & 63;
char to_print = (char)adder1 + adder2;
i++;
main ();
printf ("%c", to_print);
}
return 63;
}
Needless to say, the return value doesn’t matter any more. So you can change it to 0
or 69
depending upon your preferences.
I don’t get how that’s going to help with multiple keys on my cheap keyboard not registering properly, when pressed at the same time.
IMHO, nKRO is the best solution to get rid of ghosting.