Re: [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139

. Charles Kanngiesser, Wolfgang [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/07/2008 07:07 AM To sipp-users@lists.sourceforge.net cc Subject [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139 Hi all, recently I am asking for a error segmentation fault due

Re: [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139

To sipp-users@lists.sourceforge.net cc Subject [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139 Hi all, recently I am asking for a error segmentation fault due to the external commands, i.e. action exec command=echo pass verdict.log/ /action The problem

Re: [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139

Wolfgang, I tried the scenario with the SVN trunk and did not get an error. Charles Kanngiesser, Wolfgang [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/07/2008 07:07 AM To sipp-users@lists.sourceforge.net cc Subject [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139 Hi all

[Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139

Hi all, recently I am asking for a error segmentation fault due to the external commands, i.e. action exec command=echo pass verdict.log/ /action The problem is still relevant but all scenarios worked properly until sipp2.0. There are any hints? Thanks,Wolfgang. Deutsche Telekom AG

[Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139

Hi, a scenario containing the following element: action exec command=echo pass verdict.log/ /action breaks whith the error segmentation fault (Speicherzugriffsfehler) and the exitcode 139. sipp -v - SIPp v3.1-TLS-PCAP, version unknown, built Apr 29 2008, 14:46:06. This scenario worked