News for hackers. Stuff that matters.

A comment on The Google Cemetery – A list of dead Google products and why they died. Parent comment

Re:The Google Cemetery – A list of dead Google products and ... by nerdponx on Thursday November 22, 2018 @11:30AM (#18510923) 

                /* evil! how this this happen */                                        \
239 if (slave_start_jmp_error_to_print != NULL) \ 240 gdm_error (slave_start_jmp_error_to_print); \ 241 gdm_error ("Bad (very very VERY bad!) things happening in signal"); \ 242 _exit (DISPLAY_REMANAGE); \ 243 }

I'd hate to be the poor soul who encounters this error message and finds no information about it except the source code.

[ Parent | on HN ]
Re:The Google Cemetery – A list of dead Google products and ... by arghwhat on Thursday November 22, 2018 @12:22PM (#18511217)
It will only occur if everything is so irrevocably on fire that you need to debug a lot of code anyway, at which point the error message is useless.

Specifically, the branch is only reachable if the PID is not what was expected, or the location that the macro was supposed to longjmp to is not set, which would be fatal defects.

[ Parent | on HN ]