From: Vladimir Prus <ghost@cs.msu.su>
To: Greg Law <glaw@undo-software.com>, gdb-patches@sources.redhat.com
Subject: Re: SIGSEGV on gdb 6.7*
Date: Thu, 28 Feb 2008 07:46:00 -0000 [thread overview]
Message-ID: <E1JUczR-0000Y4-Px@zigzag.lvk.cs.msu.su> (raw)
In-Reply-To: <47C5C684.8010404@undo-software.com>
Greg Law wrote:
> Michael Snyder wrote:
>> On Tue, 2008-02-26 at 19:54 -0500, Daniel Jacobowitz wrote:
>>> On Tue, Feb 26, 2008 at 04:51:33PM -0800, Michael Snyder wrote:
>>>> Back to you... what's your inclination? ;-)
>>> OK, let's take it. I'll check it in to HEAD in a couple of minutes.
>>
>> A result that should be satisfactory to all.
>
> Thanks guys :)
This patch cause testsuite regressions for me, as follows:
FAIL: gdb.base/annota1.exp: continue to printf
FAIL: gdb.base/annota1.exp: send SIGUSR1
FAIL: gdb.base/annota1.exp: signal sent
FAIL: gdb.cp/annota2.exp: continue to exit
FAIL: gdb.cp/annota2.exp: watch triggered on a.x
This is Kubuntu 7.10 Gutsy, and gcc version is:
gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
JFYI -- I'm not sure we should bother about annotations.
- Volodya
next prev parent reply other threads:[~2008-02-28 7:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 20:50 Greg Law
2008-02-04 21:04 ` Daniel Jacobowitz
2008-02-04 21:39 ` Greg Law
[not found] ` <47A7850B.10202@undo-software.com>
2008-02-04 21:45 ` Daniel Jacobowitz
2008-02-04 21:59 ` Greg Law
2008-02-04 22:11 ` Daniel Jacobowitz
2008-02-04 22:36 ` Greg Law
2008-02-11 20:59 ` Greg Law
2008-02-26 23:00 ` Michael Snyder
2008-02-27 0:37 ` Daniel Jacobowitz
2008-02-27 0:43 ` Michael Snyder
2008-02-27 0:51 ` Daniel Jacobowitz
2008-02-27 0:54 ` Michael Snyder
2008-02-27 1:05 ` Daniel Jacobowitz
2008-02-27 1:08 ` Michael Snyder
2008-02-27 20:23 ` Greg Law
2008-02-28 7:46 ` Vladimir Prus [this message]
2008-02-28 14:17 ` Daniel Jacobowitz
2008-02-28 14:17 ` Thiago Jung Bauermann
2008-02-28 16:18 ` Daniel Jacobowitz
2008-03-04 20:09 ` Joel Brobecker
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=E1JUczR-0000Y4-Px@zigzag.lvk.cs.msu.su \
--to=ghost@cs.msu.su \
--cc=gdb-patches@sources.redhat.com \
--cc=glaw@undo-software.com \
/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