public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pastas at learn4good dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30207] New: GDB crashes on processing Apache2 crash dump Date: Tue, 07 Mar 2023 13:57:59 +0000 [thread overview] Message-ID: <bug-30207-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30207 Bug ID: 30207 Summary: GDB crashes on processing Apache2 crash dump Product: gdb Version: 12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: pastas at learn4good dot com Target Milestone: --- Created attachment 14738 --> https://sourceware.org/bugzilla/attachment.cgi?id=14738&action=edit GDB core dump GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1 Architecture: amd64 Command run: gdb /usr/sbin/apache2 CoreDump Then processed GDB core dump of its own and made output which I have attached which I hope is of help. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-03-07 13:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-07 13:57 pastas at learn4good dot com [this message] 2023-03-07 14:22 ` [Bug gdb/30207] " simark at simark dot ca 2023-03-07 18:22 ` pastas at learn4good dot com 2023-03-07 19:54 ` simark at simark dot ca 2023-03-09 19:58 ` pastas at learn4good dot com 2023-03-09 20:21 ` simon.marchi at polymtl dot ca 2023-04-01 18:11 ` pastas at learn4good dot com 2023-04-01 19:14 ` simark at simark dot ca 2023-04-02 6:26 ` pastas at learn4good dot com 2023-04-02 6:27 ` pastas at learn4good dot com 2023-04-02 6:28 ` pastas at learn4good dot com 2023-04-02 18:10 ` simark at simark dot ca
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-30207-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: 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).