From: Joel Brobecker <brobecker@adacore.com>
To: Christoph Bartoschek <bartoschek@or.uni-bonn.de>
Cc: gdb@sourceware.org
Subject: Re: Compiling on AIX 5.3 with xlC
Date: Thu, 18 Oct 2007 16:39:00 -0000 [thread overview]
Message-ID: <20071018163938.GS16618@adacore.com> (raw)
In-Reply-To: <200710181826.04526.bartoschek@or.uni-bonn.de>
> bartosch@duco:/fs/data/bartosch/work/12.1aktuell>gdb
> GNU gdb 6.7
> Copyright (C) 2007 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "powerpc-ibm-aix5.3.0.0".
> (gdb) attach 98248
> Attaching to process 98248
> 0x00000000 in ?? ()
Hmmm, that reminds me of a limitation in AIX. I just found this:
/* According to ptrace(2), ptrace may fail with EPERM if "the
Identifier parameter corresponds to a kernel thread which is
stopped in kernel mode and whose computational state cannot be
read or written." This happens quite often with register reads. */
But I've only observed this when switching to a different thread.
Perhaps it's what is happening to you too.
What happens if you run GDB with
(gdb) set debug aix-thread
before you attach?
--
Joel
next prev parent reply other threads:[~2007-10-18 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 11:30 Christoph Bartoschek
2007-10-18 12:19 ` Daniel Jacobowitz
2007-10-18 13:12 ` Christoph Bartoschek
2007-10-18 14:35 ` Christoph Bartoschek
2007-10-18 16:15 ` Joel Brobecker
2007-10-18 16:25 ` Christoph Bartoschek
2007-10-18 16:34 ` Joel Brobecker
2007-10-18 16:39 ` Joel Brobecker [this message]
2007-10-18 16:48 ` Christoph Bartoschek
2007-10-19 17:41 ` Joel Brobecker
2007-10-18 16:31 ` Christoph Bartoschek
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=20071018163938.GS16618@adacore.com \
--to=brobecker@adacore.com \
--cc=bartoschek@or.uni-bonn.de \
--cc=gdb@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