Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com, kettenis@gnu.org
Subject: Re: [rfa] Delete keep_thread_db
Date: Tue, 07 Sep 2004 18:04:00 -0000	[thread overview]
Message-ID: <413DF82A.1080000@redhat.com> (raw)
In-Reply-To: <413B3958.1060108@gnu.org>

Andrew Cagney wrote:
> It would appear that, at one stage, this variable had something to do 
> with corefiles, static programs and threads.  That's no longer the case 
> so this deletes the stray global.
> 
> Tested on FC3 with no regressions,
> 
> Ok?
> Andrew

I would have to defer to Mark Kettenis, since he added the
variable, and from the ChangeLogs, seems to be the only one
who's touched it.



> ------------------------------------------------------------------------
> 
> Index: ChangeLog
> 2004-09-05  Andrew Cagney  <cagney@gnu.org>
> 
> 	* thread-db.c (keep_thread_db): Delete.
> 	(thread_db_new_objfile, thread_db_create_inferior)
> 	(thread_db_mourn_inferior): Simplify assuming !keep_thread_db.
> 
> Index: thread-db.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/thread-db.c,v
> retrieving revision 1.43
> diff -p -u -r1.43 thread-db.c
> --- thread-db.c	22 Jul 2004 01:31:49 -0000	1.43
> +++ thread-db.c	5 Sep 2004 15:57:45 -0000
> @@ -63,10 +63,6 @@ static void (*target_new_objfile_chain) 
>  /* Non-zero if we're using this module's target vector.  */
>  static int using_thread_db;
>  
> -/* Non-zero if we have to keep this module's target vector active
> -   across re-runs.  */
> -static int keep_thread_db;
> -
>  /* Non-zero if we have determined the signals used by the threads
>     library.  */
>  static int thread_signals;
> @@ -673,8 +669,6 @@ thread_db_new_objfile (struct objfile *o
>  	  using_thread_db = 0;
>  	}
>  
> -      keep_thread_db = 0;
> -
>        goto quit;
>      }
>  
> @@ -703,18 +697,6 @@ thread_db_new_objfile (struct objfile *o
>        push_target (&thread_db_ops);
>        using_thread_db = 1;
>  
> -      /* If the thread library was detected in the main symbol file
> -         itself, we assume that the program was statically linked
> -         against the thread library and well have to keep this
> -         module's target vector activated until forever...  Well, at
> -         least until all symbols have been discarded anyway (see
> -         above).  */
> -      if (objfile == symfile_objfile)
> -	{
> -	  gdb_assert (proc_handle.pid == 0);
> -	  keep_thread_db = 1;
> -	}
> -
>        /* We can only poke around if there actually is a child process.
>           If there is no child process alive, postpone the steps below
>           until one has been created.  */
> @@ -1106,12 +1088,8 @@ static void
>  thread_db_create_inferior (char *exec_file, char *allargs, char **env,
>  			   int from_tty)
>  {
> -  if (!keep_thread_db)
> -    {
> -      unpush_target (&thread_db_ops);
> -      using_thread_db = 0;
> -    }
> -
> +  unpush_target (&thread_db_ops);
> +  using_thread_db = 0;
>    target_beneath->to_create_inferior (exec_file, allargs, env, from_tty);
>  }
>  
> @@ -1141,17 +1119,9 @@ thread_db_mourn_inferior (void)
>  
>    target_beneath->to_mourn_inferior ();
>  
> -  /* Detach thread_db target ops if not dealing with a statically
> -     linked threaded program.  This allows a corefile to be debugged
> -     after finishing debugging of a threaded program.  At present,
> -     debugging a statically-linked threaded program is broken, but
> -     the check is added below in the event that it is fixed in the
> -     future.  */
> -  if (!keep_thread_db)
> -    {
> -      unpush_target (&thread_db_ops);
> -      using_thread_db = 0;
> -    }
> +  /* Detach thread_db target ops.  */
> +  unpush_target (&thread_db_ops);
> +  using_thread_db = 0;
>  }
>  
>  static int



  reply	other threads:[~2004-09-07 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 16:05 Andrew Cagney
2004-09-07 18:04 ` Michael Snyder [this message]
2004-09-08  7:01 M.M. Kettenis
2004-09-08 14:15 ` Andrew Cagney
2004-09-08 19:45   ` Andrew Cagney
2004-09-08 14:38 ` Daniel Jacobowitz
2004-09-09 17:35   ` Michael Snyder

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=413DF82A.1080000@redhat.com \
    --to=msnyder@redhat.com \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@gnu.org \
    /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