I spent several hours today trying to get asan to run on Android. Ended up giving up, writing and using a debug version of our allocator to place and check canaries around heap blocks to successfully identify a heap corruption. This was less painful than dealing with Gradle etc.
-
-
To people who are trying to fix this from inside Google - I can imagine you know all this and it’s probably a hard problem in more ways than one and I have seen similar situations and I am sorry. And I worry that at this point it’s too little too late.
এই থ্রেডটি দেখানধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
-
-
This thread was painful to read (as someone who used to work on android dev tools) but I know exactly what you mean. Best I can do is forward it internally though I doubt it will magically fix things.
-
To offer some perspective: I write a lot of native code for android as part of my job these days. I do not have to deal with Gradle, because we just use Bazel. Unfortunately, Bazel wasn't open source when Gradle became a thing.
-
However, I really wish Android would switch to Bazel by default. IMO it would improve things because a) there would be just one build system, and b) it would be the one used internally.
-
P.S.: debugging is still a pain though, gpu debugging included :(
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
লোড হতে বেশ কিছুক্ষণ সময় নিচ্ছে।
টুইটার তার ক্ষমতার বাইরে চলে গেছে বা কোনো সাময়িক সমস্যার সম্মুখীন হয়েছে আবার চেষ্টা করুন বা আরও তথ্যের জন্য টুইটারের স্থিতি দেখুন।