![]() Teapot gives the following build error:Įxecution failed for task ':GameApplication:configureNinjaDebugGameApplication'. Following the directions got all of them to work except for Teapot. The samples page ( ) has instructions to get each sample working. I was expecting the samples to build out-of-the-box, but I don't think that is the intention. It turns out that it was sort of user error. I got swamped at work and haven't had time to respond.Ĭan you include an example so we can pass that on? TL DR: you could try this, but it's not for the faint of heart! (iirc the last gdb update i did took me a couple of weeks to get something that mostly worked, and i already had the pieces lying around from the previous update :-( ) specifically for your case, we had mixed results debugging clang-built code with gdb (or gcc-built code with lldb) sometimes it works, sometimes it fails obviously, sometimes it fails subtly. ![]() one thing we learned in the course of our llvm transition is that - although things like DWARF are theoretically standardized - in practice, a compiler and its associated tools co-evolve to only really support each other. iirc, it doesn't even build out of the box with a current NDK, and even if you get past that, it's missing support for the domain sockets stuff that we used to be able to debug despite the various security restrictions.Īnd even if you get past those hurdles (which, though non-trivial, is doable if you're brave enough, you can reverse engineer our last patches by diffing the NDK r23 source against the corresponding gdb version, and then port those to the current gdb). we only ever cross-compile from Linux.Īdditionally, we were never able to get upstream gdb to take our Android support patches. On Windows? we don't even build the Windows clang on Windows. In the meanwhile, can you point me to any resources for download or building an updated gdb+gdbserver for Android on Windows? What process were you guys using? Thanks! (given how much IDE developers seem to prefer lldb, i'd assume they also have lldb support ready and waiting, and only used gdb for Android for historical reasons?) I've updated my Visual Studio support issue to request that they update their tools to use lldb or to distribute their own gdb+gdbserver builds for Android. Affected versionsĪh, thanks so much for the help. Incidentally, I have a simple test app to demonstrate the issue if that is helpful for you guys. Given that native Android apps need to run on a non-UI thread, this bug makes it terribly difficult to get my game engine code ported to Android. Thanks so much for any information you can give me on this issue. Is that correct? If so, does that mean that the NDK is dropping support for gdbserver? If so, I can request that Visual Studio update their Android support package to use that instead. The debug output window seemed to indicate that Android Studio was using lldbserver instead of gdbserver. Incidentally, tried reproducing this issue in Android Studio, but it worked just fine. Visual Studio seems to be using adb to communicate with gdbserver, although I'll admit that I'm not terribly familiar yet with specifically how all that works, so I could be mistaken. Visual Studio is currently getting those from NDK 620, which I also have installed. ![]() I'm currently using NDK 393, although that version doesn't seem to contain any prebuilt gdbserver app files. ![]() It looks like Visual Studio is simply deploying the gdbserver version from the NDK, so now I'm here to ask if you guys can update that version. I originally filed a bug with Visual Studio support ( ), who sent me over to Sourceware support ( ), who diagnosed the error as my gdb version being out-of-date. The reason is that it encounters an unhandled-command error from gdbserver: "Call Frame Instruction op 45 in vendor extension space is not handled on this architecture." I'm currently seeing an issue where Visual Studio's debugger will crash when hitting a breakpoint on a non-UI thread (the UI thread works just fine). I'm using Visual Studio's Android support, which relies on Android NDK build and debug tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |