public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "wkor97gy0eef1fr at p dot mintemail.com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/13014] New: member th is only added to struct lwp_info if HAVE_THREAD_DB_H defined, but code doesnt check Date: Thu, 21 Jul 2011 20:18:00 -0000 [thread overview] Message-ID: <bug-13014-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13014 Summary: member th is only added to struct lwp_info if HAVE_THREAD_DB_H defined, but code doesnt check Product: gdb Version: 7.2 Status: NEW Severity: normal Priority: P2 Component: build AssignedTo: unassigned@sourceware.org ReportedBy: wkor97gy0eef1fr@p.mintemail.com thread-db.c: In function `find_one_thread': thread-db.c:293: warning: long int format, thread_t arg (arg 3) thread-db.c:316: error: structure has no member named `th' line 316 (uncoditional access): lwp->th = th; is defined earlier in the function as struct lwp_info *lwp; definiton in ./gdb/gdbserver/linux-low.h (line 245) #ifdef HAVE_THREAD_DB_H /* The thread handle, used for e.g. TLS access. Only valid if THREAD_KNOWN is set. */ td_thrhandle_t th; #endif there is no code in the Makefile, configure, or any source file that defines this symbol. note, compilation was done on a system using musl libc. -- 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 reply other threads:[~2011-07-21 20:18 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-21 20:18 wkor97gy0eef1fr at p dot mintemail.com [this message] 2022-02-27 23:49 ` [Bug build/13014] " tromey at sourceware dot org
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-13014-4717@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).