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. 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. > > I can't possibly know how and what the aapt tool does. Like I said, I > added probably 50 lines of code tops, tried to build and the tool > crashed. > I did try to rollback the code (as I think it was), but it didn't > help. I deleted the bin folder again to no avail. > > David, I just saw your next post. What syntax are you interested in? > I'm just building from Eclipse with the default SDK 1.1 installation, > I'm not passing any extra parameters to aapt. > > I don't understand what's the big deal for the tool's developer to > just open the .map file of the release build (provided that he created > such file), find the function near the crash address and see what's > the problem. > I understand that if the appt tool implements a parser or something > which has been partly code-gen'ed by another tool, which has generated > functions with thousands of lines of code it will be a lot more > difficult, but if that's not the case, finding the bug should be a > matter of minutes. > > In the mean time I'll rollback my code from version control and will > try re-adding and rebuilding until I see what causes the tool to > crash. > > On Thu, Mar 26, 2009 at 1:02 AM, David Turner <di...@android.com> wrote: > > It would be better if you could provide a way to reproduce the problem. > > try b.android.com to report the problem > > > > On Wed, Mar 25, 2009 at 11:38 PM, Stoyan Damov <stoyan.da...@gmail.com> > > wrote: > >> > >> This is a showstopper, and I'm experiencing for the 2nd time. > >> > >> Shouldn't be hard to find, if the apt tool developers have created a > >> .map file for the release build. > >> It seems like the dev has dereferenced a null pointer (see below). > >> > >> I didn't do anything fancy. Just added a dozen lines of code and tried > >> to build. I don't remember the URL for bug reports, so here it is. If > >> Mark's not lazy, he could file the bug ;) > >> > >> Environment: WinXP SP2, Eclipse 3.4.1, SDK 1.1 > >> > >> Stack trace -- useless to me, but that's what you get for not shipping > >> symbols (lack of Windows symbols is my bad but I reinstalled my > >> machine fairly recently and didn't need them). > >> > >> > aapt.exe!004363b2() > >> [Frames below may be incorrect and/or missing, no symbols loaded > >> for > >> aapt.exe] > >> ntdll.dll!7c9106eb() > >> aapt.exe!0040df1c() > >> aapt.exe!0043a05c() > >> aapt.exe!0040dd14() > >> ntdll.dll!7c9106eb() > >> aapt.exe!0043a05c() > >> ... > >> > >> Assembly around the crash: > >> > >> 0043638F jae 004363B8 > >> 00436391 cmp word ptr [edx],7Ch > >> 00436395 jmp 004363B6 > >> 00436397 add dword ptr [ebp-8Ch],2 > >> 0043639E mov edx,dword ptr [ebp-88h] > >> 004363A4 cmp dword ptr [ebp-8Ch],edx > >> 004363AA jae 004363B8 > >> 004363AC mov ecx,dword ptr [ebp-8Ch] // *ecx is 0 (see below) > >> 004363B2 cmp word ptr [ecx],7Ch <----------- breaks here, > >> crash is on mov above > >> 004363B6 jne 00436397 > >> 004363B8 xor edx,edx > >> 004363BA mov edi,eax > >> > >> Registers: > >> > >> EAX = 00FC79DC EBX = 00000053 ECX = 012FA000 EDX = 012FA008 ESI = > >> 012F9F50 EDI = 00FC7A5C EIP = 004363B2 ESP = 0022F5F0 EBP = 0022F6A8 > >> EFL = 00000293 > >> > >> 012FA000 = ???? > >> > >> Memory around ECX: > >> > >> 0x012F9F50 6d 00 63 00 63 00 7c 00 6d 00 6e 00 63 00 7c 00 6c 00 6f > >> 00 63 00 61 00 6c 00 65 00 7c 00 74 00 6f 00 75 00 63 00 68 00 73 00 > >> 63 00 m.c.c.|.m.n.c.|.l.o.c.a.l.e.|.t.o.u.c.h.s.c. > >> 0x012F9F7C 72 00 65 00 65 00 6e 00 7c 00 6b 00 65 00 79 00 62 00 6f > >> 00 61 00 72 00 64 00 7c 00 6b 00 65 00 79 00 62 00 6f 00 61 00 72 00 > >> 64 00 r.e.e.n.|.k.e.y.b.o.a.r.d.|.k.e.y.b.o.a.r.d. > >> 0x012F9FA8 48 00 69 00 64 00 64 00 65 00 6e 00 7c 00 6e 00 61 00 76 > >> 00 69 00 67 00 61 00 74 00 69 00 6f 00 6e 00 7c 00 6f 00 72 00 69 00 > >> 65 00 H.i.d.d.e.n.|.n.a.v.i.g.a.t.i.o.n.|.o.r.i.e. > >> 0x012F9FD4 6e 00 74 00 61 00 74 00 69 00 6f 00 6e 00 7c 00 66 00 6f > >> 00 6e 00 74 00 53 00 63 00 61 00 6c 00 65 00 00 00 30 00 00 00 00 00 > >> 00 00 n.t.a.t.i.o.n.|.f.o.n.t.S.c.a.l.e...0....... > >> 0x012FA000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > >> 00 00 ............................................ > >> 0x012FA02C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > >> 00 00 ............................................ > >> 0x012FA058 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > >> 00 00 ............................................ > >> > >> *PLEASE*, fix this ASAP :( > >> > >> > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
