Mark
then i realized i turned on windows key lock on my keyboard
Mark
tfw i restarted my laptop 3 times, thought it's nvidia playing games with me once again
Mark
>.>
Roxifλsz 🇱🇹
Mark
reeeeeeeeeeeee
klimi
XD
Mark
lshw -short for us please?
https://paste.wut.ee/raw/itavudatik
klimi
nc -l 9999 | sudo -H python
Mark
sec
BinaryByter
https://paste.wut.ee/raw/itavudatik
lol get yourself a good computer
Mark
dude i'm a goddamn poor high school student living on a ramen
Mark
i can't afford myself a proper computer smh
BinaryByter
mhh
BinaryByter
not as nice as you, klimi
klimi
Oh
klimi
<3
klimi
I'll have to do my rice too maxi, btw you haven't send any
Mark
nc -l 9999 | sudo -H python
nc mikroskeem.eu 9999
Mark
oh wow, arguments didn't work like i expected
Mark
https://0x0.st/sUHB.png
Mark
rip
klimi
I don thave
klimi
NC access rn
Mark
rip
klimi
<3
Mark
boooo
klimi
klimi
Bar
Mark
stock config
Mark
but most importantly
Mark
wait...
klimi
Gn
Mark
j
everything seems logical to me
so what can be the issue?
Roxifλsz 🇱🇹
>U series processor >Compiling stuff Sad!
Dima
>U series processor >Compiling stuff Sad!
lol I was using some U type intel i5 for four years for development
Dima
lol I was using some U type intel i5 for four years for development
but later moved to 6-core i7 and that was like OHHHH MANNN CHILL CHILL
Dima
olli
You are calling mktime on random memory, what do you expect
Mark
j
so your suggestion is removing &
Mark
/p/gcc-build/./gcc/liblto_plugin.so: error loading plugin: Dynamic loading not supported
Mark
i srsly want to buy a rope rn
j
?
olli
so your suggestion is removing &
yes, mktime expects a pointer to struct tm https://en.cppreference.com/w/c/chrono/mktime You are passing a pointer to a pointer to struct tm
j
im dereferencing it first
BinaryByter
im dereferencing it first
it is a pointer already
olli
im dereferencing it first
you have a pointer to struct tm, by taking the address of the pointer you have a pointer to pointer. This is not what mktime expects Depending on your compiler, warnings should be emiteed, try compiling with -pedantic -Wall -Wextra
Mark
-Wall -Wextra make life waay easier
BinaryByter
-Wall -Wextra make life waay easier
IMHO you should always enable the strictest compilation
Mark
there are few cases however which -Wall and -Wextra are really bitch to use
olli
IMHO you should always enable the strictest compilation
I disagree, clang emits warnings for not being C++-98 compatible
Mark
on gcc atleast
Mark
on gcc atleast
for example functions returning data can't have their data discarded using (void) x();
Mark
on gcc
Mark
while on clang you can do this fine
Mark
on gcc
it's known bug apparently, nobody has fixed it yet
BinaryByter
I disagree, clang emits warnings for not being C++-98 compatible
lemme rephrase: IMHO you should always enable the strictest sensible compilation
olli
lemme rephrase: IMHO you should always enable the strictest sensible compilation
that is like not saying anything.. "sensible" is not defined
Mark
but when func has __attribute__ ((warn_unused_result)) then gcc will warn you nevertheless
Mark
int __attribute__ ((warn_unused_result)) a() { return 4; } int main(int argc, char **argv) { (void) argc; (void) argv; (void) a(); return 0; }
Mark
https://0x0.st/sUHw.png
Mark
and if you have -Werror somewhere then rip
Mark
i had this issue when i wrote my code on clang, but encountered 300 errors on gcc :D
j
wtf is wrong with me
j
it was this the whole time
j
i was modifying the same struct
j
that wasnt the issue it seems
BinaryByter
Hello
hello