Is it possible to get backtraces from lttng without LD_PRELOADing liblttng-ust-cyg-profile and compiling with -finstrument-functions? I can’t see from the lttng code what it’s doing differently when pre-loading that library to allow a trace viewer (tracecompass) to show the backtraces!? Here’s my test app: test_tracepoints.h: test_tracepoints.c: test.lttng.c: I’m testing this with: Answer No, it’s currently not directly supported. But it’s
Tag: gcc
configure: error: no acceptable C compiler found in $PATH
I am trying to Build and Install the Apache Thrift compiler and libraries I had to type this command is shown in instructions ./configure && make But I get this error: When I type in my command prompt gcc –version I get this gcc (GCC) 5.3.0 Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source
dynamic_cast fails between “long distance” siblings on linux compilation
There is a class DerivedClass which inherits from both BaseClassA and BaseClassB publicly. All classes have virtual functions to make sure the virtual table is built properly. BaseClassA and BaseClassB are located in Library1 and DerivedClass is in Library2. One function in Library1 retrieves a DerivedClass in the form of a BaseClassA pointer and tries to dynamic_cast to BaseClassB but
Issues with compiling caffe with python, undefined reference to `std::__cxx11::….’
I used to compile successfully caffe with WITH_PYTHON_LAYER:=1 on Ubuntu 14.04. Then I switched to Ubuntu 16.04, using the same settings but different built-in software such as g++ 5.4 for 16.04 instead of g++ 4.8 for 14.04, I failed to compile caffe with python. Would you please give me some advice on this issue? The following is part of the
Responsibility of stack alignment in 32-bit x86 assembly
I am trying to get a clear picture of who (caller or callee) is reponsible of stack alignment. The case for 64-bit assembly is rather clear, that it is by caller. Referring to System V AMD64 ABI, section 3.2.2 The Stack Frame: The end of the input argument area shall be aligned on a 16 (32, if __m256 is passed
“Illegal instruction” when running ARM code targeting my CPU
I’m compiling a rather large project for ARM. I’m using an AT91SAM9G25-EK as a devboard running a Debian ARM image. All libraries and executables in the image seem to be compiled for the armv4t instruction set. My CPU is an ARM926EJ-S, which should run armv5tej code. I’m using GCC to cross compile for my board. My CXX flags look like
ld undefined reference, despite library found and symbols exported
Been fighting with this on and off for 48 hours now; I’m still getting undefined reference errors when attempting to link a dynamic library with its dependency – despite all exports existing, and the library being found successfully. Scenario: libmemory (C++) – exports functions with extern “C” libstring (C) – exports functions, imports from libmemory libmemory builds successfully: libstring compiles
When changing the comment of a .c file, scons still re-compile it?
It’s said that scons uses MD5 signature as default decider to dertermine whether a source file needs re-compilation. E.g. I’ve got SConstruct as below: And my o.c is: Run scons and remove the comment line, run scons again. I expect that scons should not compile it again, but actually it’s: If I change SConstruct file to add one line: Still
linux: ranlib doesn’t seem to add any new information into an archive file?
The man page of ranlib says: DESCRIPTION ranlib generates an index to the contents of an archive and stores it in the archive. The index lists each symbol defined by a member of an archive that is a relocatable object file. Well, I tried to compile an archive file like below: I tried to compare the size of library file
How to cross-platform compile on windows for linux using gcc?
My aim is to create cross-platform C++ python modules. I’m usingCyther (cross-platform The Cross-Platform Cython/Python Compiler). Cyther uses GCC to compile modules and gives the user the ability to add GCC command-line args. So, I need run compiler on Windows, but compile for Linux. What args I must pass to GCC to compile a module for Linux (or other platform)?