Re: gdb, insight, and tcltk

2009-10-11 Thread Charles Wilson
Christopher Faylor wrote: > With all due respect, Chuck, when are interactions with you ever > *minimal*? Nearly every message you send is a slightly longer retelling > of War and Peace. :-) Rgt. Wz trng t ly out al issuz to permnently nd subthrd wrt gdb/insight. So no mor dscssn abt that. > I

Re: gdb, insight, and tcltk

2009-10-11 Thread Christopher Faylor
On Sat, Oct 10, 2009 at 07:30:10AM -0400, Charles Wilson wrote: >Christopher Faylor wrote: >>I'm sorry. I haven't been giving this my full attention since I have a >>working version of gdb and insight and thought you were asking insight >>questions. > >'salright. > >>I'm wondering if it would just

Re: gdb, insight, and tcltk

2009-10-10 Thread Charles Wilson
Christopher Faylor wrote: > I'm sorry. I haven't been giving this my full attention since I have a > working version of gdb and insight and thought you were asking insight > questions. 'salright. > I'm wondering if it would just be best for me to continue in this vein. > It probably won't be wor

Re: gdb, insight, and tcltk

2009-10-08 Thread Christopher Faylor
On Thu, Oct 08, 2009 at 05:25:20PM -0400, Christopher Faylor wrote: >On Thu, Oct 08, 2009 at 05:23:11PM -0400, Christopher Faylor wrote: >>I'm wondering if it would just be best for me to continue in this vein. > >"this vein" == continue to maintain insight and gdb. But before I do that I'm gettin

Re: gdb, insight, and tcltk

2009-10-08 Thread Christopher Faylor
On Thu, Oct 08, 2009 at 05:23:11PM -0400, Christopher Faylor wrote: >I'm wondering if it would just be best for me to continue in this vein. "this vein" == continue to maintain insight and gdb. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com

Re: gdb, insight, and tcltk

2009-10-08 Thread Christopher Faylor
On Thu, Oct 08, 2009 at 02:53:57PM -0400, Charles Wilson wrote: >The existing cygwin gdb/insight 6.8-2 package has the following change: > >2007-11-30 Pedro Alves <...> > > * i386-tdep.c (struct i386_frame_cache): Rename saved_sp to > prev_frame_sp. Add saved_sp_regnum field. >

Re: gdb, insight, and tcltk

2009-10-08 Thread Charles Wilson
Christopher Faylor wrote: > Use the insight mailing list, Luke. Keith Seitz is a friend and he does > not hate Cygwin. Since it was detailed in "gdb/ChangeLog.Cygwin" I figured it was appropriate here. But... http://www.cygwin.com/ml/cygwin-announce/2008-04/msg00011.html "Unlike most cygwin pac

Re: gdb, insight, and tcltk

2009-10-08 Thread Charles Wilson
Charles Wilson wrote: > (patch vs. "regular" gdb-6.8 attached). Oops. diff -urN old/insight-6.8/gdb/i386-tdep.c new/insight-6.8/gdb/i386-tdep.c --- old/insight-6.8/gdb/i386-tdep.c 2008-03-04 14:49:39.0 -0500 +++ new/insight-6.8/gdb/i386-tdep.c 2008-03-22 18:24:36.0 -0400 @@ -296,6

Re: gdb, insight, and tcltk

2009-10-08 Thread Christopher Faylor
On Thu, Oct 08, 2009 at 02:53:57PM -0400, Charles Wilson wrote: >The existing cygwin gdb/insight 6.8-2 package has the following change: > >2007-11-30 Pedro Alves <...> > > * i386-tdep.c (struct i386_frame_cache): Rename saved_sp to > prev_frame_sp. Add saved_sp_regnum field. >

Re: gdb, insight, and tcltk

2009-10-08 Thread Charles Wilson
The existing cygwin gdb/insight 6.8-2 package has the following change: 2007-11-30 Pedro Alves <...> * i386-tdep.c (struct i386_frame_cache): Rename saved_sp to prev_frame_sp. Add saved_sp_regnum field. (i386_alloc_frame_cache): Update. (i386_analyze_stack_align

Re: gdb, insight, and tcltk

2009-10-07 Thread Christopher Faylor
On Wed, Oct 07, 2009 at 05:46:56PM -0400, Charles Wilson wrote: >Chris -- > >Since gdb-7.0 was just released, I figure you'll probably be doing a >cygwin package fairly soon. However, I know you long to drop insight -- >at least to separate it out from gdb proper. > >So, I've got a proposal for you

gdb, insight, and tcltk

2009-10-07 Thread Charles Wilson
Chris -- Since gdb-7.0 was just released, I figure you'll probably be doing a cygwin package fairly soon. However, I know you long to drop insight -- at least to separate it out from gdb proper. So, I've got a proposal for you: I'll do an insight-only build (sans gdb.exe, gdb-tui.exe) which inst