Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "David L" <idht4n@hotmail.com>
To: drow@false.org
Cc: gdb@sourceware.org
Subject: Re: restart -> "Can't attach LWP" + hang
Date: Fri, 25 Aug 2006 16:06:00 -0000	[thread overview]
Message-ID: <BAY104-F19F198A65CF4EC6E4BD0C484450@phx.gbl> (raw)
In-Reply-To: <20060825154320.GA9895@nevyn.them.org>

>On Fri, Aug 25, 2006 at 08:41:59AM -0700, David L wrote:
> > I just installed gdb 6.5 and tried to use checkpoint/restart.  After
> > entering restart and next, I got the message:
> >
> > [New Thread -1210636064 (LWP 20892)]
> > Can't attach LWP 20892: Operation not permitted
> >
> > I typed next again and gdb stopped responding.
> >
> > What am I doing wrong?
>
>Are you using a threaded program?  I'm pretty sure that doesn't work
>(and I can't think of any way to make it work, either).
>
Not intentionally, but I'm pretty sure a library I've linked to is
spawning a thread under the covers.  I'm not sure which one.
Below is a list of my dependencies.  In any case, could gdb
detect that it's multithreaded and prevent me from inserting
checkpoint or restarting?

Thanks...

               David

PS - Here are my library dependencies.  I think one of them
starts another thread in a C++ constructor or something.
Perhaps there is a way to avoid that if there is a single-threaded
option in the configuration for that library so I can use the
fancy new checkpoint feature.

       linux-gate.so.1 =>  (0xffffe000)
        libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x008fd000)
        libGLU.so.1 => /usr/lib/libGLU.so.1 (0x02396000)
        libGL.so.1 => /usr/lib/libGL.so.1 (0x02801000)
        libXmu.so.6 => /usr/lib/libXmu.so.6 (0x00dc8000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0x007d6000)
        libtcl8.4.so => /usr/lib/libtcl8.4.so (0xb7e8b000)
        libtk8.4.so => /usr/lib/libtk8.4.so (0x009bf000)
        libdl.so.2 => /lib/libdl.so.2 (0x00784000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7da0000)
        libm.so.6 => /lib/libm.so.6 (0x007a7000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7d93000)
        libc.so.6 => /lib/libc.so.6 (0x0064f000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0x008d5000)
        libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0x07fe8000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x008e7000)
        libdrm.so.2 => /usr/lib/libdrm.so.2 (0x07fef000)
        libXt.so.6 => /usr/lib/libXt.so.6 (0x0233b000)
        libSM.so.6 => /usr/lib/libSM.so.6 (0xb7d89000)
        libICE.so.6 => /usr/lib/libICE.so.6 (0xb7d6f000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0x0079f000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x007ce000)
        /lib/ld-linux.so.2 (0x00632000)

_________________________________________________________________
Search from any web page with powerful protection. Get the FREE Windows Live 
Toolbar Today!   http://get.live.com/toolbar/overview


  reply	other threads:[~2006-08-25 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25 15:42 David L
2006-08-25 15:43 ` Daniel Jacobowitz
2006-08-25 16:06   ` David L [this message]
2006-08-25 16:31     ` Daniel Jacobowitz
2006-08-25 19:41       ` Michael Snyder

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=BAY104-F19F198A65CF4EC6E4BD0C484450@phx.gbl \
    --to=idht4n@hotmail.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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