This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/18363] New: source line echoing on "next" mysteriously turned off
- From: "jason.vas.dias at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 01 May 2015 12:16:44 +0000
- Subject: [Bug gdb/18363] New: source line echoing on "next" mysteriously turned off
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18363
Bug ID: 18363
Summary: source line echoing on "next" mysteriously turned off
Product: gdb
Version: 7.7
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: jason.vas.dias at gmail dot com
Target Milestone: ---
With fully up-to-date Ubuntu 14.04.2 LTS @2015-05-01 's GDB
7.7.1-0ubuntu5~14.04.2 , this sequence of input somehow turned
off echoing of input source lines, and I cannot understand why:
At this point, gdb is still echoing source lines with the 'n' / 'next' command:
(gdb) n
233 if( i == Q_MSG_DURATION )
(gdb) p (p - &buf[0])
$20 = 140
(gdb) p *((char[140]*)buf)
$21 = "INSERT INTO quantiles VALUES( 1, 2, 0, 3, 2, 18, 419.362526251996 ,
15 , 1 , 469.946678558381 , 1 , 0 , 678.247236170935 , 7.73105044050213 "
But now it isn't - what did I do to turn it off ? Now only the source line
numbers are echoed on 'next' ( there were no intervening input lines between
the last one shown above and this 'next'):
(gdb) n
290
(gdb)
301
(gdb)
293
(gdb) n
300
(gdb)
293
(gdb)
299
(gdb)
293
I can't find any setting documented that turns echoing of source lines on or
off on 'next' .
I had previously done :
(gdb) set print elements 0
to print whole arrays ( I now know I should have used 'set print null-stop
on').
But I can't understand how these settings would have effected source line
echoing or how a few print commands could turn off source line echoing .
Is there a setting that turns source line echoing on 'next' on or off that
I might have inadvertently set ?
--
You are receiving this mail because:
You are on the CC list for the bug.