Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <Richard.Earnshaw@arm.com>, <gdb@sources.redhat.com>
Subject: Re: ARM stack alignment on hand called functions
Date: Wed, 20 Nov 2002 09:35:00 -0000	[thread overview]
Message-ID: <197101c290bb$25e628c0$0202040a@catdog> (raw)
In-Reply-To: <3DDBC3EC.4010401@redhat.com>

----- Original Message -----
From: "Andrew Cagney" <ac131313@redhat.com>
To: "Kris Warkentin" <kewarken@qnx.com>
Cc: <Richard.Earnshaw@arm.com>; <gdb@sources.redhat.com>
Sent: Wednesday, November 20, 2002 12:18 PM
Subject: Re: ARM stack alignment on hand called functions


> > The problem arises only with functions which return structures whose
size is
> > not evenly divisible by 4.  Below is what I did to solve it.
>
> Kris, FYI,
> It's very important to always reproduce problems using the current GDB
> sources.  That way, any confusion arrising from either local
> modifications (does QNX 6 ship an un-modified GDB 5.2.1?) or out-of-date
> sources (has the problem been fixed?).

We had to pick a snapshot for our current release so we chose 5.2.1 which is
the current, stable gdb release.  Our modifications mostly lie in the procfs
interface and the remote communications ends of things.

> For the problem at hand, I suspect the post 5.3 architecture method -
> gdbarch_frame_align() - is needed.  That method is used to align each
> element's stack address (e.g., struct return) and not the size of each
> element.

So perhaps this is a FIXME for us for later.  The thing is, there isn't any
QNX specific code down this path so I suspect this alignment issue is a
generic gdb problem.  Once we finish up with this release, the plan is to
port our QNX modifications to the gdb head branch for eventual inclusion in
the generic release.

> (I think I might add a few more juicy comments to valops.c so its
> clearer what the fix to your problem is :-).

Thanks Andrew.

Kris


  reply	other threads:[~2002-11-20 17:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20  7:29 Kris Warkentin
2002-11-20  7:58 ` Richard Earnshaw
2002-11-20  8:10   ` Kris Warkentin
2002-11-20  8:21     ` Richard Earnshaw
2002-11-20  8:26       ` Kris Warkentin
2002-11-20  9:18         ` Andrew Cagney
2002-11-20  9:35           ` Kris Warkentin [this message]
2002-11-26 14:01             ` Andrew Cagney
2002-11-27  1:18               ` Richard Earnshaw
2002-11-20 10:37         ` Richard Earnshaw
2002-11-20 10:59           ` Kris Warkentin
2002-11-20 11:40             ` Kris Warkentin
2002-11-21  2:58               ` Richard Earnshaw
     [not found] <200211272021.PAA04606@hub.ott.qnx.com>
2002-11-27 13:13 ` Kris Warkentin

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='197101c290bb$25e628c0$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    /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