From: Max Krummenacher <max.oss.09@gmail.com>
To: Khem Raj <raj.khem@gmail.com>,
Brian Avery <avery.brian@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: RFC: eclipse debug functionality issue
Date: Fri, 05 Aug 2016 10:58:49 +0200 [thread overview]
Message-ID: <1470387529.2393.4.camel@gmail.com> (raw)
In-Reply-To: <b41fd09b-cb0e-8702-d789-27ab70d56787@gmail.com>
Hi Brian
Am Donnerstag, den 04.08.2016, 19:49 -0700 schrieb Khem Raj:
>
> On 8/4/16 2:20 PM, Brian Avery wrote:
> > The core issue:
> > The busybox resize command breaks the eclipse ssh debug stream.
> > This is
> > because the resize command for busybox sends a set of cursor
> > control
> > escape sequences to stderr. The resize cfg was added to Krogoth and
> > is
> > still in master. The point of resize is to set the environment and
> > terminal settings to the current xterm window size.
> >
> > Additional complexity:
> > eclipse-debug is an IMAGE_FEATURE. If it is turned on by a user in
> > local.conf via EXTRA_IMAGE_FEATURES then I can conditionally turn
> > off
> > busybox/resize in the cfg file. Unfortunately, if a user makes a
> > new
> > image with IMAGE_FEATURES += " eclipse-debug " in it, I do not see
> > this
> > from the scope of the busybox##.bb recipe.
> >
> > So, there are a couple of ways to solve this and I'm not sure which
> > is
> > the best one.
> >
> > 1) conditionally turn off the resize.cfg if eclipse-debug is in
> > extra-image-features. Also, make a rm_resize.bbclass to rm the
> > usr/bin/resize from the rootfs in a do_rootfs[postfuncs] which can
> > be
> > inherited by the various sdk images we build.
> >
> > This is problematic since if a user makes a new image recipe of
> > their
> > own and includes eclipse-debug but doesn't inherit the
> > rm_resize.bbclass
> > eclipse debug will fail.
> >
> > 2) elevate eclipse-debug to a distro feature which would make it
> > visible
> > to the busybox###.bb recipe. Unfortunately, it is really an image
> > specific set of packages to be included so elevating it doesn't
> > seem
> > reasonable.
> >
> > 3) use the update-alternatives method (busybox is currently doing
> > this
> > for syslog) to make a separate busybox-resize package and make an
> > eclipse friendly resize package that is empty and add the eclipse
> > one to
> > the eclipse-debug packagegroup.
> >
> > 4) Just turn off resize or patch it so it doesn't try to control
> > the
> > cursor via escape sequences sent to stderr but still sets up the
> > environment. It's worth noting that the ubuntu resize doesn't
> > send
> > escape sequences to any of the streams.
>
> this seems to be best option.
We fixed this by only executing resize if logging in from a serial
console:
http://git.toradex.com/cgit/meta-toradex.git/commit/?h=V2.6-next&id=9d1
32ea3cf75562ef5610dd6ff1c89d0cffa334d
I guess one could apply the same fix to here
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/b
ase-files/base-files/profile?h=krogoth
Regards
Max
> >
> > 5) Something else?
> >
> > Thanks,
> > Brian
> > an Intel employee
> >
> >
> >
> >
next prev parent reply other threads:[~2016-08-05 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 21:20 RFC: eclipse debug functionality issue Brian Avery
2016-08-05 2:49 ` Khem Raj
2016-08-05 8:58 ` Max Krummenacher [this message]
2016-08-05 16:19 ` Brian Avery
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=1470387529.2393.4.camel@gmail.com \
--to=max.oss.09@gmail.com \
--cc=avery.brian@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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