public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/16138] layout asm when run from emacs exits gdb complaining "Error opening terminal: emacs"
Date: Tue, 12 Nov 2013 09:49:00 -0000	[thread overview]
Message-ID: <bug-16138-4717-U6jTYgQaxZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16138-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Pedro Alves <palves at redhat dot com> ---
Urgh, this is ncurses itself calling exit.  Reproducing outside of emacs:

$ gdb -q -nx \
  -ex "set env TERM=emacs" \
  -ex "b exit" \
  -ex "r" \
  -ex "bt" \
  --args ./gdb -ex "layout asm" 

...
Error opening terminal: emacs.

Breakpoint 1, __GI_exit (status=1) at exit.c:100
100       __run_exit_handlers (status, &__exit_funcs, true);
#0  __GI_exit (status=1) at exit.c:100
#1  0x000000324d00de43 in initscr () at ../../ncurses/base/lib_initscr.c:89
#2  0x00000000005040da in tui_enable () at ../../src/gdb/tui/tui.c:385
#3  0x00000000004fbfed in tui_layout_command (arg=0x7fffffffdf32 "asm",
from_tty=1) at ../../src/gdb/tui/tui-layout.c:609
#4  0x00000000004dcdfb in do_cfunc (c=0xd9c8c0, args=0x7fffffffdf32 "asm",
from_tty=1) at ../../src/gdb/cli/cli-decode.c:107
#5  0x00000000004dfe90 in cmd_func (cmd=0xd9c8c0, args=0x7fffffffdf32 "asm",
from_tty=1) at ../../src/gdb/cli/cli-decode.c:1882
#6  0x00000000006ea5d9 in execute_command (p=0x7fffffffdf34 "m", from_tty=1) at
../../src/gdb/top.c:467
#7  0x00000000005e53dc in catch_command_errors (command=0x6ea366
<execute_command>, arg=0x7fffffffdf2b "layout asm", from_tty=1,
mask=RETURN_MASK_ALL)
    at ../../src/gdb/exceptions.c:551
#8  0x00000000005e8d17 in captured_main (data=0x7fffffffda30) at
../../src/gdb/main.c:1043
#9  0x00000000005e5306 in catch_errors (func=0x5e7bff <captured_main>,
func_args=0x7fffffffda30, errstring=0x8ab1f4 "", mask=RETURN_MASK_ALL)
    at ../../src/gdb/exceptions.c:524
#10 0x00000000005e8dbb in gdb_main (args=0x7fffffffda30) at
../../src/gdb/main.c:1076
#11 0x000000000045b53a in main (argc=3, argv=0x7fffffffdb38) at
../../src/gdb/gdb.c:34
(gdb)

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


  parent reply	other threads:[~2013-11-12  9:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 16:33 [Bug tui/16138] New: " xdje42 at gmail dot com
2013-11-11 11:36 ` [Bug tui/16138] " palves at redhat dot com
2013-11-11 11:36 ` palves at redhat dot com
2013-11-12  4:47 ` xdje42 at gmail dot com
2013-11-12  9:49 ` palves at redhat dot com [this message]
2013-11-12  9:52 ` palves at redhat dot com
2013-11-12 10:17 ` palves at redhat dot com
2013-11-23 20:28 ` xdje42 at gmail dot com
2013-11-25  9:26 ` palves at redhat dot com
2013-11-25  9:26 ` [Bug tui/16138] TUI commands when run from emacs exit " palves at redhat dot com
2013-12-15 21:40 ` b.r.longbons at gmail dot com
2013-12-16  9:54 ` palves at redhat dot com
2013-12-18  1:42 ` b.r.longbons at gmail dot com
2014-10-29 14:34 ` cvs-commit at gcc dot gnu.org
2014-10-29 14:52 ` cvs-commit at gcc dot gnu.org
2014-10-29 14:53 ` palves at redhat dot com
2014-12-25  0:46 ` cvs-commit at gcc dot gnu.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-16138-4717-U6jTYgQaxZ@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).