[issue926] tcsh consumes much cpu when trying to gdb anything

Simon 'corecode' Schubert corecode at fs.ei.tum.de
Thu Jan 24 11:17:42 PST 2008

Matthew Dillon wrote:
    Hmm.  There are two functions there that test for P_TRACED, do both
    need to be fixed?
No, cursig() will always stop the process and let the tracing parent look 
at the signal.

However, as we don't want to block there, we are returning ERESTART from 
fork1().  Now we should *only* do this if there is a signal.  Otherwise 
we'll just restart the syscall and the situation won't change.

    Also I'm not entirely sure what the mechanism is here.  Clearly the
    original code (this is original code) isn't quite compatible with
    the new signaling code, but the question is:  What is the correct
    thing to do about it?
No, this is "new" code :)  It was added by you in 2006, sys/signalvar.h 
rev 1.15.

I'm sure this is the correct fix.

Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \

More information about the Bugs mailing list