Patch didn't attach. You have to remember to tick that
"Attach file" box. Without that, it's hard to judge what
you mean by "doesn't take advantage of it". That snippet
is necessary for some platforms to make their curses library
survive SIGWINCH. Without it, cscope would just hang itself
if the xterm size is changed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm worried by this patch. Fixing SIGWINCH is tricky
business --- the difference between an registering an action
and actually handling the signal may very well be what makes
the whole fix work in the first place.
As to HURD not having SA_SIGINFO: given that this is a
standardized feature of sigaction() (per SUS v3), I tend to
view that as a bug in HURD, not in cscope. Unconditionally
disabling cscope's usage of it is thus out of the question.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=27517
Patch didn't attach. You have to remember to tick that
"Attach file" box. Without that, it's hard to judge what
you mean by "doesn't take advantage of it". That snippet
is necessary for some platforms to make their curses library
survive SIGWINCH. Without it, cscope would just hang itself
if the xterm size is changed.
Logged In: YES
user_id=620211
Sorry, I forgot to tick the option. Here it goes now.
Logged In: YES
user_id=27517
I'm worried by this patch. Fixing SIGWINCH is tricky
business --- the difference between an registering an action
and actually handling the signal may very well be what makes
the whole fix work in the first place.
As to HURD not having SA_SIGINFO: given that this is a
standardized feature of sigaction() (per SUS v3), I tend to
view that as a bug in HURD, not in cscope. Unconditionally
disabling cscope's usage of it is thus out of the question.