|
»
gdb and SIGWINCH
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
gdb and SIGWINCH
by james morris-8
::
Rate this Message:
Hi, gdb shows: (gdb) handle SIGWINCH Signal Stop Print Pass to program Description SIGWINCH No No Yes Window size changed but resizing the window still has no effect (KEY_RESIZE is detected in my code ;-) Is there any way around this? gdb --version GNU gdb 6.8-debian Cheers, james. _______________________________________________ Bug-ncurses mailing list Bug-ncurses@... http://lists.gnu.org/mailman/listinfo/bug-ncurses |
|
|
Re: gdb and SIGWINCH
by Thomas Dickey-2
::
Rate this Message:
On Thu, 24 Sep 2009, james morris wrote:
> > Hi, > > gdb shows: > > (gdb) handle SIGWINCH > Signal Stop Print Pass to program Description > SIGWINCH No No Yes Window size changed > > but resizing the window still has no effect (KEY_RESIZE is detected in my > code ;-) I'm not sure what's not working: if your program reads KEY_RESIZE, and then does a refresh (or another wgetch which does a refresh), ncurses is supposed to call resizeterm, which resizes stdscr, etc., to fit in the new LINES/COLS limits. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net _______________________________________________ Bug-ncurses mailing list Bug-ncurses@... http://lists.gnu.org/mailman/listinfo/bug-ncurses |
|
|
Re: gdb and SIGWINCH
by james morris-8
::
Rate this Message:
On 24/9/2009, "Thomas Dickey" <dickey@...> wrote: >On Thu, 24 Sep 2009, james morris wrote: > >> >> Hi, >> >> gdb shows: >> >> (gdb) handle SIGWINCH >> Signal Stop Print Pass to program Description >> SIGWINCH No No Yes Window size changed >> >> but resizing the window still has no effect (KEY_RESIZE is detected in my >> code ;-) > >I'm not sure what's not working: if your program reads KEY_RESIZE, and >then does a refresh (or another wgetch which does a refresh), ncurses >is supposed to call resizeterm, which resizes stdscr, etc., to fit >in the new LINES/COLS limits. > Yes, that happens normally, but when I run the program in gdb and resize the window, wgetch never returns KEY_RESIZE. (Sorry, in an effort to get straight to the point I omitted too much detail.) So it seems that gdb is not passing SIGWINCH to ncurses, despite the above output claiming it does. As much as I could find on the subject was this: http://www.mail-archive.com/debian-bugs-dist@.../msg231762.html Is it still a bug in the Debian gdb, or is there something else which needs setting within gdb for it to pass SIGWINCH to program? One last question: is this list meant for developers and debuggers of ncurses rather than developers who wish to use it in their programs? Thanks, James. _______________________________________________ Bug-ncurses mailing list Bug-ncurses@... http://lists.gnu.org/mailman/listinfo/bug-ncurses |
|
|
Re: gdb and SIGWINCH
by Thomas Dickey-2
::
Rate this Message:
On Thu, 24 Sep 2009, james morris wrote:
> > On 24/9/2009, "Thomas Dickey" <dickey@...> wrote: > >> On Thu, 24 Sep 2009, james morris wrote: >> >>> >>> Hi, >>> >>> gdb shows: >>> >>> (gdb) handle SIGWINCH >>> Signal Stop Print Pass to program Description >>> SIGWINCH No No Yes Window size changed >>> >>> but resizing the window still has no effect (KEY_RESIZE is detected in my >>> code ;-) >> >> I'm not sure what's not working: if your program reads KEY_RESIZE, and >> then does a refresh (or another wgetch which does a refresh), ncurses >> is supposed to call resizeterm, which resizes stdscr, etc., to fit >> in the new LINES/COLS limits. >> > > Yes, that happens normally, but when I run the program in gdb and resize > the window, wgetch never returns KEY_RESIZE. > > (Sorry, in an effort to get straight to the point I omitted too much > detail.) > > So it seems that gdb is not passing SIGWINCH to ncurses, despite the > above output claiming it does. As much as I could find on the subject > was this: > > http://www.mail-archive.com/debian-bugs-dist@.../msg231762.html > > Is it still a bug in the Debian gdb, or is there something else which > needs setting within gdb for it to pass SIGWINCH to program? The bug's not marked closed - I'd have to assume it's not been fixed. > One last question: is this list meant for developers and debuggers of > ncurses rather than developers who wish to use it in their programs? There's some discussion - which as long as it's topical doesn't seem to bother people. (I'm on the lookout for details which may be a bug or limitation in ncurses). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net _______________________________________________ Bug-ncurses mailing list Bug-ncurses@... http://lists.gnu.org/mailman/listinfo/bug-ncurses |
| Free embeddable forum powered by Nabble | Forum Help |
