Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ranjan Parthasarathy <Ranjan.Parthasarathy@efi.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb / glibc querry
Date: Fri, 28 Sep 2001 16:36:00 -0000	[thread overview]
Message-ID: <c9f288e76bb17e04562c17772731ef43@NO-ID-FOUND.mhonarc.org> (raw)
In-Reply-To: <20010928192504.A32065@nevyn.them.org>

Yes once it is working I do plan to post it and hopefully that will be soon 
enough :-).

copyright assignment ????

Thanks

Ranjan

On Friday 28 September 2001 16:25, Daniel Jacobowitz wrote:
> On Thu, Sep 27, 2001 at 05:17:58AM -0700, Ranjan Parthasarathy wrote:
> > I am working on a pthreads aware gdbserver with an implementation as done
> > in gdb.
> >
> > I have a working release however occasionally my gdbserver causes a
> > thread to die reporting a SIGSEGV in __DTOR_END__ . This is somewhat
> > random and I do not get such an error in many programs but only in
> > certain cases but reproducable in all such cases.
> >
> > Also I found that the __DTOR_END__ is declared in some file in glibc.
> > What is the purpose of that and how is it used.
>
> __DTOR_END__ describes the end of the static destructors section.  It's
> unlikely that you're really crashing there; more likely, it's the last
> symbol before the address where you are really crashing.
>
> Are you planning on posting this code soon (I hope so!)?  Do you have a
> copyright assignment in place?


  reply	other threads:[~2001-09-28 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E15n6tZ-000761-00@crack.them.org>
2001-09-28 16:24 ` Daniel Jacobowitz
2001-09-28 16:36   ` Ranjan Parthasarathy [this message]
     [not found]   ` <200109281531.IAA21241@messenger.mvista.com>
2001-09-28 16:44     ` Daniel Jacobowitz
     [not found]   ` <200109282337.f8SNbA511877@chmls12.mediaone.net>
2001-09-28 16:53     ` Craig Rodrigues
2001-09-28 16:17 Ranjan Parthasarathy

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=c9f288e76bb17e04562c17772731ef43@NO-ID-FOUND.mhonarc.org \
    --to=ranjan.parthasarathy@efi.com \
    --cc=drow@mvista.com \
    --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