MinidumpCallback should pass full minidump path instead of just id about google-breakpad HOT 7 CLOSED

I think the thinking was that you supplied the dump path and should know what 
it is,
and we're only giving you the guid, which you might want to do other stuff 
with.  Is
that erroneous?

Yes, I do know what it is, but I have to keep another variable around to keep 
track
of it.  Also, I don't see anything I'd want to use the GUID for aside from 
locating
the dump file.  In addition, as I mentioned, you already construct the path in 
that
function, so I'm just duplicating work.

This is trivially fixable now that you fixed
http://code.google.com/p/airbag/issues/detail?id=86

The Mac handler has dump_path and dump_id split into two parameters that are 
passed
to the minidump callback.  We're going to make the Windows handler match (and 
fix
this bug).  I already have this rolled in to my patch for #81, which is still 
under
development.

Checked in along with the patch for #81, revision [79].  The string parameters 
to
callbacks are now wchar_t*, and we pass both dump_path and minidump_id.