I don't know if will be useful for you, but I have used SystemTap.
You can see at least a trace of the functions called.
Info:
http://fedoraproject.org/wiki/Features/SystemtapStaticProbes
http://sourceware.org/systemtap/wiki/PythonMarkers
With
stap /usr/share/doc/python-libs-2.7.3/systemtap-exampl
On Wed, Sep 19, 2012 at 4:54 PM, Gonzalo Odiard wrote:
> You already have the line
> export SUGAR_LOGGER_LEVEL=debug
> uncommented in .sugar/debug, right?
Yes. And with that, datastore.log is very chatty, which is good.
But when the datastore code hits an unhandled exception, the exception
does
You already have the line
export SUGAR_LOGGER_LEVEL=debug
uncommented in .sugar/debug, right?
Gonzalo
On Wed, Sep 19, 2012 at 5:41 PM, Martin Langhoff
wrote:
> On Wed, Sep 19, 2012 at 4:15 PM, Martin Langhoff
> wrote:
> > I'm debugging odd situations w Sugar datastore, and I wonder whether
> >
On Wed, Sep 19, 2012 at 4:15 PM, Martin Langhoff
wrote:
> I'm debugging odd situations w Sugar datastore, and I wonder whether
> there is any tricks to debugging python programs that are run under
> dbus.
>
> I can see the sugar-datastore PID growing steadily while I test, which
> means that it's
I'm debugging odd situations w Sugar datastore, and I wonder whether
there is any tricks to debugging python programs that are run under
dbus.
I can see the sugar-datastore PID growing steadily while I test, which
means that it's dying and respawning plenty, likely from unhandled
exceptions...
th
5 matches
Mail list logo
