All of lore.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: Tue, 12 Nov 2002 20:19:04 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805407@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805292@msgid-missing>

David-

Duh, cockpit error on my part.  Turns out I run with SHELL set to
`/bin/bash'.  I copied the IA32 version of `bash' to the `emul'
directory and everything works just fine.

On Tue, Nov 12, 2002 at 10:23:21AM -0800, David Mosberger wrote:
> >>>>> On Tue, 12 Nov 2002 10:34:46 -0700, Don Dugger <n0ano@n0ano.com> said:
> 
>   Don> David- Nope, that didn't work.  I'm running a 2.4.18 kernel,
>   Don> the EMUL_PREFIX_LINUX_IA32 is set to `emul/ia32-linux/', I put
>   Don> the IA32 version of `sh' into `/emul/ia32-linux/bin/sh' and the
>   Don> IA32 `gdb' didn't work.  Do you think this is something we need
>   Don> to worry about or is it just a quirk of `gdb'?
> 
> Hmmh, to be honest, I always have used gdb.x86 without doing anything
> special about the shell and it always worked for me.  Perhaps we're
> using different gdb versions or we're doing something differently?  I
> seem to be using "gdb 5.0rh-5" from x86 Red Hat 7.1.
> 
> 	--david

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


      parent reply	other threads:[~2002-11-12 20:19 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
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 [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-105590709805407@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.