blob: c04a10eef0c00bb9a57152d84b5165cfa59e4339 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
[[!meta copyright="Copyright © 2008, 2009, 2010, 2011 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!meta title="GDB: thread ids"]]
[[!tag open_issue_gdb]]
GNU GDB's Pedro Alves:
> One thing [I asked
> myself](http://lists.gnu.org/archive/html/bug-hurd/2008-10/msg00045.html)
> was, if gnu-nat.c couldn't be using the port's id as thread ids instead of a
> locally auto-generated number. Maybe the thread id of the main thread would
> be preserved across execs this way
Also see [[thread numbering of ps and GDB]].
---
`attach` to a multi-threaded process. See threads 1 to 5. `detach`. `attach`
again -- thread numbers continue where they stopped last time: now they're
threads 6 to 10.
|
