On Thu, Mar 26, 2009 at 2:50 AM, Dianne Hackborn <[email protected]> wrote:
> On Wed, Mar 25, 2009 at 5:44 PM, Stoyan Damov <[email protected]>
>
> Can you please just provide a complete example that doesn't work?  We have
> lots of manifest files with spaces in them.  This isn't enough to help
> reproduce the problem.

I have attached the 2 manifest files to the issue.

>> >> 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.
>> > a crash address is not enough information.
>> In some cases perhaps, in many cases, especially if the code is
>> written with many small functions, as opposed to a few big ones, it's
>> quite enough.
>
> It really doesn't make sense to be treating this as a SUPER SERIOUS MUST BE
> FIXED bug, and push off requests for help.  Doesn't it make sense that it
> would be easier to debug if someone can look at the input files aapt is
> getting to know what it is trying to do?  If it isn't important enough for
> you to spend some of your time helping diagnose the problem, why should
> anyone else believe that it is actually that important?

This is a "super super serious must be fixed asfp" bug because perhaps
tomorrow a CR/LF won't help!
Of course it makes sense that a sample input to the parser would help,
and I did provided one.

I still insist that a crash address is extremely helpful and in many
cases all you need to know to find a bug, but now that you said you
primarily develop on mac, I'm not sure whether gcc's map files are as
useful as VC's ones (although I suspect they are).

> Anyway, I have other work I need to do today, so I'll be looking forward to
> the bug being updated with a repro case.  (Or would love to have a patch for
> aapt submitted that fixes it!)

So did I :(

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to