public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "marian.buschsieweke at posteo dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30431] segfault when inspecting remote variable
Date: Sat, 03 Jun 2023 21:33:56 +0000	[thread overview]
Message-ID: <bug-30431-4717-3y4rkYotpM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30431-4717@http.sourceware.org/bugzilla/>

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

--- Comment #9 from Marian Buschsieweke <marian.buschsieweke at posteo dot net> ---
> My gdb isn't sending exactly the same remote protocol traffic as yours;

Sorry, this my fault. When I reported the bug I was using version 13.1, but in
the meantime Alpine updated to version 13.2. The remotelogfile was captured
with version 13.2.

$ gdb --version            
GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ gdb --config 
This GDB was configured as follows:
   configure --host=x86_64-alpine-linux-musl --target=x86_64-alpine-linux-musl
            --with-auto-load-dir=$debugdir:$datadir/auto-load
            --with-auto-load-safe-path=$debugdir:$datadir/auto-load
            --with-expat
            --with-gdb-datadir=/usr/share/gdb (relocatable)
            --with-jit-reader-dir=/usr/lib/gdb (relocatable)
            --without-libunwind-ia64
            --without-lzma
            --without-babeltrace
            --without-intel-pt
            --without-mpfr
            --without-xxhash
            --with-python=/usr (relocatable)
            --with-python-libdir=/usr/lib (relocatable)
            --without-debuginfod
            --without-guile
            --disable-source-highlight
            --enable-threading
            --with-separate-debug-dir=/usr/lib/debug (relocatable)

("Relocatable" means the directory can be moved with the GDB installation
tree, and GDB will still find it.)

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

  parent reply	other threads:[~2023-06-03 21:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 21:05 [Bug gdb/30431] New: " marian.buschsieweke at ovgu dot de
2023-05-09 15:01 ` [Bug gdb/30431] " tromey at sourceware dot org
2023-05-09 15:59 ` marian.buschsieweke at ovgu dot de
2023-05-09 16:53 ` marian.buschsieweke at ovgu dot de
2023-06-02  7:19 ` marian.buschsieweke at posteo dot net
2023-06-02 15:06 ` tromey at sourceware dot org
2023-06-03 18:28 ` marian.buschsieweke at posteo dot net
2023-06-03 18:29 ` marian.buschsieweke at posteo dot net
2023-06-03 20:31 ` tromey at sourceware dot org
2023-06-03 21:33 ` marian.buschsieweke at posteo dot net [this message]
2023-06-03 21:35 ` marian.buschsieweke at posteo dot net
2023-06-04 17:25 ` tromey at sourceware dot org
2023-06-04 20:19 ` marian.buschsieweke at posteo dot net
2023-06-20 21:20 ` tromey at sourceware dot org
2023-06-20 21:21 ` tromey at sourceware dot org
2023-07-10 17:19 ` cvs-commit at gcc dot gnu.org
2023-07-10 17:19 ` 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-30431-4717-3y4rkYotpM@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).