On Thu, Jun 16, 2016 at 10:02:52AM -0700, Adrian McCarthy via cfe-dev wrote:
> > Most free and open-source software packages, including MediaWiki, treat
> > versions as a series of individual numbers, separated by periods, with a
> > progression such as 1.7.0, 1.8.0, 1.8.1, 1.9.0, 1.10.0, 1.11.0, 1
| Note that 81 > 8, so those examples would still work.
Right, but also 81 > 9 so that example would not work, if you don't understand
how the project does version numbers.
As different projects work by different rules, I guess the interpretation of
version numbers by other tools would have to b
>Version numbers aren't strings, and they aren't floating point numbers,
they are a series of integers separated by dots. I can't think of a project
where interpreting version numbers that way won't work.
TeX (asymptotically approaches pi), METAFONT (asymptotically approaches e),
Opera (decimal nu
https://llvm.org/bugs/show_bug.cgi?id=27416
Marius Trandafir changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|marius.tranda...@live
https://llvm.org/bugs/show_bug.cgi?id=28156
Todd Fiala changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |apra...@apple.com
--- Comment #1 from Todd Fiala
https://llvm.org/bugs/show_bug.cgi?id=28156
Bug ID: 28156
Summary: TestWithModuleDebugging.py: failing on macOS
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
Status: NEW
Severity: normal
Hello All,
In the context of Intel® Processor Trace support in LLDB I
asked, a while ago, about the syntax of remote packets.
Directions were mixed:
1. Taking GDBSERVER/GDB packets (available from 7.10)
2. Going to a brand new packets for lldb/lldbserve
Bug in cmake (or more likely the makefile?), pure and simple. Version
numbers aren't strings, and they aren't floating point numbers, they are a
series of integers separated by dots. I can't think of a project where
interpreting version numbers that way won't work.
On Wed, Jun 15, 2016 at 7:21 AM,
I'm using lldb to debug the OS X kernel, and it works great.
I would like to have more flexibility in analysing user programs while
debugging the kernel itself,
and specifically symbolicate the code of the user programs.
For example I often use the command showthreaduserstack defined here
http://o
