public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dvitek at grammatech dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/13294] New: printing bit field causes infinite loop Date: Thu, 13 Oct 2011 22:35:00 -0000 [thread overview] Message-ID: <bug-13294-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13294 Bug #: 13294 Summary: printing bit field causes infinite loop Product: gdb Version: 7.0 Status: NEW Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: dvitek@grammatech.com Classification: Unclassified I think this is a duplicate of bug 9261, but that one is with an extremely old version of gdb and is reported in the ada component. I have below a minimal C test case that reproduces the problem. This is on an x86_64 ubuntu system using gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9). gdb --version says: GNU gdb (GDB) 7.0-ubuntu /* Build me with gcc -g -o foo foo.c */ /* bug doesn't repro without the typedef (weird?) */ typedef unsigned char ui8; typedef struct _S _S, *S; struct _S{ ui8 a : 1; ui8 b : 1; ui8 c : 1; ui8 d : 1; }; int main() { _S s; S p = &s; /* break on or single step to the return statement. * Type "p p->d" in GDB. * GDB will go into an infinite loop. * When I attach gdb to gdb, it seems to be getting SIGFPE. * Maybe a division by zero? */ return 0; } -- 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-10-13 22:35 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-13 22:35 dvitek at grammatech dot com [this message] 2011-10-13 22:53 ` [Bug gdb/13294] " dvitek at grammatech dot com 2011-10-14 10:15 ` pedro at codesourcery 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-13294-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).