From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: FYI: fix PR gdb/8869
Date: Fri, 07 Aug 2009 22:16:00 -0000 [thread overview]
Message-ID: <200908072305.39587.pedro@codesourcery.com> (raw)
In-Reply-To: <m363czcq4p.fsf@fleche.redhat.com>
Thanks!
We now trip on this snag though:
(gdb) set language f<TAB>ortran<ENTER>
Unknown language `fortran '.
(top-gdb) set language a<TAB>uto<ENTER>
Unknown language `auto '.
This works, because there's c++ in the list, so no extra
space:
(gdb) set language c<TAB><ENTER>
I guess this would go away automaticaly if this command
was a real enum command.
(gdb) set language <TAB>
ada auto c++ java minimal objective-c scheme
asm c fortran local modula-2 pascal unknown
Eh, I hadn't realized we were able to set "unknown" manually,
"set language" doesn't show it:
(gdb) set language
The currently understood settings are:
local or auto Automatic setting based on source file
ada Use the Ada language
c Use the C language
c++ Use the C++ language
asm Use the Asm language
minimal Use the Minimal language
fortran Use the Fortran language
objective-c Use the Objective-c language
java Use the Java language
modula-2 Use the Modula-2 language
pascal Use the Pascal language
scheme Use the Scheme language
--
Pedro Alves
next prev parent reply other threads:[~2009-08-07 22:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 20:48 Tom Tromey
2009-08-07 22:05 ` Tom Tromey
2009-08-07 22:16 ` Pedro Alves [this message]
2009-08-07 22:29 ` Tom Tromey
2009-08-08 1:55 ` Tom Tromey
2009-08-08 16:17 ` Pedro Alves
2009-08-08 16:39 ` Pedro Alves
2009-08-08 18:08 ` Pedro Alves
2009-08-12 23:00 ` Tom Tromey
2009-08-13 17:06 ` Pedro Alves
2009-08-13 17:34 ` Eli Zaretskii
2009-08-13 18:30 ` Pedro Alves
2009-08-08 8:37 ` Eli Zaretskii
2009-08-10 17:59 ` Tom Tromey
2009-08-10 19:38 ` Eli Zaretskii
2009-08-10 19:59 ` Tom Tromey
2009-08-10 20:10 ` Eli Zaretskii
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=200908072305.39587.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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