[PyKDE] Segv debugging

[Phil Thompson]

When I said "as of now" I was referring to current snapshots.

Phil

On Thursday 16 October 2003 11:49 am, Patrick Stinson wrote:
> Is that the -r option on build.py? Doesn't that set the dir containing qt
> lib files?
>
> bash-2.05b$ python build.py --help
> ...
>     -r dir         the directory containing the Qt library [default
> $QTDIR/lib]
> ...
> bash-2.05b$
>
> On Wednesday 15 October 2003 19:47, Phil Thompson wrote:
> > On Thursday 16 October 2003 4:21 am, Derek Fountain wrote:
> > > When getting a segv from a PyQt script, is there a way of getting and
> > > using a core dump such that it might provide a clue as to what I've
> > > done wrong? What steps do developers take when faced with a segv?
> >
> > Getting a core dump depends on your shell...
> >
> > ulimit -c unlimited
> >
> > ...for bash.
> >
> > As of now you can also build a trace enabled version of PyQt (build it
> > with the -r flag). To switch traces on, put the following in your
> > script...
> >
> > # The SIP v4 module is called sip.
> > import libsip as sip
> >
> > sip.settracemask(0xff)
> >
> > ...you can change the mask at any time. See the SIP_TRACE_* values in
> > sip.h to see the detail of which trace messages correspond to which bit
> > of the mask.
> >
> > Phil
> >
> > _______________________________________________
> > PyKDE mailing list    PyKDE at mats.imk.fraunhofer.de
> > http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
>
> _______________________________________________
> PyKDE mailing list    PyKDE at mats.imk.fraunhofer.de
> http://mats.imk.fraunhofer.de/mailman/listinfo/pykde