[Bug gdb/30677] New: [native-gdbserver] FAIL: gdb.python/py-thread-exited.exp: python print(threadOneExit)

[Bug gdb/30677] New: [native-gdbserver] FAIL: gdb.python/py-thread-exited.exp: python print(threadOneExit)

[simon.marchi at polymtl dot ca]

https://sourceware.org/bugzilla/show_bug.cgi?id=30677

            Bug ID: 30677
           Summary: [native-gdbserver] FAIL:
                    gdb.python/py-thread-exited.exp: python
                    print(threadOneExit)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simon.marchi at polymtl dot ca
  Target Milestone: ---

$ make check TESTS="gdb.python/py-thread-exited.exp"
RUNTESTFLAGS="--target_board=native-gdbserver"
FAIL: gdb.python/py-thread-exited.exp: python print(threadOneExit)
FAIL: gdb.python/py-thread-exited.exp: python print(threadTwoExit)

Fails with native-extended-gdbserver too.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/30677] [native-gdbserver] FAIL: gdb.python/py-thread-exited.exp: python print(threadOneExit)

[simon.marchi at polymtl dot ca]

https://sourceware.org/bugzilla/show_bug.cgi?id=30677

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simon.farre.cx at gmail dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/30677] [native-gdbserver] FAIL: gdb.python/py-thread-exited.exp: python print(threadOneExit)

[simon.marchi at polymtl dot ca]

https://sourceware.org/bugzilla/show_bug.cgi?id=30677

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |14.1

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/30677] [native-gdbserver] FAIL: gdb.python/py-thread-exited.exp: python print(threadOneExit)

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30677

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at sourceware dot org   |tromey at sourceware dot org
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I have a patch for the test case.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/30677] [native-gdbserver] FAIL: gdb.python/py-thread-exited.exp: python print(threadOneExit)

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30677

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
https://sourceware.org/pipermail/gdb-patches/2023-July/201247.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/30677] [native-gdbserver] FAIL: gdb.python/py-thread-exited.exp: python print(threadOneExit)

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30677

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=78e7f66e75f93d49a7accf3a7552b2378533b52b

commit 78e7f66e75f93d49a7accf3a7552b2378533b52b
Author: Tom Tromey <tromey@adacore.com>
Date:   Mon Jul 31 11:30:30 2023 -0600

    Change py-thread-exited.exp to work with gdbserver

    gdbserver does not notify gdb of new threads when they are created.
    I'm not sure if this is documented anywhere, but it is mentioned on
    this page:

    https://sourceware.org/gdb/wiki/LocalRemoteFeatureParity

    Search for "Finding new threads in the inferior".

    This behavior is a bit unfortunate -- I would think that it would be
    better to arrange for such notification if something on the gdb side
    is interested.

    Meanwhile, this patch fixes py-thread-exited.exp to work around this
    problem.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30677

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/30677] [native-gdbserver] FAIL: gdb.python/py-thread-exited.exp: python print(threadOneExit)

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30677

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.