From: Jelle de Jong <jelledejong@powercraft.nl>
To: gdb@sourceware.org
Subject: how can i stop a running process to do a backtrace?
Date: Sat, 19 Jul 2008 15:00:00 -0000 [thread overview]
Message-ID: <488200CC.6000900@powercraft.nl> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
My name is Jelle and i am new to this list, so thanks you for all the
hard work everybody is doing on the gdb debugger.
I have a problem with freezing sshfs mounts on my systems, so I wanted
to debug the sshfs system.
I contacted the fuse-devel mailinglist and ask them how I could help to
create some usefull bug reports, they told me to do some backtrace with
gdb: (the archive does not seem to be working on this moment)
Message-ID: <487C568C.4010504@powercraft.nl>
https://lists.sourceforge.net/lists/listinfo/fuse-devel
I use debian sid and there were no sshfs-dbg packages, so I created a
bug-report and attached my debdiff and new deb packages:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491210
I now wanted to run my gdb in the following way:
pidof sshfs
1948
gdb 2>&1 | tee gdb-sshfs.txt
(gdb) handle SIG33 pass nostop noprint
(gdb) set pagination 0
(gdb) attach 1948
(gdb) continue
# ok how to stop the continue command so i can do a backtrace?
# kill 1948 wil stop the process but leaves no traceabale info
(gdb) backtrace full
(gdb) info registers
(gdb) thread apply all backtrace
(gdb) quit
But when the gdb is in "Continue" mode and the sshfs is freezing i want
to go back to gdb and do a backtrace its still in "Continue" mode and i
cant do anything. If i kill sshfs then there is no backtrace information
left. So how can i get debug information out of my frozen sshfs program?
I asked this question today on the IRC channel with an exception of hlep
from "jeremybennett" nobody was there. So i decided to send this mail.
I hope somebody can help me?
Best regards,
Jelle
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iJwEAQECAAYFAkiCAMoACgkQ1WclBW9j5HnhegQAjKoIl1zAAtR+bPFYJlinZLK1
KOKXCBvceuk1ri6neb3aGK/RsWtKf63hP4VLrdT8Gh6Aif5GWAR6ojhe7HI5yrKl
1roeSf4/0rPSpgY7coIopcsgcKBLAqMxpXdD/sbw6clLMOcE5pIn3+5BbvjW1Z0V
V7o+q7CXqgJUg3Gy0KY=
=Poet
-----END PGP SIGNATURE-----
next reply other threads:[~2008-07-19 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 15:00 Jelle de Jong [this message]
2008-07-19 15:04 ` Daniel Jacobowitz
2008-07-19 16:37 ` Jelle de Jong
2008-07-19 18:25 ` Paul Pluzhnikov
2008-07-20 23:37 ` Jelle de Jong
2008-07-21 3:43 ` Paul Pluzhnikov
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=488200CC.6000900@powercraft.nl \
--to=jelledejong@powercraft.nl \
--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