5 ms·

Had the journalist tryied Linux, would have known that it gives much better error messages than some random looking number.

by GTP 3y ago

brettermeier 3y ago
It's about one-click-solutions what makes Windows a nice-to-use-tool, not the error messages.
crimbles 3y ago
Exit code 139. Hm.
- GTP 3y ago
  That's usually not the full error message, and you can still easily find the number's meaning by opening the man page of wathever piece of software terminated with that exit code.
  - nullindividual 3y ago
    Likewise, if you knew about err.exe, you'd also know how to be able to get the error message behind the error code.
  - crimbles 3y ago
    Depends really. If it's some kind of runtime or VM you pretty much have zero idea what the exit code was. Python, CLR, JVM tend to leave you in this mire.
    - GTP 3y ago
      Yes, but remember that usually nowadays a piece of software also logs something to stderr instead of relying just on exit codes to signal error.
      - crimbles 3y ago
        Not necessarily. Most of the 139's I get these days are SIGSEGV related. Obviously if you annoy the MMU at that level it's not going to get given an opportunity to write anything useful to stderr.
OsrsNeedsf2P 3y ago
It literally gave the wrong error message? > Unfortunately, according to Microsoft, "because of an error in the error code handling routine," this might not be the correct error.
- GTP 3y ago
  Yes, and it's ironic that there's an error in the error handling routine :D
HKH2 3y ago
Yes, but sometimes useful messages can only be found in dmesg.
- xxs 3y ago
  dmesg has been there since forever. If anything windows (auto) update has been one of the worst part, esp. when it fails to update... or worse replaces your video/printer driver with whatever it finds. The latter (video) messes up audio for hdmi/displayport in addition of installing bogus drivers. I'd be tad happier to have apt install/apt update/upgrade instead of windows schedule 'updates'

Had the journalist tryied Linux, would have known that it gives much better error messages than some random looking number.

by GTP 3y ago

Had the journalist tryied Linux, would have known that it gives much better error messages than some random looking number.

brettermeier 3y ago

It's about one-click-solutions what makes Windows a nice-to-use-tool, not the error messages.

crimbles 3y ago

Exit code 139. Hm.

GTP 3y ago
That's usually not the full error message, and you can still easily find the number's meaning by opening the man page of wathever piece of software terminated with that exit code.
- nullindividual 3y ago
  Likewise, if you knew about err.exe, you'd also know how to be able to get the error message behind the error code.
- crimbles 3y ago
  Depends really. If it's some kind of runtime or VM you pretty much have zero idea what the exit code was. Python, CLR, JVM tend to leave you in this mire.
  - GTP 3y ago
    Yes, but remember that usually nowadays a piece of software also logs something to stderr instead of relying just on exit codes to signal error.
    - crimbles 3y ago
      Not necessarily. Most of the 139's I get these days are SIGSEGV related. Obviously if you annoy the MMU at that level it's not going to get given an opportunity to write anything useful to stderr.

OsrsNeedsf2P 3y ago

It literally gave the wrong error message? > Unfortunately, according to Microsoft, "because of an error in the error code handling routine," this might not be the correct error.

GTP 3y ago
Yes, and it's ironic that there's an error in the error handling routine :D

HKH2 3y ago

Yes, but sometimes useful messages can only be found in dmesg.

xxs 3y ago
dmesg has been there since forever. If anything windows (auto) update has been one of the worst part, esp. when it fails to update... or worse replaces your video/printer driver with whatever it finds. The latter (video) messes up audio for hdmi/displayport in addition of installing bogus drivers. I'd be tad happier to have apt install/apt update/upgrade instead of windows schedule 'updates'