similar to: [LLVMdev] Build problems with llvm-gcc

Hi everyone, -r136747 of llvm-gcc (and possibly others) is apparently tickling a binutils issue on linux x86-64 Has anyone seen anything like this? Thanks -jason -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110806/e7e717ef/attachment.html> -------------- next part --------------

This shouldn't be considered our bug (should it?). I'm going to report it to Ubuntu. I will restart my build, but does anyone else see this on Ubuntu 11.04? Note that I have a 32-bit machine with 2 GB of RAM and no swap. $ ld --version GNU ld (GNU Binutils for Ubuntu) 2.21.0.20110327 Copyright 2011 Free Software Foundation, Inc. $ uname -a Linux frylock 2.6.38-11-generic #50-Ubuntu

I have been following the "Asterisk CLI unresponsive" thread and saw the suggestion to enable BETTER_BACKTRACES when I went in to do that it said it requires libbfd.. When I went to add that from yast I get no packages by that name. I am on openSUSE an ideas if this is part of another package or how I would get it? Thanks Bryant -------------- next part -------------- An HTML

ok I know this isn't realy a samba issue but I'm trying to gather some debug info on winbindd for the samba development guys, but I can't compile gdb 5.x or 6.0 on my solaris 9 box! Every other compile problem I've come across I've resolved by searching through google but not this time. If anyone can help I'd realy appreciate it, problem is (using gcc 3.3.2) gcc -g -O2

Hi, What does llvm use for testing. The area of testing I am interested in are how to test the accuracy of the assembler/disassembler. So, if you take an IR level instruction. How do you verify that the generated CPU specific instruction is correct? Is there an automated method for this? I wish to implement automated testing on a decompiler I am writing, and thought that the test methods used in

Thanks for the reply. On 28 April 2014 20:01, Reid Kleckner <rnk at google.com> wrote: > The problem with tcmalloc seems like a real problem. I can't think of any > good workarounds. My best worst idea is to try to figure out if malloc is > coming from libc with dlsym and dlopen, and then use that to decide whether > we add these two numbers together. I'm not sure we

While trying to run libguestfs tests after building with "--enable-appliance --with-supermin-extra-options=--use-installed", I ran into a peculiar error message in the c-api test: ,---- | libguestfs: error: strings: /abssymlink: strings: error while loading | shared libraries: libbfd-2.24-multiarch.so: cannot open shared object | file: No such file or directory `---- The problem here

Hi Holger, > Note that I did specify "-g", but not any "-Ox" switches. That > made the size of all *.o files together being 143 MB. LLVM represents debug info as explicit calls to intrinsics. This approach has many advantages, but a possible disadvantage is that it can significantly increase the size of the bitcode. I don't know if that explains your observations.

I'am now considering converting x86 machine assembly into LLVM IR, does anyone know about any existing project or resource related to this area? Any difficulities or any ideas on this? thanks for your replies in advance. cradnil 2008-03-04 -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I am trying to preload two shared libraries while running Qemu using libvirt. To preload the shared libraries I have added an environment variable in the $domain.xml file with the following command: ``` virt-xml generic --edit --confirm --qemu-commandline

The Asterisk Development Team has announced the release of Asterisk 1.4.40. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.4.40 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this

The Asterisk Development Team has announced the release of Asterisk 1.4.40. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.4.40 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this

The Asterisk Development Team has announced the release of Asterisk 1.6.2.17. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.6.2.17 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this

The Asterisk Development Team has announced the release of Asterisk 1.6.2.17. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.6.2.17 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this

The Asterisk Development Team has announced the release of Asterisk 1.8.3. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.8.3 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this release:

The Asterisk Development Team has announced the release of Asterisk 1.8.3. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.8.3 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this release:

Hello, Jeff. You wrote Saturday, April 29, 2006, 10:50:08 PM: JC> You will. You haven't gotten that far yet. It shows up as a crash JC> running gccas. Ok. Switched to 2.1 JC> As for ld crashing, I have no suggestions. It seems to be bug in bfd/cofflink.c file of libbfd. I can even name the function, where weird thing happens. But it's out of my possibilities to debug this

> LLVM represents debug info as explicit calls to intrinsics. > This approach has many advantages, but a possible disadvantage > is that it can significantly increase the size of the bitcode. > I don't know if that explains your observations. I'm curious > to know how gcc stores debug info... GCC stores debug info in ELF sections of the .o file, e.g.: $ objdump -h wtd.o

> What you are looking for is smbwrapper, which is in fact included with Samba > 2.0. However as it is not supported on all systems it is not included > in the default build (it should work nicely on Solaris though). > Essentially smbwrapper is a preloaded library which intercepts system calls and > simulates a /smb filesystem, so you can access /smb/SERVER/SHARE/file.txt.

Hi, This is a proposed fix for bug 16847 [1]. It is essentially the patch provided by Martin Nowack in the bug report but I have added a test case and an ifdef macro around the modified code in Process::GetMallocUsage() The issue seems to be that the ptmalloc2 allocator used in glibc (in my case 2.19) does not include mmap()'ed memory in mallinfo.uordblks and so mallinfo.hblkhd needs to be