Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Vijay Saha, Noida" <vsaha@noida.hcltech.com>
To: gdb@sources.redhat.com
Subject: gdbserver tcsetpgrp() ??
Date: Mon, 04 Aug 2003 13:05:00 -0000	[thread overview]
Message-ID: <E04CF3F88ACBD5119EFE00508BBB21210B095C6D@exch-01.noida.hcltech.com> (raw)

Hi

I have ported the gdbserver 5.3 on arm-linux target.
But as soon as debugging finishes, the target system gets logged out.

Then I had found that the "tcsetpgrp" in server.c:start_inferior() of
gdbserver was the culprit.
After commenting the line "tcsetpgrp (fileno (stderr), signal_pid);" , the
logout problem got solved !!!

I have also found that gdb-5.2 was not using this system call !!

What does this tcsetpgrp  actually doing ..?? (It has something to do with
foreground processing of terminal ..means..??)

How much is this necessary for remote debugging...??



**************************** clip of
server.c***************************************

start_inferior (char *argv[], char *statusptr)
{

  signal (SIGTTOU, SIG_DFL);
  signal (SIGTTIN, SIG_DFL);

  signal_pid = create_inferior (argv[0], argv);

  fprintf (stderr, "Process %s created; pid = %d\n", argv[0],
           signal_pid);
  signal (SIGTTOU, SIG_IGN);
  signal (SIGTTIN, SIG_IGN);

  /* chagall temp fix */
  /* when we use this function chagall gets logged out */
  //tcsetpgrp (fileno (stderr), signal_pid);

  /* Wait till we are at 1st instruction in program, return signal number.
*/
  return mywait (statusptr, 0);
}
**************************************end clip
*****************************************

Thanks and regards
Vijay


             reply	other threads:[~2003-08-04 13:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 13:05 Vijay Saha, Noida [this message]
2003-08-04 14:12 ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E04CF3F88ACBD5119EFE00508BBB21210B095C6D@exch-01.noida.hcltech.com \
    --to=vsaha@noida.hcltech.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox