public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/15541] New: arguments printed in reverse order Date: Tue, 28 May 2013 05:41:00 -0000 [thread overview] Message-ID: <bug-15541-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15541 Bug ID: 15541 Summary: arguments printed in reverse order Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: dje at google dot com Found this while debugging something else. Filing it so it's not forgotten. bash$ gdb gdb (top-gdb) b classify_inner_name (top-gdb) r hello (gdb) p ::main Breakpoint 3, c_lex () at ../../src/gdb/c-exp.y:3051 3051 classification = classify_inner_name (search_block, context_type); (top-gdb) bt 3 #0 c_lex () at ../../src/gdb/c-exp.y:3051 During symbol reading, incomplete CFI data; unspecified registers (e.g., rax) at 0x50efb0. #1 c_parse_internal () at c-exp.c:2220 During symbol reading, cannot get low and high bounds for subprogram DIE at 5588382. During symbol reading, Child DIE 0x554d33 and its abstract origin 0x55459e have different parents. #2 0x00000000005123c6 in c_parse () at ../../src/gdb/c-exp.y:3145 (More stack frames follow...) (top-gdb) s classify_inner_name (context=<optimized out>, block=<optimized out>) at ../../src/gdb/c-exp.y:2929 2929 if (context == NULL) (top-gdb) The arguments to classify_inner_name are printed in reverse order. c-exp.y: static int classify_inner_name (const struct block *block, struct type *context) { struct type *type; char *copy; -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-05-28 5:41 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-28 5:41 dje at google dot com [this message] 2013-05-28 5:51 ` [Bug symtab/15541] " jan.kratochvil at redhat 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-15541-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).