public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "lkn0371 at 163 dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/12866] fail to load elf compiled by ARM RVCT3.1 Date: Mon, 13 Jun 2011 04:58:00 -0000 [thread overview] Message-ID: <bug-12866-4717-AGvM0KpdMR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12866-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=12866 --- Comment #4 from 1avender <lkn0371 at 163 dot com> 2011-06-13 04:57:40 UTC --- Additional information: Environment: C, C++, RVCT 3.1 (1021), dwarf2, Host=i686-pc-mingw32, target=i686-pc-mingw32 When I changed to use RVCT 3.1 (569) to link the elf, it can be loaded successful. Then, I changed to another big project and used RVCT 3.1 (569) to link, it fails to be loaded this time. So file size is one of the affect factor. I'm trying to change the target (target=i686-pc-mingw32 -> target=arm-elf)... -- 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:[~2011-06-13 4:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-09 14:15 [Bug gdb/12866] New: " lkn0371 at 163 dot com 2011-06-09 14:20 ` [Bug gdb/12866] " lkn0371 at 163 dot com 2011-06-10 12:25 ` qiyao at gcc dot gnu.org 2011-06-13 2:39 ` lkn0371 at 163 dot com 2011-06-13 2:41 ` lkn0371 at 163 dot com 2011-06-13 4:58 ` lkn0371 at 163 dot com [this message] 2011-06-15 14:30 ` lkn0371 at 163 dot com 2011-06-16 5:45 ` [Bug gdb/12866] gdb " lkn0371 at 163 dot com 2013-10-30 19:38 ` will.newton at gmail dot com 2013-10-31 20:55 ` tromey at redhat dot com 2013-11-06 15:15 ` cvs-commit at gcc dot gnu.org 2013-11-06 15:17 ` will.newton 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-12866-4717-AGvM0KpdMR@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).