|
yes, I run openser with
fork=no
but, I can't debug a module using
kdevelop.
I set the breakpoint, but don't
stop.
run only the "main" and
exit.
if I type "ps -e" I see the deamon
of openser
another program to debug openser
?
----- Original Message -----
Sent: Monday, July 17, 2006 11:40
AM
Subject: Re: [Devel] How I configure
kdevelop to see the debug of any module?
On 07/17/06 17:37, Javier Ramirez wrote:
>
> How I configure kdevelop to see the debug of any module?
most
probably you have to start openser in no fork mode (fork=no in the
config
file). In this way you can watch the processing of the sip
messages with
the main openser process.
Cheers,
Daniel
>
>
> *From:*
Javier Ramirez <mailto:[EMAIL PROTECTED]>
>
*To:* Ron Winacott <mailto:[EMAIL PROTECTED]>
;
> [email protected] <mailto:[email protected]>
>
*Sent:* Friday, July 14, 2006 11:11
AM
> *Subject:* Re:
[Devel] kdevelop
?
>
> I don't
undestand.
> How
attach/debug openser
?
>
> best
regards
>
>
>
>
>
Javier,
> The problem is
kdevelop must debug (attach its self to) a
main
> process
and
> the modules in
OpenSER/SER ae dynamically loaded
libraries
> (*.so =
shared
> object) To
debug the module code, you must
attach/debug
> openser
then set a
> break point
in your module code so when the
openser.cfg
> line
"loadmodule /usr/local/openser/modules/YourMod.so" is
run
> openser
will
> call dl_open()
and locate the module expore structure. Then
it
> will call
the
> modules exported
initialization function. (mod_init()
or
> something
along
> those lines,
depending on what you called it., look at
the
> source in
the
> struct
module_exports exports {
structure)
>
>
Once you have stopped the debugger in your module you
should
> be able to
see
> the source,
symbols, etc of your module and set break
points.
>
> The
other issues (bigger one in my mind) is you must
start
>
openser
> in
"non-forking" mode to stop it from creating a bunch
of
> listener
processes
> where in
each one you are running a copy of your module.
In
> the
openser.cfg
> set
"fork=no" to stop it from forking. Also you waht to
make
> sure you
debug
> the correct
process. If you start openser, then
run
> "openserctl ps"
you will
> see a list of
processes. You what to debug the
"receiver"
> process. It
is the
> one that will
call into your
module.
>
> Hope
this helps,
>
ronw
>
> --
> Ron Winacott - SOMA
Networks, Inc.
>
---
> The scientists of
today think deeply instead of clearly.
One
> must be sane
to
> think clearly, but
one can think deeply and be quite
insane.
> - Nikola
Tesla
>
>
>
----- Original Message
-----
>
*From:* Ron Winacott <mailto:[EMAIL PROTECTED]>
>
*To:* [email protected] <mailto:[email protected]>
>
*Cc:* Javier Ramirez <mailto:[EMAIL PROTECTED]>
>
*Sent:* Thursday, July 06, 2006 3:15
PM
>
*Subject:* Re: [Devel] kdevelop
?
>
>
On Thursday 06 July 2006 11:15, Javier Ramirez
wrote:
>
> Hi, I have a problem with my
module,
>
> when I try debug using kdevelop, rhis don't show me
a
>
debug of my
module,
>
> only show the debug of
openser.
>
>
>
> How I configure kdevelop to see the debug of any
module?
>
> or, can you recomend any program to use for this
?
>
> best
regards
>
> Javier
Ramirez
>
>
------------------------------------------------------------------------
>
_______________________________________________
>
Devel mailing list
> [email protected]
>
http://openser.org/cgi-bin/mailman/listinfo/devel
>
>
------------------------------------------------------------------------
>
_______________________________________________
>
Devel mailing list
> [email protected]
>
http://openser.org/cgi-bin/mailman/listinfo/devel
>
>
------------------------------------------------------------------------
>
>
_______________________________________________
> Devel mailing
list
> [email protected]
>
http://openser.org/cgi-bin/mailman/listinfo/devel
>
__________ NOD32 1.1663 (20060716) Information __________
This
message was checked by NOD32 antivirus system.
http://www.eset.com
|
