public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Dugger <n0ano@n0ano.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gdb'ing 32-bit executable on IA64
Date: Mon, 11 Nov 2002 19:16:00 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805388@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805292@msgid-missing>

David-

Maybe.  I used the shell variable long before we had the IA32
working as seamlessly as it does today.  I'll give this a try
tonight and let you know what happens.

On Mon, Nov 11, 2002 at 11:24:49AM -0800, David Mosberger wrote:
> >>>>> On Mon, 11 Nov 2002 12:05:27 -0700, Don Dugger <n0ano@n0ano.com> said:
> 
>   Don> Nitin- I just remembered, there's one more gotcha you have to
>   Don> deal with to run `gdb' on IA32 processes.  `gdb' uses the shell
>   Don> to actually execute the target program and, by default, it
>   Don> winds up using the IA64 version of the shell.  This doesn't
>   Don> work.
> 
>   Don> What you have to do is spcify an IA32 shell through the `SHELL'
>   Don> environment variable when using the IA32 `gdb'.  If all of the
>   Don> IA32 programs are in the directory `/usr/ia32/bin' then the
>   Don> following sommand should work:
> 
>   Don> 	SHELL=/usr/ia32/bin/sh /usr/ia32/bin/gdb $*
> 
> Wouldn't it be much easier to copy the x86 version of bash into
> 
> 	/emul/ia32-linux/bin/sh
> 
> ?
> 
> 	--david

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@n0ano.com


  parent reply	other threads:[~2002-11-11 19:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 14:58 [Linux-ia64] gdb'ing 32-bit executable on IA64 Sane_Purushottam
2002-10-30 15:14 ` Don Dugger
2002-11-11 19:05 ` Don Dugger
2002-11-11 19:16 ` Don Dugger [this message]
2002-11-11 19:24 ` David Mosberger
2002-11-12 17:34 ` Don Dugger
2002-11-12 18:23 ` David Mosberger
2002-11-12 20:19 ` Don Dugger

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-105590709805388@msgid-missing \
    --to=n0ano@n0ano.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