public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30207] GDB crashes on processing Apache2 crash dump
Date: Tue, 07 Mar 2023 19:54:41 +0000	[thread overview]
Message-ID: <bug-30207-4717-py8enbdhRq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30207-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30207

--- Comment #3 from Simon Marchi <simark at simark dot ca> ---
Ah, that's unfortunate, it must be that the dbgsym package is out of date.

Alternatively, you can build GDB yourself, it's quite simple, just ./configure
&& make.  There are only a few dependencies that are very common packages.

Another option would be for you to upload your executable and core, see if
somebody else can reproduce.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-03-07 19:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 13:57 [Bug gdb/30207] New: " pastas at learn4good dot com
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 [this message]
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-py8enbdhRq@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).