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/31008] „Layout” crashes gdb 13.2 Date: Mon, 30 Oct 2023 19:46:12 +0000 [thread overview] Message-ID: <bug-31008-4717-SZNdj6CQfj@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31008-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31008 --- Comment #4 from Tom Tromey <tromey at sourceware dot org> --- strace shows a trace of system calls that gdb uses. Unfortunately this isn't very useful for diagnosing this particular problem. What's needed instead is a stack trace at the point of the crash. (It isn't guaranteed this will help but it might.) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-30 19:46 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-30 12:03 [Bug gdb/31008] New: " zbigniew2011 at gmail dot com 2023-10-30 13:06 ` [Bug gdb/31008] " zbigniew2011 at gmail dot com 2023-10-30 14:20 ` tromey at sourceware dot org 2023-10-30 15:49 ` zbigniew2011 at gmail dot com 2023-10-30 19:46 ` tromey at sourceware dot org [this message] 2023-10-30 20:22 ` zbigniew2011 at gmail dot com 2023-10-31 17:20 ` tromey at sourceware dot org 2023-10-31 17:25 ` zbigniew2011 at gmail dot com 2023-11-02 8:47 ` zbigniew2011 at gmail dot com 2023-11-02 12:19 ` tromey at sourceware dot org 2023-11-03 15:40 ` zbigniew2011 at gmail dot com 2023-11-05 16:09 ` tromey at sourceware dot org 2023-11-05 17:00 ` zbigniew2011 at gmail dot com 2023-11-05 18:10 ` tromey at sourceware dot org 2023-11-05 18:18 ` zbigniew2011 at gmail dot com 2023-11-05 19:26 ` tromey at sourceware dot org 2023-11-05 19:45 ` zbigniew2011 at gmail dot com 2023-11-05 22:49 ` tromey at sourceware dot org 2023-11-06 8:48 ` zbigniew2011 at gmail dot com 2023-11-08 9:18 ` zbigniew2011 at gmail dot com 2023-11-10 22:04 ` 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-31008-4717-SZNdj6CQfj@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: linkBe 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).