Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: sami wagiaalla <swagiaal@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Support inferior events in python
Date: Wed, 09 Feb 2011 16:30:00 -0000	[thread overview]
Message-ID: <20110209163022.GA16069@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <4D52BE89.2040807@redhat.com>

On Wed, 09 Feb 2011 17:19:21 +0100, sami wagiaalla wrote:
> Hmm... I thought I fixed that by avoiding checking for the prompt.

I also find that one incorrect but I do not have a FAIL reproducer for it.

> I can't reproduce the problem

Reproducible for me in 90% of runs on Fedora 14 i386 (not x86_64).


Thanks,
Jan


Test Run By jkratoch on Wed Feb  9 17:28:09 2011
Native configuration is i386-unknown-linux-gnu

		=== gdb tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./gdb.python/py-evsignal.exp ...
Executing on host: gcc ./gdb.python/py-evthreads.c  -w -g  -lpthreads -lm   -o /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/gdb.python/py-evthreads    (timeout = 300)
spawn -ignore SIGHUP gcc ./gdb.python/py-evthreads.c -w -g -lpthreads -lm -o /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/gdb.python/py-evthreads
/usr/bin/ld: cannot find -lpthreads
collect2: ld returned 1 exit status
compiler exited with status 1
output is:
/usr/bin/ld: cannot find -lpthreads
collect2: ld returned 1 exit status

Executing on host: gcc ./gdb.python/py-evthreads.c  -w -g  -lpthread -lm   -o /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/gdb.python/py-evthreads    (timeout = 300)
spawn -ignore SIGHUP gcc ./gdb.python/py-evthreads.c -w -g -lpthread -lm -o /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/gdb.python/py-evthreads
PASS: gdb.python/py-evsignal.exp: successfully compiled posix threads test case
spawn /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/../data-directory
GNU gdb (GDB) 7.2.50.20110209-cvs
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir ./gdb.python
Source directories searched: /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/./gdb.python:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/gdb.python/py-evthreads
Reading symbols from /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/gdb.python/py-evthreads...done.
(gdb) python print 'test'
test
(gdb) python execfile ('./gdb.python/py-events.py')
(gdb) Test_Events
Event testers registered.
(gdb) PASS: gdb.python/py-evsignal.exp: Test_Events
set non-stop on
(gdb) PASS: gdb.python/py-evsignal.exp: set non-stop on
set target-async on
(gdb) PASS: gdb.python/py-evsignal.exp: set target-async on
run
Starting program: /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/gdb.python/py-evthreads 
event type: continue
thread num: 1
[Thread debugging using libthread_db enabled]
[New Thread 0xf7feeb70 (LWP 28517)]
event type: continue
thread num: 1
[New Thread 0xf77edb70 (LWP 28518)]
event type: continue
thread num: 1
[Thread 0xf7feeb70 (LWP 28517) exited]
[Thread 0xf77edb70 (LWP 28518) exited]

Program exited with code 014.
event type: exit
exit code: 12
(gdb) FAIL: gdb.python/py-evsignal.exp: thread 3 was not signalled
testcase ./gdb.python/py-evsignal.exp completed in 11 seconds

		=== gdb Summary ===

# of expected passes		4
# of unexpected failures	1
Executing on host: /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/../data-directory --version    (timeout = 300)
spawn -ignore SIGHUP /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/../data-directory --version
GNU gdb (GDB) 7.2.50.20110209-cvs
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
/home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/../../gdb/gdb version  7.2.50.20110209-cvs -nw -nx -data-directory /home/jkratoch/redhat/gdb-clean-m32/gdb/testsuite/../data-directory 

runtest completed at Wed Feb  9 17:28:21 2011


  reply	other threads:[~2011-02-09 16:30 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 15:54 sami wagiaalla
2011-01-04 18:22 ` Eli Zaretskii
2011-01-04 20:09 ` Tom Tromey
2011-01-17 22:59   ` sami wagiaalla
2011-01-19 16:42     ` Tom Tromey
2011-01-21 23:06       ` sami wagiaalla
2011-01-28 16:21         ` Tom Tromey
2011-02-02 21:04           ` sami wagiaalla
2011-02-02 21:35             ` Tom Tromey
2011-02-03 16:41               ` sami wagiaalla
2011-02-03 18:26                 ` Eli Zaretskii
2011-02-03 19:45                   ` sami wagiaalla
2011-02-03 21:42                 ` Tom Tromey
2011-02-04 20:07                   ` sami wagiaalla
2011-02-04 20:29                     ` Tom Tromey
2011-02-04 20:35                       ` sami wagiaalla
2011-02-04 23:00                         ` Paul Pluzhnikov
2011-02-05  5:44                           ` Hui Zhu
2011-02-07 15:22                             ` sami wagiaalla
2011-02-07 15:24                               ` Tom Tromey
2011-02-07 15:34                                 ` Paul Pluzhnikov
2011-02-07 16:01                                   ` sami wagiaalla
2011-02-07 15:39                                 ` sami wagiaalla
2011-04-20 20:26                         ` Patch for non-stop remote assertion (was: RE: [patch] Support inferior events in python) Marc Khouzam
2011-04-25 18:12                           ` Patch for non-stop remote assertion Tom Tromey
2011-04-25 18:31                             ` Marc Khouzam
2011-05-16 15:41                               ` Marc Khouzam
2011-05-19 18:38                               ` Tom Tromey
2011-02-09  7:55                     ` [patch] Support inferior events in python Jan Kratochvil
2011-02-09 16:19                       ` sami wagiaalla
2011-02-09 16:30                         ` Jan Kratochvil [this message]
2011-02-11 15:28                           ` sami wagiaalla
2011-02-11 15:55                             ` Joel Brobecker
2011-02-11 19:19                               ` sami wagiaalla
2011-02-11 19:46                                 ` Jan Kratochvil
2011-02-11 15:57                             ` Pedro Alves
2011-02-14 17:36                               ` sami wagiaalla
2011-02-16 11:48                                 ` Jan Kratochvil
2011-07-06 19:42                                   ` Jan Kratochvil
2011-07-07 13:51                                     ` sami wagiaalla
2011-07-07 14:03                                       ` Jan Kratochvil
2011-09-13 21:45                                       ` Jan Kratochvil

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=20110209163022.GA16069@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=swagiaal@redhat.com \
    --cc=tromey@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