I'd like to do something like "Make current" but for Windows because I'm finding bugs to report.? One was on how the dialplan's extensions are being parsed. Extensions in some cases like when doing originates with sched_api, loose their last character and I have to add a white space after to solve the problem. Another issue is that dialing one extension landed me into another totally different extension. I had to comment it out to target the right extension. Maybe the reporting bugs wiki needs updating for Windows users (experienced and inexperienced). Thanks. Mark. ? -----Original Message----- From: Brian West <brian@freeswitch.org> To: freeswitch-users@lists.freeswitch.org Sent: Wed, 25 Mar 2009 12:07 pm Subject: Re: [Freeswitch-users] Question about FAQ question On Mar 25, 2009, at 2:01 PM, Josh Forman wrote:

I'm running Freeswitch on Ubuntu 64bit Intrepid and on a svn rev 12722, freeswitch would install and run fine but as soon as calls started coming in it would have a segmentation fault. This is the second svn snapshot I've had this happen on.

Please review http://wiki.freeswitch.org/wiki/Reporting_Bugs Collect the info and report it on jira. If it still happens on SVN trunk as of NOW then please collect the back trace as per the reporting bugs guide and we'll investigate the issue. Also be aware if you aren't doing a "make current", you could have build skew which could be the whole problem all along. Incorrectly updating your system will result in all kinds of strange behaviors.

In the Freeswitch FAQs there is a question concerning segmentation fault on ubuntu 64bit except they say it occurs on start. Their solution is to recompile libedit which I plan to try regardless, but I just wanted to know if the scenario they refer to is the same as what I'm experiencing or was there some other problem where freeswitch would segfault while initially loading.

I don't think this is the problem you're having.

Until then I'm still running rev 12289 on the system that is having issues.

This is a rather old REV, How about you report your back trace to jira as per the instructions above.

Thanks -Josh

_______________________________________________ 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

_______________________________________________ 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

Maybe the reporting bugs wiki needs updating for Windows users (experienced and inexperienced).

Quite possibly. The instructions are not explicit. I will add something for the Windows users that's a bit more specific. -MC

2009/3/25 <mszlazak@aol.com>:

Thanks MC, maybe a link to that "TortoiseSVN" would help for some in the Windows crowd.

Done!

TortoiseSVN has a bunch of stuff in it but to make it simple, especially for doing updates to report bugs, then mentioning if doing just an "SVN update" will work before rebuild. Also, what to do if one gets an errror using SVN Update. I got one about not being able to open a file. So, I didn't know if any of the rest of the SVN update succeeded. I guess it wasn't a "clean" update. I didn't bother rebuilding afterwards since I also didn't know if it would work. There was to much to go through in TortoiseSVN documentation for the time I had so I didn't report the errors and left things for later when I would just download and install a newer version of FS. It sounds lazy but as an inexperienced user it's enough discouragment to let these things go. Anyway, just a bit more instructions might get more bugs reported.

Understood. We can't anticipate every possible error and give documentation otherwise the Reporting Bugs page would be a lot larger than it is. In cases like this I recommend the panacea for all ills: Google. :) -MC