Hi ,
So rather than manually backporting a patch from upstream "trunk" I
decided to try using bzr for this yesterday. Even though this was a
slow process and thanks to some help from Michael on IRC last night I
think I got it right finally. However I can't get bzr visualize to
show me the revision
On Wed, 19 Jan 2011, Loïc Minier wrote:
> actually, I thought ltrace was still a toolchain WG topic, but it had
> been moved to developer platform:
> https://wiki.linaro.org/Releases/1105/TechnicalTopics#Developer%20Platform
> https://blueprints.launchpad.net/ubuntu/+spec/other-linaro-n-profil
On Wed, Jan 19, 2011 at 05:24:38PM +0100, Loïc Minier wrote:
> actually, I thought ltrace was still a toolchain WG topic, but it had
> been moved to developer platform:
> https://wiki.linaro.org/Releases/1105/TechnicalTopics#Developer%20Platform
> https://blueprints.launchpad.net/ubuntu/+spec/o
actually, I thought ltrace was still a toolchain WG topic, but it had
been moved to developer platform:
https://wiki.linaro.org/Releases/1105/TechnicalTopics#Developer%20Platform
https://blueprints.launchpad.net/ubuntu/+spec/other-linaro-n-profiling-tools
oddly, ltrace was apparently verified
On Wed, 19 Jan 2011, Loïc Minier wrote:
> Hey
>
> I think we need to keep an eye on this and be ready to check ltrace if
> this gets merged
I think ltrace is broken already and needs to be fixed regardless.
Motivations for the removal of PTRACE_SINGLESTEP on ARM are:
1.) Only a subs
Hey
I think we need to keep an eye on this and be ready to check ltrace if
this gets merged
Cheers
--
Loïc Minier
--- Begin Message ---
Hi Russell,
> On Wed, Jan 19, 2011 at 03:07:15PM +, Will Deacon wrote:
> > I'm posting this as an RFC to see if anybody has a good reason to k
