Extracting debugging information from core files

like below fixes the issue Here are a few libraries which can be used to parse .sgm files:
SGMLtools-lite BeautifulSoup

around this issue "Limited Debug Information" is an option that only affects the Android targeting compiler. However, since all the compilers share the same interface, this option appears for every target. It only applies to how much debug information goes into each individual object (.o) file. For Android (and iOS), the debug info format is DWARF. DWARF is a very verbose format and can contain highly detailed structural type information about all the types in a given unit and for all the types from all the units "used" by a given unit. Under "Limited Debug Information", the type information for all the used units is not generated. This can mean some field and local variables may not be inspectable while debugging.
As for whether debug information is included into the final executable, that is controlled by the linker option, not by the compiler option. The linker will link whatever debug information is available. If building for Android and "Debug Information" is selected, then the final image will have much more information and be much larger.

help you fix your problem The following may help. I assume that you brought your text to character vector(s)
Data example

ex<-c("The annual observed flow rate: 99.99")

res<-regmatches(ex, regexpr("[0-9]{1,2}.[0-9]{1,2}",ex))

library(cwhmisc)
A<-cpos(ex,"rate", start=1) #position in string
res<-substr(ex, start=A+5, stop=A+9)

ex<-c("The annual observed flow rate: 99.99; the monthly flow rate: 90.03; the weekly observed flow rate: 92.22")
ndat<-unlist(strsplit(ex, "flow"))