Fix StackTrace on Windows....

Fix StackTrace on Windows.

The previous implementation was overly verbose. The new one is now functional and the unit test now works.

TEST=unit_test
BUG=none

[awong, 2009-08-21 20:52:20]

http://codereview.chromium.org/174250/diff/1/3
File base/debug_util_unittest.cc (right):

http://codereview.chromium.org/174250/diff/1/3#newcode22
Line 22: ASSERT_GE(frames_found, 5u) <<
Did you mean to make these more strict?  I remember having problems previously
with the test failing for various people due to different build configurations.

Having it just "pass" isn't ideal, but having it fail seemed worse.

[M-A Ruel, 2009-08-21 20:54:47]

On 2009/08/21 20:52:20, awong wrote:
> http://codereview.chromium.org/174250/diff/1/3
> File base/debug_util_unittest.cc (right):
> 
> http://codereview.chromium.org/174250/diff/1/3#newcode22
> Line 22: ASSERT_GE(frames_found, 5u) <<
> Did you mean to make these more strict?  I remember having problems previously
> with the test failing for various people due to different build
configurations.
> 
> Having it just "pass" isn't ideal, but having it fail seemed worse.

Yes, I'll relax it if necessary. On my system, the stack is 18 deep, and there's
>10 just in base_unittest so 6 is very safe.

Also, I verify that dumping actually works.

[awong, 2009-08-21 20:56:26]

LGTM

Sounds good to me.  If it starts failing, we can always flip it back.