Move mappings aggregation and reordering from linux_dumper to minidump_writer

Make the executable module first and merge adjacent mappings at the
minidump_writer level instead of linux_dumper

[glandium]

Whitespace fixes for pointers

[glandium]

Simplified a bit

[glandium]

On 2013/05/02 08:45:30, glandium wrote:
> Simplified a bit

Please ignore this patch for now, I'm going to fold something else with it,
which will change it significantly.

[glandium]

Final version, hopefully

[glandium]

This should be the last one

[glandium]

This time, it should be the last one

[Ted Mielczarek]

LGTM, just one question.

https://breakpad.appspot.com/573002/diff/24001/src/client/linux/minidump_writ...
File src/client/linux/minidump_writer/minidump_writer.cc (right):

https://breakpad.appspot.com/573002/diff/24001/src/client/linux/minidump_writ...
src/client/linux/minidump_writer/minidump_writer.cc:857: PageAllocator
allocator;
Is there any reason not to just use dumper_->allocator() here?

https://breakpad.appspot.com/573002/diff/24001/src/client/linux/minidump_writ...
src/client/linux/minidump_writer/minidump_writer.cc:914: // First write all the
mappings from the dumper
This comment doesn't really make sense anymore.

[glandium]

https://breakpad.appspot.com/573002/diff/24001/src/client/linux/minidump_writ...
File src/client/linux/minidump_writer/minidump_writer.cc (right):

https://breakpad.appspot.com/573002/diff/24001/src/client/linux/minidump_writ...
src/client/linux/minidump_writer/minidump_writer.cc:857: PageAllocator
allocator;
On 2013/06/07 15:42:02, Ted Mielczarek wrote:
> Is there any reason not to just use dumper_->allocator() here?

I wanted the allocations from this one to be freed without waiting the dumper to
be released.