VoIP Mailing List Archives

[carole.olivier at enst.fr]

Sorry, here is the profile profile speaker

<profile name="profilespeaker">
< param name="rate" value="8000" />
< param name="interval" value="20" />
< param name="energy-level" value="300" />
< param name="caller-id-name" value="$${outbound_caller_name}" />
< param name="caller-id-number" value="$${outbound_caller_id}" />
< param name="comfort-noise-level" value="1400" />
< param name="comfort-noise" value="true" />
< param name="member_flags" value="waste" />
< param name="auto-record"
value="$${base_dir}/recordings/${conference_name}_${strftime(%Y-%m-%d-%H-%M-%S)}.wav"
/>
</profile>

--
View this message in context: http://www.nabble.com/segmentation-fault-by-auto-record-tp20935513p20935752.html
Sent from the Freeswitch-users mailing list archive at Nabble.com.


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[msc at freeswitch.org]

Thanks for reporting this. It would be helpful to know a bit more. Can
you start freeswitch and press F12 (or type "version" at the CLI) and
report back what it says?
Also, a backtrace (bt) is generally useful. If you could produce a
"bt" and a "bt full" from you core file that would be extremely
helpful.

see this link for more information:
http://wiki.freeswitch.org/wiki/Debugging_Freeswitch

you should have a "core" file for each segfault that occurred. Use the
gdb program to get the back trace:

gdb /path/to/fs/binary core.xxx

then capture the output from these two commands:

bt <enter>
bt full <enter>

When you type those commands you'll see tons of debugging info;
capture that and put it in a pastebin (pastebin.freeswitch.org) then
report back here.

You can exit the gdb debugger by typing q <enter>

Thanks for helping us collect information!

-MC


On Wed, Dec 10, 2008 at 5:37 AM, Carole O. <carole.olivier@enst.fr> wrote:

[brian at freeswitch.org]

I have already labbed this up on SVN trunk and I don't get a segfault but I get something else that prevents it from working properly. We are working on it today. Also what version are you running?

/b

On Dec 10, 2008, at 9:53 AM, Michael Collins wrote:

[carole.olivier at enst.fr]

Hello,

I am running the version 1.0.1.
Do you still need me to run the debugging?

Carole


Brian West-3 wrote:

[msc at freeswitch.org]

Carole,

There have been many updates since 1.0.1 was officially released. If
you could start FreeSWITCH and then press F12 it will reveal which SVN
revisionnumber you are running. Please supply that number and it will
help us to know if you are on a recent revision.

Thanks,
MC

On Wed, Dec 10, 2008 at 10:51 PM, Carole O. <carole.olivier@enst.fr> wrote:

[carole.olivier at enst.fr]

I have got the following:
Freeswitch Version 1.0.1 (9171)

Carole



Michael Collins-11 wrote:

[msc at freeswitch.org]

Wow! That is really old. I strongly recommend that you update to the
latest trunk using svn.

-MC


On Dec 10, 2008, at 11:33 PM, "Carole O." <carole.olivier@enst.fr>
wrote:

[carole.olivier at enst.fr]

ok !

Well, I installed it from opensuse.org, I thought it would be easier for me
since I am completely new here.
Is there a simple way to update this package or would you recommend me to
uninstall the rpm and install freeswitch completely new from the source code
you provide?

Thanks,
Carole


Michael Collins-11 wrote:

[william at channelxstr...]

Carole,

1.0.1 is known to be broken now. Can you go into the directory where you
have the freeswitch source from the svn repo and type 'make current'.
This will update freeswitch to trunk.

-William

On Wed, 2008-12-10 at 22:51 -0800, Carole O. wrote:

[anthony.minessale at g...]

issue should be fixed in SVN r10723

On Thu, Dec 11, 2008 at 1:01 AM, William King <william@channelxstream.com (william@channelxstream.com)> wrote: