From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2164 invoked by alias); 27 Feb 2004 20:02:57 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 2154 invoked from network); 27 Feb 2004 20:02:51 -0000 Received: from unknown (HELO msrvr.intellambda.com) (207.5.82.234) by sources.redhat.com with SMTP; 27 Feb 2004 20:02:51 -0000 Message-ID: <403FA285.8070808@intellambda.com> Date: Fri, 27 Feb 2004 20:02:00 -0000 From: Albert Ho MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb@sources.redhat.com Subject: Re: gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() References: <403EB813.90408@intellambda.com> <20040227032447.GA24747@nevyn.them.org> In-Reply-To: <20040227032447.GA24747@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-02/txt/msg00418.txt.bz2 The first spawn thread died on startup under gdbserver. It has a pid of 1024. System was just started and the main thread has pid 110. Daniel Jacobowitz wrote: >On Thu, Feb 26, 2004 at 07:22:59PM -0800, Albert Ho wrote: > > >>Should gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() always >>succeed when dealing with 's' in main? >> >>I run into a problem when a thread is not found in >>set_desired_inferior(), causing &status to become some bogus addr and >>hence gdbserve segv. >> >> > >I've never seen this behavior before. Please explain how it happens; I >don't see any way to get a bogus pointer unless your thread list is >corrupted. > > >