This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug python/14513] New: setting extended-prompt triggers spuriousnewline to be emitted


http://sourceware.org/bugzilla/show_bug.cgi?id=14513

             Bug #: 14513
           Summary: setting extended-prompt triggers spurious newline to
                    be emitted
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: minor
          Priority: P2
         Component: python
        AssignedTo: unassigned@sourceware.org
        ReportedBy: vapier@gentoo.org
    Classification: Unclassified


$ gdb -nx -q
(gdb) set extended-prompt (gdb-new) 

(gdb-new) 

what's with that newline after the set command ?  if i do the same thing with
my .gdbinit:
set extended-prompt (gdb-new) 

when i launch gdb, i get:
$ gdb -q

(gdb-new) 

looking at the code, it appears to be coming from python/py-param.c's
get_set_value:
  fprintf_filtered (gdb_stdout, "%s\n", set_doc_string);

the set_doc_string here is empty, so we just get an empty newline printed out.

i've never looked through the python code before to suggest a suitable fix ...

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]