Quite possible -- I believe I have run into these same issues in the past. I have found careful placement of debug statements helps (i.e. right at the place that fails, or where you want to see the value of something, so you don't have to step).
I believe there may also be a gdb command to tell all other threads to continue at full speed while the thread you have the breakpoint stop at steps through code -- though that probably wouldn't help either.. On 1/2/08, Jeremy A <[EMAIL PROTECTED]> wrote: > > Jeremy A wrote: > > Hello, > > > > I have got the latest svn of sipXtapi to compile and build libraries on > > my Centos 5.1 system. However when I compile, link and run my > > application against the libraries I get an assertion error in one of the > > tapi threads > > Problem cause found to be gdb. Or at least it occurs when running the > executable under gdb and not when running it stand-alone. > > Possibly it is a timing dependency in the api that gets triggered when > running slowly under the debugger? > > Jeremy > _______________________________________________ > sipxtapi-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/ > -- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
