Protect macros from user code to the left of them

remove time from raw logging

for `&CheckStackAddress`, VisualStudio emits address of a trampoline like PLT, 
not the actual address of `CheckStackTrace`.

We need address of `CheckStackTrace` to guess the address range of the function.
`static` function seems to return the actual address of the function.

Fixes #421 

Stop using auto_ptr

std::unique_ptr requires -std=c++11. just use raw pointer.

project/google/glog -> project/google-admin/glog

Use push/pop macro when supressing warning

* Same as PR #397 , but for the `.in` file. Useful for some unusual cross-platform build environments (e.g. WSL).

Support ABI tags after <local-source-name> in demangle.cc.
Update the reference URL.

Fixes #50 

* Fix demangling template parameter packs

Clang 4.0.1-10 and gcc 7.3.0 both mangle the function "void add<int>(int)" as
"_Z3addIJiEEvDpT_".  The template parameter pack is of the form
J <template-arg>* E

The opening character for a param pack could be either I or J, as libiberty
follows [1].  This change simply adds the J case.

[1] https://github.com/gcc-mirror/gcc/blob/fbd263526ad105a953fd51d9f7bca2c3f268cf82/libiberty/cp-demangle.c#L3209

build: cleanup temps and remove NEWS

The code references `@ac_cv_have_libgflags@` but not `@ac_cv_have_libgflags_h@`. This corrects that.

`int(with_gflags)` incorporates the possibility of `True/False`: https://github.com/bazelbuild/bazel/issues/4792

Fix unused variable warning in GCC

With automake GNU standard relaxed, these are no longer needed.

automake: relax GNU standard directory style

Now, we can build.

GNU standard assumes `README` under root dir, while PR #403
didn't fix the building issue exactually.
https://www.gnu.org/software/automake/manual/html_node/List-of-Automake-options.html

update README.md filename in Makefile.am

ci: add clang-cxx17 toolchain

remove register keyword from unittest

Use push/pop macro when supressing warning

ci: add appveyor and travis config

* Previous implementation did not correctly restore the warning state if initially disabled.

* Upstream Chromium local changes to symbolize.cc

Chromium has its own fork of symbolize.cc and symbolize.h, and it has
several not-yet-upstreamed changes, that are not specific to Chromium.

This patch upstreams such a changes.

  Fixed google::FindSymbol reading past end of a section
  https://chromium.googlesource.com/chromium/src/+/3dae0a2d7da309159a301e40a592692ec8431a38

  Fix -INT_MIN integer overflow in itoa_r().
  https://chromium.googlesource.com/chromium/src/+/ac4d28e9cb934e01ff16a9e67a5f387caa82719f

  Add print_unsymbolized_stack_traces gn arg.
  https://chromium.googlesource.com/chromium/src/+/6a2726776f59cdcf0090f584a15db4a1ab8c40d7

  Switch to standard integer types in base/.
  https://chromium.googlesource.com/chromium/src/+/9b6f42934e5a1e65ebfc668d91a28a6e2678a14c

* Add a build option to print unsymbolized traces

This PRINT_UNSYMBOLIZED_STACK_TRACES option to cmake, and
--enable-unsymbolized-traces option to autoconf.

The newly-released gflags 2.2.2 includes fixes to the Bazel BUILD files
that weren't in the older 2.2.1 release.

Make symbolize.cc thread safe even on shared fds

ReadFromOffset in symbolize.cc used to call lseek() + read() to read
data from fd. However, the fd may be reused for multiple symbolize
requests from multiple threads, and causes a race around the fd read
offset.

This updates it to use pread() to resolve the race.

To fix https://github.com/google/glog/issues/376

Don't crash on some forms of invalid ELF files

Fix mistype in comment