Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kamal R. Prasad" <kamalpr@yahoo.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>, kamalp@acm.org
Cc: gdb@sources.redhat.com
Subject: Re: stack unwinding on aix
Date: Wed, 22 Jun 2005 05:13:00 -0000	[thread overview]
Message-ID: <20050622051316.19707.qmail@web52709.mail.yahoo.com> (raw)
In-Reply-To: <200506212219.j5LMJbic008540@elgar.sibelius.xs4all.nl>



--- Mark Kettenis <mark.kettenis@xs4all.nl> wrote:

>    Date: Mon, 20 Jun 2005 23:25:50 -0700 (PDT)
>    From: "Kamal R. Prasad" <kamalpr@yahoo.com>
> 
>    Hello,
> 
>     I am trying to locate a piece of code in gdb 6.3
>    which does srack unwinding in AIX (5.3). When
>    unwinding the stack in my C code, I noticed a lot
> of
>    dummy frames whose pc points to the data segment
>    and/or outside th text segment(s). Can someone
> tell me
>    how gdb identifies such dummy frames and wherein
> the
>    code base it is? rs6000-tdep.c contains some algo
> for
>    frameless function detection etc.., but that
> isn't all
>    to it.
> 
> I'm afraid the AIX/RS6000/POWER code is suffering
> from quite a bit of
> bit-rot.  It's a bit of a mess, so I can't blame you
> for failing to
> understand the code.  The sparc, vax or m88k code
> might be much easier
> for you to understand..  Look frame functions name
> xxx_frame_cache,
> xxx_prev_register for code that does the stack
> unwinding.
> 
Doing the stack unwinding is the easier part. The
difficult part is identifying intermediate aka dummy
frames.I believe some dummyframes get introduced due
to late binding.
> Anyway, the AIX/RS6000/POWER support in gdb really
> could use some
> loving care.  AFAIK almost none of the gdb
> developers actually have
> access to an AIX system.  So I'm not sure we'll be
> able to help you.
> 
gdb actually works fine on AIX -and Im looking to
import existing functionality from gdb to my s/w, not
re-work gdb which you seem to be implying. I have a
set of AIX systems at the workplace, but Im not sure
if I can give outsiders access for security reasons.
Is  skip_prologue() the core of functionality that
identifies what to do with a frame?

regards
-kamal

> Mark
> 


------------------------------------------------------------
Kamal R. Prasad
UNIX systems consultant 
http://members.fortunecity.com/kamalp
kamalp@acm.org

In theory, there is no difference between theory and practice. In practice, there is.
------------------------------------------------------------


		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com


      reply	other threads:[~2005-06-22  5:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21  6:25 Kamal R. Prasad
2005-06-21 22:19 ` Mark Kettenis
2005-06-22  5:13   ` Kamal R. Prasad [this message]

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=20050622051316.19707.qmail@web52709.mail.yahoo.com \
    --to=kamalpr@yahoo.com \
    --cc=gdb@sources.redhat.com \
    --cc=kamalp@acm.org \
    --cc=mark.kettenis@xs4all.nl \
    /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