[lldb-dev] Losing prompt when running any python commands

[Malea, Daniel]

Looks like the list stripped out the extra CC..I'm trying to add Sylvestre to the "to:" field in case that helps.

Sylvestre, regarding the eventual libedit update, would people with existing released versions of Ubuntu be able to take advantage of it (via a 3rd party repo like llvm.org/apt) or would it be something that's targeting strictly upcoming releases of Debian/Ubuntu? That is to say, what's the easiest way to get lldb built against libedit 3.0 (statically or otherwise) into the hands of people who are running Ubuntu 12.04 for example?


Thanks,
Dan



From: Michael Sartain <mikesart at gmail.com<mailto:mikesart at gmail.com>>
Date: Friday, 5 July, 2013 5:46 PM
To: Daniel Malea <daniel.malea at intel.com<mailto:daniel.malea at intel.com>>
Cc: Matthew Sorrels <sorrels.m at gmail.com<mailto:sorrels.m at gmail.com>>, "lldb-dev at cs.uiuc.edu<mailto:lldb-dev at cs.uiuc.edu>" <lldb-dev at cs.uiuc.edu<mailto:lldb-dev at cs.uiuc.edu>>
Subject: Re: [lldb-dev] Losing prompt when running any python commands

On Fri, Jul 5, 2013 at 12:06 PM, Malea, Daniel <daniel.malea at intel.com<mailto:daniel.malea at intel.com>> wrote:
Yeah, after thinking about this a little more, I'm not sure how nice it will be to integrate libedit into the lldb source tree — it looks like lots of activity is going on in libedit upstream, and it will be annoying to tie ourselves to a single version, or to update the version we build against at some regular interval.

I had a chat with Sylvestre (cc'd; he's responsible for the Debian/Ubuntu llvm-toolchain packages) and he's looking into what it would take to update the libedit-dev version that we're all building against. If it's possible to just update everyone's libedit packages, I think that would be a more favourable route to a less buggy LLDB on Debian/Ubuntu :)

I don't see anyone extra cc'd?

What would this "update libedit-dev" look like? We've got most folks running Ubuntu 12.04 and it'd sure be nice to be able to build with a #define set (or the like) to get a newer version of libedit that doesn't have these issues even if it isn't enabled by default on those platforms.

Thanks.
 -Mike