|
»
»
GDB 7.0
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
GDB 7.0
by Chris Sutcliffe-2
::
Rate this Message:
Hey Brandon,
I'm not sure how closely you follow the GDB mailing list, but 7.0 is on it's way. I've build 6.8.91 (the first 7.0 test release) from source OOTB and it seems to be working nicely. Are you going to package it for MinGW? If not and there are no other takers, I wouldn't mind taking it on. Chris -- Chris Sutcliffe http://emergedesktop.org ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ MinGW-dvlpr mailing list MinGW-dvlpr@... https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
|
|
Re: GDB 7.0
by keithmarshall
::
Rate this Message:
On Thursday 17 September 2009 03:28:36 Chris Sutcliffe wrote:
> Hey Brandon, Brandon, we haven't heard from you for a lonnnnng time; are you still actively working on any MinGW projects? > I'm not sure how closely you follow the GDB mailing list, but 7.0 > is on it's way. I've build 6.8.91 (the first 7.0 test release) > from source OOTB and it seems to be working nicely. Are you going > to package it for MinGW? If not and there are no other takers, I > wouldn't mind taking it on. Thanks for this offer, Chris. If we don't see any reply from Brandon in the next few days, I suggest you go ahead. Will you also be looking into the `insight' bundled variant? I find that to be much more user friendly than bare GDB. -- Regards, Keith. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ MinGW-dvlpr mailing list MinGW-dvlpr@... https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
|
|
Re: GDB 7.0
by Chris Sutcliffe-2
::
Rate this Message:
Hey Keith,
>> I'm not sure how closely you follow the GDB mailing list, but 7.0 >> is on it's way. I've build 6.8.91 (the first 7.0 test release) >> from source OOTB and it seems to be working nicely. Are you going >> to package it for MinGW? If not and there are no other takers, I >> wouldn't mind taking it on. > > Thanks for this offer, Chris. If we don't see any reply from Brandon > in the next few days, I suggest you go ahead. Will do. > Will you also be looking into the `insight' bundled variant? I find > that to be much more user friendly than bare GDB. To be honest, I never had much luck with the previous insight builds for MinGW so I gave up on them and got used to gdb command line. If there is a call for the insight build, I can see what I can do to build it. If the insight build proves to be problematic I will release a bare GDB first and work on the insight build after. Cheers! Chris -- Chris Sutcliffe http://emergedesktop.org ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ MinGW-dvlpr mailing list MinGW-dvlpr@... https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
|
|
Re: GDB 7.0
by Charles Wilson-8
::
Rate this Message:
Chris Sutcliffe wrote:
> To be honest, I never had much luck with the previous insight builds > for MinGW so I gave up on them and got used to gdb command line. If > there is a call for the insight build, I can see what I can do to > build it. If the insight build proves to be problematic I will > release a bare GDB first and work on the insight build after. I just built CVS insight yesterday for cygwin (which is really a very native-ish build; the tcl/tk parts are all "native windowing" rather than "X11"). Most of the problems I had were related to conflicts between cygwin's sys/select.h header and winsock2.h -- which wouldn't happen in a true mingw build. Take a look at this patch: http://cygwin.com/ml/cygwin/2009-09/msg00397.html However... I think it would *still* be advantageous to release a separate gdb package and insight package, because I discovered that if you configure --with-gdbtk (e.g. enabling the insight bits), then the "regular" gdb executable also links to the tcl/tk libraries, even though it doesn't use them. It's better to build gdb.exe --without-gdbtk, package that, and then build insight.exe --with-gdbtk. You'd need to carefully compare the installation footprints of the two packages, and remove the duplicate files from the "insight add-on", though. `course, it's best if both are based on the same CVS checkout and patch level, for obvious reasons. -- Chuck ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ MinGW-dvlpr mailing list MinGW-dvlpr@... https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
|
|
Re: GDB 7.0
by Chris Sutcliffe-2
::
Rate this Message:
> I just built CVS insight yesterday for cygwin (which is really a very
> native-ish build; the tcl/tk parts are all "native windowing" rather > than "X11"). Most of the problems I had were related to conflicts > between cygwin's sys/select.h header and winsock2.h -- which wouldn't > happen in a true mingw build. Take a look at this patch: > http://cygwin.com/ml/cygwin/2009-09/msg00397.html Cool, I noticed the thread on the Cygwin list, I'll have to read it a little more carefully to see what snags you ran in to. > However... > > I think it would *still* be advantageous to release a separate gdb > package and insight package, because I discovered that if you configure > --with-gdbtk (e.g. enabling the insight bits), then the "regular" gdb > executable also links to the tcl/tk libraries, even though it doesn't > use them. It's better to build gdb.exe --without-gdbtk, package that, > and then build insight.exe --with-gdbtk. You'd need to carefully > compare the installation footprints of the two packages, and remove the > duplicate files from the "insight add-on", though. `course, it's best if > both are based on the same CVS checkout and patch level, for obvious > reasons. I agree with your approach. As I mentioned, I don't personally like insight, I prefer command line gdb, but thank you again for the configure tip, I'll be sure to do that. Speaking of Tcl/Tk, I assume it would make sense to package it as a separate entity from insight? I assume that there are other MinGW users that may like a Tcl/Tk library but don't necessarily want to install insight. Thoughts? Chris -- Chris Sutcliffe http://emergedesktop.org ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ MinGW-dvlpr mailing list MinGW-dvlpr@... https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
|
|
Re: GDB 7.0
by Charles Wilson-8
::
Rate this Message:
Chris Sutcliffe wrote:
> Speaking of Tcl/Tk, I assume it would make sense to package it as a > separate entity from insight? I assume that there are other MinGW > users that may like a Tcl/Tk library but don't necessarily want to > install insight. Thoughts? Actually, I don't think so -- at least, not in the form you would get if you merely built --with-gdbtk from the insight src tree. 1) Those versions are quite old, and will probably not ever be updated again -- especially as insight will be going into "deep maintenance" mode after the release of 7.0. 2) Newer versions of tcl/tk can be built for win32 as standalone packages pretty easily. Naturally, the end user who does so should be warned against installing into C:\MinGW\ for fear of mucking up the gdb versions. [*] 3) In the 7.0 src tree, the insight maintainer added support for building insight against "installed" versions of tcl/tk, rather than using the in-tree versions. And, as I said, new tcl/tk CAN be build for native win32 pretty easily -- but it's still more work than I think *you* want to put in to the effort of providing insight. And let's face it; this is no solution anyway given insight's imminent maintenance mode: do you want to recompile the dead insight AGAIN in two years, when folks start clamoring for an updated libtcl88.dll to replace the insight libtcl8[4567].dll? Don't go there. [*] Apparently, the old versions of tck/tk installed from the insight src tree don't have modern support for "non-interference" between versions. So, either THEY get to live in C:\MinGW, or (many) new versions WITH such support get to do so. But not new + old. Frankly, I'd just build from the insight src, tcl/tk and all, and package it all up as "insight". If you don't include the .a or .h files, then nobody will be tempted to use these old tcl/tk libraries for other purposes -- and when they ask about that, we say "They are old and only intended for use by insight.exe. If you want newer implementations of tcl/tk, either compile them yourself from source (http://www.tcl.tk/) but be sure NOT to install them into C:\MinGW. Alternatively, go to http://www.activestate.com/activetcl/ and download win32 binaries and libraries (but don't install them into C:\MinGW". -- Chuck ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ MinGW-dvlpr mailing list MinGW-dvlpr@... https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
| Free embeddable forum powered by Nabble | Forum Help |
