This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug mi/15596] New: emacs interface with "gdb -i=mi" hangs on quoted newlines
- From: "stolfi at ic dot unicamp.br" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 07 Jun 2013 03:25:56 +0000
- Subject: [Bug mi/15596] New: emacs interface with "gdb -i=mi" hangs on quoted newlines
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15596
Bug ID: 15596
Summary: emacs interface with "gdb -i=mi" hangs on quoted
newlines
Product: gdb
Version: 7.5
Status: NEW
Severity: normal
Priority: P2
Component: mi
Assignee: unassigned at sourceware dot org
Reporter: stolfi at ic dot unicamp.br
I am running GDB 7.5 (Fedora 7.5.1-38.fc18) under emacs 24.2.1
(x86_64-redhat-linux-gnu, GTK+ Version 3.6.4) with the default command META-x
gdb ENTER ("gdb -i=mi")
It seems that GDB command lines that end with "\" just before the newline are
mishandled. The debugger apparently ignores the entire line.
For example, after loading the target program, try starting it with the command
line
(gdb) run FOO BAR \
BAZ QUX
and finish with an unquoted newline (ENTER). The response is
Undefined command: "BAZ". Try "help".
(gdb)
and the target program is NOT started.
This behavior is rather annoying since my target programs often have lots of
arguments and are executed from Makefiles by multiline commands with
backlash-quoted newlines, like
./myprogram \
-source s1_bl1 \
-subject 001 \
-outPrefix out/split \
-framesPerRun 5400 \
-firstRun 001 \
-pulsesPerRun 4 \
-trigger TR -nElectrodes 20 \
-fSampling 600 \
< foo.txt
With some older version of GBD I could simply copy-paste the command arguments
above from the "*compilation*" buffer to the GDB buffer and hit ENTER. Now I
have to manually remove the backslashes every time.
--
You are receiving this mail because:
You are on the CC list for the bug.