[Python-Dev] Re: Mixed Python/C debugging

2019-12-02 Thread Fabio Zadrozny
 Hi Skip,

I just wanted to note that what I usually do in this case is having 2
debuggers attached.

i.e.: start one any way you want and then do an attach to from the other
debugger -- in my case as I'm usually on the Python side I usually start
the Python debugger and then do an attach to from the C++ IDE, but you can
probably do it the other way around too :)

On Sun, Dec 1, 2019 at 1:57 PM Skip Montanaro 
wrote:

> Having tried comp.lang.python with no response, I turn here...
>
> After at least ten years away from Python's run-time interpreter &
> byte code compiler, I'm getting set to familiarize myself with that
> again. This will, I think, entail debugging a mixed Python/C
> environment. I'm an Emacs user and am aware that GDB since 7.0 has
> support for debugging at the Python code level. Is Emacs+GDB my best
> bet? Are there any Python IDEs which support C-level breakpoints and
> debugging?
>
> Thanks,
>
> Skip
> ___
> Python-Dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/L2KBZM64MYPXIITN4UU3X6L4PZS2YRTB/
> Code of Conduct: http://python.org/psf/codeofconduct/
>
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/ZJOFXW2K42YUMP3MQY6POBLRJKMU2BLU/
Code of Conduct: http://python.org/psf/codeofconduct/


[Python-Dev] Re: Mixed Python/C debugging

2019-12-02 Thread Sasha Kacanski
Same here, I do Pycharm and it is possible to add clion plugin and go
through C code ...

On Mon, Dec 2, 2019 at 8:34 AM Fabio Zadrozny  wrote:

> Hi Skip,
>
> I just wanted to note that what I usually do in this case is having 2
> debuggers attached.
>
> i.e.: start one any way you want and then do an attach to from the other
> debugger -- in my case as I'm usually on the Python side I usually start
> the Python debugger and then do an attach to from the C++ IDE, but you can
> probably do it the other way around too :)
>
> On Sun, Dec 1, 2019 at 1:57 PM Skip Montanaro 
> wrote:
>
>> Having tried comp.lang.python with no response, I turn here...
>>
>> After at least ten years away from Python's run-time interpreter &
>> byte code compiler, I'm getting set to familiarize myself with that
>> again. This will, I think, entail debugging a mixed Python/C
>> environment. I'm an Emacs user and am aware that GDB since 7.0 has
>> support for debugging at the Python code level. Is Emacs+GDB my best
>> bet? Are there any Python IDEs which support C-level breakpoints and
>> debugging?
>>
>> Thanks,
>>
>> Skip
>> ___
>> Python-Dev mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> https://mail.python.org/mailman3/lists/python-dev.python.org/
>> Message archived at
>> https://mail.python.org/archives/list/[email protected]/message/L2KBZM64MYPXIITN4UU3X6L4PZS2YRTB/
>> Code of Conduct: http://python.org/psf/codeofconduct/
>>
> ___
> Python-Dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/ZJOFXW2K42YUMP3MQY6POBLRJKMU2BLU/
> Code of Conduct: http://python.org/psf/codeofconduct/
>


-- 
Aleksandar Kacanski
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/AJ2CBQDHOALBBK3F6YCJ42V34SF6HH3K/
Code of Conduct: http://python.org/psf/codeofconduct/


[Python-Dev] Re: Mixed Python/C debugging

2019-12-02 Thread Skip Montanaro
Thanks for the responses. I know there are multiple tools out there (to
wit, Wes's response), but I'm really after what people actually use and
find works. I apologize that wasn't clear. I did neglect to mention that my
environment is Linux (specifically Ubuntu 18.04), so Windows-based
solutions aren't likely to be workable for me.

For the time being, I've been working through one or two of the
docs/tutorials about the parsing/compiler internals which focus on the C
side, so gdb with curses display enabled (Ctrl-X a) and built-in PyObject
support has been sufficient. I will eventually need mixed language
debugging though. And, as an Emacs user, how this might play in that
sandbox is of interest.

Skip
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/IZRJX3YYOBJWJ6UAE5PIAJBPKB7IOHS2/
Code of Conduct: http://python.org/psf/codeofconduct/