From: Gabriel Paubert <paubert@iram.es>
To: Srinivasa Ds <srinivasa@in.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, paulus@samba.org,
"H. Peter Anvin" <hpa@zytor.com>,
akpm@linux-foundation.org, Thomas Gleixner <tglx@linutronix.de>,
Roland McGrath <roland@redhat.com>
Subject: Re: [RFC][PATCH] Demultiplexing SIGTRAP signal -v2
Date: Tue, 23 Sep 2008 17:53:58 +0200 [thread overview]
Message-ID: <20080923155358.GA15776@iram.es> (raw)
In-Reply-To: <200809231955.01564.srinivasa@in.ibm.com>
On Tue, Sep 23, 2008 at 07:55:01PM +0530, Srinivasa Ds wrote:
> On Tuesday 23 September 2008 17:00:01 Ingo Molnar wrote:
>
> > > applied to [the new topic] tip/core/signal, thanks Srinivasa! There
> > > are some other pending x86 signal changes already, so i based
> > > tip/core/signal on tip/x86/signal.
> >
> > -tip testing found the following build error with the attached config:
> >
>
> Ingo, Reproduced build break issue with your config on tip tree. It was a costly overlook
> to miss one header file. I included it in this patch and tested it out.
>
>
> Currently a SIGTRAP can denote any one of below reasons.
> - Breakpoint hit
> - H/W debug register hit
> - Single step
> - Signal sent through kill() or rasie()
Typo: s/rasie/raise/
No strong opinion about the patch, but more info is usually better.
Regards,
Gabriel
WARNING: multiple messages have this Message-ID (diff)
From: Gabriel Paubert <paubert@iram.es>
To: Srinivasa Ds <srinivasa@in.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, paulus@samba.org,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
akpm@linux-foundation.org, Roland McGrath <roland@redhat.com>
Subject: Re: [RFC][PATCH] Demultiplexing SIGTRAP signal -v2
Date: Tue, 23 Sep 2008 17:53:58 +0200 [thread overview]
Message-ID: <20080923155358.GA15776@iram.es> (raw)
In-Reply-To: <200809231955.01564.srinivasa@in.ibm.com>
On Tue, Sep 23, 2008 at 07:55:01PM +0530, Srinivasa Ds wrote:
> On Tuesday 23 September 2008 17:00:01 Ingo Molnar wrote:
>
> > > applied to [the new topic] tip/core/signal, thanks Srinivasa! There
> > > are some other pending x86 signal changes already, so i based
> > > tip/core/signal on tip/x86/signal.
> >
> > -tip testing found the following build error with the attached config:
> >
>
> Ingo, Reproduced build break issue with your config on tip tree. It was a costly overlook
> to miss one header file. I included it in this patch and tested it out.
>
>
> Currently a SIGTRAP can denote any one of below reasons.
> - Breakpoint hit
> - H/W debug register hit
> - Single step
> - Signal sent through kill() or rasie()
Typo: s/rasie/raise/
No strong opinion about the patch, but more info is usually better.
Regards,
Gabriel
next prev parent reply other threads:[~2008-09-23 15:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 10:32 [RFC][PATCH] Demultiplexing SIGTRAP signal Srinivasa Ds
2008-09-22 10:42 ` Ingo Molnar
2008-09-22 10:42 ` Ingo Molnar
2008-09-22 13:11 ` Srinivasa Ds
2008-09-22 13:11 ` Srinivasa Ds
2008-09-22 14:54 ` Ingo Molnar
2008-09-22 14:54 ` Ingo Molnar
2008-09-23 9:53 ` Srinivasa Ds
2008-09-23 9:53 ` Srinivasa Ds
2008-09-23 11:28 ` Ingo Molnar
2008-09-23 11:28 ` Ingo Molnar
2008-09-23 11:30 ` Ingo Molnar
2008-09-23 11:30 ` Ingo Molnar
2008-09-23 14:25 ` [RFC][PATCH] Demultiplexing SIGTRAP signal -v2 Srinivasa Ds
2008-09-23 14:25 ` Srinivasa Ds
2008-09-23 14:31 ` Ingo Molnar
2008-09-23 14:31 ` Ingo Molnar
2008-09-26 9:06 ` Roland McGrath
2008-09-26 9:06 ` Roland McGrath
2008-09-26 9:06 ` Roland McGrath
2008-09-29 13:34 ` Srinivasa DS
2008-09-29 13:34 ` Srinivasa DS
2008-09-23 15:53 ` Gabriel Paubert [this message]
2008-09-23 15:53 ` Gabriel Paubert
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=20080923155358.GA15776@iram.es \
--to=paubert@iram.es \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=roland@redhat.com \
--cc=srinivasa@in.ibm.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.