Bug#385425: gdb does not manage SIGWINCH apparently

2006-09-01 Thread Francesco Paolo Lovergine
On Thu, Aug 31, 2006 at 06:27:44PM -0400, Daniel Jacobowitz wrote:
 On Thu, Aug 31, 2006 at 05:46:07PM -0400, Thomas Dickey wrote:
  On Thu, Aug 31, 2006 at 10:40:11AM +0200, Francesco Paolo Lovergine wrote:
   Package: gdb
   Version: 6.4.90.dfsg-1
   Severity: normal
   
   That's in TUI mode of course. Screen is not redraw when xterm window is
   resized.
  
  (gdb) help handle
  Specify how to handle a signal.
 
 That's the other handle - how to pass signals to the running program.
 GDB's TUI also needs to handle SIGWINCH.  But, I'm not entirely sure
 how this will work out with process groups... anyway, I can reproduce
 the bug.
 

Yep, I'm referring to its own window, in the case tty as been redirect 
elsewhere for the program, even. 
I would expect the debugger window would be managed by gdb, 
not the program at least in that case.

-- 
Francesco P. Lovergine


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#385425: gdb does not manage SIGWINCH apparently

2006-08-31 Thread Francesco Paolo Lovergine
Package: gdb
Version: 6.4.90.dfsg-1
Severity: normal

That's in TUI mode of course. Screen is not redraw when xterm window is
resized.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gdb depends on:
ii  libc62.3.6.ds1-4 GNU C Library: Shared libraries
ii  libncurses5  5.5-2   Shared libraries for terminal hand
ii  libreadline5 5.1-7   GNU readline and history libraries

gdb recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#385425: gdb does not manage SIGWINCH apparently

2006-08-31 Thread Thomas Dickey
On Thu, Aug 31, 2006 at 10:40:11AM +0200, Francesco Paolo Lovergine wrote:
 Package: gdb
 Version: 6.4.90.dfsg-1
 Severity: normal
 
 That's in TUI mode of course. Screen is not redraw when xterm window is
 resized.

(gdb) help handle
Specify how to handle a signal.
Args are signals and actions to apply to those signals.
Symbolic signals (e.g. SIGSEGV) are recommended but numeric signals
from 1-15 are allowed for compatibility with old versions of GDB.
Numeric ranges may be specified with the form LOW-HIGH (e.g. 1-5).
The special arg all is recognized to mean all signals except those
used by the debugger, typically SIGTRAP and SIGINT.
Recognized actions include stop, nostop, print, noprint,
pass, nopass, ignore, or noignore.
Stop means reenter debugger if this signal happens (implies print).
Print means print a message if this signal happens.
Pass means let program see this signal; otherwise program doesn't know.
Ignore is a synonym for nopass and noignore is a synonym for pass.
Pass and Stop may be combined.
(gdb) handle SIGWINCH
SignalStop  Print   Pass to program Description
SIGWINCH  NoNo  Yes Window size changed
(gdb) 

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpFyY8k2RBGR.pgp
Description: PGP signature


Bug#385425: gdb does not manage SIGWINCH apparently

2006-08-31 Thread Daniel Jacobowitz
On Thu, Aug 31, 2006 at 05:46:07PM -0400, Thomas Dickey wrote:
 On Thu, Aug 31, 2006 at 10:40:11AM +0200, Francesco Paolo Lovergine wrote:
  Package: gdb
  Version: 6.4.90.dfsg-1
  Severity: normal
  
  That's in TUI mode of course. Screen is not redraw when xterm window is
  resized.
 
 (gdb) help handle
 Specify how to handle a signal.

That's the other handle - how to pass signals to the running program.
GDB's TUI also needs to handle SIGWINCH.  But, I'm not entirely sure
how this will work out with process groups... anyway, I can reproduce
the bug.

-- 
Daniel Jacobowitz
CodeSourcery


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]