public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/13582] issues with accessing errno in non-threaded program Date: Wed, 11 Jan 2012 09:47:00 -0000 [thread overview] Message-ID: <bug-13582-4717-hoEIkitJGU@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13582-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13582 Jan Kratochvil <jan.kratochvil at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.kratochvil at redhat | |dot com --- Comment #1 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-01-11 09:47:40 UTC --- (In reply to comment #0) > (gdb) p errno > Cannot find thread-local variables on this target This is work arounded in Fedora GDB the straightforward way of substituting it by "*((int *(*) (void)) __errno_location) ()": http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob_plain;f=gdb-6.5-bz185337-resolve-tls-without-debuginfo-v2.patch;hb=master > [and on amd64-linux gdb doesn't know __errno_location returns a 64-bit value > and tries to deference the sign-extended 32-bit result] This works on normal distros featuring debug info for system components. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-01-11 9:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-11 1:04 [Bug threads/13582] New: " dje at google dot com 2012-01-11 9:47 ` jan.kratochvil at redhat dot com [this message] 2012-07-14 20:58 ` [Bug threads/13582] " jan.kratochvil at redhat dot com 2013-01-29 22:54 ` naesten at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-13582-4717-hoEIkitJGU@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).