public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "hebm12 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/28552] New: SIGSEGV when tui is enabled, Linux, source-highlight Date: Fri, 05 Nov 2021 18:50:45 +0000 [thread overview] Message-ID: <bug-28552-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28552 Bug ID: 28552 Summary: SIGSEGV when tui is enabled, Linux, source-highlight Product: gdb Version: 11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: hebm12 at gmail dot com Target Milestone: --- Hi, When I launch gdb with the tui enabled I get a segmentation fault. I compiled gdb with source-highlight support in Linux. Here is the backtrace when I launch "gdb --args gdb -tui ls": hread 1 "gdb" received signal SIGSEGV, Segmentation fault. 0x00007ffff74018dd in wnoutrefresh () from /home/hector/spack/opt/spack/linux-ubuntu16.04-ivybridge/gcc-11.2.0/ncurses-6.2-q2y3avovizfplvyqoaw3gwion2ktivmz/lib/libncursesw.so.6 (gdb) bt #0 0x00007ffff74018dd in wnoutrefresh () from /home/hector/spack/opt/spack/linux-ubuntu16.04-ivybridge/gcc-11.2.0/ncurses-6.2-q2y3avovizfplvyqoaw3gwion2ktivmz/lib/libncursesw.so.6 #1 0x00007ffff7401cb7 in wrefresh () from /home/hector/spack/opt/spack/linux-ubuntu16.04-ivybridge/gcc-11.2.0/ncurses-6.2-q2y3avovizfplvyqoaw3gwion2ktivmz/lib/libncursesw.so.6 #2 0x00000000007cfa85 in tui_enable () at /tmp/hector/spack-stage/spack-stage-gdb-11.1-2htjjgz5ehdbcqa4t4hsg5fbfcqumpl6/spack-src/gdb/tui/tui.c:440 #3 0x000000000065f914 in captured_main_1 (context=<optimized out>) at /tmp/hector/spack-stage/spack-stage-gdb-11.1-2htjjgz5ehdbcqa4t4hsg5fbfcqumpl6/spack-src/gdb/main.c:1167 #4 0x000000000066059b in captured_main (data=data@entry=0x7fffffff8220) at /tmp/hector/spack-stage/spack-stage-gdb-11.1-2htjjgz5ehdbcqa4t4hsg5fbfcqumpl6/spack-src/gdb/main.c:1343 #5 gdb_main (args=args@entry=0x7fffffff8250) at /tmp/hector/spack-stage/spack-stage-gdb-11.1-2htjjgz5ehdbcqa4t4hsg5fbfcqumpl6/spack-src/gdb/main.c:1368 #6 0x0000000000436d85 in main (argc=<optimized out>, argv=<optimized out>) at /tmp/hector/spack-stage/spack-stage-gdb-11.1-2htjjgz5ehdbcqa4t4hsg5fbfcqumpl6/spack-src/gdb/gdb.c:32 (gdb) What could be the problem? Thank you for your help, Best, Hector -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-11-05 18:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-05 18:50 hebm12 at gmail dot com [this message] 2021-11-05 18:57 ` [Bug tui/28552] " hebm12 at gmail dot com 2023-02-12 19:59 ` 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-28552-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: linkBe 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).