Hey Andrew,
we're sprinting on the Packaging system tonight. Why don't you show
up so we can figure out:
1) how to do what you want;
2) improve the doc so it's going to be obvious for the next person who
need to do that.
Cheers,
--
Yannick Gingras
http://ygingras.net
http://montrealpython.org -- lead organizer
http://ajah.ca -- technical lead
Can you make a little post with your findings on this discussion once
you've figure that out? I would have liked to attend to this sprint
but could not. :o(
I am, myself, trying to learn more about the distutils package and my
knowledge is quite elementary. Any additional info/tutorial would be
cool.
You know what? If the doc reflects that, could you just please point
out where to look for and I'll just grab it there; hope this would
avoid any redundancy and additional work for you. Be pragmatic and DRY
(don't repeat yourself) ! If this means I'll have to get into
BitBucket, then I'll do (and start leaving Git aside...).
Regards,
- Eric
2010/12/8 Andy Frances <af.sta...@gmail.com>:
> --
> Vous recevez ce message, car vous êtes abonné au groupe Google
> Groupes Montréal-Python.
> Pour envoyer un message à ce groupe, adressez un e-mail
> à montrea...@googlegroups.com.
> Pour vous désabonner de ce groupe, envoyez un e-mail à l'adresse
> montrealpytho...@googlegroups.com.
> Pour plus d'options, consultez la page de ce groupe :
> http://groups.google.com/group/montrealpython?hl=fr-CA
>
You need to install a debug build of Python and run setup.py with it.
On a Debian or related distribution, just apt-get the "python-dbg"
package.
-- Alexandre
Actually... if you just want the debugging symbol for gdb, you could
do "python setup.py build --debug" and that should pass the -g flag to
the compiler.
-- Alexandre
--
My usual trick for this is to start a Python interpreter under gdb,
import the extension and then hit Ctrl-C to set the breakpoints in
gdb. If I can't debug from interpreter for some reason, then I specify
the breakpoints by filename:lineno before starting the interpreter and
let gdb insert the breakpoints when the extension is loaded at
runtime.
-- Alexandre
I have tried doing something to that effect but I had problems.
What we did was a bit more intrusive.
We altered greenlet.c and added a signal(getpid(), SIGUSR1)
recompiled.
in gdb set handle SIGUSR1 ignore
run
and that stops the code in the right spot and we can proceed from there
That said, the main thing I want to do is see how greenlets play with
the C stack and
if anything is done to PyEvalFrameEx() ?
Cheers,
Andrew