[[!meta copyright="Copyright © 2012 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: attach"]]

[[!tag open_issue_gdb]]


# [[gdb_thread_ids]]


# IRC, freenode, #hurd, 2012-06-30

    <braunr> hm, gdb isn't able to determine which thread is running when
      attaching to a process


# IRC, freenode, #hurd, 2012-07-02

    <braunr> woah, now that's a weird message !
    <braunr> when using gdb on a hanged ext2fs :
    <braunr> Pid 938 has an additional task suspend count of 1; clear it? (y or
      n) 
    <braunr> when hanged, gdb thinks the target task is already being debugged
      :/
    <braunr> no wonder why it's completely stuck
    <braunr> hm, the task_suspend might actually be the crash-dump-core server
      attempting to create the core :/
    <braunr> hm interesting, looks like a problem with the
      diskfs_catch_exception macro
    <pinotree> braunr: what's up with it?
    <braunr> pinotree: it uses setjmp
    <braunr> hm random corruptions :/
    <braunr> definitely looks like a concurrency problem