Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Albert Ho <alberth@intellambda.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior()
Date: Fri, 27 Feb 2004 20:02:00 -0000	[thread overview]
Message-ID: <403FA285.8070808@intellambda.com> (raw)
In-Reply-To: <20040227032447.GA24747@nevyn.them.org>

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.
>
>  
>



  reply	other threads:[~2004-02-27 20:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27  3:22 gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() Albert Ho
2004-02-27  3:24 ` gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() Daniel Jacobowitz
2004-02-27 20:02   ` Albert Ho [this message]
2004-02-27 20:04     ` gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() Daniel Jacobowitz
2004-02-27 20:11       ` gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() Albert Ho
2004-02-27 20:15         ` gdb-6.0/gdb/gdbserver/target.c::set_desired_inferior() 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=403FA285.8070808@intellambda.com \
    --to=alberth@intellambda.com \
    --cc=drow@false.org \
    --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