public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] status of debugging ia32 executables on ia64
Date: Mon, 15 Jan 2001 19:57:01 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005045@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005043@msgid-missing>

Jose-

I've found all of my IA32 problems with one of two tools.

1)  `strace'.  The IA64 version will also trace an IA32 program
so you can just use it as you normally would.  Most failures these
days are from bad system calls that should be identified by this tool.

2)  The IA32 version of `gdb' should work.  If `gdb' from a generic
IA32 system doesn't work let me know, I've got a version that I've
created that I know works.

Check your system log to make sure there aren't any funny messages.  If
you program makes a call we haven't implemented yet a message will be
printed to the console.

Also, are you running the EFI `wkaround' program before you boot your
kernel?  There are still some CPU erratas that affect IA32 execute that
are solved by this program.

On Mon, Jan 15, 2001 at 08:19:36PM +0100, Jose Luu wrote:
> 
> Hi,
> 
> I have a non functional ia32 executable (which of course works well on a
> regular ia32 machine).
> 
> What are my options for debugging it ?
> 
> There has a message from Don in march 2000 on an attempt to make gdb work
> for ia32 executables, since then no news, do we have a status on this ? What
> would be involved to make gdb work ?
> 
> Thanks
> Jose
> 
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838


      reply	other threads:[~2001-01-15 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15 19:19 [Linux-ia64] status of debugging ia32 executables on ia64 Jose Luu
2001-01-15 19:57 ` Don Dugger [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=marc-linux-ia64-105590693005045@msgid-missing \
    --to=n0ano@valinux.com \
    --cc=linux-ia64@vger.kernel.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