3 ms·

> Also: print-debugging all the way. There were exactly zero ways to attach any kind of modern debugger That's just laziness from the original developer. To me

> Also: print-debugging all the way. There were exactly zero ways to attach any kind of modern debugger That's just laziness from the original developer. To me, no debugger support means it's time for a re-write.

fsckboy 5y ago
> That's just laziness from the original developer. To me, no debugger support means it's time for a re-write. when do you plan to get started on the linux kernel? that Linus is a lazy pri*k, he'll never get to it! *printk https://www.kernel.org/doc/html/latest/core-api/printk-basics.html https://www.kernel.org/doc/html/latest/core-api/printk-basic...
- 908B64B197 5y ago
  There's also KDB and KGDB (he eventually conceded that having a debugger in the main tree was for the best). https://www.kernel.org/doc/html/v4.16/dev-tools/kgdb.html https://www.kernel.org/doc/html/v4.16/dev-tools/kgdb.html
theshrike79 5y ago
Yes, please tell me the argumentation you would use to completely rewrite a 10 year old perfectly working stack, which is actively used to read tens of millions of devices of varying age daily. A piece of software that has around 50 coders on it actively keeping it running and adding new features and supported devices. (It took around 5 years and a team of 20 with millions of funding to "rewrite it" eventually and even they had to drop support for all but the latest devices. The old system is still chugging away, reading the old devices) Also I would like to know how you would attach a debugger to a stack that contained, among others, ASM/C-code running on an embedded device on the other side of the world, some MFC/C code on a gateway windows computer, perl scripts running god knows where and a PL/SQL bundle on an Oracle server in another country and some Java logic on a different server. This is the life legacy coders live. Of course, if you have a modern stack you can just click "debug" on your IDE and it'll automatically attach to a remote process and let you step through the code. We don't have that :)
- 908B64B197 5y ago
  > Also I would like to know how you would attach a debugger to a stack that contained, among others, ASM/C-code running on an embedded device on the other side of the world, some MFC/C code on a gateway windows computer, perl scripts running god knows where and a PL/SQL bundle on an Oracle server in another country and some Java logic on a different server. That sounds incredibly brittle. But each of these components should be debuggable individually and have a well defined interface.
  - warble 5y ago
    "should"
    - fL0per 5y ago
      Exactly my thoughts as well

fsckboy 5y ago

> That's just laziness from the original developer. To me, no debugger support means it's time for a re-write. when do you plan to get started on the linux kernel? that Linus is a lazy pri*k, he'll never get to it! *printk https://www.kernel.org/doc/html/latest/core-api/printk-basics.html https://www.kernel.org/doc/html/latest/core-api/printk-basic...

908B64B197 5y ago
There's also KDB and KGDB (he eventually conceded that having a debugger in the main tree was for the best). https://www.kernel.org/doc/html/v4.16/dev-tools/kgdb.html https://www.kernel.org/doc/html/v4.16/dev-tools/kgdb.html

theshrike79 5y ago

Yes, please tell me the argumentation you would use to completely rewrite a 10 year old perfectly working stack, which is actively used to read tens of millions of devices of varying age daily. A piece of software that has around 50 coders on it actively keeping it running and adding new features and supported devices. (It took around 5 years and a team of 20 with millions of funding to "rewrite it" eventually and even they had to drop support for all but the latest devices. The old system is still chugging away, reading the old devices) Also I would like to know how you would attach a debugger to a stack that contained, among others, ASM/C-code running on an embedded device on the other side of the world, some MFC/C code on a gateway windows computer, perl scripts running god knows where and a PL/SQL bundle on an Oracle server in another country and some Java logic on a different server. This is the life legacy coders live. Of course, if you have a modern stack you can just click "debug" on your IDE and it'll automatically attach to a remote process and let you step through the code. We don't have that :)

908B64B197 5y ago
> Also I would like to know how you would attach a debugger to a stack that contained, among others, ASM/C-code running on an embedded device on the other side of the world, some MFC/C code on a gateway windows computer, perl scripts running god knows where and a PL/SQL bundle on an Oracle server in another country and some Java logic on a different server. That sounds incredibly brittle. But each of these components should be debuggable individually and have a well defined interface.
- warble 5y ago
  "should"
  - fL0per 5y ago
    Exactly my thoughts as well