diff options
| author | Paolo Bonzini | 2015-10-12 10:02:52 +0200 |
|---|---|---|
| committer | Stefan Hajnoczi | 2015-10-29 18:59:26 +0100 |
| commit | 1138f24645e9e1e2d55d280caab4e2539dfcdb49 (patch) | |
| tree | fd5f95413812b7f0929ae4cfc0ae557162440cac /scripts/qemu-gdb.py | |
| parent | Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (diff) | |
| download | qemu-1138f24645e9e1e2d55d280caab4e2539dfcdb49.tar.gz qemu-1138f24645e9e1e2d55d280caab4e2539dfcdb49.tar.xz qemu-1138f24645e9e1e2d55d280caab4e2539dfcdb49.zip | |
qemu-gdb: allow using glibc_pointer_guard() on core dumps
get_fs_base() cannot be run on a core dump, because it uses the arch_prctl
system call. The fs base is the value that is returned by pthread_self(),
and it would be nice to just glean it from the "info threads" output:
* 1 Thread 0x7f16a3fff700 (LWP 33642) pthread_cond_wait@@GLIBC_2.3.2 ()
^^^^^^^^^^^^^^
but unfortunately the gdb API does not provide that. Instead, we can
look for the "arg" argument of the start_thread function if glibc debug
information are available. If not, fall back to the old mechanism.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-id: 1444636974-19950-2-git-send-email-pbonzini@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'scripts/qemu-gdb.py')
0 files changed, 0 insertions, 0 deletions