similar to: [LLVMdev] Expressiveness of column numbers in dwarf using clang 3.0?

On 31.05.2011 19:22, Devang Patel wrote: > > On May 30, 2011, at 11:11 AM, trash-stuff at gmx.de > <mailto:trash-stuff at gmx.de> wrote: > >> Hi all, >> >> I am processing DWARF line and column information in (x86 and ARM) >> executables in order to produce a mapping from the machine >> instructions back to the original source code (C/C++). Using

On May 30, 2011, at 11:11 AM, trash-stuff at gmx.de wrote: > Hi all, > > I am processing DWARF line and column information in (x86 and ARM) executables in order to produce a mapping from the machine instructions back to the original source code (C/C++). Using the line numbers is quite straightforward ("libdwarf" [1] is doing the work me.) But when comparing the column numbers

On May 31, 2011, at 10:36 AM, trash-stuff at gmx.de wrote: > On 31.05.2011 19:22, Devang Patel wrote: >> >> >> On May 30, 2011, at 11:11 AM, trash-stuff at gmx.de wrote: >> >>> Hi all, >>> >>> I am processing DWARF line and column information in (x86 and ARM) executables in order to produce a mapping from the machine instructions back to

On 31.05.2011 19:45, Devang Patel wrote: > > On May 31, 2011, at 10:36 AM, trash-stuff at gmx.de > <mailto:trash-stuff at gmx.de> wrote: > >> On 31.05.2011 19:22, Devang Patel wrote: >>> >>> On May 30, 2011, at 11:11 AM,trash-stuff at gmx.de >>> <mailto:trash-stuff at gmx.de>wrote: >>> >>>> Hi all, >>>>

Hi, I am trying to use existing C++ code from R. I have no problems compiling C code and using it in R, but with C++ I'm running into problems. Here's the compiler output: Macintosh-10:~/Desktop/dissertation/Model - CPP version/R labguest$ g++ -I/Library/Frameworks/R.framework/Resources/include -I/Library/Frameworks/R.framework/Resources/include/i386 *.cpp In file included from

Dear R-SIG-Debians, I have difficulties installing packages from within R through install.packages(). R version is 3.2.0 and OS is Linux Mint 17.1. For most packages, a lot of error messages come up which seem to be related to compilation. Installing packages provided by the ubuntu distro through apt-get works just fine. I followed all directions given in CRAN's

Hello xapian users, The server I'm compiling on is a little odd. SunOS on a sun4 architecture. Fails when linking, gives the following, memcpy 0x10 /usr/local/gcc-3.3.2/lib/./libstdc++.a(ctype.o) ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status *** Error code 1 make: Fatal error:

No, Chris, I'm not buying that argument, due to I've tweaked /usr/include/types.h a little bit, so the configuration and compilation of the cfrontend would be correct: /* * 64bit type for BSD compatability */ #ifdef __GNUC__ typedef long long int quad_t; typedef unsigned long long int u_quad_t; typedef long long int int64_t; typedef unsigned long long int u_int64_t;

Hi guys Is some one able to explain me, why these errors emerge: gmake[2]: Entering directory `/usr/local/src/llvm/lib/VMCore' Compiling AsmWriter.cpp AsmWriter.cpp: In function `void WriteConstantInt(std::ostream&, const llvm::Constant*, bool, std::map<const llvm::Type*, std::string, std::less<const llvm::Type*>, std::allocator<std::pair<const llvm::Type* const,

On Wed, 7 Jul 2004, Henrik Bach wrote: > This tweak seems to work. > > As far as I can see, correct me if I'm wrong, it is the compiler, that can't > figure out which std::basic_ostream to use. Why? What I'm saying is that it appears that your implementation of operator<< is not functional or is missing. You said that you are using GCC on internix. Is it possible

Yes, Chris you're right. It seems that my << operator for int64_t is missing in my '/opt/gcc.3.3/include/c++/3.3/bits/ostream.tcc' file. Which ordinary version of GCC are you working with and how do your definition of the << operator for int64_t look like? /Henrik > >Here is an excerpt from the config.log for LLVM: > >configure:19451: checking for int64_t

Hi, Consider the following file. ******************************* foo.cc ******************************* #include <R.h> #include <Rinternals.h> #include <iostream> ******************************* R CMD SHLIB foo.cc gives scads of errors. I've use C++ extensively with R before (using C linkage) but not with Rinternals.h. I'm puzzled. The errors make no sense to me. Am

Thanks for the suggestion, Andre. I downloaded GNAT GPL 2007, and followed the directions on your web page. Now I get a lot of C++ errors. In fact, the output I captured to a log file is over six megabytes just from the start of the problem command to the termination of the make. I'm obviously not going to include it all here, but the command and the first few errors are copied below.

Hello, I use the zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs are producing these errors every so often, but AFAICT the messages themselves aren't getting corrupted. Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0) Fatal: master: service(imap): child 80128 killed with

Hi all, With the newest patches to LLVM, there should be no reason for having "#include <iostream>" in any library source code file, except for lib/ Support/Streams.cpp. Please use the following instead: OLD NEW --- --- std::ostream llvm::OStream std::istream llvm::IStream std::cerr llvm::cerr std::cerr llvm::cout

I see this in my logs after 2.3.3: using zlib plugin, ofc. Oct 02 10:01:39 imap(user at example.com)<50643></2k4Sjp3vMqC496W>: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0 || zstream->ostream.error_handling_disabled) Oct 02 10:01:39 imap(user at

Hi! After upgrade I'm noticing many coredummps, below is backtrace: $ echo "bt"|gdb .... #0 o_stream_zlib_flush (stream=0xc8be5b27640) at ostream-zlib.c:222 222 if (o_stream_zlib_send_flush(zstream) < 0) (gdb) #0 o_stream_zlib_flush (stream=0xc8be5b27640) at ostream-zlib.c:222 #1 0x00007a695e8f09cd in o_stream_flush (stream=stream at entry=0xc8be5b276d0) at

On 5 Jan 2018, at 18.33, Carsten Uppenbrink <info at uppenbrink.net> wrote: > > On 24.12.2017 15:58, Adam Weinberger wrote: >> Hello, >> I use the zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs >> are producing these errors every so often, but AFAICT the messages >> themselves aren't getting corrupted. >> Panic: file ostream-zlib.c: line

Hi Timo, I Trying to integrate my antispam with dovecot, using the imap folder to do certain actions. I Do almost every thing, but i have some problems saving the message. Explaining this function, i try to use a imap folder like a "collector folder", the user append a message from outside (ie another imap or pop message) to this folder, and i don't want to copy this message, i

On 12 Jul 2019, at 21.05, Michael Grimm via dovecot <dovecot at dovecot.org> wrote: > > Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > >> We are pleased to release Dovecot release v2.3.7. > > My upgrade from 2.3.6 to 2.3.7 broke replication (FreeBSD 12.0-STABLE r349799): > > | dovecot[76032]: master: Dovecot v2.3.7 (494d20bdc) starting up for