search for: allocations

....3 0:00.06 bash 11316 root 15 0 3332 1112 572 S 0.0 0.2 0:01.14 crond 16282 root 25 0 4756 1008 820 S 0.0 0.2 0:00.00 safe_asterisk 22514 root 25 0 494m *445m* 6612 S 0.0 *87.0* 663:08.66 asterisk virtual1_ast1*CLI> memory show summary 4644 bytes in 2 allocations in file 'res_timing_pthread.c' 4096 bytes in 1 allocations in file 'chan_unistim.c' 484 bytes in 1 allocations in file 'res_clialiases.c' 96 bytes in 2 allocations in file 'devicestate.c' 244 bytes in 1 allocations in file 'iax2-pr...

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

...fter compiling Asterisk with the MALLOC_DEBUG flag, when the problem happened we could see this output with the most consuming files, using "memory show summary" command: # cat memory_show_summary_201711101144.log | sort -nr | head 3060904798 bytes allocated (431496 in caches) in 16185877 allocations 1467180225 bytes in 1647238 allocations in file stasis_channels.c 1217035109 bytes in 10229320 allocations in file json.c 240064732 bytes in 1765287 allocations in file stasis_message.c 56402000 bytes in 1762250 allocations in file taskprocessor.c 26125344 bytes in 203171 alloca...

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

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 > > >

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

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

...this to behave in our code? Some options: - Assert that Allocate never gets a size 0 allocation. So fix StringRef::copy to see this case - Remove the attributes from Allocate but continue to return nullptr (or base of the allocator?) in this case - Keep the attributes on Allocate and treat size 0 allocations as size 1 Thanks, Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160322/619fe5dc/attachment.html>

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

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

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

...e? > > Some options: > - Assert that Allocate never gets a size 0 allocation. So fix StringRef::copy to see this case > - Remove the attributes from Allocate but continue to return nullptr (or base of the allocator?) in this case > - Keep the attributes on Allocate and treat size 0 allocations as size 1 > > I believe the last is closer to 'new's behavior - which I think returns a unique non-null address (well, unique amongst current allocations - can be recycled once deleted) if I recall correctly. That’s what I would have expected too. Its like sizeof(struct {}) which ca...

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

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

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

...; Some options: >> - Assert that Allocate never gets a size 0 allocation. So fix StringRef::copy to see this case >> - Remove the attributes from Allocate but continue to return nullptr (or base of the allocator?) in this case >> - Keep the attributes on Allocate and treat size 0 allocations as size 1 >> >> I believe the last is closer to 'new's behavior - which I think returns a unique non-null address (well, unique amongst current allocations - can be recycled once deleted) if I recall correctly. > That’s what I would have expected too. Its like sizeof(struc...

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

...t;> - Assert that Allocate never gets a size 0 allocation. So fix >> StringRef::copy to see this case >> - Remove the attributes from Allocate but continue to return nullptr (or >> base of the allocator?) in this case >> - Keep the attributes on Allocate and treat size 0 allocations as size 1 >> > > I believe the last is closer to 'new's behavior - which I think returns a > unique non-null address (well, unique amongst current allocations - can be > recycled once deleted) if I recall correctly. > > That’s what I would have expected too. Its lik...

...gt; Some options: > - Assert that Allocate never gets a size 0 allocation. So fix > StringRef::copy to see this case > - Remove the attributes from Allocate but continue to return nullptr (or > base of the allocator?) in this case > - Keep the attributes on Allocate and treat size 0 allocations as size 1 A fourth option would be return a non-null pointer (maybe the address of some static char) for allocations of size 0; unless I'm mistaken about the noalias bit above. -- Sanjoy

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. >