public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sourceware at fastmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/28437] New: `fs status` followed by `fs next` fails to switch focus on Mac
Date: Sat, 09 Oct 2021 00:37:03 +0000	[thread overview]
Message-ID: <bug-28437-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28437
           Summary: `fs status` followed by `fs next` fails to switch
                    focus on Mac
           Product: gdb
           Version: 10.1
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: tui
          Assignee: unassigned at sourceware dot org
          Reporter: sourceware at fastmail dot com
  Target Milestone: ---

GDB 10.2 installed from macports, NOT 10.1 (but I don't see it in the list)

Switching focus in tui mode breaks.
To repro:

```
$ gdb -tui ./baseq3/cpma/bin/a.out
Reading symbols from ./baseq3/cpma/bin/a.out...
Reading symbols from
/Applications/ioquake3/baseq3/cpma/bin/a.out.dSYM/Contents/Resources/DWARF/a.out...
(gdb) fs status
Focus set to status window.
(gdb) fs next
/opt/local/var/macports/build/_private_tmp_macports-ports_devel_gdb/gdb/work/gdb-10.2/gdb/tui/tui-data.c:116:
internal-error: struct tui_win_info *tui_next_win(struct tui_win_
info *): Assertion `cur_win->can_focus ()' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

/opt/local/var/macports/build/_private_tmp_macports-ports_devel_gdb/gdb/work/gdb-10.2/gdb/tui/tui-data.c:116:
internal-error: struct tui_win_info *tui_next_win(struct tui_win_
info *): Assertion `cur_win->can_focus ()' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) yAbort trap: 6 (core dumped)
                                                                [Exit 134
(ABRT)]

```
This works with whatever code is being debugged, I repro with a hello world in
C


ADDITIONAL DETAILS
GDB 10.2 installed from macports
Mac OS X Big Sur 11.6
gcc 11.2.0_1 installed from macports
```
$ uname -a
Darwin macbook 20.6.0 Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT
2021; root:xnu-7195.141.6~3/RELEASE_X86_64 x86_64 i386 MacBookPro11,4 Darwin
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin20/11.2.0/lto-wrapper
Target: x86_64-apple-darwin20
Configured with:
/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_gcc11/gcc11/work/gcc-11.2.0/configure
--prefix=/opt/local --build=x86_64-apple-darwin20
--enable-languages=c,c++,objc,obj-c++,lto,fortran,jit
--libdir=/opt/local/lib/gcc11 --includedir=/opt/local/include/gcc11
--infodir=/opt/local/share/info --mandir=/opt/local/share/man
--datarootdir=/opt/local/share/gcc-11 --with-local-prefix=/opt/local
--with-system-zlib --disable-nls --program-suffix=-mp-11
--with-gxx-include-dir=/opt/local/include/gcc11/c++/ --with-gmp=/opt/local
--with-mpfr=/opt/local --with-mpc=/opt/local --with-isl=/opt/local
--enable-stage1-checking --disable-multilib --enable-lto
--enable-libstdcxx-time --with-build-config=bootstrap-debug
--with-bugurl=https://trac.macports.org/newticket --enable-host-shared
--disable-tls --with-as=/opt/local/bin/as --with-ld=/opt/local/bin/ld
--with-ar=/opt/local/bin/ar --with-pkgversion='MacPorts gcc11 11.2.0_1'
--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.2.0 (MacPorts gcc11 11.2.0_1)
$ gdb
(gdb) show config
(gdb) show config
This GDB was configured as follows:
   configure --host=x86_64-apple-darwin20.6.0
--target=x86_64-apple-darwin20.6.0
             --with-auto-load-dir=:${prefix}/share/auto-load
             --with-auto-load-safe-path=:${prefix}/share/auto-load
             --with-expat
             --with-gdb-datadir=/opt/local/share/gdb (relocatable)
             --with-jit-reader-dir=/opt/local/lib/gdb (relocatable)
             --without-libunwind-ia64
             --without-lzma
             --without-babeltrace
             --without-intel-pt
             --without-mpfr
             --without-xxhash
            
--with-python=/opt/local/Library/Frameworks/Python.framework/Versions/3.9
(relocatable)
            
--with-python-libdir=/opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib
(relocatable)
             --without-debuginfod
             --without-guile
             --disable-source-highlight
             --with-separate-debug-dir=/opt/local/lib/debug (relocatable)
```

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

             reply	other threads:[~2021-10-09  0:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09  0:37 sourceware at fastmail dot com [this message]
2021-10-09  1:45 ` [Bug tui/28437] Internal error with `fs status` followed by `fs next` simark at simark dot ca
2021-10-09  1:46 ` simark at simark dot ca
2021-10-09  1:53 ` sourceware at fastmail dot com
2023-02-12 19:57 ` tromey at sourceware dot org
2023-02-15  9:27 ` free_software at fastmail dot com
2023-02-15  9:40 ` free_software at fastmail dot com
2023-02-15 21:42 ` 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-28437-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: 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).