A pair of scripts to make it easier to run and debug 32 bit executables on 64 bit systems

A pair of scripts to make it easier to run and debug 32 bit executables on 64 bit systems

For Example:

  # run the 32 bit binary located ad ../platform/foo/a.out
  $ run_32bit.sh ../platform/foo/a.out

  # run a.out from the current directory, and pass it the --verbose=3 command line option
  $ ../../scripts/run_32bit.sh -- a.out --verbose=3

  # debug a.out from the current directory, include ../v8 in the library search path
  $ LIB_PATHS='../v8/' ../../scripts/debug_32bit.sh a.out


run_32bit.sh runs a 32bit executable, debug_32bit.sh starts up gdb so that it's ready to
debug a 32bit target.  Both scripts work from in or out of the chroot.

If you're running from outside the chroot, you can pass a --chroot command line option to
locate the chroot, otherwise a default is computed through the normal mechanism.

Pass the 32 bit target as the parameter to either of these scripts.  If you need to provide
additional parameters to your command, then you should use -- to signify the end of *_32bit.sh
parameters.

These could be useful to people developing parts of chromeos that can be easily isolated
from the rest of the system.  If your code doesn't NEED to run on a chromeos device it
can be a bit easier to try it out on your owm machine during dev/test.

[Will Drewry, 2010-03-18 20:59:59]

LGTM after the "$@" stuff is fixed up.

I feel like maybe we could come up with more explicit names, but I'm drawing a
blank.  That aside, we might also want move this functionality into common.sh so
that stuff like run_tests.sh can just use a function.  Doesn't have to be done
now though (we can prove these out first, etc)

Thanks for doing this!

http://codereview.chromium.org/1131002/diff/1/2
File src/scripts/debug_32bit.sh (right):

http://codereview.chromium.org/1131002/diff/1/2#newcode52
src/scripts/debug_32bit.sh:52: --args $@
Might want "$@" so expansion doesn't drop quoting.

http://codereview.chromium.org/1131002/diff/1/3
File src/scripts/run_32bit.sh (right):

http://codereview.chromium.org/1131002/diff/1/3#newcode38
src/scripts/run_32bit.sh:38: $@
exec "$@"  might be a bit more friendly (don't leave bash hanging around and
make sure $@ is expanded properly)

That aside, does the lib32 fix up the ld-linux mismatch issues for now?

[rginda, 2010-03-18 21:06:47]

Adding /lib32 to LD_LIBRARY_PATH seems to fix all my woes, but I've only tried
it with a dirt simple program so far.

I'm working on getting a v8 ebuild, and once that's done I'll actually need to
debug something more complicated.  I'll hold off on landing these scripts until
I've successfully used them on a more complicate target.