This is the mail archive of the mailing list for the eCos project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1001468] eCos GNU tools 4.6.3

Please do not reply to this email. Use the web interface provided at:

--- Comment #48 from Jonathan Larmour <> 2012-04-27 17:16:04 BST ---
(In reply to comment #47)
> (In reply to comment #46)
> > If there is a 7.4.2 it would be very unlikely to contain these patches. It
> > would be a bugfix release only from the 7.4 branch - I only applied my patches
> > to the trunk and would need separate approval from the release manager to apply
> > them to the 7.4 branch (which I doubt I would get). We would need to wait for a
> > GDB 7.5, and that won't be happening any time soon. The most important thing
> > for us getting them committed is so that we would have certainty that a future
> > GDB 7.5 (and later) would continue to work.
> I'm afraid waiting for 7.5 would be too long.

Yes, that's what I was trying to say.

> I wander that provided that we patch 7.4.1 and we test it and it works for us,
> could then we consider it our release? It will bear mark "eCos GNU tools 4.6.3"
> so there will be no confuse with "standard" GDB 7.4.1.

Yes, which is why I wrote: "I had been thinking more of just applying these
patches to a stable release, presumably 7.4.1."

We will already be applying my other GDB patches as well (for avoiding
backtrace loops, as well as the workaround for NULL frames), so it wouldn't be
a standard GDB anyway.

That prompted me to have a look at the build scripts you attached to this bug
and I noticed a little thing... You should also configure all the tools with:


Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]