From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: tty related hangs with 2.6.31-rc3
Date: Thu, 16 Jul 2009 23:27:15 +0530 [thread overview]
Message-ID: <20090716175715.GA4292@skywalker> (raw)
In-Reply-To: <20090715204902.GA4205@skywalker>
On Thu, Jul 16, 2009 at 02:19:02AM +0530, Aneesh Kumar K.V wrote:
> Hi Alan,
>
> On Wed, Jul 15, 2009 at 10:23:08PM +0530, Aneesh Kumar K.V wrote:
> > On Wed, Jul 15, 2009 at 04:11:42PM +0100, Alan Cox wrote:
> > > On Wed, 15 Jul 2009 18:59:56 +0530
> > > "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:
> > >
> > > > Hi,
> >
>
> I am finding a new error with emacs now. Now i am not sure how to explain the problem
> as a nice bug report. But anyhow i will try. emacs support a mode to compile different
> prg. So to reproduce write a small program something like below
>
> main()
> {
> printf("%d\n", i);
> }
>
> Now in emacs say ALT-x compile
>
> use cc a.c command to compile. It is supposed to show the error messages in the compile
> window. With 2.6.30 it works fine. Where as 2.6.31-rc3 it doesn't list me any error.
> My limitted understanding about emacs compile window is, it looks for error messages
> using pattern matching from the compile ouput. I guess it is missing some of the
> compile message output.
>
>
> sorry that the report is sparse. If you need any specific inforation let me know.
reverting the patch d945cb9cce20ac7143c2de8d88b187f62db99bdc fix the bug for me.
So i guess that would imply it is pty changes related
-aneesh
next prev parent reply other threads:[~2009-07-16 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 13:29 tty related hangs with 2.6.31-rc3 Aneesh Kumar K.V
2009-07-15 14:02 ` Aneesh Kumar K.V
2009-07-15 15:11 ` Alan Cox
2009-07-15 16:53 ` Aneesh Kumar K.V
[not found] ` <20090715204902.GA4205@skywalker>
2009-07-16 17:57 ` Aneesh Kumar K.V [this message]
2009-07-17 11:06 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090716175715.GA4292@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox