From: Kris Warkentin <kewarken@qnx.com>
To: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] remove deprecated core support from QNX NTO
Date: Thu, 23 Dec 2004 17:12:00 -0000 [thread overview]
Message-ID: <41CAF4EC.3040804@qnx.com> (raw)
In-Reply-To: <73193856100971104@weblx058.utsp.utwente.nl>
M.M. Kettenis wrote:
>>regs since our kernel just uses the opcode to push them in the normal
>>order. Unfortunately though, our gpregs are in a different order and
>>not all of them are there so we have some unique mappings.
>>
>>
>
>QNX NTO is in no way special about this. I was thinking about something
>like the attached patch. Could you test that one? This approach simply
>reduces the amount of code needed.
>
>
Looks good. I didn't know the i386-tdep had the mapping ability. Do
other arches have that as well? I'm assuming you meant to return the
value here:
static int
nto_reg_offset (int regnum)
{
if (regnum >= 0 && regnum < ARRAY_SIZE (i386nto_gregset_reg_offset))
i386nto_gregset_reg_offset[regnum];
^^^^ return?
return -1;
}
When I run an app, it's dumping core in i386_supply_gregset because
tdep->regset is not initialized. Not quite sure what the proper way to
do that is. Still investigating.
>The patch also contains a unrelated change to the shared library code.
>It also removes a unneeded function. But it'd be nice if you could test
>that I didn't mess things up.
>
>
Thanks for all the help Mark. I'm always a big fan of eliminating
redundant code.
cheers,
Kris
next prev parent reply other threads:[~2004-12-23 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41CA34EF.6040401@qnx.com>
2004-12-23 16:28 ` M.M. Kettenis
2004-12-23 17:12 ` Kris Warkentin [this message]
2004-12-23 22:31 ` Kris Warkentin
2004-12-23 22:34 ` Mark Kettenis
2004-12-22 22:03 Kris Warkentin
2004-12-23 3:02 ` Mark Kettenis
2004-12-23 9:21 ` 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=41CAF4EC.3040804@qnx.com \
--to=kewarken@qnx.com \
--cc=gdb-patches@sources.redhat.com \
--cc=m.m.kettenis@alumnus.utwente.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