MemorySim_LoadFromFlashImage() now takes base address

Previously this function assumed that the FLASH binary image file
should always be loaded at a base address of FLASH_BASE_ADDRESS
(0x00000000).  The caller now has to specify this base address
explicitly.

I was testing CrashDebug with some old Smoothie dumps that I had
sitting around and discovered that it didn't work properly because
the .bin needed to be loaded at address 0x4000 since Smoothie uses
a bootloader in the lower portion of FLASH.
Grow GdbLogParser line buffer to 1024 chars

The sample Smoothie crash dumps that I had on my machine contained
lines longer than the old 128 width because of the symbols in the
memory lines.  My future recommended GDB commands to create such a
dump won't include these symbols so that the lines are a much smaller
fixed length.
Command line now support --bin with baseAddress

I rename the old --image command line option to be --bin and it now
requires the user provide the desired base address for where this
binary content should be loaded into FLASH.

Usage: CrashDebug --bin imageFilename baseAddress
                  --dump dumpFilename
Where: --bin is the required name of the image loaded into the device's
             FLASH when the crash occurred.
         These binary images are typically generated by running
            "arm-none-eabi-objcopy -O binary input.elf output.bin"
Add mri.log to ignore list

I typically have GDB create this log file while it is communicating
with the CrashDebug remote debug stub.
Initial CrashDebug application

Now builds an actual CrashDebug application that pulls all of the
modules together and actually allows for post-mortem debugging from
GDB.  The sources for this tool can be found in the main/ directory.

What follows is an example GDB command line which also launches
CrashDebug for remote debugging:

arm-none-eabi-gdb /depots/SmoothieCrashDumps/issue93/main.elf
                 -ex "set target-charset ASCII"
                 -ex "set print pretty on"
                 -ex "set remotelogfile mri.log"
                 -ex "target remote |
                      CrashDebug
                        --bin main.bin 0x4000
                        --dump FullCrashDump.txt"