std::bad_alloc in snappy_unittest

[GoogleCodeExporter]

I want to test how snappy performs against other compression librarys. I saw 
that there is support fo this. Because there seems no windows support and it 
looks complicated to compile with all librarys on windows, I tested in a Linux 
Mint Debian VM.

After compiling snappy, the test terminates after a std::bad_alloc exception.
I recompiled without everything (even without google-test and gflags)
The result is the same (minus the gtest table)

I have the output of snappy_unittest and configure attached.

Original issue reported on code.google.com by josef.schneider on 24 Mar 2011 at 11:44

Attachments:

• test.txt
• config.log

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[reposting from the right user again]

Hi,

What architecture is this on? I'm unable to verify it on 32-bit and 64-bit x86. 
What GCC version does Linux Mint use?

Note that the latest checkouts from Subversion should support Windows just fine.

Original comment by se...@google.com on 24 Mar 2011 at 11:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It is a virtual x86 32bit System on a x86-64 host.
The GCC Version is gcc (Debian 4.5.2-4) 4.5.2
Mint Debian is basically debian testing with a few additions.

I am going to try it on windows.

Is there a simple way to exclude some tests, so I can see if other tests fail?

Original comment by josef.schneider on 25 Mar 2011 at 1:03

[GoogleCodeExporter]

You can use --gtest_filter to pick out only specific tests.

How much RAM/swap does your VM have?

Original comment by se...@google.com on 25 Mar 2011 at 1:35

[GoogleCodeExporter]

Sorry for bothering you, it was indeed a problem with noth enough RAM available.
I guess I am too much of a windows-guy for expecting some sort of warning.

Original comment by josef.schneider on 25 Mar 2011 at 1:54

[GoogleCodeExporter]

Original comment by se...@google.com on 25 Mar 2011 at 1:58

• Changed state: Invalid