This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Python] Input from user from extended breakpoint `stop' function

From: Kevin Pouget <kevin dot pouget at gmail dot com>
To: Andreas Schwab <schwab at linux-m68k dot org>
Cc: gdb at sourceware dot org
Date: Thu, 21 Apr 2011 07:37:35 -0400
Subject: Re: [Python] Input from user from extended breakpoint `stop' function
References: <BANLkTimrLOuWZSsA8t315wRAhzxNPKkFVA@mail.gmail.com> <m38vv6dmtz.fsf@redhat.com> <m2tydudla7.fsf@igel.home> <m38vv6c4l6.fsf@redhat.com> <BANLkTi=-t7XocAbzFdcSvbeoKLVreH+rEw@mail.gmail.com> <m2ipu9mkhy.fsf@igel.home>

>> that's interesting, but why `print' functions work correctly, without
>> sending any SIGTTOU
>
> Try stty tostop.

indeed !
what do consider as the default/good behavior? I mean, it is okay for
GDB to 'ignore' SIGTTOU, or shall I report such situations as bugs ?

References:
- [Python] Input from user from extended breakpoint `stop' function
  - From: Kevin Pouget
- Re: [Python] Input from user from extended breakpoint `stop' function
  - From: Phil Muldoon
- Re: [Python] Input from user from extended breakpoint `stop' function
  - From: Andreas Schwab
- Re: [Python] Input from user from extended breakpoint `stop' function
  - From: Phil Muldoon
- Re: [Python] Input from user from extended breakpoint `stop' function
  - From: Kevin Pouget
- Re: [Python] Input from user from extended breakpoint `stop' function
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]