[Bug python/22223] New: python event.new_thread does not exist but described in online document

[vivi00791 at gmail dot com]

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

Bug ID: 22223
Summary: python event.new_thread does not exist but described
in online document
Product: gdb
Version: 8.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: python
Assignee: unassigned at sourceware dot org
Reporter: vivi00791 at gmail dot com
Target Milestone: ---

gdb-mi output:

&"source ./Command/new_thread_trigger.py\n"
&"Traceback (most recent call last):\n"
&" File \"./Command/new_thread_trigger.py\", line 9, in <module>\n"
&" gdb.events.new_thread.connect (new_thread_handler)\n"
&"AttributeError: 'module' object has no attribute 'new_thread'\n"

source file(new_thread_trigger.py):

import gdb


def new_thread_handler (event):

print("NEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEW Thread!!!!!")


gdb.events.new_thread.connect (new_thread_handler)

event document:

https://sourceware.org/gdb/current/onlinedocs/gdb/Events-In-Python.html#Events-In-Python

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

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

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
The online document is generated from the gdb tree.
You probably have an older gdb, and this functionality
was added after the version you have was released.
So, I don't think there is a bug here.

Normally most linux distros, and "make install", will install
the info form of the gdb manual. So for the most consistent
results, you should consult the manual that you have.

The web page says that the latest release's manual is online,
but I see that the links are wrong...

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

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

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
Closing because it is not a bug.