On Thu, Mar 26, 2009 at 2:50 AM, Dianne Hackborn wrote:
> On Wed, Mar 25, 2009 at 5:44 PM, Stoyan Damov
>
> 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 attache
On Thu, Mar 26, 2009 at 2:42 AM, David Turner wrote:
>
>> 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?
Attached
> Please follow
On Thu, Mar 26, 2009 at 2:43 AM, Dianne Hackborn wrote:
> On Wed, Mar 25, 2009 at 4:59 PM, Stoyan Damov
> wrote:
>>
>> The information I provided (consistent crash address and assembly
>> around it) should be sufficient to any skilled Windows C++ developer
>> to find the bug in 10 minutes, provi
On Thu, Mar 26, 2009 at 1:44 AM, Stoyan Damov wrote:
> I don't have a problem sharing my manifest file, but here's the
> current difference between a manifests with which the app builds, and
> one it doesn't - a SINGLE empty line.
> For example, if my manifest contains these lines:
>
>
>
>
>
> i
On Wed, Mar 25, 2009 at 5:44 PM, Stoyan Damov wrote:
> I don't have a problem sharing my manifest file, but here's the
> current difference between a manifests with which the app builds, and
> one it doesn't - a SINGLE empty line.
> For example, if my manifest contains these lines:
>
>
>
>
Can
On Thu, Mar 26, 2009 at 2:39 AM, Mark Murphy wrote:
>
> Stoyan Damov wrote:
>> It would be nice, if you stopped playing Google's advocate for one day :)
>
> You mean like this:
>
> http://www.networkworld.com/community/node/40044
> http://www.networkworld.com/community/node/39099
> http://www.net
On Thu, Mar 26, 2009 at 2:36 AM, David Turner wrote:
> On Thu, Mar 26, 2009 at 1:17 AM, Stoyan Damov
> As I said previously, we need the input passed to aapt, or at a minimum some
> information about the things that contributed to the crash (e.g. your
> manifest file,
> for example).
I don't
On Wed, Mar 25, 2009 at 4:59 PM, Stoyan Damov wrote:
> The information I provided (consistent crash address and assembly
> around it) should be sufficient to any skilled Windows C++ developer
> to find the bug in 10 minutes, provided that the appt tool was built
> with Microsoft Visual Studio, or
On Thu, Mar 26, 2009 at 1:34 AM, Stoyan Damov 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 ju
Stoyan Damov wrote:
> It would be nice, if you stopped playing Google's advocate for one day :)
You mean like this:
http://www.networkworld.com/community/node/40044
and this:
http://www.networkworld.com/community/node/39099
and this:
http://www.networkworld.com/community/node/38830
and many
On Thu, Mar 26, 2009 at 1:17 AM, Stoyan Damov wrote:
>
> >
> > 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 bee
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 cra
Mark,
It would be nice, if you stopped playing Google's advocate for one day :)
If my game crashes, I'm the ONLY one to suffer the consequences.
If a tool, such as appt crashes, it could seize the development of
unlimited number of development companies (and affect even more
users).
Plus, I do
Stoyan Damov wrote:
> 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?).
To quote yourself:
"Am I supposed to wrap ALL my code in exception handlers? What good if
I do that?"
On Thu, Mar 26, 2009 at 2:09 AM, David Turner wrote:
>
>
> On Thu, Mar 26, 2009 at 12:12 AM, Stoyan Damov
> 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 so
HOW HORRIBLE bug is this?!?!?!
I started experimenting what would happen if I comment out an
activity, and so I did - I commented out a RANDOM activity in
AndroidManifest.xml and WHAT THE ..., the build SUCCEEDED.
And I just sensed that this bug is SO RIDICULOUS that I should
probably remove the
On Thu, Mar 26, 2009 at 12:12 AM, Stoyan Damov 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
On Thu, Mar 26, 2009 at 1:37 AM, Mark Murphy wrote:
>
> Stoyan Damov wrote:
>> I can't provide a way to reproduce the problem.
>
> 1. Create a fresh project.
>
> 2. Copy your entire res/ tree out of your current project into the fresh
> project.
>
> 3. Try building.
Will try. If this helps, I wi
On Mar 25, 4:37 pm, Mark Murphy wrote:
> Stoyan Damov wrote:
> > I can't provide a way to reproduce the problem.
> [... helpful advice elided ...]
>
> Providing steps to reproduce failures, whether in tools or class
> libraries or whatever, has been a standard of professional application
> develo
Stoyan Damov wrote:
> I can't provide a way to reproduce the problem.
1. Create a fresh project.
2. Copy your entire res/ tree out of your current project into the fresh
project.
3. Try building.
If the build crashes, then zip up the new project and attach it to the
issue. Or, try winnowing ou
Actually it might be exactly deferencing a null pointer!
It's possible that I'm mistaken that if the debugger breaks on a line,
the error occurred on the line above.
In this case, the crash would be here:
004363AC mov ecx,dword ptr [ebp-8Ch]
004363B2 cmp word ptr [ecx],7Ch <---
On Thu, Mar 26, 2009 at 1:13 AM, Marco Nelissen wrote:
>
> On Wed, Mar 25, 2009 at 3:38 PM, Stoyan Damov 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
On Wed, Mar 25, 2009 at 3:38 PM, Stoyan Damov 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).
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.
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
thanks, still it would be nice if you could provide a simple example that
exhibits the crash.
On Thu, Mar 26, 2009 at 12:02 AM, Stoyan Damov wrote:
>
> Found the URL for bug submissions, submitted here --
> http://code.google.com/p/android/issues/detail?id=2301
>
> On Thu, Mar 26, 2009 at 12:38 A
Found the URL for bug submissions, submitted here --
http://code.google.com/p/android/issues/detail?id=2301
On Thu, Mar 26, 2009 at 12:38 AM, Stoyan Damov 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
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 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 cr
27 matches
Mail list logo
