public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/15161] New: symfile.c:struct load_section_data::load_offset is "unsigned long" but should be wider. Date: Tue, 19 Feb 2013 15:22:00 -0000 [thread overview] Message-ID: <bug-15161-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15161 Bug #: 15161 Summary: symfile.c:struct load_section_data::load_offset is "unsigned long" but should be wider. Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: palves@redhat.com Classification: Unclassified symfile.c has: /* Opaque data for load_section_callback. */ struct load_section_data { unsigned long load_offset; struct load_progress_data *progress_data; VEC(memory_write_request_s) *requests; }; static void load_section_callback (bfd *abfd, asection *asec, void *data) { struct memory_write_request *new_request; ... new_request->begin = bfd_section_lma (abfd, asec) + args->load_offset; ... void generic_load (char *args, int from_tty) { ... cbdata.load_offset = strtoul (argv[1], &endptr, 0); "unsigned long" is not wide enough in the cases of 32-bit gdb x 64-bit target, or LLP64 (like Windows 64-bit). load_offset should be ULONGEST or CORE_ADDR. -- 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:[~2013-02-19 15:22 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-19 15:22 palves at redhat dot com [this message] 2013-02-19 16:19 ` [Bug gdb/15161] " palves at redhat dot com 2013-02-19 18:32 ` cvs-commit at gcc dot gnu.org 2013-02-19 19:27 ` cvs-commit at gcc dot gnu.org 2013-02-19 20:53 ` cvs-commit at gcc dot gnu.org 2013-02-19 20:57 ` palves at redhat dot com 2013-02-19 20:59 ` palves at redhat dot com 2013-02-19 21:11 ` palves at redhat dot com 2013-02-19 21:20 ` palves at redhat dot com 2013-02-19 21:21 ` palves 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-15161-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).