Well, it's just a matter of adding a check for
optarg being NULL and
printing an appropriate message (e.g.,
if (optarg == NULL) {
fprintf(stderr, Missing key-value
separator\n);
usage();
}
).
Yup looks easy but I may better patch the DLL to use
On Tue, 1 Mar 2005, Alexander Joerg Herrmann wrote:
Well, it's just a matter of adding a check for
optarg being NULL and
printing an appropriate message (e.g.,
if (optarg == NULL) {
fprintf(stderr, Missing key-value
separator\n);
usage();
On Sun, 27 Feb 2005, Alexander Joerg Herrmann wrote:
Why aren't you using 'mount' and/or 'umount' to manipulate the mounts?
There should be no need to modify the registry directly to add or
remove mounts and doing so may break in the future. Regtool is not the
proper program to use to
On Sat, 26 Feb 2005, Brian Dessent wrote:
Alexander Joerg Herrmann wrote:
What I was mentioning is that
regtool -K
causes a core fault and something similar under windows because the
argument is broken. I know that the argument is missing and so should
regtool. It should produce a
On Sun, 27 Feb 2005, Igor Pechtchanski wrote:
On Sat, 26 Feb 2005, Brian Dessent wrote:
Alexander Joerg Herrmann wrote:
What I was mentioning is that
regtool -K
causes a core fault and something similar under windows because the
argument is broken. I know that the argument is
On Sun, Feb 27, 2005 at 11:04:49AM -0500, Igor Pechtchanski wrote:
On Sun, 27 Feb 2005, Alexander Joerg Herrmann wrote:
Why aren't you using 'mount' and/or 'umount' to manipulate the mounts?
There should be no need to modify the registry directly to add or
remove mounts and doing so may
Alexander Joerg Herrmann wrote:
BTW: Why does CygWin use something evil like the
Window$ Registry anyway for mount points?
Because a bootstrap is needed on startup. Cygwin can't tell where to
look for the mount table until after it already has the Windows path to
/, and it can't get that until
Dear Arturus,
regtool dosn't dpend on the Cygwin environment as it
can also run from the Windows command line without any
Cygwin souroundings.
What I was mentioning is that
rgetool -K
causes a core fault and something similar under
windows because the argument is broken. I know that
the argument
Alexander Joerg Herrmann wrote:
regtool dosn't dpend on the Cygwin environment as it
can also run from the Windows command line without any
Cygwin souroundings.
What I was mentioning is that
rgetool -K
causes a core fault and something similar under
windows because the argument is broken.
False. regtool is a cygwin app and depends on the
cygwin DLL:
Was my mistake as I run it within the Cygwin startup
bat as
E:\aIEngine\CYGWINbin\regtool
in order to set all the moutn points on computers
without CygWin installed.
Alex
=
Alexander Joerg Herrmann wrote:
False. regtool is a cygwin app and depends on the
cygwin DLL:
Was my mistake as I run it within the Cygwin startup
bat as
E:\aIEngine\CYGWINbin\regtool
in order to set all the moutn points on computers
without CygWin installed.
That doesn't change the
That doesn't change the fact that it's still a
Cygwin application,
because it's linked against cygwin1.dll. Because
you have cygwin1.dll
on the system and in the same directory as
regtool.exe means it will be
found when you run regtool.
I got that. I just didn't check.
Why aren't you
It dosn't feel like a feature so it must be a Bug for
sure :)
Don't worry it's easy to reproduce:
bash-2.05b$ ./regtool -K
Segmentation fault (core dumped)
crashes with a core dump insteed of printing the usage
information while
regtool --key-seperator and regtool --key-seperator=
does the right
13 matches
Mail list logo
