On Thu, Mar 26, 2009 at 1:34 AM, Stoyan Damov <stoyan.da...@gmail.com>wrote:
> > Now that I can continue working, and being the single developer > experienced this particular crash, and realizing I was being very > harsh to Android engineers tonight, I *want* to help others. > > I can reproduce the crash ALL I want. I just remove a single empty > line in AndroidManifest.xml and the crash occurs. Add the line and the > crash is gone. > can you attach these two files to the bug report? > > Is appt open source, where can I get the source code, and how do I > build it on Windows, so I can debug and fix the bug? > Please follow the instructions here: http://source.android.com/download The aapt sources are located in platform/frameworks/base/tools/aapt > > Cheers > > On Thu, Mar 26, 2009 at 2:17 AM, Stoyan Damov <stoyan.da...@gmail.com> > wrote: > > On Thu, Mar 26, 2009 at 2:09 AM, David Turner <di...@android.com> wrote: > >> > >> > >> On Thu, Mar 26, 2009 at 12:12 AM, Stoyan Damov <stoyan.da...@gmail.com> > >> wrote: > >>> > >>> David, > >>> > >>> I can't provide a way to reproduce the problem. This is not a problem, > >>> it is a crash. It's not like I'm tapping this menu here, and that > >>> button there and something crashes. > >> > >> A crash is a problem. We need the input that aapt receives to be able to > >> reproduce and analyze the crash, otherwise even having the symbols is > not > >> going to help tremendously. > > > > David, give me a break. The tool should have been instrumented in the > > 1st place to catch these crashes (SetUnhandledExceptionFilter and > > MiniDumpWriteDump ring a bell?). > > > >> I understand that you can't send your whole project to the bug tracker, > but > >> can you repeat the crash with a simpler program that you could share ? > >> If this is not possible, what kind of things did you add to reproduce > the > >> crash. Can you remove half of what you added and still reproduce the > crash ? > >> Can you find the exact culprit in your additions ? Does adding even more > >> code, or changing a few things in it gets rid of the crash ? > >> As said previously, if we can't reproduce this, chances of debugging it > are > >> pretty dim. > > > > If you've seen the workaround post you've noticed that I did try to > > change something. > > Actually first I rolled back to what I had in SVN. It worked. I then > > tried to figure out how to start adding the new stuff (I've written > > more than those lines today, and haven't committed) incrementally. And > > then I decided to first check what would happen if I simply remove the > > new activity I've added today from the manifest file, -- the rest you > > can see in the post. > > > > However, make the difference -- this is not a bug report in the lines > > of "aapt.exe crashed". I gave enough (for me at least) information how > > to get from the crash address to the actual culprit code in aapt. > > > > Cheers > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
