[lldb-dev] "bad_alloc" crash after downloading dependent modules.
labath at google.com
Wed Jun 10 10:18:30 PDT 2015
Thanks for the report. android-arm is not as stable as we would like
it to be, but we are actively working on changing that. Could you
provide us with more information about your setup:
- which android version/device are you encountering this on (try
running "adb bugreport")?
- which application are you attaching this to (if possible, send me an apk)
ps: these things can be big, so feel free to send it to me privately
On 10 June 2015 at 08:12, Aidan Dodds <aidan at codeplay.com> wrote:
> Hi Folks,
> I have been seeing a crash when connecting lldb tip to a remote arm
> lldb-server platform running on android.
> The crash occurs directly after all the remote modules have been downloaded.
> I have attached a transcript of a session which shows the error and displays
> a backtrace after the crash.
> The same crash can be reproduced on both linux and windows.
> Might I be doing something wrong with my setup / build?
> Is 32bit Arm + Android a stable target for lldb / lldb-server or is this
> somewhat unstable?
> I should point out that if I connect to lldb-server in gdbserver mode rather
> then platform this problem doesn't present itself.
> That's perhaps because in that case the platform defaults to remote-linux
> rather then remote-android.
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
More information about the lldb-dev