Invalid free(): boost::filesystem::path::~path() - c++

Question

I'm working on a program on a CentOS 7.5.1804 using the g++ 6.3.0 compiler
When I run the program, it returns a error:
-bash-4.2$ ./lost_drv
*** Error in `./lost_drv': free(): invalid pointer: 0x0000000002375cf8 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x81499)[0x7f5c65e85499]
./lost_drv(_ZN5boost10filesystem4pathD2Ev+0x18)[0x521564]
/lib64/libc.so.6(__cxa_finalize+0x9a)[0x7f5c65e3df4a]
/lib64/libboost_filesystem.so.1.53.0(+0x7573)[0x7f5c68317573]
======= Memory map: ========
Valgrind reveals it to be an issue with the boost::filesystem::path destructor
-bash-4.2$ valgrind ./lost_drv
==32523== Memcheck, a memory error detector
==32523== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==32523== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==32523== Command: ./lost_drv
==32523==
==32523== Invalid free() / delete / delete[] / realloc()
==32523== at 0x4C2B1CD: operator delete(void*) (vg_replace_malloc.c:576)
==32523== by 0x521563: boost::filesystem::path::~path() (path.hpp:55)
==32523== by 0x73DBF49: __cxa_finalize (in /usr/lib64/libc-2.17.so)
==32523== by 0x5053572: ??? (in /usr/lib64/libboost_filesystem.so.1.53.0)
==32523== by 0x40101C9: _dl_fini (in /usr/lib64/ld-2.17.so)
==32523== by 0x73DBBD8: __run_exit_handlers (in /usr/lib64/libc-2.17.so)
==32523== by 0x73DBC26: exit (in /usr/lib64/libc-2.17.so)
==32523== by 0x73C444B: (below main) (in /usr/lib64/libc-2.17.so)
The error occurs after the final return statement, as everything is getting cleaned up. The program apparently works OK prior to that.
This is an extensive program, but I've simplified it a bit by putting a return statement immediately following the main statement:
int main(int argc, char *argv[])
{
return 0;
...
I am using boost::filesystem to check path integrity ... code like this:
try
{
boost::filesystem::path fn(ifilenm);
if(!boost::filesystem::exists(fn) || !boost::filesystem::is_regular_file(fn))
{
cout << "ERROR: Input file does not exist or isn't a file:\t" << ifilenm << "\n";
return -2;
}
}
catch (const boost::filesystem::filesystem_error& ex)
{
cout << "ERROR: Failed accessing input file. File doesn't exist or isn't a file or isn't accesible:\t" << ifilenm << "\n";
return -3;
}
Which isn't being run in this degenerate case of course. There aren't any global boost variables being initialized before execution either.
I've tried this with the system boost install (1.53) as well as static & dynamic links against boost 1.59 built with the g++ 6.3 compiler. Same behavior.
One more bit ... there's another version of this executable which accesses some additional functionality via linking against some other 3rd party libraries. That build doesn't have this problem.
One other data point - if I rebuild the whole business with the default CentOS 7 compiler (g++ 4.8.5), I don't get this error. But that's not an option overall, because the 3rd party libraries used for the full monty require g++ 6
Any idea what's going on?
Thanks