search for: curlybracket

On 29 July 2015 at 23:11, Ben Pye <ben at curlybracket.co.uk> wrote: > 4.8.4, again packaged from Ubuntu 14.04 LTS, not sure if they include any > patches that'd change this behaviour. This should be similar to 4.8.2 that I have, so no worries there. cheers, --renato

> There are a lot of Windows folks in LLVM, and certainly good support > for it, including on ARM, so maybe that would get more traction and > even get done quicker than trying to debug here a problem in an > external library. Even though you want your CoreCLR to work on > Android, I assume this will be mainly developed from a Windows IDE, so > IDE folks that know a thing or two

...much higher priority currently) and sorry for not being responsive. I will look into this soon. But there is no estimation on the work time. Regards, Logan On Thu, Jul 30, 2015 at 6:17 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 29 July 2015 at 23:11, Ben Pye <ben at curlybracket.co.uk> wrote: > > 4.8.4, again packaged from Ubuntu 14.04 LTS, not sure if they include any > > patches that'd change this behaviour. > > This should be similar to 4.8.2 that I have, so no worries there. > > cheers, > --renato > _________________________________...

On 29 July 2015 at 22:46, Ben Pye <ben at curlybracket.co.uk> wrote: > I certainly understand the issue in using PathScale's libunwind, but the > lack of unw_get_save_loc is somewhat problematic and means that it is > preferable to use the other libunwind within coreclr. Or, you could try to persuade people to implement that in LLVM?...

On 29 July 2015 at 22:20, Ben Pye <ben at curlybracket.co.uk> wrote: > Not sure if you got the other message, I think I managed to split the topic > as I wasn't subscribed to receive the previous message. This error has been > on the Raspberry Pi 2, so that's a Cortex A7 I believe, certainly ARMv7. Excellent! > I > haven...

> You should also realise that using another libunwind makes matters > more complex, because now it's far less likely that the LLVM's > libunwind folks will be interested in fixing that... I certainly understand the issue in using PathScale's libunwind, but the lack of unw_get_save_loc is somewhat problematic and means that it is preferable to use the other libunwind within

> Yes, so, that's yet another missing info. Which ARM? RaspberyPi, > although popular, is a very old and somewhat deprecated architecture > (ARMv6). Most people work on ARMv7 and ARMv8 nowadays, so if you can't > reproduce the bugs on those, you'll have a hard time finding people to > help you. > Also, Clang 3.6 is not that old, but we don't really provide >

Sorry for the time it has taken me to reply. Looking at what you have said though Renato, I would think that you are perhaps using LLVMs libunwind? I have been using the libunwind packaged in Ubuntu 14.04 as that is the target platform currently, but I believe it should (more or less), be the same as https://github.com/pathscale/libunwind/tree/pathscale/ . In addition to that you will want to