search for: allocable

Displaying 20 results from an estimated 25285 matches for "allocable".

2010 Jun 23
2
"Hidden" memory leak
Hi all, Anyone know why this happens? Mem: 524288k total, 508120k used, 16168k free, 0k buffers Swap: 0k total, 0k used, 0k free, 0k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 15 0 2152 664 576 S 0.0 0.1 0:49.26 init 7398 root 18 0 10172 2904 2312 S 0.0 0.6 0:00.21 sshd 9856
2006 Aug 12
1
Strategy pattern: comparing Context/Specify to Given/When/Then
Comments and suggestions for improving the specifications are welcome. Thanks, Alvin One example comparing context/specify (CS) with given/when/then (GWT) with a strategy pattern follows: Consider a pipeline transporting oil supplied by multiple partners. The amounts transported on behalf of each partner are recorded as transactions in a general ledger. There are multiple approaches to
2017 Nov 14
2
RTCP + Stasis causing high memory consumption
Hello Asterisk list, I've facing a memory allocation issue that happens occasionally but on a consistent basis. The problem happens as follow, suddenly Asterisk starts consuming a lot of memory, in a rate of more than 1GB per hour. Kernel will eventually kill it via the OOM killer when memory is really exausted... This situation does not generate backtrace because Asterisk is responsive
2018 Jan 29
1
Panic: data stack: Out of memory when allocating bytes
Any idea what the problem could be? Is there anything more i could do to encircle the problem? Or perhaps is the information i provided uncomplete? Am 25.01.2018 um 16:24 schrieb Thomas Robers: > Hi, > > Am 24.01.2018 um 23:39 schrieb Josef 'Jeff' Sipek: >> It looks like the binaries are stripped.? There should be a "debug" >> package >> you can
2018 Jan 24
2
Panic: data stack: Out of memory when allocating bytes
On Wed, Jan 24, 2018 at 18:55:47 +0100, Thomas Robers wrote: > Am 23.01.2018 um 20:07 schrieb Josef 'Jeff' Sipek: > > On Tue, Jan 23, 2018 at 14:03:27 -0500, Josef 'Jeff' Sipek wrote: > > > On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote: ... > > > 1. Do you have any idea what the imap process was doing at the time of the > > >
2018 Jan 25
0
Panic: data stack: Out of memory when allocating bytes
Hi, Am 24.01.2018 um 23:39 schrieb Josef 'Jeff' Sipek: > It looks like the binaries are stripped. There should be a "debug" package > you can install with symbol information. Then, the backtrace should be much > more helpful. I installed the debug package and the backtrace now is: --- snip --- (gdb) bt full #0 0x00007f73f1386495 in raise () from /lib64/libc.so.6 No
2010 Nov 23
1
Sims 3 Color & Graphics Issues
I've been trying to install The Sims 3 for the last couple of days, and it hasn't been opening. Now that I've finally figured out what i've been doing wrong there's still a major problem. I've installed using playonlinux, and when i open (I use the launcher made by playonlinux, not the actual sims 3 launcher)The screen might turn white, but it always turns black before the
2016 Mar 23
4
UBSan, StringRef and Allocator.h
Hi all (No idea if I have the correct audience. Please CC more people as needed). I have an UBSan failure in BumpPtrAllocatorImpl.Allocate. The problem is that lld requests that we StringRef::copy an empty string. This passes a length of 0 to a BumpPtrAllocator. The BumpPtrAllocator happened to not have anything allocated yet so the CurPtr is nullptr, but given that we need 0 space we think
2019 Sep 03
2
SourceMgr vs EXPENSIVE_CHECKS
Hi, I'm trying to build llvm (git monorepo) on Ubuntu 18.04 with EXPENSIVE_CHECKS enabled and running into various errors compiling SourceMgr.cpp, depending on which host compiler I use. For example with GCC: $ CC=gcc-8 CXX=g++-8 cmake -GNinja -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_EXPENSIVE_CHECKS=ON ~/git/llvm-project/llvm/ && ninja ... [89/2690] Building CXX object
2019 Sep 03
2
SourceMgr vs EXPENSIVE_CHECKS
Hmm. What about the errors I quoted from using clang-7 (starting about a third of the way down my email, sorry if they got kinda lost in all the noise)? Thanks, Jay. On Tue, 3 Sep 2019 at 20:00, David Blaikie <dblaikie at gmail.com> wrote: > > Looks to me like a bug in GCC's constexpr+_GLIBCXX_CONCEPT_CHECKS support. Small test case: > > $ g++-8 test.cpp -std=c++2a
2019 Oct 02
2
SourceMgr vs EXPENSIVE_CHECKS
I just ran into this today. Do we need to update our requirements on libstdc++ version? Jay, did you figure out a way around this? On Wed, Sep 4, 2019 at 5:29 AM David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > It's a bug in libstdc++ - so if you have clang using libstdc++ (which it will by default, I think) then it's the same thing. You could try with
2016 Mar 23
3
UBSan, StringRef and Allocator.h
> On Mar 22, 2016, at 5:35 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Tue, Mar 22, 2016 at 5:30 PM, Pete Cooper <peter_cooper at apple.com <mailto:peter_cooper at apple.com>> wrote: > Hi all > > (No idea if I have the correct audience. Please CC more people as needed). > > I have an UBSan failure in
2018 Dec 11
2
Using LLD to link against third-party libraries? How?
In my code here https://github.com/DragonOsman/currency_converter , I used C++17 and managed to get it to work (though I'm only using std::map::insert_or_assign() from C++17). And I'm using Windows, so I shouldn't use LDFLAGS or CXXFLAGS as environment variables. I'll use them directly on the compiler command line instead. The libraries I need to link against are
2008 Aug 17
1
Allocated Memory Warnings in Vista 32 bit with 4 GB (PR#12557)
Hello I am running Windows Vista 32 with 4 GB (installed, though Windows of cours= e only recognizes 3326 MB, as reported by Windows "My Computer") I am running R 2.7.1 I was trying to read in a comma delimited single column CSV file, assign th= at file to a variable ("data") and then extract a sample (assigned to "part= ial"). I was getting memory allocation
2018 Dec 11
3
Using LLD to link against third-party libraries? How?
Are you linking with a C++ compiler? A lot of those missing symbols look like they come from the C++ standard library. -David Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org> writes: > @blubee blubeeme So what do you think? Got any ideas? > ---------------------------------------------------------------------- > From: Osman Zakir <osmanzakir90
2016 Mar 23
0
UBSan, StringRef and Allocator.h
> On Mar 22, 2016, at 5:39 PM, Pete Cooper via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> >> On Mar 22, 2016, at 5:35 PM, David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> wrote: >> >> >> >> On Tue, Mar 22, 2016 at 5:30 PM, Pete Cooper <peter_cooper at apple.com <mailto:peter_cooper at
2018 Dec 12
2
Using LLD to link against third-party libraries? How?
I couldn't get it to build libcxx... You need c++ and c++abi to compile c++ code. On Wed, Dec 12, 2018, 07:01 Osman Zakir via llvm-dev < llvm-dev at lists.llvm.org> wrote: > LLVM on a Developer Command Prompt. The ones I want to fix first are the > ones from Boost and Jinja2Cpp. I saw some from those as well. > > If there any standard library ones missing, could it be
2016 Mar 28
2
UBSan, StringRef and Allocator.h
FWIW, I agree with Mehdi that we should just assert that our types don't get called with size zero. That said, I don't think we can be terribly cavalier with what we expect from standard allocator types, operator new, or malloc. And so I would expect LLVM_ATTRIBUTE_RETURNS_NOALIAS to not imply NONNULL, and while it seems reasonable to put NONNULL on *our* allocate function because of the
2016 Mar 23
0
UBSan, StringRef and Allocator.h
On Tue, Mar 22, 2016 at 5:30 PM, Pete Cooper via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi all > > (No idea if I have the correct audience. Please CC more people as needed). > > I have an UBSan failure in BumpPtrAllocatorImpl.Allocate. > > The problem is that lld requests that we StringRef::copy an empty string. > This passes a length of 0 to a
2006 Nov 05
0
[LLVMdev] Port succesful
Anton Korobeynikov pravi: > Hello, Ziga. > > >> VCPP throws a warning that class is previously declared as struct. >> Either it must be struct everywhere or class everywhere. >> Declaration uses struct, while the definition uses class. >> > Nice! However it will be better to do the opposite: have it struct > everywhere. I'll fix this. >