From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] port simple gdb.threads/schedlock.c test fix to branch
Date: Mon, 02 Dec 2002 21:23:00 -0000 [thread overview]
Message-ID: <20021203052426.GA22838@nevyn.them.org> (raw)
In-Reply-To: <200212030519.gB35JOt21685@duracef.shout.net>
On Mon, Dec 02, 2002 at 11:19:24PM -0600, Michael Elizabeth Chastain wrote:
> > This is OK for the branch. I think I meant to do it at the time and
> > dropped the ball. I should also check that the lin-lwp fix for
> > schedlock.exp made the branch...
>
> >From the black box point of view, gdb HEAD and gdb 5.3 branch are
> behaving very differently with schedlock.exp. This is with all the
> same compilers and binutils and yada. gdb HEAD gives me 2 FAILs
> consistently, and gdb 5.3 branch gives me 8 FAILs most of the time
> and 4 FAILs some of the time.
>
> Gory details below.
>
> My version is from 2002-11-25, a week ago, and you checked in one
> fix to lin-lwp.c since then, to call linux_proc_xfer_memory.
> Is that the fix that lin-lwp.c needs?
No. It should be, um...
2002-10-31 Daniel Jacobowitz <drow@mvista.com>
* lin-lwp.c (lin_lwp_resume): Remove resume_all test for !step.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-03 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 21:19 Michael Elizabeth Chastain
2002-12-02 21:23 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-02 20:20 Michael Elizabeth Chastain
2002-12-02 20:29 ` Daniel Jacobowitz
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=20021203052426.GA22838@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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