This is the mail archive of the insight@sources.redhat.com mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Insight 5.0 on Linux


>>>>> "Syd" == Syd Polk <spolk@redhat.com> writes:

Syd> Insight will not work if executed in background. It is really
Syd> hard to get it to work that way, as every different operating
Syd> system has really bizarre ways to do pseudo-terminals.

Actually, I think a patch to make Insight work in the background
wouldn't be too hard.  You have to change inflow.c:gdb_has_a_terminal()
to say that there is never a controlling terminal when the gui is
running.  I hacked this in to my gdb and it seems to work ok.  Of
course if you do this and want to debug a program that actually uses
its terminal then you have to enable the xterm-for-inferior feature.

I've appended my patch.  I don't know whether it is really advisable
or not, so I haven't submitted it to gdb-patches.

Tom

Index: inflow.c
===================================================================
RCS file: /cvs/src/src/gdb/inflow.c,v
retrieving revision 1.4
diff -u -r1.4 inflow.c
--- inflow.c	2000/12/15 01:01:47	1.4
+++ inflow.c	2001/01/08 19:07:43
@@ -138,6 +138,13 @@
 #endif
 
       gdb_has_a_terminal_flag = no;
+
+      /* If we have a window system then by default we assume there is
+	 no controlling terminal.  If the inferior needs one then it
+	 is up to the GUI to deal with it.  */
+      if (use_windows)
+	return 0;
+
       stdin_serial = SERIAL_FDOPEN (0);
       if (stdin_serial != NULL)
 	{

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]