bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Insight debugger for bash


From: Gianluca Sforza
Subject: Insight debugger for bash
Date: Thu, 19 Jul 2007 18:23:02 +0200

Configuration Information:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/$uname output: Linux debian 2.6.18-4-686 #1
SMP Mon Mar 26 17:17:36 UTC 2007 i686 GNU/Linux
Machine Type: i686-pc-linux-gnu

Bash Version: 3.0
Patch Level: 0
Release Status: release

Description:
The Insight debugger is stopped by the function `initialize_job_control ()'
of `jobs.c' while running bash. This problem affects also bash-3.2.

Repeat-By:
       Start Insight and run the bash executable; `shell.c' initializes the
data structures for storing and running jobs calling `initialize_job_control
(0)' from `jobs.c';
       it executes - among others - the following lines:

       2978      /*     Compensate for a bug in systems that compiled the
BSD
       2979             rlogind with DEBUG defined, like NeXT and Alliant.
*/
       2980          if (shell_pgrp == 0)
       2981            {
       2982              shell_pgrp = getpid ();
       2983              setpgid (0, shell_pgrp);
       2984              tcsetpgrp (shell_tty, shell_pgrp);
       2985            }
       2986
       2987          while ((terminal_pgrp = tcgetpgrp (shell_tty)) != -1)
       2988            {
       2989              if (shell_pgrp != terminal_pgrp)
       2990                {
       2991                  SigHandler *ottin;
       2992
       2993                  ottin = set_signal_handler(SIGTTIN, SIG_DFL);
       2994                  kill (0, SIGTTIN);
       2995                  set_signal_handler (SIGTTIN, ottin);
       2996                  continue;
       2997                }
       2998              break;
       2999            }

       Line 2994 stops Insight.


Fix:
       Roughly commenting the code quoted above and remaking bash
executable I can go on with my bash debugging.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]