Bug 14502 - Identify version
Summary: Identify version
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: unknown
: P2 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-21 12:50 UTC by Andre'
Modified: 2012-08-21 15:06 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andre' 2012-08-21 12:50:17 UTC
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.
Comment 1 Andreas Schwab 2012-08-21 14:57:04 UTC
This information is supposed to be availble from gdb/NEWS.
Comment 2 Andre' 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.