1. exu not working
Hi, I wonder if anyne can help me with this problem.
I've been running Euphoria CGI scripts on a shared Linux sever for some
months now but at the weekend my ISP upgraded the server and now exu no
longer works. Their Tech Support has been of no use. I understand that
they are now running Redhat 7.3 but I have this at home and can run Euphoria
with no problems.
When I enter "exu" at the telnet command prompt nothing happens and I get an
exit code of 127. Does anyone have any idea how to sort this out? I really
don't want to rewrite everything in C or to try and learn Perl (especially
as I'm using a Euphoria database).
chris.
2. Re: exu not working
An exit code of 127 means a failure to execute the specified program.
Hence, exu is not loading for some reason (bad PATH? corrupted binary?
libraries not loaded? (glibc, ncurses, etc. (glibc is unlikely, cuz if that
was the problem then the system wouldnt even boot ... i'd bet my money
on ncurses not being there) anything else you can think of perhaps?)
HTH,
jbrown
On Thu, Feb 06, 2003 at 03:04:35PM -0000, tubby.toast at ntlworld.com wrote:
>
> Hi, I wonder if anyne can help me with this problem.
>
> I've been running Euphoria CGI scripts on a shared Linux sever for some
> months now but at the weekend my ISP upgraded the server and now exu no
> longer works. Their Tech Support has been of no use. I understand that
> they are now running Redhat 7.3 but I have this at home and can run Euphoria
> with no problems.
>
> When I enter "exu" at the telnet command prompt nothing happens and I get an
> exit code of 127. Does anyone have any idea how to sort this out? I really
> don't want to rewrite everything in C or to try and learn Perl (especially
> as I'm using a Euphoria database).
>
> chris.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
3. Re: exu not working
jbrown wrote:
> An exit code of 127 means a failure to execute the specified program.
>
> Hence, exu is not loading for some reason (bad PATH? corrupted binary?
It's neither of these.
> libraries not loaded? (glibc, ncurses, etc. (glibc is unlikely, cuz if
that
> was the problem then the system wouldnt even boot ... i'd bet my money
> on ncurses not being there) anything else you can think of perhaps?)
No, ncurses is definitely there. What else does Euphoria need?
Thanks for trying,
chris.
4. Re: exu not working
Hmm .... Does it have correct execute permissions? In which context does
exu work, and in which does it fail (besides in the cgi scrips)?
Do the scripts themselves have correct execute permission? What user owns
the scripts/exu, and what user is running it? What is the first line of the
scripts?
As to which libraries are required for exu, I don't rememeber all of them,
sorry, the big one was ncurses, which is a pain really. (I went as far as
writing a huge wrapper to allow Linux Euphoria programs to use plain I/O
by redefining a bunch of builtins and interfacing directly with glibc...
however, that doesn't solve dependancy errors caused by a lack of ncurses
on a machine. Rather annoying, really ... :/)
jbrown
On Thu, Feb 06, 2003 at 09:05:57PM -0000, tubby.toast at ntlworld.com wrote:
>
> jbrown wrote:
>
> > An exit code of 127 means a failure to execute the specified program.
> >
> > Hence, exu is not loading for some reason (bad PATH? corrupted binary?
>
> It's neither of these.
>
> > libraries not loaded? (glibc, ncurses, etc. (glibc is unlikely, cuz if
> that
> > was the problem then the system wouldnt even boot ... i'd bet my money
> > on ncurses not being there) anything else you can think of perhaps?)
>
> No, ncurses is definitely there. What else does Euphoria need?
>
> Thanks for trying,
> chris.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
5. Re: exu not working
> Hmm .... Does it have correct execute permissions? In which context does
> exu work, and in which does it fail (besides in the cgi scrips)?
>
Permissions for exu are 755. exu doesn't work at all. Like I say, just
entering "exu" at the command prompt does absolutely nothing; I just get the
prompt again as if I had merely pressed enter. And, using "echo $?" I get
an exit code of 127.
> Do the scripts themselves have correct execute permission? What user owns
> the scripts/exu, and what user is running it? What is the first line of
the
> scripts?
>
This should all be ok. At the moment I'm just trying to get the interpreter
running on its own. The owner is "chrissy" and that is who I log on as over
telnet.
> As to which libraries are required for exu, I don't rememeber all of them,
> sorry, the big one was ncurses, which is a pain really. (I went as far as
> writing a huge wrapper to allow Linux Euphoria programs to use plain I/O
> by redefining a bunch of builtins and interfacing directly with glibc...
> however, that doesn't solve dependancy errors caused by a lack of ncurses
> on a machine. Rather annoying, really ... :/)
Can Rob or anyone else with the source tell me? Even if I do find out it's
going to be difficult to do much since it's not my system and tech support
are pretty unresponsive. I can't afford to move hosts right now and anyway
I doubt anyone would let me "test-drive" Euphoria on their system before I
pay up.
Is 2.4 going to be more compatible? I'd prefer not to wait but if it's that
or learn Perl...
chris.
6. Re: exu not working
Well, turns out, if it was a library error, you'd see a msg like
"ld.so.2: failed to load libncurses.so.6" or something, so that cant be it.
Also, the other possibility i can think of, ncurses failing to initalize
the terminal, cant be it either, as it'd also error an error on stdout/stderr.
Are you doing something to its stdin/stdout/stderr? Thats the only thing I could
think of ... unless ... hmm.
How are you invoking it? Via a remote telnet/ssh shell I suppose? Not that that
would change anything, but still .... hmm.
No matter how cryptic, an error is nearly always shown on the terminal (or, to
be more precise, on stdout/stderr, often used interchangably for error
messages).
Only thing I can think of, either you're running something else called exu,
or your binary is corrupted ... or exu's output is being redirected and lost
somewhere.
What happens if you type the full path to exu on the command line? And,
what does "du -b <full path to exu" show?
jbrown
On Thu, Feb 06, 2003 at 10:21:59PM -0000, tubby.toast at ntlworld.com wrote:
>
> > Hmm .... Does it have correct execute permissions? In which context does
> > exu work, and in which does it fail (besides in the cgi scrips)?
> >
> Permissions for exu are 755. exu doesn't work at all. Like I say, just
> entering "exu" at the command prompt does absolutely nothing; I just get the
> prompt again as if I had merely pressed enter. And, using "echo $?" I get
> an exit code of 127.
>
> > Do the scripts themselves have correct execute permission? What user owns
> > the scripts/exu, and what user is running it? What is the first line of
> the
> > scripts?
> >
> This should all be ok. At the moment I'm just trying to get the interpreter
> running on its own. The owner is "chrissy" and that is who I log on as over
> telnet.
>
> > As to which libraries are required for exu, I don't rememeber all of them,
> > sorry, the big one was ncurses, which is a pain really. (I went as far as
> > writing a huge wrapper to allow Linux Euphoria programs to use plain I/O
> > by redefining a bunch of builtins and interfacing directly with glibc...
> > however, that doesn't solve dependancy errors caused by a lack of ncurses
> > on a machine. Rather annoying, really ... :/)
>
> Can Rob or anyone else with the source tell me? Even if I do find out it's
> going to be difficult to do much since it's not my system and tech support
> are pretty unresponsive. I can't afford to move hosts right now and anyway
> I doubt anyone would let me "test-drive" Euphoria on their system before I
> pay up.
>
> Is 2.4 going to be more compatible? I'd prefer not to wait but if it's that
> or learn Perl...
>
> chris.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
7. Re: exu not working
- Posted by gertie at visionsix.com
Feb 06, 2003
Good luck. After months of working with exu on remote nix boxen, i gave up,
it never worked right. Even after i gave the account password to the gurus
here.
Kat
On 6 Feb 2003, at 22:21, tubby.toast at ntlworld.com wrote:
>
> > Hmm .... Does it have correct execute permissions? In which context does
> > exu work, and in which does it fail (besides in the cgi scrips)?
> >
> Permissions for exu are 755. exu doesn't work at all. Like I say, just
> entering "exu" at the command prompt does absolutely nothing; I just get the
> prompt again as if I had merely pressed enter. And, using "echo $?" I get an
> exit code of 127.
>
> > Do the scripts themselves have correct execute permission? What user owns
> > the
> > scripts/exu, and what user is running it? What is the first line of
> the
> > scripts?
> >
> This should all be ok. At the moment I'm just trying to get the interpreter
> running on its own. The owner is "chrissy" and that is who I log on as over
> telnet.
>
> > As to which libraries are required for exu, I don't rememeber all of them,
> > sorry, the big one was ncurses, which is a pain really. (I went as far as
> > writing a huge wrapper to allow Linux Euphoria programs to use plain I/O by
> > redefining a bunch of builtins and interfacing directly with glibc...
> > however,
> > that doesn't solve dependancy errors caused by a lack of ncurses on a
> > machine.
> > Rather annoying, really ... :/)
>
> Can Rob or anyone else with the source tell me? Even if I do find out it's
> going to be difficult to do much since it's not my system and tech support are
> pretty unresponsive. I can't afford to move hosts right now and anyway I
> doubt
> anyone would let me "test-drive" Euphoria on their system before I pay up.
>
> Is 2.4 going to be more compatible? I'd prefer not to wait but if it's that
> or
> learn Perl...
>
> chris.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
>
8. Re: exu not working
> Well, turns out, if it was a library error, you'd see a msg like
> "ld.so.2: failed to load libncurses.so.6" or something, so that cant be
it.
>
> Also, the other possibility i can think of, ncurses failing to initalize
> the terminal, cant be it either, as it'd also error an error on
stdout/stderr.
>
> Are you doing something to its stdin/stdout/stderr? Thats the only thing I
could
> think of ... unless ... hmm.
Nope. Other programs write to stdout fine. I deliberately made some syntax
errors too and stderr works normally.
> How are you invoking it? Via a remote telnet/ssh shell I suppose? Not that
that
> would change anything, but still .... hmm.
Yes, ssh2. Also all the cgi scripts fail in a web browser which is how I
first noticed the problem
> No matter how cryptic, an error is nearly always shown on the terminal
(or, to
> be more precise, on stdout/stderr, often used interchangably for error
messages).
>
> Only thing I can think of, either you're running something else called
exu,
> or your binary is corrupted ... or exu's output is being redirected and
lost
> somewhere.
>
I uploaded a copy from my computer (it definitely works on that) - still no
joy.
> What happens if you type the full path to exu on the command line?
Same result.
> And,
> what does "du -b <full path to exu" show?
>
90112 /home/chrissy/bin/exu
It's strange, it's all been running perfectly for six months. I know
they've changed to Redhat 7.3 (but I run that with no problems) and have
changed their versions of PHP, Perl and Apache but surely none of that's
relevant, at least for just trying to run the interpreter over telnet.
Thanks for your thoughts,
chris.
9. Re: exu not working
On Thu, Feb 06, 2003 at 05:03:49PM -0600, gertie at visionsix.com wrote:
>
> Good luck. After months of working with exu on remote nix boxen, i gave up,
> it never worked right. Even after i gave the account password to the gurus
> here.
>
> Kat
>
Actually, you never gave us the password (not the account one I mean).
Moot point now, of course. (And, yeah I have no idea whats wrong with chris's
exu.)
jbrown
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
10. Re: exu not working
On Thu, Feb 06, 2003 at 11:52:32PM -0000, tubby.toast at ntlworld.com wrote:
>
> > Well, turns out, if it was a library error, you'd see a msg like
> > "ld.so.2: failed to load libncurses.so.6" or something, so that cant be
> it.
> >
> > Also, the other possibility i can think of, ncurses failing to initalize
> > the terminal, cant be it either, as it'd also error an error on
> stdout/stderr.
> >
> > Are you doing something to its stdin/stdout/stderr? Thats the only thing I
> could
> > think of ... unless ... hmm.
>
> Nope. Other programs write to stdout fine. I deliberately made some syntax
> errors too and stderr works normally.
Huh? Can you get any euphoria program working under exu?
>
> > How are you invoking it? Via a remote telnet/ssh shell I suppose? Not that
> that
> > would change anything, but still .... hmm.
>
> Yes, ssh2. Also all the cgi scripts fail in a web browser which is how I
> first noticed the problem
Hmm ... odd.
>
> > No matter how cryptic, an error is nearly always shown on the terminal
> (or, to
> > be more precise, on stdout/stderr, often used interchangably for error
> messages).
> >
> > Only thing I can think of, either you're running something else called
> exu,
> > or your binary is corrupted ... or exu's output is being redirected and
> lost
> > somewhere.
> >
> I uploaded a copy from my computer (it definitely works on that) - still no
> joy.
>
> > What happens if you type the full path to exu on the command line?
>
> Same result.
Not a PATH thing then.
>
> > And,
> > what does "du -b <full path to exu" show?
> >
> 90112 /home/chrissy/bin/exu
Looks like the full and correct binary.
>
> It's strange, it's all been running perfectly for six months. I know
> they've changed to Redhat 7.3 (but I run that with no problems) and have
> changed their versions of PHP, Perl and Apache but surely none of that's
> relevant, at least for just trying to run the interpreter over telnet.
"man system" and "man 2 exec" might get some better answers perhaps.
Thats how I found out what 127 meant.
>
> Thanks for your thoughts,
> chris.
exu is a dynamic ELF i386 binary ... but I assume the Redhat 7.3 servers
have ELF support and are Intel machines, so that doesnt help much. :/
perplexed but still trying,
jbrown
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
11. Re: exu not working
- Posted by gertie at visionsix.com
Feb 07, 2003
On 6 Feb 2003, at 20:25, jbrown1050 at hotpop.com wrote:
>
> On Thu, Feb 06, 2003 at 05:03:49PM -0600, gertie at visionsix.com wrote:
> >
> > Good luck. After months of working with exu on remote nix boxen, i gave up,
> > it
> > never worked right. Even after i gave the account password to the gurus
> > here.
> >
> > Kat
> >
>
> Actually, you never gave us the password (not the account one I mean).
I did, in channel, too:
[22:46] <robsz1> we cant really do anything with your account, kat
[22:46] <jbrown> kat, you know how to make RSA keys with ssh-keygen or
pgp right?
[22:46] <WingZero> even if you get it right....
[22:46] <WingZero> the name is wrong
[22:46] <robsz1> not without yer psswd anyways
[22:46] <kat> 0gertie1
[22:47] [10:47] <Epyon> <color> it's authorized_keys
[22:47] <kat> Epyon, it IS
[22:47] [10:47] <Epyon> <color> with a z
[22:47] <kat> z?
[22:47] <WingZero> yes
[22:47] <WingZero> it's is not with a Z
[22:47] <WingZero> it*
[22:47] <WingZero> it *should* have a z, not an s
[22:48] <kat> fine, it is
[22:49] <kat> the ssh key is fucklinux
[22:49] <WingZero> i dont care what that is
[22:49] <kat> do whatever you want to it, it isn't useable YET
Check the bot's logs on the webpage, if you don't believe me, it was 12/13/02.
Kat
12. Re: exu not working
Why don't you simply remove all your programs and
reinstall exu and a fresh cgi program instead of
trying to guess what they may of corrupted in your
files.
Bernie
13. Re: exu not working
On Fri, Feb 07, 2003 at 10:44:48AM -0500, Bernie Ryan wrote:
>
>
> Why don't you simply remove all your programs and
> reinstall exu and a fresh cgi program instead of
> trying to guess what they may of corrupted in your
> files.
>
> Bernie
Chris uploaded a fresh, working exu. This new exu has the exact same problem.
And "exu" all by itself on a command line, fails. (According to Chris, that is.)
So, a fresh install and a fresh cgi probably would do nothing.
"gdb exu", the last resort (gdb is oriented to C and asm programmers), might
tell us more about the problem however.
jbrown
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
14. Re: exu not working
> "gdb exu", the last resort (gdb is oriented to C and asm programmers),
might
> tell us more about the problem however.
>
Hmmm just had a play with this; it's way over my head!
chris.
15. Re: exu not working
I know. That was the ssh key password, not the account password. (The ssh
key
password is completely useless without the ssh key that goes along with
it,
btw.) The other one, didn't seem to be a password for anything, neither
password
allowed me to ftp to your acount.
Not that this has anything to do with Chris's nonfunctional exu, or
anything ...
On that note, I'd recommend trying exu with gdb to see what happens (as
gdb
can give useful debuggin information) and posting the debugging session to
this
list, Chris. (Not sure if you are familar with gdb, if not email me
privately
and I'll try to give you a rundown of how it works.)
jbrown
On Fri, Feb 07, 2003 at 01:20:06AM -0600, gertie at visionsix.com wrote:
>
> On 6 Feb 2003, at 20:25, jbrown1050 at hotpop.com wrote:
>
> >
> > On Thu, Feb 06, 2003 at 05:03:49PM -0600, gertie at visionsix.com wrote:
> > >
> > > Good luck. After months of working with exu on remote nix boxen, i
gave up, it
> > > never worked right. Even after i gave the account password to the
gurus here.
> > >
> > > Kat
> > >
> >
> > Actually, you never gave us the password (not the account one I mean).
>
> I did, in channel, too:
>
> [22:46] <robsz1> we cant really do anything with your account, kat
> [22:46] <jbrown> kat, you know how to make RSA keys with ssh-keygen or
> pgp right?
> [22:46] <WingZero> even if you get it right....
> [22:46] <WingZero> the name is wrong
> [22:46] <robsz1> not without yer psswd anyways
> [22:46] <kat> 0gertie1
> [22:47] [10:47] <Epyon> <color> it's authorized_keys
> [22:47] <kat> Epyon, it IS
> [22:47] [10:47] <Epyon> <color> with a z
> [22:47] <kat> z?
> [22:47] <WingZero> yes
> [22:47] <WingZero> it's is not with a Z
> [22:47] <WingZero> it*
> [22:47] <WingZero> it *should* have a z, not an s
> [22:48] <kat> fine, it is
> [22:49] <kat> the ssh key is fucklinux
> [22:49] <WingZero> i dont care what that is
> [22:49] <kat> do whatever you want to it, it isn't useable YET
>
> Check the bot's logs on the webpage, if you don't believe me, it was
12/13/02.
>
> Kat
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
16. Re: exu not working
On Fri, Feb 07, 2003 at 08:46:03PM -0000, tubby.toast at ntlworld.com wrote:
>
> > "gdb exu", the last resort (gdb is oriented to C and asm programmers),
> might
> > tell us more about the problem however.
> >
> Hmmm just had a play with this; it's way over my head!
>
> chris.
Hmm ... well I'll give it a go then.
<transcript>
$ gdb ./exu
GNU gdb 4.17.0.11 with Linux support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
"/home/jbrown105/./exu": not in executable format: File format not recognized
(gdb) quit
$ file ./exu
./exu: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked,
stripped
$
</transcript>
Ah, its statically linked. That means you don't need ncurses to be installed at
all to use it (or glibc for that matter). Heh.
However, a staticly linked exu can't be used in gdb it seems. My version of
exu is rather old, but since its the same size as Chris's, I'd assume that Chris
has a staticly linked exu as well. RC, can you provide a dynamicly linked exu
for us perhaps?
jbrown
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
17. Re: exu not working
> On that note, I'd recommend trying exu with gdb to see what happens (as
> gdb
> can give useful debuggin information) and posting the debugging session to
> this
> list, Chris. (Not sure if you are familar with gdb, if not email me
> privately
> and I'll try to give you a rundown of how it works.)
OK this is what I get:
Starting program: /home/chrissy/bin/exu
warning: shared library handler failed to enable breakpoint
Program exited with code 0177.
I'm guessing this isn't very useful?
Well thanks for all the help anyway.
chris.
18. Re: exu not working
- Posted by gertie at visionsix.com
Feb 08, 2003
On 7 Feb 2003, at 14:19, jbrown1050 at hotpop.com wrote:
>
> I know. That was the ssh key password, not the account password. (The
ssh
> key
> password is completely useless without the ssh key that goes along with
> it,
[22:49] <kat> the ssh key is fucklinux
[22:49] <WingZero> i dont care what that is
> btw.) The other one, didn't seem to be a password for anything, neither
> password
> allowed me to ftp to your acount.
Strange, the problem at that point was i could not ftp or ssh to the
account
either! EVERYTHING i did was useless, and the thing is, i was offering
money to have a WORKING account. Not an account that i could waste
days on when you (collectively, not "you" particularly) might know one
command to fix it, and wouldn't tell me about it.
> Not that this has anything to do with Chris's nonfunctional exu, or
> anything ...
It does in that Eu won't run on a remote box.
Kat
> On that note, I'd recommend trying exu with gdb to see what happens (as
> gdb
> can give useful debuggin information) and posting the debugging session
to
> this
> list, Chris. (Not sure if you are familar with gdb, if not email me
> privately
> and I'll try to give you a rundown of how it works.)
>
> jbrown
>
> On Fri, Feb 07, 2003 at 01:20:06AM -0600, gertie at visionsix.com wrote:
> >
> > On 6 Feb 2003, at 20:25, jbrown1050 at hotpop.com wrote:
> >
> > >
> > > On Thu, Feb 06, 2003 at 05:03:49PM -0600, gertie at visionsix.com
wrote:
> > > >
> > > > Good luck. After months of working with exu on remote nix boxen, i
> gave up, it
> > > > never worked right. Even after i gave the account password to the
> gurus here.
> > > >
> > > > Kat
> > > >
> > >
> > > Actually, you never gave us the password (not the account one I
mean).
> >
> > I did, in channel, too:
> >
> > [22:46] <robsz1> we cant really do anything with your account, kat
> > [22:46] <jbrown> kat, you know how to make RSA keys with ssh-keygen or
> > pgp right?
> > [22:46] <WingZero> even if you get it right....
> > [22:46] <WingZero> the name is wrong
> > [22:46] <robsz1> not without yer psswd anyways
> > [22:46] <kat> 0gertie1
> > [22:47] [10:47] <Epyon> <color> it's authorized_keys
> > [22:47] <kat> Epyon, it IS
> > [22:47] [10:47] <Epyon> <color> with a z
> > [22:47] <kat> z?
> > [22:47] <WingZero> yes
> > [22:47] <WingZero> it's is not with a Z
> > [22:47] <WingZero> it*
> > [22:47] <WingZero> it *should* have a z, not an s
> > [22:48] <kat> fine, it is
> > [22:49] <kat> the ssh key is fucklinux
> > [22:49] <WingZero> i dont care what that is
> > [22:49] <kat> do whatever you want to it, it isn't useable YET
> >
> > Check the bot's logs on the webpage, if you don't believe me, it was
> 12/13/02.
> >
> > Kat
> >
> >
> > TOPICA - Start your own email discussion group. FREE!
>
> --
> /"\ ASCII ribbon |
> \ / campain against | Linux User:190064
> X HTML in e-mail and | Linux Machine:84163
> /*\ news, and unneeded MIME |
>
>
>
> TOPICA - Start your own email discussion group. FREE!
>
19. Re: exu not working
My results, for what it's worth, on Mandrake 9.0 with Euphoria 2.3
public domain edition:
[travis@12-218-230-127 travis]$ cd programs/euphoria/bin
[travis@12-218-230-127 bin]$ gdb ./exu
GNU gdb 5.2.1-2mdk (Mandrake Linux)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-mandrake-linux-gnu"...(no debugging
symbols found)...
(gdb) run
Starting program: /home/travis/programs/euphoria/bin/exu
warning: shared library handler failed to enable breakpoint
Program received signal SIGTRAP, Trace/breakpoint trap.
0x400012e0 in ?? ()
(gdb) quit
The program is running. Exit anyway? (y or n) y
[travis@12-218-230-127 bin]$ file ./exu
./exu: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linked, stripped
[travis@12-218-230-127 bin]$
Travis Beaty
Mason City, Iowa.
jbrown1050 at hotpop.com wrote:
>
>On Fri, Feb 07, 2003 at 08:46:03PM -0000, tubby.toast at ntlworld.com wrote:
>
>
>>>"gdb exu", the last resort (gdb is oriented to C and asm programmers),
>>>
>>>
>>might
>>
>>
>>>tell us more about the problem however.
>>>
>>>
>>Hmmm just had a play with this; it's way over my head!
>>
>>chris.
>>
>>
>Hmm ... well I'll give it a go then.
>
><transcript>
>$ gdb ./exu
>GNU gdb 4.17.0.11 with Linux support
>Copyright 1998 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you are
>welcome to change it and/or distribute copies of it under certain conditions.
>Type "show copying" to see the conditions.
>There is absolutely no warranty for GDB. Type "show warranty" for details.
>This GDB was configured as "i386-redhat-linux"...
>
>"/home/jbrown105/./exu": not in executable format: File format not recognized
>
>(gdb) quit
>$ file ./exu
>./exu: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked,
>stripped
>$
></transcript>
>
>Ah, its statically linked. That means you don't need ncurses to be installed at
>all to use it (or glibc for that matter). Heh.
>
>However, a staticly linked exu can't be used in gdb it seems. My version of
>exu is rather old, but since its the same size as Chris's, I'd assume that
>Chris
>has a staticly linked exu as well. RC, can you provide a dynamicly linked exu
>for us perhaps?
>
>jbrown
>
>
>>TOPICA - Start your own email discussion group. FREE!
>>
>>
20. Re: exu not working
On Fri, Feb 07, 2003 at 04:46:16PM -0600, gertie at visionsix.com wrote:
>
> On 7 Feb 2003, at 14:19, jbrown1050 at hotpop.com wrote:
>
> >
> > I know. That was the ssh key password, not the account password. (The
> ssh
> > key
> > password is completely useless without the ssh key that goes along
with
> > it,
>
> [22:49] <kat> the ssh key is fucklinux
> [22:49] <WingZero> i dont care what that is
>
I didnt have your key, so that password was useless. (I think you left
before
someone asked for the key tho, and seeing as you never used ssh before,
its not your fault. Its not anyone elses either, really, tho.)
> > btw.) The other one, didn't seem to be a password for anything,
neither
> > password
> > allowed me to ftp to your acount.
>
> Strange, the problem at that point was i could not ftp or ssh to the
> account
> either! EVERYTHING i did was useless, and the thing is, i was offering
> money to have a WORKING account. Not an account that i could waste
> days on when you (collectively, not "you" particularly) might know one
> command to fix it, and wouldn't tell me about it.
The only person who could have fixed it instantly, orkim, wasn't around.
He had the root password, if we had the root password we could have fixed
it
for you in seconds. (Or, if orkim had been around, he could have fixed it
in minutes.) So then, there was one command that would fix it (or rather,
a
small set of commands that could be easy be typed on a single line), but
only orkim would be allowed to type that, anyone else who tried would be
denied access. Sorry.
>
> > Not that this has anything to do with Chris's nonfunctional exu, or
> > anything ...
>
> It does in that Eu won't run on a remote box.
Ok fine (tho yours was an account problem, not a dsyfunctional exu, to be
picky),
but this doesn't really help Chris, does it?
*sigh* I'm doing the best I can, considering the millions of different
possible
combinations there are.
btw, Chris, what does typing "file `which exu`" give you?
>
> Kat
>
<snip>
jbrown
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
21. Re: exu not working
Hello Kat,
Could you provide a copy of the dialogue you have with the UNIX system?
Also at the UNIX prompt ($) type:
echo $EUDIR
echo $PATH
echo $TERM
stty -a
Record all the output into a file and email it back to the list. We can
then take a closer look.
BTW if you are still interested upgrading to Windows 98 SE then email me
privately.
Regards,
Andy Cranston.
At 04:46 PM 2/7/03 -0600, you wrote:
>
>On 7 Feb 2003, at 14:19, jbrown1050 at hotpop.com wrote:
>
>>
>> I know. That was the ssh key password, not the account password. (The
>ssh
>> key
>> password is completely useless without the ssh key that goes along with
>> it,
>
> [22:49] <kat> the ssh key is fucklinux
> [22:49] <WingZero> i dont care what that is
>
>> btw.) The other one, didn't seem to be a password for anything, neither
>> password
>> allowed me to ftp to your acount.
>
>Strange, the problem at that point was i could not ftp or ssh to the
>account
>either! EVERYTHING i did was useless, and the thing is, i was offering
>money to have a WORKING account. Not an account that i could waste
>days on when you (collectively, not "you" particularly) might know one
>command to fix it, and wouldn't tell me about it.
>
>> Not that this has anything to do with Chris's nonfunctional exu, or
>> anything ...
>
>It does in that Eu won't run on a remote box.
>
>Kat
>
>> On that note, I'd recommend trying exu with gdb to see what happens (as
>> gdb
>> can give useful debuggin information) and posting the debugging session
>to
>> this
>> list, Chris. (Not sure if you are familar with gdb, if not email me
>> privately
>> and I'll try to give you a rundown of how it works.)
>>
>> jbrown
>>
>> On Fri, Feb 07, 2003 at 01:20:06AM -0600, gertie at visionsix.com wrote:
>> >
>> > On 6 Feb 2003, at 20:25, jbrown1050 at hotpop.com wrote:
>> >
>> > >
>> > > On Thu, Feb 06, 2003 at 05:03:49PM -0600, gertie at visionsix.com
>wrote:
>> > > >
>> > > > Good luck. After months of working with exu on remote nix boxen,
i
>> gave up, it
>> > > > never worked right. Even after i gave the account password to the
>> gurus here.
>> > > >
>> > > > Kat
>> > > >
>> > >
>> > > Actually, you never gave us the password (not the account one I
>mean).
>> >
>> > I did, in channel, too:
>> >
>> > [22:46] <robsz1> we cant really do anything with your account, kat
>> > [22:46] <jbrown> kat, you know how to make RSA keys with ssh-keygen
or
>> > pgp right?
>> > [22:46] <WingZero> even if you get it right....
>> > [22:46] <WingZero> the name is wrong
>> > [22:46] <robsz1> not without yer psswd anyways
>> > [22:46] <kat> 0gertie1
>> > [22:47] [10:47] <Epyon> <color> it's authorized_keys
>> > [22:47] <kat> Epyon, it IS
>> > [22:47] [10:47] <Epyon> <color> with a z
>> > [22:47] <kat> z?
>> > [22:47] <WingZero> yes
>> > [22:47] <WingZero> it's is not with a Z
>> > [22:47] <WingZero> it*
>> > [22:47] <WingZero> it *should* have a z, not an s
>> > [22:48] <kat> fine, it is
>> > [22:49] <kat> the ssh key is fucklinux
>> > [22:49] <WingZero> i dont care what that is
>> > [22:49] <kat> do whatever you want to it, it isn't useable YET
>> >
>> > Check the bot's logs on the webpage, if you don't believe me, it was
>> 12/13/02.
>> >
>> > Kat
>> >
>> >
>> > TOPICA - Start your own email discussion group. FREE!
>>
>> --
>> /"\ ASCII ribbon |
>> \ / campain against | Linux User:190064
>> X HTML in e-mail and | Linux Machine:84163
>> /*\ news, and unneeded MIME |
>>
>>
>> TOPICA - Start your own email discussion group. FREE!
>>
>
>
>
>TOPICA - Start your own email discussion group. FREE!
>
>
22. Re: exu not working
- Posted by gertie at visionsix.com
Feb 08, 2003
On 8 Feb 2003, at 1:05, acran at readout.fsnet.co.uk wrote:
>
> Hello Kat,
>
> Could you provide a copy of the dialogue you have with the UNIX system?
No, that was months ago, i lost the job and potential demonstration of what
Eu can do in text processing. I can do it, i just haveto do it on a windows box
of my own, which is going to cost me a lot more per month than a little shell
account.
Kat
23. Re: exu not working
> btw, Chris, what does typing "file `which exu`" give you?
bash-2.05a$ file`which exu`
/home/chrissy/bin/exu: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV),
statically linked, stripped
chris.
24. Re: exu not working
Since 0177 is octal for 127 (why C uses a prefixed 0 for octal is beyond me),
it does tell us that its not system() thats returning 127, but exu.
I.e., system() is finding and running exu just fine. exu is the one returning
127.
Very strange, not sure why this is happening.
jbrown
On Sat, Feb 08, 2003 at 12:04:40AM -0000, tubby.toast at ntlworld.com wrote:
>
> > On that note, I'd recommend trying exu with gdb to see what happens (as
> > gdb
> > can give useful debuggin information) and posting the debugging session to
> > this
> > list, Chris. (Not sure if you are familar with gdb, if not email me
> > privately
> > and I'll try to give you a rundown of how it works.)
>
> OK this is what I get:
>
> Starting program: /home/chrissy/bin/exu
> warning: shared library handler failed to enable breakpoint
>
> Program exited with code 0177.
>
> I'm guessing this isn't very useful?
> Well thanks for all the help anyway.
>
> chris.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
25. Re: exu not working
On Sat, Feb 08, 2003 at 10:55:57AM -0000, tubby.toast at ntlworld.com wrote:
>
> > btw, Chris, what does typing "file `which exu`" give you?
>
> bash-2.05a$ file`which exu`
> /home/chrissy/bin/exu: ELF 32-bit LSB executable, Intel 80386, version 1
> (SYSV),
> statically linked, stripped
>
> chris.
No doubt about it, the exu binary is the same one as mine, and exu itself
is working fine. Being staticly linked, its not a linker or missing library
error. And, when run, it doesn't do anything and just returns an exitcode of
127. Since no error message is emited, it _probably_ isn't an ncurses error.
I know what its not, but I'm out of ideas to guess what it might be.
Are any other programs of yours acting funny like this? Anything else go odd
on the server once it was upgraded? or was it just exu?
And, do you know, what the server was upgraded from?
jbrown
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
26. Re: exu not working
> No doubt about it, the exu binary is the same one as mine, and exu itself
> is working fine. Being staticly linked, its not a linker or missing
library
> error. And, when run, it doesn't do anything and just returns an exitcode
of
> 127. Since no error message is emited, it _probably_ isn't an ncurses
error.
> I know what its not, but I'm out of ideas to guess what it might be.
Does anyone know on what conditions exu will give an exit code of 127?
Presumably it's in the source somewhere/
> Are any other programs of yours acting funny like this? Anything else go
odd
> on the server once it was upgraded? or was it just exu?
>
Well actually, I can't log on to their new Control Panel thingy. This is a
CGI program for managing my account and webspace. I'm not particularly
bothered as I can do everything that this does over telnet and FTP. I have
informed tech support about this but that was four days ago. Maybe if they
get this fixed, exu will miraculously work again. though I can't see how
they are related.
Everything else is fine though. I have just re-written one of the scripts
in C (a counter, which is about all my limited knowledge of C will allow)
and that runs fine.
> And, do you know, what the server was upgraded from?
Sorry, I don't, just that it was another version of Linux.
chris.
27. Re: exu not working
Hmm ... interesting.
I assume your C counter program is a dynamicly linked ELF binary.
Do you have any other staticly linked binaries to test out? If not
perhaps you could recompile your counter program as a static binary,
and see what happens. (I'm guessing this might be an error that only applies
to staticly linked programs.)
jbrown
On Sat, Feb 08, 2003 at 09:15:48PM -0000, tubby.toast at ntlworld.com wrote:
>
> > No doubt about it, the exu binary is the same one as mine, and exu itself
> > is working fine. Being staticly linked, its not a linker or missing
> library
> > error. And, when run, it doesn't do anything and just returns an exitcode
> of
> > 127. Since no error message is emited, it _probably_ isn't an ncurses
> error.
> > I know what its not, but I'm out of ideas to guess what it might be.
>
> Does anyone know on what conditions exu will give an exit code of 127?
> Presumably it's in the source somewhere/
>
> > Are any other programs of yours acting funny like this? Anything else go
> odd
> > on the server once it was upgraded? or was it just exu?
> >
> Well actually, I can't log on to their new Control Panel thingy. This is a
> CGI program for managing my account and webspace. I'm not particularly
> bothered as I can do everything that this does over telnet and FTP. I have
> informed tech support about this but that was four days ago. Maybe if they
> get this fixed, exu will miraculously work again. though I can't see how
> they are related.
>
> Everything else is fine though. I have just re-written one of the scripts
> in C (a counter, which is about all my limited knowledge of C will allow)
> and that runs fine.
>
> > And, do you know, what the server was upgraded from?
>
> Sorry, I don't, just that it was another version of Linux.
>
> chris.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
28. Re: exu not working
> Hmm ... interesting.
>
> I assume your C counter program is a dynamicly linked ELF binary.
Yes, it is.
> Do you have any other staticly linked binaries to test out? If not
> perhaps you could recompile your counter program as a static binary,
> and see what happens. (I'm guessing this might be an error that only
applies
> to staticly linked programs.)
Can you tell me how to do that? (Like I say, *very* limited C knowledge)
chris.
29. Re: exu not working
IIRC, just use the -static flag.
For example:
gcc -static -o counter counter.c
Someone correct me if I'm wrong here.
jbrown
On Sun, Feb 09, 2003 at 01:17:19AM -0000, tubby.toast at ntlworld.com wrote:
>
> > Hmm ... interesting.
> >
> > I assume your C counter program is a dynamicly linked ELF binary.
>
> Yes, it is.
>
> > Do you have any other staticly linked binaries to test out? If not
> > perhaps you could recompile your counter program as a static binary,
> > and see what happens. (I'm guessing this might be an error that only
> applies
> > to staticly linked programs.)
>
> Can you tell me how to do that? (Like I say, *very* limited C knowledge)
>
> chris.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
30. Re: exu not working
On Sat, 8 Feb 2003 21:15:48 -0000, tubby.toast at ntlworld.com wrote:
>Does anyone know on what conditions exu will give an exit code of 127?
>Presumably it's in the source somewhere/
Hmm:
http://en.tldp.org/LDP/abs/html/exitcodes.html
http://www-rn.informatik.uni-bremen.de/software/elk/split/unix/unix-11.ht=
ml
http://www.opengroup.org/onlinepubs/007908799/xcu/env.html
command does not exist.
My guess would therefore be this is a path, or your ISP deliberately
spannering your ability to run exu type problem.
Pete
31. Re: exu not working
The command definately exists. No doubt about that.
Its a staticly linked ELF binary chmod'd 0755.
My guess ... something on that server doesnt like static binaries ... but
thats merely a guess.
jbrown
On Sun, Feb 09, 2003 at 03:12:34AM +0000, Pete Lomax wrote:
>
> On Sat, 8 Feb 2003 21:15:48 -0000, tubby.toast at ntlworld.com wrote:
>
> >Does anyone know on what conditions exu will give an exit code of 127?
> >Presumably it's in the source somewhere/
>
> Hmm:
> http://en.tldp.org/LDP/abs/html/exitcodes.html
> http://www-rn.informatik.uni-bremen.de/software/elk/split/unix/unix-11.html
> http://www.opengroup.org/onlinepubs/007908799/xcu/env.html
>
> command does not exist.
>
> My guess would therefore be this is a path, or your ISP deliberately
> spannering your ability to run exu type problem.
>
> Pete
>
> ==^^===============================================================
> This email was sent to: jbrown1050 at hotpop.com
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
32. Re: exu not working
> My guess ... something on that server doesnt like static binaries ... but
> thats merely a guess.
No, it's not that. The counter program re-compiled as a static binary works
fine.
Still, Euphoria 2.4 alpha is due any day. If that doesn't work, I can
submit a bug report and maybe get some input from Rob. (I can understand
he'd be a bit busy right now).
chris.
33. Re: exu not working
Just as an experiment, try running another ncurses program.
Do other ncurses programs work? Or is it only exu that fails?
jbrown
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
34. Re: exu not working
> Just as an experiment, try running another ncurses program.
> Do other ncurses programs work? Or is it only exu that fails?
What else uses ncurses? Does vi use it? That works.
chris.
35. Re: exu not working
Here are a few things to check.
1. Did you upload (FTP) exu in "text" mode?
It should be uploaded in binary mode, or a few bytes
could be altered (i.e. \r\n changes to \n).
Or do the tar extraction on the Linux machine,
after uploading the compressed .tar file in binary mode.
If exu is altered in any way, it will probably return
an exit code 127. This is actually the upx decompressor
returning a failure code.
2. Do you have permission to cd into /tmp and do:
touch junk
to create a new file there? Is /tmp out of space?
3. Other things to try:
run:
strace -o junk exu
"junk" will have the system calls that exu executed.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
36. Re: exu not working
This is a multi-part message in MIME format.
------=_NextPart_000_0025_01C2D093.69776F00
charset="iso-8859-1"
Robert Craig wrote:
> Here are a few things to check.
>
> 1. Did you upload (FTP) exu in "text" mode?
> It should be uploaded in binary mode, or a few bytes
> could be altered (i.e. \r\n changes to \n).
> Or do the tar extraction on the Linux machine,
> after uploading the compressed .tar file in binary mode.
> If exu is altered in any way, it will probably return
> an exit code 127. This is actually the upx decompressor
> returning a failure code.
Checked all this again; still doesn't work.
> 2. Do you have permission to cd into /tmp and do:
> touch junk
> to create a new file there? Is /tmp out of space?
>
Yes, was able to create a file in /tmp.
> 3. Other things to try:
> run:
> strace -o junk exu
> "junk" will have the system calls that exu executed.
>
I don't really understand the output, so I've attatched it.
Thanks for your help,
chris.
------=_NextPart_000_0025_01C2D093.69776F00
Content-Type: text/plain;
name="junk.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="junk.txt"
execve("/home/chrissy/bin/exu", ["exu"], [/* 21 vars */]) =3D 0
open("/proc/self/exe", O_RDONLY) =3D 3
lseek(3, 1644, SEEK_SET) =3D 1644
read(3, "C\376_\21p\36\3\0p\36\3\0", 12) =3D 12
getpid() =3D 415
gettimeofday({1044832552, 664475}, NULL) =3D 0
unlink("/tmp/upxHRHHULVAAPZ") =3D -1 ENOENT (No such file or =
directory)
open("/tmp/upxHRHHULVAAPZ", O_WRONLY|O_CREAT|O_EXCL, 0700) =3D 4
ftruncate(4, 204400) =3D 0
old_mmap(NULL, 206448, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, =
-1, 0) =3D 0x40000000
read(3, "p\36\3\0002H\1\0", 8) =3D 8
read(3, "\177?d\371\177ELF\1\0\2\0\3\0\r \255\4\377\333\330\335"..., =
84018) =3D 84018
write(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\2\0\3\0\1\0\0\0 \255\4"..., =
204400) =3D 204400
read(3, "\0\0\0\0UPX!", 8) =3D 8
munmap(0x40000000, 206448) =3D 0
close(3) =3D 0
close(4) =3D 0
open("/tmp/upxHRHHULVAAPZ", O_RDONLY) =3D 3
fcntl(3, F_GETFD) =3D 0
fcntl(3, F_SETFD, FD_CLOEXEC) =3D 0
unlink("/tmp/upxHRHHULVAAPZ") =3D 0
execve("/proc/self/fd/3", ["exu"], [/* 21 vars */]) =3D -1 EACCES =
(Permission denied)
execve("/dev/fd/3", ["exu"], [/* 21 vars */]) =3D -1 EACCES (Permission =
denied)
unlink("/tmp/upxHRHHULVAAPZ") =3D -1 ENOENT (No such file or =
directory)
_exit(127) =3D ?
------=_NextPart_000_0025_01C2D093.69776F00--
37. Re: exu not working
OK, the problem is definitely with UPX. I've just tried tunning UPX on the
server and...no output; exit code 127.
The latest beta of UPX does work though. However, I don't expect Rob to use
an unstable beta.
So, what can have changed on the server to cause UPX to fail? And if we
don't find an answer, is there anyway at all that an uncompressed version of
exu can be made available?
Thanks,
chris.
38. Re: exu not working
Chris writes:
> So, what can have changed on the server to cause UPX to fail?
>From your strace output, I'd guess that maybe your host
is now denying you execute permission in /proc
/proc is a kind of virtual filesystem.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
39. Re: exu not working
Hmm ...
Judging by the attachment you provided, I'd have to say that you don't
have permission to execute the file handle 3 "/proc/self/fd/3", i.e.
the server you are running exu on is not compatible with UPX compression it
would appear.
jbrown
On Sun, Feb 09, 2003 at 11:31:46PM -0000, tubby.toast at ntlworld.com wrote:
<snip>
> Robert Craig wrote:
<snip>
>
> > 3. Other things to try:
> > run:
> > strace -o junk exu
> > "junk" will have the system calls that exu executed.
> >
> I don't really understand the output, so I've attatched it.
>
> Thanks for your help,
> chris.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
> execve("/home/chrissy/bin/exu", ["exu"], [/* 21 vars */]) = 0
> open("/proc/self/exe", O_RDONLY) = 3
> lseek(3, 1644, SEEK_SET) = 1644
> read(3, "C\376_\21p\36\3\0p\36\3\0", 12) = 12
> getpid() = 415
> gettimeofday({1044832552, 664475}, NULL) = 0
> unlink("/tmp/upxHRHHULVAAPZ") = -1 ENOENT (No such file or
> directory)
> open("/tmp/upxHRHHULVAAPZ", O_WRONLY|O_CREAT|O_EXCL, 0700) = 4
> ftruncate(4, 204400) = 0
> old_mmap(NULL, 206448, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
> = 0x40000000
> read(3, "p\36\3\0002H\1\0", 8) = 8
> read(3, "\177?d\371\177ELF\1\0\2\0\3\0\r \255\4\377\333\330\335"..., 84018) =
> 84018
> write(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\2\0\3\0\1\0\0\0 \255\4"..., 204400)
> = 204400
> read(3, "\0\0\0\0UPX!", 8) = 8
> munmap(0x40000000, 206448) = 0
> close(3) = 0
> close(4) = 0
> open("/tmp/upxHRHHULVAAPZ", O_RDONLY) = 3
> fcntl(3, F_GETFD) = 0
> fcntl(3, F_SETFD, FD_CLOEXEC) = 0
> unlink("/tmp/upxHRHHULVAAPZ") = 0
> execve("/proc/self/fd/3", ["exu"], [/* 21 vars */]) = -1 EACCES (Permission
> denied)
> execve("/dev/fd/3", ["exu"], [/* 21 vars */]) = -1 EACCES (Permission denied)
> unlink("/tmp/upxHRHHULVAAPZ") = -1 ENOENT (No such file or
> directory)
> _exit(127) = ?
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
40. Re: exu not working
Great to hear you fixed it ... mind telling us how you fixed it?
(To clear up matters in case this ever happens again.)
jbrown
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
41. Re: exu not working
> Great to hear you fixed it ... mind telling us how you fixed it?
> (To clear up matters in case this ever happens again.)
>
> jbrown
Well, just downloaded UPX (upx.sourceforge.net), decompressed a copy of exu
on my local machine and uploaded it.
chris.
42. Re: exu not working
Too bad RC doesn't have an un-UPX'ed exu on the main web site.
Oh well.
jbrown
On Mon, Feb 10, 2003 at 12:30:54PM -0000, tubby.toast at ntlworld.com wrote:
>
> > Great to hear you fixed it ... mind telling us how you fixed it?
> > (To clear up matters in case this ever happens again.)
> >
> > jbrown
>
> Well, just downloaded UPX (upx.sourceforge.net), decompressed a copy of exu
> on my local machine and uploaded it.
>
> chris.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
--
/"\ ASCII ribbon |
\ / campain against | Linux User:190064
X HTML in e-mail and | Linux Machine:84163
/*\ news, and unneeded MIME |
