public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30207] GDB crashes on processing Apache2 crash dump
Date: Thu, 09 Mar 2023 20:21:53 +0000	[thread overview]
Message-ID: <bug-30207-4717-lc110pqhDq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30207-4717@http.sourceware.org/bugzilla/>

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

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simon.marchi at polymtl dot ca

--- Comment #5 from Simon Marchi <simon.marchi at polymtl dot ca> ---
(In reply to Erlandas from comment #4)
> Have removed version 12.1 which comes with "apt install gdb"
> 
> Built version 13.1 from source. But I do not see gdb-dbgsym executable. Am I
> missing something or did I have to build it with some additional config?

If you build it from source, you wouldn't use the dbgsym package.  The dbgsym
packages contain debug info matching the binaries distributed in the distro
packages.

When configuring (./configure) GDB, pass:

  CFLAGS="-g -O0" CXXFLAGS="-g -O0"

That will make it build with no optimizations (it will be slower, but easier to
debug) and with debug info directly inside the binary.

Btw, since you are using Ubuntu 22.04, you could have also configured the
top-level GDB to use debuginfod, as described here:

https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Debuginfod

This is pretty cool, it makes GDB download debug info for distro packages
transparently, when it needs it.

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

  parent reply	other threads:[~2023-03-09 20:21 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
2023-03-09 19:58 ` pastas at learn4good dot com
2023-03-09 20:21 ` simon.marchi at polymtl dot ca [this message]
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-lc110pqhDq@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).