TeamForge : Post

Forum Topic - Disappearing binaries ...:

View: as

Rajat Jain

10/03/2008 4:55 AM

post14396

Hi,

I could not find an appropriate forum for this and hence...

This is regarding a very very strange behaviour I am observing on a freescale powerPC platform. The problem is that few 
binaries (related to USB in my case) just DISAPPEAR from the filesystem when executed once. I mean you can see they are 
present just before executing them, and you execute them and they DO get executed, but then Poof! they are gone:

# pwd
/proc/boot
#
#
# ls u* i*
i2c-mpc5200    io-net         umount         usb
ifconfig       io-usb         uname

Process 24589 (ls) exited status=0.
#
# usb
usb: unable to connect to USB - No such file or directory

Process 32781 (usb) exited status=1.
#
# usb
ksh: usb: not found
# us
ksh: us: not found
# usb
ksh: usb: not found
# ls u* i*
i2c-mpc5200    io-net         umount
ifconfig       io-usb         uname

Process 40973 (ls) exited status=0.
#

Can some one please suggest what could be the reason? The same is happening with "io-usb" binary. Please note that this 
is only happening with some binaries. The othe rbinaries in the same binary (say "kill") are working fine...

I'm really puzzled.

Rajat

Rajat Jain

10/03/2008 5:00 AM

post14398

Re: Disappearing binaries ...

Hi,

I found a work around immediately after posting my query. But I still do not know the reason of the problem.

The "problematic" binaries were included at the begining of the build script (near to libc.so). When I included them in 
the end of the build script, everything is OK. Although I don't undertsand this ...

Thanks,

Rajat

Jeevan Mathew(deleted)

10/03/2008 7:23 AM

post14402

Re: Disappearing binaries ...

> Hi,
> 
> I found a work around immediately after posting my query. But I still do not 
> know the reason of the problem.
> 
> The "problematic" binaries were included at the begining of the build script (
> near to libc.so). When I included them in the end of the build script, 
> everything is OK. Although I don't undertsand this ...
> 
> Thanks,
> 
> Rajat


Can You post your complete buildfile ?

Jeevan

Rajat Jain

10/03/2008 7:28 AM

post14403

RE: Disappearing binaries ...

Hi,

Here is the buildfile that works. Please note the location of following
binaries in the end: 

usb
io-usb
devu-ehci-8349.so
libusbdi.so

If I move these to just after where libc.so is included, the problemn
appears...

Thanks,

Rajat


----Original Message----
From: Jeevan Mathew [mailto:community-noreply@qnx.com]
Sent: Friday, October 03, 2008 4:53 PM
To: general-toolchain
Subject: Re: Disappearing binaries ...

>> Hi,
>> 
>> I found a work around immediately after posting my query. But I still
>> do not know the reason of the problem.
>> 
>> The "problematic" binaries were included at the begining of the build
>> script ( near to libc.so). When I included them in the end of the
>> build script, everything is OK. Although I don't undertsand this ...
>> 
>> Thanks,
>> 
>> Rajat
> 
> 
> Can You post your complete buildfile ?
> 
> Jeevan
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post14402

Attachment:

build 12.31 KB

Jeevan Mathew(deleted)

10/03/2008 8:52 AM

post14415

Re: RE: Disappearing binaries ...

Hi Rajat,
have a look here:
http://www.qnx.com/developers/docs/6.3.2/neutrino/utilities/m/mkifs.html#data
and then here:
http://www.qnx.com/developers/docs/6.3.2/neutrino/utilities/m/mkifs.html#XIPvsCopy

So [data=c] directive/attribute is mandatory , if you want to run a programm multiple times.

Hope this helps.
Jeevan


> 
> Hi,
> 
> Here is the buildfile that works. Please note the location of following
> binaries in the end: 
> 
> usb
> io-usb
> devu-ehci-8349.so
> libusbdi.so
> 
> If I move these to just after where libc.so is included, the problemn
> appears...
> 
> Thanks,
> 
> Rajat
> 
> 
> ----Original Message----
> From: Jeevan Mathew [mailto:community-noreply@qnx.com]
> Sent: Friday, October 03, 2008 4:53 PM
> To: general-toolchain
> Subject: Re: Disappearing binaries ...
> 
> >> Hi,
> >> 
> >> I found a work around immediately after posting my query. But I still
> >> do not know the reason of the problem.
> >> 
> >> The "problematic" binaries were included at the begining of the build
> >> script ( near to libc.so). When I included them in the end of the
> >> build script, everything is OK. Although I don't undertsand this ...
> >> 
> >> Thanks,
> >> 
> >> Rajat
> > 
> > 
> > Can You post your complete buildfile ?
> > 
> > Jeevan
> > 
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post14402
>

Return