sudo chown user:user -R *
Author: ludek.vodicka
Problem with compiling Boost
Warning: "using python" expects a two part (major, minor) version number; got %d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" instead Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\feature.jam:276: in implied-feature from module featureerror: "version_info[1]" is not an implicit feature value Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\feature.jam:355: in expand-subfeatures-aux from module featureQ:/ExternalLibraries/boost_trunk/tools/build/v2/build\feature.jam:424: in feature.expand-subfeatures from module feature Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\property.jam:186: in property.expand-subfeatures-in-conditions from module property Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\property-set.jam:407: in property-set.create-from-user-input from module property-set Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\property-set.jam:461: in property-set.refine-from-user-input from module property-set Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\targets.jam:1580: in targets.main-target-requirements from module targets Q:/ExternalLibraries/boost_trunk/tools/build/v2/tools\builtin.jam:532: in lib from module builtin Q:/ExternalLibraries/boost_trunk/tools/build/v2/tools\python.jam:680: in declare-libpython-target from module python Q:/ExternalLibraries/boost_trunk/tools/build/v2/tools\python.jam:925: in configure from module python Q:/ExternalLibraries/boost_trunk/tools/build/v2/tools\python.jam:110: in python.init from module python Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\toolset.jam:41: in using from module toolset libs\python\build\Jamfile.v2:16: in modules.load from module Jamfile<Q:\External Libraries\boost_trunk\libs\python\build> Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\project.jam:311: in load-jamfile from module project Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\project.jam:64: in load from module project Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\project.jam:89: in load-used-projects from module project Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\project.jam:75: in load from module project Q:/ExternalLibraries/boost_trunk/tools/build/v2/build\project.jam:145: in project.find from module project Q:/ExternalLibraries/boost_trunk/tools/build/v2\build-system.jam:552: in load from module build-system Q:\ExternalLibraries\boost_trunk\tools\build\v2/kernel\modules.jam:289: in import from module modules Q:\ExternalLibraries\boost_trunk\tools\build\v2/kernel/bootstrap.jam:139: in boost-build from module Q:\ExternalLibraries\boost_trunk\boost-build.jam:17: in module scope from module
The problem was that boost build helper run my python.bat instead of correct python.exe from %PATH% directory.
To check which python is used enter following param:
b2 --debug-configuration:
notice: [python-cfg] Configuring python... notice: [python-cfg] Registry indicates Python 2.7 installed at "C:\Python27\" notice: [python-cfg] Checking interpreter command "python"... notice: [python-cfg] running command 'python -c "from sys import *; print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" 2>&1' notice: [python-cfg] ...does not invoke a working interpreter notice: [python-cfg] Checking interpreter command "C:\Python27\python"... ####HERE#### notice: [python-cfg] running command 'DIR /-C /A:S "C:\Python27\python.exe" 2>&1' ####HERE#### notice: [python-cfg] running command 'C:\Python27\python -c "from sys import *;print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" 2>&1' notice: [python-cfg] ...requested configuration matched! notice: [python-cfg] Details of this Python configuration: notice: [python-cfg] interpreter command: "C:\Python27\python" notice: [python-cfg] include path: "C:\Python27\Include" notice: [python-cfg] library path: "C:\Python27\libs" notice: [python-cfg] DLL search path: "C:\Python27"
How to change Ubuntu computer network name and setup SSH access
To change computer network use following commands:
sudo nano /etc/hostname sudo reboot [/surcecode] To check host name: hostname
To setup SSH access use:
sudo apt-get install ssh sudo apt-get install openssh-server
Trac commands
Create new project
trac-admin c:\PATH\TO\PROJECT initenv
Enable web admin
trac-admin c:\PATH\TO\PROJECT >permission add <username> TRAC_ADMIN >permission list <username>
Qt and Google breakpad Windows/Linux/MacOS
Integration of Google breakpad on any platform is really challenge. I didn’t figure out how to do it by using recommended ways. So I did it my way 😉
Create your own Qt project
As first thing I did when integrating Qt and Breakpad is creation of my own .pri file. I manually add all required files from Breakpad one-by-one, starting with src/platform/exception_handler continuing with all files included in previous ones. The complete .pri file you will find at end of this post.
After that I created simple CCrashHandler (inspired by qt-breakpad project) class which register exception handler. It’s necessary to implement this handler for each platform separately because each platform have different parameters in google_breakpad::ExceptionHandler() constructor. CrashHandler source code you can find also at end of this post.
Using Breakpad on Linux:
Article about Linux integration.
Notes Linux
- GCC 4.6.3
- Ubuntu 12.04.1 32/64bit
Get and Compile Breakpad
#get breakpad latest version svn checkout http://google-breakpad.googlecode.com/svn/trunk/ google-breakpad-read-only #compile all breakpad tools for extracting symbol files ./configure make sudo make install #when compilation is ready, you should have installed file dump_syms from original directory /src/tools/linux/dump_syms in your /usr/bin dump_syms
Generate symbol file and test debug info
Now how to generate and use symbol file:
#generate .sym file dump_syms ./Application > Application.sym #store sym file in the correct location #this step is necessary. Without that minidump_stackwalk tool doesn't work head -n1 Application.sym #Result: MODULE Linux x86_64 6EDC6ACDB282125843FD59DA9C81BD830 Application mkdir -p ./symbols/Application/6EDC6ACDB282125843FD59DA9C81BD830 mv Application.sym ./symbols/Application/6EDC6ACDB282125843FD59DA9C81BD830 #show stack with using minidump_stackwalk tool minidump_stackwalk ./crash.dmp ./symbols
Result of minidump_stackwalk tool can look like this:
Use additional tools
There is script written by Mozzila corp which simplifies extracting and storing .sym file:
http://mxr.mozilla.org/mozilla-central/source/toolkit/crashreporter/tools/symbolstore.py?raw=1
Now with this script, you can do only one step instead of all described above.
python /path/to/script/symbolstore.py /usr/local/bin/dump_syms ./symbol-storage ./Application
This command correctly creates folder Application/uuid in path symbol-storage and copy generated .sym file inside.
Using Breakpad on MacOS:
To integrate Breakpad and Qt on MacOS I used the same article as for Linux because I’m using gcc and linux-like development toolchain. For native XCode integration you have to probably use this article.
Notes MacOS
- GCC 4.6.3
- Qt creator toolchain
- Mac OS 10.7.3 64bit
- Don’t using any of XCode tool chaing
Do almost all steps like on Linux integration. There is one exception, because you can’t compile Breakpad tools using linux-like configure&make. You have to build these tools with XCode.
Compile google_breakpad/src/tools/mac/dump_syms/dump_syms.xcodeproj with XCode
Before I managed to successfully compile dump_syms in XCode, I have to update Architectures Debug/Release to 64-bit Intel and BaseSDK to “Latest Mac OS X”. I also fix all issues displayed in the left part of XCode window.
Next step is change compilation type from Debug to Release. After a short searching I found a way in “Schema->Edit schema->Build configuration”.
To be honest, I was not sure what I did, but it worked ;-). Maybe there is some easier way how to compile dump_syms in xcode, but I don’t know how. This was my first contact with XCode ;-).
The application is compiled to path “/Users/User/Library/Developer/Xcode/DerivedData/dump_syms-bjvr/Build/Products/Release/dump_syms”. Now copy dump_syms to safe location from where you will use it.
The rest steps are same like in the Linux.
Using Breakpad on Windows
Notes Windows
Article about Windows integration.
- Compile with Visual Studio 2010
- Post-mortem debugging is done also via VS2010
- Google breakpad under windows generates common .dmp files which can by simply load directly to VS
Generate symbol files and test debug info
You have to choices for Windows. First option is use standard .PDB and .DMP files mechanism in VS. Second is use the same way how you can did it for Linux and Mac.
First way: Let compiler generate .PDB file. Store this files and use them later in VS together with your crash dump.
Second way: Use dump_sys.exe. This file is located in the google breakpad directory tree: google-breakpad\src\tools\windows\binaries\dump_syms.exe .
dump_syms.exe AtomixDevelopment.exe >AtomixDevelopment.sym
And also like under Linux, you can use Python script symbolstore.py to extract symbols to correct directory:
python.exe symbolstore.py binaries\dump_syms.exe .\Symbols AtomixDevelopment.exe
Minidump stackwalk for windows:
http://code.google.com/p/pcxfirefox/source/browse/trunk/betterpgo/talos/talos/breakpad/win32/minidump_stackwalk.exe?r=19
The best thing at end
The most amazing thing I found about dump_syms is their platform independence. If you correctly extract symbol file on each platform and store it in one location, you can analyze any crashdump on one location. No matter what is source platform, you will analyze .dmp file by using minidump_stackwalk ./crash.dmp ./symbols.
How to include CrashHandler directly to your project
This is what I get when I follow all includes from .h and .cpp files starting with exception_handler.h for all platforms. With small modification you can include it to your project and your application will be fully breakpad-able ;-).
# ---------- HEADER ----------------------------------------------------------- OTHERS += $$PWD/axCrashHandler.pri HEADERS += $$PWD/CrashHandler.h SOURCES += $$PWD/CrashHandler.cpp BREAKPAD_PATH=$$EXTERNAL_LIBRARIES_PATH/breakpad-qt INCLUDEPATH += $$BREAKPAD_PATH/src OSMAC { HEADERS += $$BREAKPAD_PATH/src/client/mac/handler/exception_handler.h HEADERS += $$BREAKPAD_PATH/src/client/mac/crash_generation/crash_generation_client.h HEADERS += $$BREAKPAD_PATH/src/client/mac/crash_generation/crash_generation_server.h HEADERS += $$BREAKPAD_PATH/src/client/mac/crash_generation/client_info.h HEADERS += $$BREAKPAD_PATH/src/client/mac/handler/minidump_generator.h HEADERS += $$BREAKPAD_PATH/src/client/mac/handler/dynamic_images.h HEADERS += $$BREAKPAD_PATH/src/client/mac/handler/breakpad_nlist_64.h HEADERS += $$BREAKPAD_PATH/src/client/mac/handler/mach_vm_compat.h HEADERS += $$BREAKPAD_PATH/src/client/minidump_file_writer.h HEADERS += $$BREAKPAD_PATH/src/client/minidump_file_writer-inl.h HEADERS += $$BREAKPAD_PATH/src/common/mac/macho_utilities.h HEADERS += $$BREAKPAD_PATH/src/common/mac/byteswap.h HEADERS += $$BREAKPAD_PATH/src/common/mac/MachIPC.h HEADERS += $$BREAKPAD_PATH/src/common/mac/scoped_task_suspend-inl.h HEADERS += $$BREAKPAD_PATH/src/common/mac/file_id.h HEADERS += $$BREAKPAD_PATH/src/common/mac/macho_id.h HEADERS += $$BREAKPAD_PATH/src/common/mac/macho_walker.h HEADERS += $$BREAKPAD_PATH/src/common/mac/macho_utilities.h HEADERS += $$BREAKPAD_PATH/src/common/mac/bootstrap_compat.h HEADERS += $$BREAKPAD_PATH/src/common/mac/string_utilities.h HEADERS += $$BREAKPAD_PATH/src/common/linux/linux_libc_support.h HEADERS += $$BREAKPAD_PATH/src/common/string_conversion.h HEADERS += $$BREAKPAD_PATH/src/common/md5.h HEADERS += $$BREAKPAD_PATH/src/common/memory.h HEADERS += $$BREAKPAD_PATH/src/common/using_std_string.h HEADERS += $$BREAKPAD_PATH/src/common/convert_UTF.h HEADERS += $$BREAKPAD_PATH/src/processor/scoped_ptr.h HEADERS += $$BREAKPAD_PATH/src/google_breakpad/common/minidump_exception_mac.h HEADERS += $$BREAKPAD_PATH/src/google_breakpad/common/breakpad_types.h HEADERS += $$BREAKPAD_PATH/src/google_breakpad/common/minidump_format.h HEADERS += $$BREAKPAD_PATH/src/google_breakpad/common/minidump_size.h HEADERS += $$BREAKPAD_PATH/src/third_party/lss/linux_syscall_support.h SOURCES += $$BREAKPAD_PATH/src/client/mac/handler/exception_handler.cc SOURCES += $$BREAKPAD_PATH/src/client/mac/crash_generation/crash_generation_client.cc SOURCES += $$BREAKPAD_PATH/src/client/mac/crash_generation/crash_generation_server.cc SOURCES += $$BREAKPAD_PATH/src/client/mac/handler/minidump_generator.cc SOURCES += $$BREAKPAD_PATH/src/client/mac/handler/dynamic_images.cc SOURCES += $$BREAKPAD_PATH/src/client/mac/handler/breakpad_nlist_64.cc SOURCES += $$BREAKPAD_PATH/src/client/minidump_file_writer.cc SOURCES += $$BREAKPAD_PATH/src/common/mac/macho_id.cc SOURCES += $$BREAKPAD_PATH/src/common/mac/macho_walker.cc SOURCES += $$BREAKPAD_PATH/src/common/mac/macho_utilities.cc SOURCES += $$BREAKPAD_PATH/src/common/mac/string_utilities.cc SOURCES += $$BREAKPAD_PATH/src/common/mac/file_id.cc SOURCES += $$BREAKPAD_PATH/src/common/mac/MachIPC.mm SOURCES += $$BREAKPAD_PATH/src/common/mac/bootstrap_compat.cc SOURCES += $$BREAKPAD_PATH/src/common/md5.cc SOURCES += $$BREAKPAD_PATH/src/common/string_conversion.cc SOURCES += $$BREAKPAD_PATH/src/common/linux/linux_libc_support.cc SOURCES += $$BREAKPAD_PATH/src/common/convert_UTF.c LIBS += /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation LIBS += /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices #breakpad app need debug info inside binaries QMAKE_CXXFLAGS+=-g } OSLIN { HEADERS += $$BREAKPAD_PATH/src/client/linux/handler/exception_handler.h HEADERS += $$BREAKPAD_PATH/src/client/linux/crash_generation/crash_generation_client.h HEADERS += $$BREAKPAD_PATH/src/client/linux/handler/minidump_descriptor.h HEADERS += $$BREAKPAD_PATH/src/client/linux/minidump_writer/minidump_writer.h HEADERS += $$BREAKPAD_PATH/src/client/linux/minidump_writer/line_reader.h HEADERS += $$BREAKPAD_PATH/src/client/linux/minidump_writer/linux_dumper.h HEADERS += $$BREAKPAD_PATH/src/client/linux/minidump_writer/linux_ptrace_dumper.h HEADERS += $$BREAKPAD_PATH/src/client/linux/minidump_writer/directory_reader.h HEADERS += $$BREAKPAD_PATH/src/client/linux/log/log.h HEADERS += $$BREAKPAD_PATH/src/client/minidump_file_writer-inl.h HEADERS += $$BREAKPAD_PATH/src/client/minidump_file_writer.h HEADERS += $$BREAKPAD_PATH/src/common/linux/linux_libc_support.h HEADERS += $$BREAKPAD_PATH/src/common/linux/eintr_wrapper.h HEADERS += $$BREAKPAD_PATH/src/common/linux/ignore_ret.h HEADERS += $$BREAKPAD_PATH/src/common/linux/file_id.h HEADERS += $$BREAKPAD_PATH/src/common/linux/memory_mapped_file.h HEADERS += $$BREAKPAD_PATH/src/common/linux/safe_readlink.h HEADERS += $$BREAKPAD_PATH/src/common/linux/guid_creator.h HEADERS += $$BREAKPAD_PATH/src/common/linux/elfutils.h HEADERS += $$BREAKPAD_PATH/src/common/linux/elfutils-inl.h HEADERS += $$BREAKPAD_PATH/src/common/using_std_string.h HEADERS += $$BREAKPAD_PATH/src/common/memory.h HEADERS += $$BREAKPAD_PATH/src/common/basictypes.h HEADERS += $$BREAKPAD_PATH/src/common/memory_range.h HEADERS += $$BREAKPAD_PATH/src/common/string_conversion.h HEADERS += $$BREAKPAD_PATH/src/common/convert_UTF.h HEADERS += $$BREAKPAD_PATH/src/google_breakpad/common/minidump_format.h HEADERS += $$BREAKPAD_PATH/src/google_breakpad/common/minidump_size.h HEADERS += $$BREAKPAD_PATH/src/google_breakpad/common/breakpad_types.h HEADERS += $$BREAKPAD_PATH/src/processor/scoped_ptr.h HEADERS += $$BREAKPAD_PATH/src/third_party/lss/linux_syscall_support.h SOURCES += $$BREAKPAD_PATH/src/client/linux/crash_generation/crash_generation_client.cc SOURCES += $$BREAKPAD_PATH/src/client/linux/handler/exception_handler.cc SOURCES += $$BREAKPAD_PATH/src/client/linux/handler/minidump_descriptor.cc SOURCES += $$BREAKPAD_PATH/src/client/linux/minidump_writer/minidump_writer.cc SOURCES += $$BREAKPAD_PATH/src/client/linux/minidump_writer/linux_dumper.cc SOURCES += $$BREAKPAD_PATH/src/client/linux/minidump_writer/linux_ptrace_dumper.cc SOURCES += $$BREAKPAD_PATH/src/client/linux/log/log.cc SOURCES += $$BREAKPAD_PATH/src/client/minidump_file_writer.cc SOURCES += $$BREAKPAD_PATH/src/common/linux/linux_libc_support.cc SOURCES += $$BREAKPAD_PATH/src/common/linux/file_id.cc SOURCES += $$BREAKPAD_PATH/src/common/linux/memory_mapped_file.cc SOURCES += $$BREAKPAD_PATH/src/common/linux/safe_readlink.cc SOURCES += $$BREAKPAD_PATH/src/common/linux/guid_creator.cc SOURCES += $$BREAKPAD_PATH/src/common/linux/elfutils.cc SOURCES += $$BREAKPAD_PATH/src/common/string_conversion.cc SOURCES += $$BREAKPAD_PATH/src/common/convert_UTF.c #breakpad app need debug info inside binaries QMAKE_CXXFLAGS+=-g } OSWIN { BREAKPAD_PATH=q:/Applications/breakpad-qt/third-party/latest-breakpad INCLUDEPATH += $$BREAKPAD_PATH/src HEADERS += $$BREAKPAD_PATH/src/common/windows/string_utils-inl.h HEADERS += $$BREAKPAD_PATH/src/common/windows/guid_string.h HEADERS += $$BREAKPAD_PATH/src/client/windows/handler/exception_handler.h HEADERS += $$BREAKPAD_PATH/src/client/windows/common/ipc_protocol.h HEADERS += $$BREAKPAD_PATH/src/google_breakpad/common/minidump_format.h HEADERS += $$BREAKPAD_PATH/src/google_breakpad/common/breakpad_types.h HEADERS += $$BREAKPAD_PATH/src/client/windows/crash_generation/crash_generation_client.h HEADERS += $$BREAKPAD_PATH/src/processor/scoped_ptr.h SOURCES += $$BREAKPAD_PATH/src/client/windows/handler/exception_handler.cc SOURCES += $$BREAKPAD_PATH/src/common/windows/string_utils.cc SOURCES += $$BREAKPAD_PATH/src/common/windows/guid_string.cc SOURCES += $$BREAKPAD_PATH/src/client/windows/crash_generation/crash_generation_client.cc }
And this is the minimal implementation of your new CrashHandler. My ownd crash handler is much more sophisticate to perform reporting, sending crash dump etc. But for purposes of this article this is what you need (And also I don’t want to share my whole know-how here ;-)))
CrashHandler.h
#pragma once #include <QtCore/QString> namespace Atomix { class CrashHandlerPrivate; class CrashHandler { public: static CrashHandler* instance(); void Init(const QString& reportPath); void setReportCrashesToSystem(bool report); bool writeMinidump(); private: CrashHandler(); ~CrashHandler(); Q_DISABLE_COPY(CrashHandler) CrashHandlerPrivate* d; }; }
CrashHandler.cpp
#include "CrashHandler.h" #include <QtCore/QDir> #include <QtCore/QProcess> #include <QtCore/QCoreApplication> #include <QString> #if defined(Q_OS_MAC) #include "client/mac/handler/exception_handler.h" #elif defined(Q_OS_LINUX) #include "client/linux/handler/exception_handler.h" #elif defined(Q_OS_WIN32) #include "client/windows/handler/exception_handler.h" #endif namespace Atomix { /************************************************************************/ /* CrashHandlerPrivate */ /************************************************************************/ class CrashHandlerPrivate { public: CrashHandlerPrivate() { pHandler = NULL; } ~CrashHandlerPrivate() { delete pHandler; } void InitCrashHandler(const QString& dumpPath); static google_breakpad::ExceptionHandler* pHandler; static bool bReportCrashesToSystem; }; google_breakpad::ExceptionHandler* CrashHandlerPrivate::pHandler = NULL; bool CrashHandlerPrivate::bReportCrashesToSystem = false; /************************************************************************/ /* DumpCallback */ /************************************************************************/ #if defined(Q_OS_WIN32) bool DumpCallback(const wchar_t* _dump_dir,const wchar_t* _minidump_id,void* context,EXCEPTION_POINTERS* exinfo,MDRawAssertionInfo* assertion,bool success) #elif defined(Q_OS_LINUX) bool DumpCallback(const google_breakpad::MinidumpDescriptor &md,void *context, bool success) #elif defined(Q_OS_MAC) bool DumpCallback(const char* _dump_dir,const char* _minidump_id,void *context, bool success) #endif { Q_UNUSED(context); #if defined(Q_OS_WIN32) Q_UNUSED(_dump_dir); Q_UNUSED(_minidump_id); Q_UNUSED(assertion); Q_UNUSED(exinfo); #endif qDebug("BreakpadQt crash"); /* NO STACK USE, NO HEAP USE THERE !!! Creating QString's, using qDebug, etc. - everything is crash-unfriendly. */ return CrashHandlerPrivate::bReportCrashesToSystem ? success : true; } void CrashHandlerPrivate::InitCrashHandler(const QString& dumpPath) { if ( pHandler != NULL ) return; #if defined(Q_OS_WIN32) std::wstring pathAsStr = (const wchar_t*)dumpPath.utf16(); pHandler = new google_breakpad::ExceptionHandler( pathAsStr, /*FilterCallback*/ 0, DumpCallback, /*context*/ 0, true ); #elif defined(Q_OS_LINUX) std::string pathAsStr = dumpPath.toStdString(); google_breakpad::MinidumpDescriptor md(pathAsStr); pHandler = new google_breakpad::ExceptionHandler( md, /*FilterCallback*/ 0, DumpCallback, /*context*/ 0, true, -1 ); #elif defined(Q_OS_MAC) std::string pathAsStr = dumpPath.toStdString(); pHandler = new google_breakpad::ExceptionHandler( pathAsStr, /*FilterCallback*/ 0, DumpCallback, /*context*/ 0, true, NULL ); #endif } /************************************************************************/ /* CrashHandler */ /************************************************************************/ CrashHandler* CrashHandler::instance() { static CrashHandler globalHandler; return &globalHandler; } CrashHandler::CrashHandler() { d = new CrashHandlerPrivate(); } CrashHandler::~CrashHandler() { delete d; } void CrashHandler::setReportCrashesToSystem(bool report) { d->bReportCrashesToSystem = report; } bool CrashHandler::writeMinidump() { bool res = d->pHandler->WriteMinidump(); if (res) { qDebug("BreakpadQt: writeMinidump() successed."); } else { qWarning("BreakpadQt: writeMinidump() failed."); } return res; } void CrashHandler::Init( const QString& reportPath ) { d->InitCrashHandler(reportPath); } }
Main.cpp
And here is how to use it:
#include "axCore/axCrashHandler/CrashHandler.h" #include <QDebug> #include <QCoreApplication> #include <iostream> int buggyFunc() { delete reinterpret_cast<QString*>(0xFEE1DEAD); return 0; } int main(int argc, char * argv[]) { qDebug() << "App start"; QCoreApplication app(argc, argv); #if defined(Q_OS_WIN32) Atomix::CrashHandler::instance()->Init("c:\\dump"); #elif defined(Q_OS_LINUX) Atomix::CrashHandler::instance()->Init("/Users/dev/dump"); #elif defined(Q_OS_MAC) Atomix::CrashHandler::instance()->Init("/Users/User/dump"); #endif qDebug() << "CrashHandlerSet"; buggyFunc(); return 0; }
Very slow svn updates from Virtual Machines (VMWare)
I have a lot of virtual machines used for my everyday development. It’s very frustrating the SVN update speed if you have several externals in your main SVN source.
Today when I wait for some compilation start searching if there is anything what could improve SVN speed. After searching a lot of articles about faster network, better server hdd,… I found article with mention how SVN client communicate with server (intensively 😉 ). But without any clue how to improve it.
So I start searching how SVN client communiacte from within VMWare machines to server. I noticed that VMWare default network settings is NAT: Used to share the host’s IP address:
So I start trying other network methods and this is the result:
When I use “Custom: Specific virtual network” and choose “VMnet0 Bridged”, my svn update is about ten times faster than on NAT settings!!. I also tried first option “Bridged:…” but this doesn’t work for me.
How to setup MacOS terminal to have color output
Add these lines to your ~/.bash_profile file.
export CLICOLOR=1 #if your're using white background export LSCOLORS=ExFxCxDxBxegedabagacad #if your're using black backgroud #export LSCOLORS=gxBxhxDxfxhxhxhxhxcxcx
QWidget: Must construct a QApplication before a QPaintDevice
Today I encounter this error after applying macdeployqt to my application. There is a lot of questions about this topic on google but not very answers.
The most important thing is setup following variable.
export DYLD_PRINT_LIBRARIES=1
Using this you will se which libraries are loaded during execution of your application. The interesting thing is, that I see loading a libraries from their original directories instead of Application.app. But when I temporary moved these libraries from their location, libraries begin to load from then bundle location.
The reason for my “QWidget: Must construct a QApplication before a QPaintDevice” was executing an older version of QTitanRibbon from shared libraries path instead of the newest one compiled directly to /usr/lib.
The second reason for this issue was caused by another path in “export DYLD_LIBRARY_PATH”. It seems that application search for libraries first in DYLD_LIBRARY_PATH and after in paths from their inner records.
To turn off this debug output, use:
unset DYLD_PRINT_LIBRARIES
How to get Linux / Ubuntu version
cat /etc/issue
Ubuntu 12.04.1 LTS
How to install Subversion 1.7 to Ubuntu
sudo apt-add-repository ppa:dominik-stadler/subversion-1.7 sudo apt-get update sudo apt-get upgrade sudo apt-get dist-upgrade sudo apt-get install subversion
External links
https://launchpad.net/~dominik-stadler/+archive/subversion-1.7
http://askubuntu.com/questions/65468/where-can-i-find-a-subversion-1-7-binary
How to instal JRE 7 in Ubuntu 12
First step is clean all openjdk from system
sudo apt-get purge openjdk*
Now download latest JRE version from here http://www.oracle.com/technetwork/java/javase/downloads/jre-7u13-download-1501631.html. Download package: jre-7u13-linux-i586.tar.gz.
Download package to ~/Downloads and execute following commands
tar -xvf ~/Downloads/jre-7u13-linux-i586.tar.gz sudo mkdir -p /usr/lib/jvm/jre1.7.0 sudo mv jre1.7.0_13/* /usr/lib/jvm/jre1.7.0/ sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/jre1.7.0/bin/java 0
External links
How to share Ubuntu drive
Today I need to share some testing data (deployment package) from one Ubuntu to another. Probably the simplest way is to install samba-server to Ubuntu and access it from the second one.
How to install samba server in Ubuntu
To install samba server, use:
sudo apt-get install samba sudo smbpasswd [user-name]
When asked, enter new samba access password for selected user. Now you need to install gnome-install-tools to be able use shares-admin command to view all shared folders
sudo apt-get install gnome-system-tools shares-admin
Now setup folder sharing and close dialog. From now, you can use
\\computer\shared
to access your samba-shared folder.
How to access samba sharing from Ubuntu
If you want to access samba share from ubuntu using GUI-way, follow next steps:
1) Open Places->Connect to Server
2) Choose Type: Windows Share
3) To “Server” field enter IP of your server (or computer-name)
4) To “Share” enter path of your shared folder
5) “Folder” keep as is “/”
6) Enter user details based on previous samba server settings
Now click “Connect” and your shared folder should be connected.
Mac OS – How to detect library destination platform
Today I need to check if one of third-party component compile correctly 64-bit library version.
lipo -info /path/to/library
Windows, Linux and MacOS 7za equivalent
Windows:
http://www.7-zip.org/
Ubuntu:
sudo apt-get install p7zip-full
MacOS:
sudo port install p7zip
Error compiling Qt 4.8.2 under older versions of Ubuntu
If you encounter to this error
error package gstreamer-app-0.10 not found
simply install/reinstall gstreamer packages
sudo apt-get install libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev