[Bug gdb/34390] GDB crashes with "Fatal signal: Segmentation fault" message while trying to generate stack-trace.

tromey at sourceware dot org via Gdb-prs <[email protected]>
Newsgroups gmane.comp.gdb.bugs.discuss
Message-ID <[email protected]/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=34390

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |18.1
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |tromey at sourceware dot org
           See Also|                            |https://bugzilla.redhat.com
                   |                            |/show_bug.cgi?id=2499364

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
The upstream bug was closed as a dup, and the dup says that
this was fixed by

  commit 93f536d813c41527e8c939a5f8a90a4b37a5abab
  Date:   Mon Oct 13 15:11:09 2025 +0100

    gdb/corelow: Fix use-after-free in gdb_read_core_file_mappings

So, I'm going to close this as fixed.

The crash probably doesn't happen on a pristine gdb 17, only the
Fedora one, at least based on the upstream bug and examination of
the commit.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.