Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Prabha Suresh <Prabha.Venkatachalam@alcatel.com>
To: Ranjan Parthasarathy <Ranjan.Parthasarathy@efi.com>
Cc: gdb@sources.redhat.com
Subject: Re: Attaching to an already running process on gdb 5.1
Date: Fri, 07 Dec 2001 04:05:00 -0000	[thread overview]
Message-ID: <3C11454B.1EFCB4AC@alcatel.com> (raw)
In-Reply-To: <200112061902.fB6J2UU02671@mrelay2.alcatel.com>

Ranjan Parthasarathy wrote:
> 
> Can anyone let me know as to whether attach on already running ( multi
> threaded processes works on gdb 5.1 ). I have tried the attach with a non
> threaded program but trying to attach to a multi threaded ( pthreads ) fails.
> 
> Is there an option which I am missing or is this broken?
> 
> Thanks
> 
> Ranjan
I did find the same problem,the error is as follows


#0  0x12e6f0 in ?? ()
#1  0x93cb8 in pstruct ()
#2  0x94544 in pstruct ()
#3  0x9476c in pstruct ()
#4  0x949fc in pstruct ()
#5  0x94ca4 in pstruct ()
#6  0xf3e6c in ?? ()
#7  0xad33c in pstruct ()
#8  0x76204 in pstruct ()
#9  0xca65c in ?? ()
#10 0x839a0 in pstruct ()
#11 0x840b8 in pstruct ()
#12 0x187828 in ?? ()
#13 0x8313c in pstruct ()
#14 0x83844 in pstruct ()
#15 0xe7a48 in ?? ()
#16 0xe73c0 in ?? ()
#17 0xe7410 in ?? ()
#18 0xc97a8 in ?? ()
#19 0xe744c in ?? ()
#20 0x83228 in pstruct ()
#21 0x4f320 in strstream::~strstream (this=0x0, __in_chrg=324344)
    at ../../../src/libio/iostream.h:230
#22 0xc97a8 in ?? ()
#23 0x4fdf4 in __ptmd_type_info::~__ptmd_type_info (this=0x0, __in_chrg=0)
    at ../../src/gcc/cp/tinfo2.cc:459
#24 0xc97a8 in ?? ()
#25 0x5000c in bad_cast type_info function ()
    at
/homes/diwilson/cygnus/all-builds/native-00r1-solaris/obj/gcc/include/typeinfo:1209


Is there any patches have been put up in the latest release,i use GNU gdb
5.0-gnupro-00r1

for Solaris 2.7 version


-- Prabha
-- 
************* Leadership is action,not the position *****************


       reply	other threads:[~2001-12-07 12:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200112061902.fB6J2UU02671@mrelay2.alcatel.com>
2001-12-07  4:05 ` Prabha Suresh [this message]
     [not found] <E16C3gA-0003Dx-00@crack.them.org>
2001-12-06 12:37 ` Daniel Jacobowitz
2001-12-06 10:55 Ranjan Parthasarathy
  -- strict thread matches above, loose matches on Subject: below --
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 Ranjan Parthasarathy
2001-12-06 10:55 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=3C11454B.1EFCB4AC@alcatel.com \
    --to=prabha.venkatachalam@alcatel.com \
    --cc=Ranjan.Parthasarathy@efi.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