public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "grant dot b dot edwards at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/10328] New: 6.8 broken for ARM targets (no backtrace, SIG32, etc.)
Date: Wed, 24 Jun 2009 14:38:00 -0000	[thread overview]
Message-ID: <20090624143827.10328.grant.b.edwards@gmail.com> (raw)

Gdb 6.8 just plain doesn't work on ARM targets.  If a program
is stopped in anything other than user-code (e.g. it's blocked
in read() or accept() there's no backtrace.  If the application
is multi-threaded you see SIG32 messages. There are also
reports of other odd behavior. Using 6.7.1 instead of 6.8
results in everything working.

http://news.gmane.org/find-root.php?message_id=%3ch1omae%24i07%241%40ger.gmane.org%3e
http://news.gmane.org/find-root.php?message_id=%3ch1pgtf%24oc2%241%40ger.gmane.org%3e
http://news.gmane.org/find-root.php?message_id=%3ch1p5br%2411r%241%40ger.gmane.org%3e

If you do a bit of searching you can find various other reports
that 6.8 doesn't work on ARM and 6.7.1 works fine.

My guess is that the problem underlying all of this is gdb's
failure to figure out what library files are mapped.  See the
second link above for an example, but when you compare the
output of "info files" to that of /proc/<pid>/maps, you'll see
that library files (such as libc and libpthread) show up in the
/proc/<pid>/maps but not in "info files".  My guess is that
causes the lack of backtrace, the SIG32, and all the other
problems that people see on ARM using 6.8.

-- 
           Summary: 6.8 broken for ARM targets (no backtrace, SIG32, etc.)
           Product: gdb
           Version: 6.8
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: gdb
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: grant dot b dot edwards at gmail dot com
                CC: gdb-prs at sourceware dot org
  GCC host triplet: i386-pc-linux-gnu
GCC target triplet: arm-linux-uclibc


http://sourceware.org/bugzilla/show_bug.cgi?id=10328

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


                 reply	other threads:[~2009-06-24 14:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090624143827.10328.grant.b.edwards@gmail.com \
    --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: link
Be 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).