From: Robert Nagy <robert.nagy@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: intercept trap when running a 32bit binary
Date: Tue, 26 Jun 2007 19:16:38 +0000 [thread overview]
Message-ID: <20070626191638.GA9452@bsd.hu> (raw)
In-Reply-To: <20070625221349.GA25054@bsd.hu>
Unfortunately having steam.cfg is optional and it
does not change anything.
On (26/06/07 12:13), Luck, Tony wrote:
> > Here is the output http://humppa.hu/typescript
>
> Nothing stands out there as totally off. The program did open
> and read /proc/cpuinfo shortly before it died, so it might have
> found something that it didn't like in there (though it also read
> it just after startup without apparent ill effects).
>
> Then at the very end it failed to open "steam.cfg" ... perhaps
> that was what it didn't like?
>
> -Tony
prev parent reply other threads:[~2007-06-26 19:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 22:13 intercept trap when running a 32bit binary Robert Nagy
2007-06-25 23:24 ` Luck, Tony
2007-06-25 23:35 ` Robert Nagy
2007-06-25 23:45 ` Luck, Tony
2007-06-26 0:04 ` Yu, Fenghua
2007-06-26 6:54 ` Robert Nagy
2007-06-26 10:13 ` Robert Nagy
2007-06-26 16:30 ` Luck, Tony
2007-06-26 16:58 ` Robert Nagy
2007-06-26 19:13 ` Luck, Tony
2007-06-26 19:15 ` Robert Nagy
2007-06-26 19:16 ` Robert Nagy [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=20070626191638.GA9452@bsd.hu \
--to=robert.nagy@gmail.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.