public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17626] New: attach, detach, attach did not work
Date: Wed, 19 Nov 2014 16:19:00 -0000 [thread overview]
Message-ID: <bug-17626-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17626
Bug ID: 17626
Summary: attach, detach, attach did not work
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
I'm debugging firefox in "electrolysis" mode, where it
has two processes. I used git gdb from a couple weeks ago.
First I attached to the parent process. This went fine:
(gdb) attach 8126
Attaching to process 8126
Reading symbols from
/home/tromey/firefox-git/gecko-dev/obj-x86_64-unknown-linux-gnu/dist/bin/firefox...done.
[...lots more...]
0x00007facdb22c71d in poll () at ../sysdeps/unix/syscall-template.S:81
Now I detach immediately and try to attach to the child:
(gdb) detach
Detaching from program:
/home/tromey/firefox-git/gecko-dev/obj-x86_64-unknown-linux-gnu/dist/bin/firefox,
process 8126
[Inferior 8126 detached]
(gdb) attach 8189
Attaching to program:
/home/tromey/firefox-git/gecko-dev/obj-x86_64-unknown-linux-gnu/dist/bin/firefox,
process 8189
Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from
/usr/lib/debug/usr/lib64/ld-2.18.so.debug...done.
done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
0x00007f573f1f171d in ?? ()
gdb can't find the threads or do a stack trace:
(gdb) info thr
Id Target Id Frame
* 1 process 8189 "Web Content" 0x00007f573f1f171d in ?? ()
(gdb) bt
#0 0x00007f573f1f171d in ?? ()
#1 0x0000000000000000 in ?? ()
However, if I quit gdb and attach to the child, it works.
(gdb) attach 8189
Attaching to process 8189
Reading symbols from
/home/tromey/firefox-git/gecko-dev/obj-x86_64-unknown-linux-gnu/dist/bin/plugin-container...done.
[...lots more...]
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-11-19 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 16:19 tromey at sourceware dot org [this message]
2014-11-19 16:36 ` [Bug gdb/17626] " palves at redhat dot com
2014-11-19 21:01 ` tromey at sourceware dot org
2015-05-11 13:42 ` palves at redhat dot com
2015-06-05 13:36 ` tromey at sourceware dot org
2024-01-02 17:23 ` ssbssa at sourceware dot org
2024-01-10 23:20 ` tromey at sourceware dot org
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=bug-17626-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).