public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "marc.khouzam at ericsson dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/16360] Provide a --shortversion flag Date: Tue, 14 Jan 2014 15:00:00 -0000 [thread overview] Message-ID: <bug-16360-4717-prBCiifC3E@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16360-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16360 --- Comment #2 from Marc Khouzam <marc.khouzam at ericsson dot com> --- (In reply to Tom Tromey from comment #1) > I'm curious why you use versions and what you use them for. Eclipse CDT bases itself on the GDB version to know what features are available or not. For example, Reverse debugging will only be possible to enable if we are dealing with GDB version >= 7.0; multi-process needs >= 7.2; showing information on cores needs >= 7.1 > On the whole I think it would be better if you could use > feature tests instead. Yes, the solution we use works for FSF GDB but will not work so well for any modified GDB. However, I'm not sure there is a reliable way to figure out feature availability for everything CDT uses from GDB. Futhermore, there are many drawbacks to test for features in a 'brute force' fashion: error printouts visible to the user (or the complexity of silencing them), affecting the GDB state, delayed startup time to run through the many feature tests. > In theory I think the allowable versions are defined in the > internals manual: https://sourceware.org/gdb/wiki/Internals%20Versions > I'm afraid I don't know how closely reality conforms to this. > Also see the vendor branch page: > https://sourceware.org/gdb/wiki/Internals%20Vendor-Branches Over the years, this is the list of formats we've seen in the wild. GNU gdb 6.8.50.20080730 GNU gdb (GDB) 6.8.50.20080730-cvs GNU gdb (Ericsson GDB 1.0-10) 6.8.50.20080730-cvs GNU gdb (GDB) Fedora (7.0-3.fc12) GNU gdb 6.8.0.20080328-cvs (cygwin-special) GNU gdb 7.0 GNU gdb Fedora (6.8-27.el5) GNU gdb Red Hat Linux (6.3.0.0-1.162.el4rh) GNU gdb (GDB) STMicroelectronics/Linux Base 7.4-71 [build Mar 1 2013] and then there's Apple's GDB, but I'm not sure this one has a future: GNU gdb 6.3.50-20050815 (Apple version gdb-696) (Sat Oct 20 18:20:28 GMT 2007) GNU gdb 6.3.50-20050815 (Apple version gdb-966) (Tue Mar 10 02:43:13 UTC 2009) GNU gdb 6.3.50-20050815 (Apple version gdb-1346) (Fri Sep 18 20:40:51 UTC 2009) GNU gdb 6.3.50-20050815 (Apple version gdb-1461.2) (Fri Mar 5 04:43:10 UTC 2010) GNU gdb 7.0 (Apple version gdb-1) (Fri Sep 18 20:40:51 UTC 2009) GNU gdb 7.0-20050815 (Apple version gdb-01) (Fri Sep 18 20:40:51 UTC 2009) Having a --shortversion option would reduce the risk of some unexpected format with special characters or interchanged ordering. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-01-14 15:00 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-20 20:19 [Bug gdb/16360] New: " marc.khouzam at ericsson dot com 2013-12-20 20:20 ` [Bug gdb/16360] " marc.khouzam at ericsson dot com 2014-01-14 14:43 ` tromey at redhat dot com 2014-01-14 15:00 ` marc.khouzam at ericsson dot com [this message] 2015-06-12 12:51 ` antoine.tremblay at ericsson dot com 2015-06-12 12:54 ` antoine.tremblay at ericsson dot com 2015-06-12 12:54 ` antoine.tremblay at ericsson dot com
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=bug-16360-4717-prBCiifC3E@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).