Chad Engler
d3f2d11ae6
Fix ARM compilation for windows. ( #401 )
2021-04-07 21:33:40 -06:00
Alvin
c0ae589024
Alvin/minor fixes and improvements ( #389 )
...
* Fix typos
* Fix build for MinGW
- MinGW g++ doesn't recoganize `-rdynamic`
2020-11-17 20:40:26 -07:00
Nicholas Lederer
9fb3e61e89
fix issue with stacktrace_windows not allocating sufficient memory for SYMBOL_INFO struct ( #334 )
2020-02-25 07:15:09 -07:00
John Farrier
69f21e3513
Fixed ambiguous constructor error. ( #262 )
2018-04-26 20:30:26 -06:00
Dmitry Ledentsov
f10fbe1d9c
added automatic linking pragma for StackWalk64 ( #96 )
2016-06-12 16:57:55 -06:00
Kjell Hedström
279587c567
Update stacktrace_windows.cpp
...
For access to thread_local definition
2016-02-16 20:55:28 -07:00
Aleksey Dobrunov
12beaf89de
remove unused include
2016-01-11 00:41:05 +05:00
Kjell Hedstrom
7c7012325d
Easier to install. continues
...
1) Breaking change: g3 namespace replaces g2
2) g2log.hpp remains in src/g2log.hpp... but now all it does is to include the g3log.hpp, etc
3) ALL HEADER FILES ARE IN src/g3log/ while all .cpp and .ipp files are in /src (exception for g2log.hpp)
This should make it EASIER for clients to copy/install the header files to the new location. It greatly simplifies
rpm and cpackage installationsw
2015-07-19 23:10:56 -06:00
Kjell Hedstrom
6750efe8fe
g2log.hpp is kept as a helper include. It will pull in the most frequent include files
...
All other are under g3log. Example: #include <g3log/time.hpp> #include <g3log/g3log.hpp> etc
This makes sure that the package manager (to be used soon) does NOT clutter any /usr/local/include space
instead all the includes will be in /usr/local/include/g3log (or similar)
2015-07-16 01:55:23 -06:00
Kjell Hedstrom
ebcfe9ff06
remove windows warnings. Thanks to @ctapmex
2015-06-24 14:50:46 -06:00
David Gayerie
4c45244391
fixing cross compilation on Linux for MINGW gcc 4.8.2
2015-03-29 14:29:07 +02:00
Kjell Hedstrom
7c5254c80b
thread_local issues on Linux, using atomic instead
2015-03-02 02:02:43 -07:00
Kjell Hedstrom
a5d922de49
__debugbreak in windows can easily cause recursive crashes if you are
...
NOT in debug mode in your visual IDE
2015-03-02 01:14:03 -07:00
Kjell Hedstrom
fc1acd742d
1) windows exception will now trigger break point in VS
...
2) Fatal signal will in DEBUG trigger a break point in VS
- It can be disabled by a #define
3) signal handler can be disabled by a #define
2015-02-18 03:55:16 -07:00
Kjell Hedstrom
81885e4456
Enabled vectored exception crash handling, it can also be turned off easily with a define
...
cmake -DENABLE_VECTORED_EXCEPTIONHANDLING=OFF
2015-02-16 01:37:55 -07:00
Kjell Hedstrom
b3e7032678
Signals seems to have to be installed for EVERY thread
2015-02-02 21:35:48 -07:00
KjellKod
938fc55971
What a mess to merge from Github/KjellKod/g3log to BitBucket/KjellKod/g3log
2015-02-02 00:31:43 -07:00
