This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: job control stuff in tracepoint.c
- To: Mark Kettenis <kettenis at wins dot uva dot nl>
- Subject: Re: job control stuff in tracepoint.c
- From: Elena Zannoni <ezannoni at cygnus dot com>
- Date: Thu, 12 Jul 2001 14:58:30 -0400
- Cc: gdb at sources dot redhat dot com, ezannoni at cygnus dot com
- References: <200107121217.f6CCHgT30217@delius.kettenis.local>
Mark Kettenis writes:
> Ok, I'm looking into cleaning up some host-dependent stuff;
> autoconfigifying bits and so on.
>
> I'm currently looking into stuff dealing with job-control signals
> (SIGTSTP. sigprocmask, sigsetmask). In that context we also do some
> really wierd stuff with a macro called STOP_SIGNAL. The reason for
> its existence has been eliminated (broken job-control handling on the
> Convex, support for which has been removed), yet it still exists. I'd
> like to eleminate STOP_SIGNAL (and revert to using SIGTSTP where
> appropriate), but when I did that I discovered that STOP_SIGNAL is
> used in tracepoint.c wheras it isn't defined at all, not even to
> SIGTSTP. Replacing #ifdef STOP_SIGNAL, with #ifdef SIGTSTP leads to
> compilation failure since the variable job_control isn't declared.
>
> I'm not quite sure what the code is trying to do. Something with
> redisplaying the prompt when running asynchronously? Elena, can you
> shed some light on this?
>
> Mark
Sure, I'll look into it. (Got a late start today).
Elena