Post 3109101 by Michcioperz@m.atm.pl
 (DIR) More posts by Michcioperz@m.atm.pl
 (DIR) Post #3109101 by Michcioperz@m.atm.pl
       2019-01-18T17:49:27.801023Z
       
       0 likes, 0 repeats
       
       something that never fails to disappoint me about the Pinebook is when gdb suddenly goes "inferior process exited normally" about any program I try to debug, before I even provide the program with inputno idea what causes it and I'm on a train
       
 (DIR) Post #3109102 by Wolf480pl@niu.moe
       2019-01-18T17:53:45Z
       
       0 likes, 0 repeats
       
       @Michcioperz sounds like it's not passing stdin fd properly
       
 (DIR) Post #3109157 by Michcioperz@m.atm.pl
       2019-01-18T17:54:28.589196Z
       
       0 likes, 0 repeats
       
       @Wolf480pl I mean, the underlying process could segfault in normal circumstances for all I care, gdb will still say it's all fine
       
 (DIR) Post #3109158 by Wolf480pl@niu.moe
       2019-01-18T17:55:06Z
       
       0 likes, 0 repeats
       
       @Michcioperz wat...even if you set a breakpoint before starting the underlying process?
       
 (DIR) Post #3109209 by Michcioperz@m.atm.pl
       2019-01-18T17:55:23.559225Z
       
       0 likes, 0 repeats
       
       @Wolf480pl precisely
       
 (DIR) Post #3109210 by Wolf480pl@niu.moe
       2019-01-18T17:56:20Z
       
       0 likes, 0 repeats
       
       @Michcioperz ok, so now it sounds like wait{,3,4,id,pid}(2) is fucked up in your kernel, or gdb uses it wrong on aarch64....