[sldev] Technical question

Carlo Wood carlo at alinoe.com
Wed May 6 11:04:12 PDT 2009


I wish to debug something that happens as a result
of a server message - but I have no idea where to
start (where to put the breakpoint).

I can trigger this by editting a prim. For
example-- I create a box, and then I change
a value in the Object TAB (ie, position or
rotation etc) and hit enter. This will send a
message to the server.

I am assuming that some feedback message will
be returned by the server to tell my client that
the prim changed.

What would be ideal is if I could set a break-
point somewhere where I can check WHICH object
was changed (so that I'm sure that if the breakpoint
is hit, it is what I need *), as opposed to for
example set a break point in a function that is
hit *every* message from the server. The latter
obviously won't help much cause there are too
many incoming messages.

Can someone shine a light on this for me?
What would be a good point to intercept this?

-- 
Carlo Wood <carlo at alinoe.com>

*) I think that an LLViewerObject point is
unique, so comparing a pointer passed to
the function that I have my break point in
(with a gdb condition) should do the trick
to break at the moment the prim under
investigation changed.



More information about the SLDev mailing list