public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Problem with multiple threads using gdbserver on x86.
Date: Mon, 23 Jun 2003 15:13:00 -0000	[thread overview]
Message-ID: <1056380381.13489.30.camel@numenor.codito.co.in> (raw)
In-Reply-To: <20030623132811.GA30502@nevyn.them.org>

On Mon, 2003-06-23 at 18:58, Daniel Jacobowitz wrote:
> I dunno.  Probably just providing a stub for ps_get_thread_area
> (spelling?) will be enough to make it work.
there does not seem to be any reference to this function anywhere in the
gdbserver code that i have. maybe  i have a very old version but the
source has not changed for the last 12 months or so for the thread-db.c
file. just checked that on cvs. the error seems to come in
thread_db_init() and precisely when it tries to find the new threads. 


could someone explain why this code sits inside such a function . isnt
this strange??
static void
linux_look_up_symbols (void)
{
#ifdef USE_THREAD_DB
  if (using_threads)
    return;

  using_threads = thread_db_init ();
#endif
}



	
> 
> On Mon, Jun 23, 2003 at 06:59:51PM +0530, ramana wrote:
> > could you give me a hint as to what needs to be done. i am sure i can find 
> > free time to patch it up myself. would give me a chance to fool around with 
> > some gdb stuff, things that i have been itching to do .
> > regards
> > Ramana
> > 
> > On Mon, 23 Jun 2003 09:16:06 -0400, Daniel Jacobowitz <drow@mvista.com> 
> > wrote:
> > 
> > >On Mon, Jun 23, 2003 at 06:40:40PM +0530, Ramana Radhakrishnan wrote:
> > >>
> > >>> It works perfectly fine for me.  I recommend you ask Red Hat; I know
> > >>> that gdbserver does not yet support NPTL so it's possible that they
> > >>> have disabled threading.
> > >>
> > >>I tried it again with gdbserver and gdb-5.3 rebuilt from the sources . 
> > >>with no luck . any other ideas.
> > >
> > >That won't support NPTL either :)
> > >
> > >I suspect gdbserver + threads is not usable on RH9 until someone
> > >patches gdbserver to support it.  I don't have a system to try this on
> > >myself, so someone else will have to do it.
> > >
> > 
> > 
> > 
> > -- 
> > Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
> > 

  parent reply	other threads:[~2003-06-23 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 12:15 Ramana Radhakrishnan
2003-06-23 14:08 ` Daniel Jacobowitz
2003-06-23 14:10   ` Ramana Radhakrishnan
2003-06-23 14:13     ` Daniel Jacobowitz
     [not found]       ` <oprq72f1mrocv5ka@mail.codito.co.in>
     [not found]         ` <20030623132811.GA30502@nevyn.them.org>
2003-06-23 15:13           ` Ramana Radhakrishnan [this message]
2003-06-23 15:20             ` Daniel Jacobowitz
2003-06-23 16:03               ` Ramana Radhakrishnan
2003-06-23 16:21               ` Ramana Radhakrishnan
2003-06-23 16:25                 ` Daniel Jacobowitz
2003-06-23 16:30                   ` Ramana Radhakrishnan
2003-06-23 18:35                     ` 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=1056380381.13489.30.camel@numenor.codito.co.in \
    --to=ramana.radhakrishnan@codito.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=ramana@codito.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).