Thread: [Cgdb-devel] draw_current_line crash
                
                Brought to you by:
                
                    bobbybrasko,
                    
                
                    crouchingturbo
                    
                
            
            
        
        
        
    | 
     
      
      
      From: Mike M. <mi...@su...> - 2005-07-23 09:49:40
       
   | 
I believe the crash in draw_current_line is fixed. I also tweaked the handling of tab characters, it was taking the arrow out 'n' spaces rather than advancing to the next tab stop. Please hammer on it a little bit for me, especially doing searches. If it seems stable, I think it'll finally be safe to release 0.5.3. :) --=20 Mike Mueller mi...@su...  | 
| 
     
      
      
      From: Bob R. <bo...@br...> - 2005-07-25 22:48:10
       
   | 
On Sat, Jul 23, 2005 at 05:49:27AM -0400, Mike Mueller wrote:
> I believe the crash in draw_current_line is fixed.  I also tweaked the
> handling of tab characters, it was taking the arrow out 'n' spaces rather
> than advancing to the next tab stop.
>=20
> Please hammer on it a little bit for me, especially doing searches.  If it
> seems stable, I think it'll finally be safe to release 0.5.3. :)
OK, I'll make sure to test  this within the next few days. Also, items
issued to be fixed/resolved on the release schedule for .0.5.3 is below,
- Fix runtime error with arrow style long and regex searching.
  I will test to make sure this is resolved within the next few days.
 =20
- Update FAQ, it's wrong.
  I minor change I will fix.
- Fix packaged readline to only build the static library, instead of
  both shared and static libraries.
  A minor, but confusing change. Don't know how to do this yet.
- Merge in temporary breakpoint code and choose a letter for it.
  Can't figure out what to do on this issue. I really think 't' should
  set a temporary breakpoint and am considering the change. The only GDB
  commands that begin with 't' is,
    tabset   tbreak   tdump    thbreak  tp       tstart   tstop    tui     =
=20
    target   tcatch   tfind    thread   trace    tstatus  tty     =20
  In general, out of these options, I'm going to guess tbreak is the
  most used. At least it's the command I use the most. Does anyone
  object to this change?
Bob Rossi
 | 
| 
     
      
      
      From: Mike M. <mi...@su...> - 2005-07-25 23:07:28
       
   | 
> On Sat, Jul 23, 2005 at 05:49:27AM -0400, Mike Mueller wrote: > OK, I'll make sure to test this within the next few days. Also, items > issued to be fixed/resolved on the release schedule for .0.5.3 is below= , > > - Fix runtime error with arrow style long and regex searching. > I will test to make sure this is resolved within the next few days. > > - Update FAQ, it's wrong. > I minor change I will fix. > > - Fix packaged readline to only build the static library, instead of > both shared and static libraries. > A minor, but confusing change. Don't know how to do this yet. > > - Merge in temporary breakpoint code and choose a letter for it. > Can't figure out what to do on this issue. I really think 't' should > set a temporary breakpoint and am considering the change. The only GD= B > commands that begin with 't' is, > > tabset tbreak tdump thbreak tp tstart tstop tui > target tcatch tfind thread trace tstatus tty > > In general, out of these options, I'm going to guess tbreak is the > most used. At least it's the command I use the most. Does anyone > object to this change? I agree that 't' is the best letter for this. It seems like the tty option is not used very much since it is often easier to attach to a terminal-based application running in a separate window. This kind of stuff definitely underscores the need for user-configurable mappings in the future... Mike  | 
| 
     
      
      
      From: Bob R. <bo...@br...> - 2005-07-26 03:05:43
       
   | 
On Mon, Jul 25, 2005 at 07:07:09PM -0400, Mike Mueller wrote: > > On Sat, Jul 23, 2005 at 05:49:27AM -0400, Mike Mueller wrote: > > OK, I'll make sure to test this within the next few days. Also, items > > issued to be fixed/resolved on the release schedule for .0.5.3 is below, > > > > - Fix runtime error with arrow style long and regex searching. > > I will test to make sure this is resolved within the next few days. > > > > - Update FAQ, it's wrong. > > I minor change I will fix. > > > > - Fix packaged readline to only build the static library, instead of > > both shared and static libraries. > > A minor, but confusing change. Don't know how to do this yet. > > > > - Merge in temporary breakpoint code and choose a letter for it. > > Can't figure out what to do on this issue. I really think 't' should > > set a temporary breakpoint and am considering the change. The only GDB > > commands that begin with 't' is, > > > > tabset tbreak tdump thbreak tp tstart tstop tui > > target tcatch tfind thread trace tstatus tty > > > > In general, out of these options, I'm going to guess tbreak is the > > most used. At least it's the command I use the most. Does anyone > > object to this change? >=20 > I agree that 't' is the best letter for this. It seems like the tty > option is not used very much since it is often easier to attach to a > terminal-based application running in a separate window. This kind of > stuff definitely underscores the need for user-configurable mappings in > the future... OK, with that said, I'll apply the change and give tbreak the letter 't'. I'll come up with something for switching into the "tty" window. Bob Rossi  | 
| 
     
      
      
      From: Bob R. <bo...@br...> - 2005-07-26 23:56:15
       
   | 
On Mon, Jul 25, 2005 at 07:07:09PM -0400, Mike Mueller wrote: > > On Sat, Jul 23, 2005 at 05:49:27AM -0400, Mike Mueller wrote: > > OK, I'll make sure to test this within the next few days. Also, items > > issued to be fixed/resolved on the release schedule for .0.5.3 is below, > > - Merge in temporary breakpoint code and choose a letter for it. > I agree that 't' is the best letter for this. It seems like the tty > option is not used very much since it is often easier to attach to a > terminal-based application running in a separate window. This kind of > stuff definitely underscores the need for user-configurable mappings in > the future... OK, currently it is, - t -> insert into tty window - I -> does nothing - i -> insert into GDB window - T -> open/close tty window I've changed that to - t -> set a temporary breakpoint - I -> insert into tty window - i -> insert into GDB window - T -> open/close tty window Personally, I find it more intuitve. Do you like the change? If so I'll commit it. Thanks, Bob Rossi  |