From: Martin Jansa <martin.jansa@gmail.com>
To: Joe MacDonald <joe@deserted.net>
Cc: Chris Larson <clarson@kergoth.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] bitbake: enable pdb tracing
Date: Sat, 3 Aug 2013 10:14:08 +0200 [thread overview]
Message-ID: <20130803081408.GV3280@jama> (raw)
In-Reply-To: <CANBf+V2Qx4rxbQ2KYL+-t+jA4ds9gMFeKPD1rQBQrqFsfYpj3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
On Fri, Aug 02, 2013 at 09:07:15PM -0400, Joe MacDonald wrote:
> On Fri, Aug 2, 2013 at 5:05 PM, Chris Larson <clarson@kergoth.com> wrote:
>
> > On Thu, Aug 1, 2013 at 7:19 AM, <joe@deserted.net> wrote:
> >
> >> From: Joe MacDonald <joe@deserted.net>
> >>
> >> Based on:
> >>
> >> http://blog.devork.be/2009/07/how-to-bring-running-python-program.html
> >>
> >> register a signal handler to dynamically start pdb tracing on receiving
> >> SIGUSR1.
> >>
> >> Signed-off-by: Joe MacDonald <joe@deserted.net>
> >>
> >
> > As long as you keep in mind this will only affect the UI, not the forked
> > off server, this could be useful. I'd suggest adding something for the
> > server as well, but it'd need to listen to a socket for the input, lacking
> > access to the user's tty, or would need to interface with the UI to do it :)
> >
>
> That's a really good idea. It seemed like anything was better than what I
> had at the time, but now that you mention it being able to use pdb (or
> something like it) to talk to one of the forked processes would be a really
> helpful with the current problem I'm looking at. I'll see what I can do
> about extending this (since it doesn't sound like it's a fundamentally bad
> idea, just of limited applicability here) to more than just the UI.
Hi,
one type of hangs is described here
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4338
I have no experience with pdb, but if it will help debuging this king of
issues I'll happily try it next time I get it hanging.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-08-03 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 14:19 [PATCH] bitbake: enable pdb tracing joe
2013-08-02 21:05 ` Chris Larson
2013-08-03 1:07 ` Joe MacDonald
2013-08-03 8:14 ` Martin Jansa [this message]
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=20130803081408.GV3280@jama \
--to=martin.jansa@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
--cc=joe@deserted.net \
/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