From: Raffaele Belardi <raffaele.belardi@st.com>
To: <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] remote debugging python on embedded platform
Date: Mon, 17 Sep 2018 11:53:40 +0200 [thread overview]
Message-ID: <18df828e-9851-9476-8e6c-d5fc827d832b@st.com> (raw)
In-Reply-To: <0c14cbd4-4a28-f5ef-ebfd-1d3d494ca68c@st.com>
(Moved from [pycharm-community vs pycharm-professional] thread)
R0b0t1 wrote:
> On Mon, Sep 17, 2018 at 10:54 AM, Raffaele Belardi
>> I'd use Python to develop programs for fun on an ARM-linux embedded board, with the host
>> PC running Gentoo. I suppose that for debugging on the target I'd need this feature:
>> "Remote run/debug" which is available only in the (pycharm)Pro edition, right?
>>
>
> Usually what I see is either sftp or rsync (over ssh) to the remote
> computer, then ssh to run the updated files. Alternatively you can ssh
> to the remote host and run vim within that session.
>
I suppose vim on Host + ssh for transfer/run would be fine for me.
For debugging I saw some support for python is available in gdb but I'm not sure of the
environment, would I run gdb on the host or on the target (via gdbserver)?
Also, is gdb a viable solution given the interpreted nature of python or I'd better start
off with some GUI/IDE?
I normally use gdb/gdbserver for embedded C debugging so I'm fine with the gdb command
line interface.
thanks,
raffaele
next prev parent reply other threads:[~2018-09-17 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 22:31 [gentoo-user] pycharm-community vs pycharm-professional gevisz
2018-09-15 22:40 ` Andrew Udvare
2018-09-15 22:42 ` András Csányi
2018-09-16 7:13 ` gevisz
2018-09-16 7:56 ` Arve Barsnes
2018-09-16 11:34 ` gevisz
2018-09-17 8:54 ` Raffaele Belardi
2018-09-17 9:19 ` R0b0t1
2018-09-17 9:53 ` Raffaele Belardi [this message]
2018-09-17 10:36 ` [gentoo-user] remote debugging python on embedded platform R0b0t1
2018-09-17 11:38 ` R0b0t1
2018-09-18 5:24 ` Raffaele Belardi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18df828e-9851-9476-8e6c-d5fc827d832b@st.com \
--to=raffaele.belardi@st.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox