Displaying 20 results from an estimated 20000 matches similar to: "start valgrind and asterisk via init.d script"
2005 Aug 31
4
/etc/init.d/asterisk barfing
Ok, starting to get cheesed off and feeling rather silly.
cvs head as of 5 minutes ago.
#root asterisk -vvvvvvvc
works, no problem.
#root safe_asterisk
works no problem
#root service asterisk start
Starting asterisk: [ OK ]
#root asterisk -r
Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?)
/var/run/asterisk.ctl and
2011 Mar 03
1
asterisk dump core when i try to record my name on the voicemail
i m using asterisk 1.8.3 on a centos 5.5 computer
when i try to change my name on the voicemail asterisk dump core
here what i got on the console
-- User ended message by pressing #
-- <SIP/6672-00000002> Playing 'auth-thankyou.alaw' (language 'fr')
-- <SIP/6672-00000002> Playing 'vm-review.alaw' (language 'fr')
-- Saving message as
2011 Nov 20
4
Deleting AstDB family at start
Is it possible to delete the keys belonging to a family in AstDB at Asterisk startup? I would like to repopulate it from another source each time Asterisk is restarted.
I know there is a DBdeltree(<family>) function. Is there a context that only runs once (automatically) at Asterisk startup (so that I can call this function)?
Also is AstDB lookup faster than a func_odbc lookup? Is there a
2010 Sep 02
5
How to create a coredump for Asterisk
Hi everybody,
sometimes we have an Asterisk-crash, but no clue why this is happening,
so I'm trying to make a coredump to analyse it.
I compiled Asterisk 1.4.20.1 on CentOS 5.4 i386 with "DEBUG_THREADS" and
"DONT_OPTIMIZE", then I start it with:
# /bin/bash /usr/sbin/safe_asterisk
This should do an "ulimit -c unlimited", but I entered it in the
terminal again.
2014 Mar 21
3
Need more meetme users -- hitting some limit
I'm trying to determine the capacity of my host running Asterisk 11.8.1 on
CentOS 6.5.
The host is an Intel E3-1240v3 with 8GB RAM, an SSD, and gigabit Ethernet.
The primary application will be bridging groups of users using meetme().
I'm using 2 boxes -- 1 to initiate calls using call files (box1), and 1
behaving a bit more like a production box -- bridging calls (box2).
The call
2018 Jul 01
2
[PATCH nbdkit] valgrind: Don't call dlclose when running under valgrind.
When valgrinding plugins, the following sequence can happen:
plugin_free
-> dlclose
-> unloads the plugin and symbol table
exit
-> valgrind prints failures
(the same applies to filters). When valgrind is printing the
failures, it looks up the addresses in the symbol table, but that has
been unloaded already so all you see are "???", resulting in useless
2012 May 10
0
Using valgrind to debug R, extracting column of a mts object causes valgrind to crash
Dear all,
I'm trying to debug my R package with valgrind, but I cannot get past the
point where I load make the data, as valgrind crashes when trying to
extract a single time series object of a multivariate mts object. I'm using
R 2.15.0 with platform x86_64-redhat-linux-gnu (64-bit).
The valgrind.R contains code
data(Seatbelts)
y<-Seatbelts[,"VanKilled"]
And I run
2020 Jun 22
0
valgrind-mmt: rebased against latest upstream valgrind release v3.16.1
As an update to the nouveau development community, the downstream fork of
Valgrind with a mmap tracing tool ("mmt") we maintain has been rebased
against the latest upstream release of Valgrind, v3.16.1
Code branch: https://github.com/envytools/valgrind/tree/mmt-3.16.1
Features of upstream Valgrind 3.16.x:
https://www.valgrind.org/docs/manual/dist.news.html
In selected highlights, the
2009 Aug 16
1
R CMD check --use-valgrind doesn't run valgrind on tests
R CMD check --use-valgrind <packagename> used to run valgrind on the
tests in the tests directory of the package. But it seems to have stopped.
R-2.9.1 doesn't -- at least on my box -- and neither does R-2.10.0 (devel).
I am not sure when this stopped. I think 2.8.x did this. The only old
R I have around is 2.6.0 and it certainly does.
R CMD check --help for 2.9.1 says (among other
2016 Apr 15
1
[PATCH 1/2] valgrind: Use --trace-children=no --child-silent-after-fork=yes
When we are valgrinding we don't really care about the child
processes, which might be qemu, libvirtd, etc. So disable tracing
into children (at least, as far as is possible with valgrind, which is
not entirely disabling it, but suppressing it).
---
m4/guestfs_progs.m4 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/m4/guestfs_progs.m4 b/m4/guestfs_progs.m4
index
2018 Dec 02
0
[PATCH nbdkit 3/4] valgrind: Enable valgrinding of Python plugin.
I had to add several suppressions because Python leaks memory by
design, and also increase the max depth of valgrind stack traces
because Python stack traces are very deep.
Note that to do proper valgrinding of Python itself we would need to
specially recompile Python:
https://svn.python.org/projects/python/trunk/Misc/README.valgrind
---
tests/test-lang-plugins.c | 3 +-
2017 Feb 20
0
compiling with --enable-valgrind
Hello. I want to compile trunk speex.
./configure --prefix=/opt/speex --enable-option-checking --disable-silent-rules --disable-maintainer-mode \
--enable-shared=yes --enable-static=yes --enable-fast-install=yes --enable-dependency-tracking \
--enable-libtool-lock --enable-valgrind --enable-sse --enable-binaries --enable-vbr \
--disable-fixed-point-debug --enable-vorbis-psy --with-pic
2012 Jan 24
1
[PATCH] Enable running the daemon under valgrind.
From: "Richard W.M. Jones" <rjones at redhat.com>
This commit allows you to run the daemon under valgrind. You have to
enable it at configure time:
./configure --enable-valgrind-daemon
This should *not* be done for production builds.
When this feature is enabled, valgrind is added to the appliance and
the daemon is run under valgrind. Log messages from valgrind are
passed
2009 Aug 11
0
sub-architecture installation difficulty with various valgrind-instrumentation levels
"R Installation and Administration", section 2.5 "Sub-architectures" describes
calling specific builds of R using the call "R --arch=name". I am trying to
build and install three versions of R-2.9.1, each configured with a different
valgrind-instrumentation level ("Writing R Extensions", section 4.3.2 "Using
valgrind"). My goal is to be able to
2018 Nov 14
0
[PATCH nbdkit v3 4/4] tests: Valgrind is only enabled when NBDKIT_VALGRIND = 1, not any other values.
Fix the tests so they only enable valgrind workarounds or skips when
NBDKIT_VALGRIND is exactly set to "1" and not any other values
(including empty string, or not set).
Thanks: Eric Blake.
---
tests/test-dump-plugin.sh | 3 ++-
tests/test-ext2.c | 4 +++-
tests/test-help.sh | 3 ++-
tests/test-lang-plugins.c | 4 +++-
tests/test-ocaml.c |
2012 Sep 12
2
valgrind crashing
I am trying to do a classic
R -d valgrind --vanilla < mypkg-Ex.R
as described in
http://cs.swan.ac.uk/~csoliver/ok-sat-library/internet_html/doc/doc/R/2.9.1/doc/manual/R-exts.html#Using-valgrind
The problem is valgrind crashes imediately.
I am using Ubuntu 10.04 LST (actually Biolinux) on a 64bit Dell
Precision laptop with 4 core-i5 Intel processors. I have R-2-15-0
installed from source
2015 Feb 26
2
valgrind support
Hi,
I just pushed valgrind support for the regression and unit tests. If you
run "make tests USE_VALGRIND=1" then almost all the tests will be run
under valgrind.
The valgrind output is dumped in regress/valgrind-out with a file per
{ test, binary, PID }. There is no analysis or summarisation yet (want
to help? write a summarisation script)
Some warnings:
First, it's slow. My
2013 Apr 21
0
[PATCH] Reduce valgrind num-callers to 50
My Valgrind doesn't run, saying it doesn't support showing more
than 50 entries of a stack trace
---
test/test_bins.sh | 4 ++--
test/test_flac.sh | 8 ++++----
test/test_grabbag.sh | 8 ++++----
test/test_libFLAC++.sh | 2 +-
test/test_libFLAC.sh | 2 +-
test/test_metaflac.sh | 12 ++++++------
test/test_seeking.sh | 12 ++++++------
2006 Nov 20
0
valgrind and libusb calls
NUT developers,
just thought I'd share some notes and ideas on using valgrind against
the NUT USB drivers on Linux.
Stepping back a bit, I wanted to make sure that the tripplite_usb
driver* wasn't using any uninitialized memory, or leaking memory over
time. valgrind (specifically, the memcheck tool) runs the code in a
special dynamic translator that checks every memory access to see if
2009 Dec 29
1
different behaviour of NAs under valgrind (PR#14171)
Full_Name: Martin Schlather
Version: 2.10.0
OS: linux
Submission from: (NULL) (91.3.220.231)
Bug summary:
some functions behave differently for NAs when
valgrind is used in R, e.g. sum and prod
Bug demonstration:
--- without valgrind ----
> sum(c(NA,1)[1])
[1] NA
--- with valgrind ----
> sum(c(NA,1)[1])
[1] NaN
R call with valgrind:
R -d "valgrind --tool=memcheck