Bug 19684 - gdb is unable to single step or dump registers when fs is destroyed
Summary: gdb is unable to single step or dump registers when fs is destroyed
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: 7.9
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-19 23:25 UTC by Andi Kleen
Modified: 2016-02-24 23:45 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Turn thread error into warning (387 bytes, patch)
2016-02-24 23:45 UTC, Andi Kleen 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andi Kleen 2016-02-19 23:25:16 UTC 
x86_64-linux

I have a program that overwrites the fs register (TLS base)
Once that happens gdb is unable to single step or print any registers, only get

thread_get_info_callback: cannot get thread info: generic error

Even if it cannot determine the thread it should still continue
Comment 1 Andi Kleen 2016-02-24 23:45:28 UTC 
Created attachment 9036 [details]
Turn thread error into warning

This patch works for me. Just return NULL and warn only.