Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Regression for gdb.threads/fork-plus-threads.exp  [Re: [PATCH 3/6] List inferiors/threads/pspaces in ascending order]
Date: Mon, 11 Jan 2016 14:40:00 -0000	[thread overview]
Message-ID: <5693BEBC.4020404@redhat.com> (raw)
In-Reply-To: <20160108203938.GA24397@host1.jankratochvil.net>

On 01/08/2016 08:39 PM, Jan Kratochvil wrote:
> On Thu, 22 Oct 2015 11:59:01 +0200, Pedro Alves wrote:
> 
> 7e0aa6aa9983c745aedc203db0cc360a0ad47cac is the first bad commit
> commit 7e0aa6aa9983c745aedc203db0cc360a0ad47cac
> Author: Pedro Alves <palves@redhat.com>
> Date:   Tue Nov 24 18:11:21 2015 +0000
>     List inferiors/threads/pspaces in ascending order
> 
> PASS->FAIL:
> FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: inferior 1 exited
> FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: no threads left (timeout)
> FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left (the program exited)
> 
> -PASS: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: inferior 1 exited
> +warning: Error removing breakpoint 1^M
> +Error in re-setting breakpoint 1: Warning:^M
> +Cannot insert breakpoint 1.^M
> +Cannot access memory at address 0x8048700^M
> +^M
> +Warning:^M
> +Cannot insert breakpoint 1.^M
> +Cannot access memory at address 0x8048700^M
> +^M
> +(gdb) FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: inferior 1 exited
> 
> I haven't tried to debug it.
> 
> It happens on Fedora 23 x86_64 with -m32 for the testsuite.

I see it too on F20, and indeed only with -m32.  I don't know why yet.

Thanks,
Pedro Alves


  reply	other threads:[~2016-01-11 14:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 10:56 [PATCH 0/6] PR 17539 - inferiors/threads etc. print in reverse order Pedro Alves
2015-10-22 10:57 ` [PATCH 4/6] List checkpoints in ascending order Pedro Alves
2015-10-22 10:58 ` [PATCH 2/6] Linux: dump the signalled thread first Pedro Alves
2015-10-22 11:07 ` [PATCH 3/6] List inferiors/threads/pspaces in ascending order Pedro Alves
2015-10-22 16:03   ` Eli Zaretskii
2016-01-08 20:39   ` Regression for gdb.threads/fork-plus-threads.exp [Re: [PATCH 3/6] List inferiors/threads/pspaces in ascending order] Jan Kratochvil
2016-01-11 14:40     ` Pedro Alves [this message]
2016-01-12 11:22       ` Pedro Alves
2016-01-13  0:37         ` Pedro Alves
2015-10-22 11:23 ` [PATCH 1/6] Make gdb.python/py-inferior.exp test names unique Pedro Alves
2015-10-22 11:50 ` [PATCH 6/6] NEWS: "info" commands now list in ascending order Pedro Alves
2015-10-22 16:00   ` Eli Zaretskii
2015-10-22 16:06     ` Pedro Alves
2015-10-22 16:16       ` Eli Zaretskii
2015-10-22 12:36 ` [PATCH 5/6] List displays " Pedro Alves
2015-11-24 18:44 ` [PATCH 0/6] PR 17539 - inferiors/threads etc. print in reverse order Pedro Alves

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=5693BEBC.4020404@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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