|
From: Dennis L. <pla...@in...> - 2005-08-01 16:33:32
|
Hi At 17:24 01.08.2005, Cerion Armour-Brown wrote: >Hi Dennis, > > > - ncurses support does not work completely >The stdout/stderr output panes give plain text only. They're envisaged use is >as debugging aids, not as interactive shells. Perhaps one day, if there's >enough people wanting this... Maybe lots of people just dont use the program because they see they cannot use it ;) As a workaround, maybe it can be set so the output of the program can be redirected to the console the program is started in, so ncurses and ansi color programs would work as expected. > > - A strange thing is that SIOCGIFHWADDR ioctl does not work (returns no > > such device) when run via valkyrie under valgrind3, but with valgrind3 > > pure it works... thats pretty strange... >Really?! Can you supply a test case we can look at? The real problem here was not the ioctl, but the argument passing to the program. valkyrie passes the whole "Binary flags" option as *one* parameter to the program (one argv entry) which confuses getopt/getopt_long, so I got " eth1" instead of "eth1" which of cause confuses the ioctl, since there really is no such device... maybe this should be fixed to pass them the same way the shell does ? greets Dennis Carpe quod tibi datum est |