Clone wiki

QMapShack / TroubleShooting

Prev (Maps) | Home | Manual | Index | (Reporting a bug) Next


Since the 13-Oct-2015 development version, you can start qmapshack with the commandline option "-f". Then a logfile "org.qlandkarte.QMapShack.log" will be created in the system's temporary folder. On a Windows 7 installation this temporary folder seems to be C:\Users\your user name\AppData\Local\Temp. That log file may give additional insight to the root cause.

Create a backtrace of a crash on Linux

If QMapShack crashes on Linux the best you can do to help development is to send a backtrace. A backtrace is a log of the last code lines executed before the crash. Usually this contains enough hints to fix the problem fast.

To create a backtrace you have to compile QMapShack as debug version yourself. Have a look at the getting started chapter of the wiki for basic instructions.

When you do the step:

ccmake ../QMapShack

Change the variable CMAKE_BUILD_TYPE to Debug. Now start the build process with


No need to do a "make install". To create a backtrace you have to start QMapShack with the GDB debugger:

gdb bin/qmapshack

At gdb's command line prompt enter 'r' to run QMapShack. Now you can provoke the crash. After the crash enter 'bt' on gdb's command line. This will output the backtrace. Copy the lines and attach them to your bug report.

Limitations of QMapShack for Windows (short: QMS)

To limit the build and maintenance effort, the Windows binary packages for QMS come with a restricted set of 3rd party libraries. In particular the timely maintenance of security related libraries would either put an unmanageable burden on your QMS Windows maintainer or add an incalculable risk to the users (imagine what could happen if I package a SSL library where severe bugs such as Heartbleed are not yet fixed). Due to this limitation certain kinds of maps - in particular online maps - will not work.

Below those restrictions are summarized and possible workarounds are described. Please be aware that those workarounds are on the sole risk of the users - I cannot take responsibility in which situations they work or not.

Qt comes without SSL support

Qt5 binaries are delivered without SSL support due to legal restrictions in some countries. See qt-5-ssl. This may hinder some kinds of web maps (TMS, WMTS) to be downloaded properly. As a workaround you could download the and compatible Windows SSL package and copy the 2 DLLs libeay32.dll and ssleay32.dll to QMS home directory. The DLLs from the following 2 sources have been reported to work: indy or gisinternals. Please judge by yourself whether those sources are trustable for you and whether they fit to your actual installation.

GDAL comes without curl support

The default GDAL libraries come without curl support. This may hinder some kinds of web maps to be downloaded properly. As a workaround you could download GDAL binaries from gisinternals and then brute-force-copy the complete "bin" subdirectory including subdirectories to the QMS home directory.

GDAL comes without support for exotic formats

Some raster map formats (e.g. wavelet based) are not supported by the default GDAL installation. The reasons may be various (licenses, dependencies, ...). A possible workaround is the same as to add curl support: use the GDAL binaries from gisinternals.

Proposals for extending the standard GDAL distribution for Windows with some additional plugins that support more raster map formats can be found on the "Tips & tricks for raster maps" page.

Prev (Maps) | Home | Manual | Index | Top | (Reporting a bug) Next