You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
drmemory.sh bails if it can't find a file corresponding to the app to be
run: but some shell built-ins will work properly. e.g., "time", or
"setsid". we should let it run, and either handle a blank app in
the scripts or pass the shell name?
when I do:
$exepath = $ENV{'SHELL'} if (! -e $exepath)
then:
./drmemory.pl -dr /dr -ops "-pause_at_uninitialized" ./x.sh
=> works, but complains "objdump: ./x.sh: File format not recognized"
./drmemory.pl -dr /dr -ops "-pause_at_uninitialized" setsid ./x.sh
=> just exits: exec fails on "setsid": need to run as '/bin/ash -c "setsid ./x.sh'
PR 459374: support running shell built-ins and scripts
$exepath = $ENV{'SHELL'} if (! -e $exepath)
FIXME: not so sure we should support that: we'd have to run
with -c "cmdline" for some shells, which might conflict w/ quoting
in the app args: seems reasonable to require user to pass us a
real executable, so must prefix scripts with shell or perl.
yet this results in "Segmentation fault" (note: need extra layer of quotes):
./drmemory.pl -v -dr /dr -- /bin/ash -c '"setsid ./x.sh"'
TODO: analyze seg fault
TODO: document what we support and how to run scripts
From derek.br...@gmail.com on December 10, 2010 17:57:58
PR 459374
drmemory.sh bails if it can't find a file corresponding to the app to be
run: but some shell built-ins will work properly. e.g., "time", or
"setsid". we should let it run, and either handle a blank app in
the scripts or pass the shell name?
when I do:
$exepath = $ENV{'SHELL'} if (! -e $exepath)
then:
./drmemory.pl -dr /dr -ops "-pause_at_uninitialized" ./x.sh
=> works, but complains "objdump: ./x.sh: File format not recognized"
./drmemory.pl -dr /dr -ops "-pause_at_uninitialized" setsid ./x.sh
=> just exits: exec fails on "setsid": need to run as '/bin/ash -c "setsid ./x.sh'
PR 459374: support running shell built-ins and scripts
$exepath = $ENV{'SHELL'} if (! -e $exepath)
FIXME: not so sure we should support that: we'd have to run
with -c "cmdline" for some shells, which might conflict w/ quoting
in the app args: seems reasonable to require user to pass us a
real executable, so must prefix scripts with shell or perl.
yet this results in "Segmentation fault" (note: need extra layer of quotes):
./drmemory.pl -v -dr /dr -- /bin/ash -c '"setsid ./x.sh"'
TODO: analyze seg fault
TODO: document what we support and how to run scripts
Original issue: http://code.google.com/p/drmemory/issues/detail?id=140
The text was updated successfully, but these errors were encountered: