[Bug gdb/14502] New: Identify version

[Bug gdb/14502] New: Identify version

[andre.poenitz at nokia dot com]

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

             Bug #: 14502
           Summary: Identify version
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: andre.poenitz@nokia.com
    Classification: Unclassified


When implementing a gdb frontend one needs to stay aware of which versions of
gdb support a feature directly, for which there are workarounds, and which
won't work at all. For that it would be nice if the documentation for specific
options would contain a hint saying which is the first version of gdb
supporting that option. A short "(since 7.2)" or similar would be sufficient.

Right now it is seemingly needed to check out the source from git, find the
implementation of the option, git blame the file, and make an educated guess
based on the commit date. In the documentation of other projects that kind of
information is immediately available.

-- 
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.

[Bug gdb/14502] Identify version

[schwab@linux-m68k.org]

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

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> 2012-08-21 14:57:04 UTC ---
This information is supposed to be availble from gdb/NEWS.

-- 
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.

[Bug gdb/14502] Identify version

[andre.poenitz at nokia dot com]

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

--- Comment #2 from Andre Poenitz <andre.poenitz at nokia dot com> 2012-08-21 15:06:22 UTC ---

If that's the intention, it does not seem to work like this.
The only entry related to break-insert I can see is for 6.8

  * The -break-insert MI command can optionally create pending
    breakpoints now.

which is _probably_ related to the -f option. Neither is this -f
mentioned explicitly, nor are the other ones mentioned at all.

-- 
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.