From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-41720-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 10610 invoked by alias); 30 Nov 2005 01:38:51 -0000
Received: (qmail 10596 invoked by uid 22791); 30 Nov 2005 01:38:50 -0000
X-Spam-Check-By: sourceware.org
Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.200)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 30 Nov 2005 01:38:49 +0000
Received: by zproxy.gmail.com with SMTP id l1so1362885nzf         for <gdb-patches@sources.redhat.com>; Tue, 29 Nov 2005 17:38:47 -0800 (PST)
Received: by 10.36.177.18 with SMTP id z18mr5207380nze;         Tue, 29 Nov 2005 17:38:47 -0800 (PST)
Received: by 10.37.2.35 with HTTP; Tue, 29 Nov 2005 17:38:47 -0800 (PST)
Message-ID: <8f2776cb0511291738o61780660n68b59380d2747540@mail.gmail.com>
Date: Wed, 30 Nov 2005 05:41:00 -0000
From: Jim Blandy <jimb@red-bean.com>
To: Michael Snyder <msnyder@redhat.com>
Subject: Re: [RFC] multi-process gdb (forks, checkpoints)
Cc: GDB Patches <gdb-patches@sources.redhat.com>, gdb@sources.redhat.com,  	drow@false.org, Eli Zaretskii <eliz@gnu.org>
In-Reply-To: <438B8B6F.6010706@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <438B8B6F.6010706@redhat.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2005-11/txt/msg00503.txt.bz2

What happens if we fork, and then one of the forks unloads or loads a
shared library?

We're really crippled by our symtab data structures.