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 c++/30045] GDB crashes when command is used during layout
Date: Wed, 25 Jan 2023 01:52:36 +0000 [thread overview]
Message-ID: <bug-30045-4717-ThTIp0iX3Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30045-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30045
--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
Sorry, I'm not totally sure. I'm not a windows expert and when
I do debug on windows I use cygwin and just use 'ps'.
Another option is to debug gdb with itself:
gdb gdb
(gdb) set prompt (outer) # <- make sure you put a space after that paren :)
(outer) run /your/program
(gdb) # in the inner gdb, reproduce the bug...
(outer) bt
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-25 1:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 20:49 [Bug c++/30045] New: " mmoskow1 at stevens dot edu
2023-01-24 20:49 ` [Bug c++/30045] " mmoskow1 at stevens dot edu
2023-01-24 21:53 ` tromey at sourceware dot org
2023-01-24 22:36 ` mmoskow1 at stevens dot edu
2023-01-24 23:17 ` tromey at sourceware dot org
2023-01-25 0:42 ` mmoskow1 at stevens dot edu
2023-01-25 1:52 ` tromey at sourceware dot org [this message]
2023-01-25 2:15 ` mmoskow1 at stevens dot edu
2023-01-25 2:16 ` mmoskow1 at stevens dot edu
2023-01-25 18:26 ` mmoskow1 at stevens dot edu
2023-01-26 19:33 ` mmoskow1 at stevens dot edu
2023-01-26 20:11 ` tromey at sourceware dot org
2023-01-26 22:59 ` mmoskow1 at stevens dot edu
2023-01-28 19:28 ` ssbssa at sourceware dot org
2023-01-28 23:49 ` mmoskow1 at stevens dot edu
2023-01-30 17:04 ` mmoskow1 at stevens dot edu
2023-01-30 17:22 ` ssbssa at sourceware dot org
2023-01-30 20:02 ` mmoskow1 at stevens dot edu
2023-02-05 0:24 ` mmoskow1 at stevens dot edu
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-30045-4717-ThTIp0iX3Z@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).