no output from GNUTLS package

no output from GNUTLS package

[Vasiliy]

Hello,

I could not get any output from 'gnutls' Cygwin64 package. Could
somebody invoke it as follows:

gnutls-cli - GnuTLS client

or any other example.

Compiled from the sources it passes many tests, but still no luck,
very strange, indeed.

Thank you in advance.
Best regards,

Vasiliy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: no output from GNUTLS package

[Csaba Raduly]

Hi Vasily,

On Wed, Jul 10, 2013 at 4:27 PM, Vasiliy  wrote:
> Hello,
>
> I could not get any output from 'gnutls' Cygwin64 package. Could
> somebody invoke it as follows:
>
> gnutls-cli - GnuTLS client

Try running it under the debugger:

gdb --args gnutls-cli - GnuTLS client

and at the gdb prompt, type:    run

If any silent errors are happening, gdb is likely to show them.

Don't forget
> Problem reports:       http://cygwin.com/problems.html

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Fwd: no output from GNUTLS package

[Vasiliy]

Thank you, Csaba,

I was able to track down a stranded library which shouldn't be there,
and now it works!

I've also tracked down that problem with 'test-driver'. Look at that:

$ gdb --args /usr/bin/sh /usr/share/automake-1.14/test-driver
GNU gdb (GDB) 7.6.50.20130320-cvs
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-cygwin".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/sh...Reading symbols from
/usr/lib/debug/usr/bin/sh.exe.dbg...done.
done.
(gdb) run
Starting program: /usr/bin/sh /usr/share/automake-1.14/test-driver
[New Thread 9900.0xc10]
[New Thread 9900.0x1bec]
[New Thread 9900.0xe38]
/usr/share/automake-1.14/test-driver: line 95: $log_file: ambiguous redirect
FAIL:
/usr/share/automake-1.14/test-driver: line 114: $trs_file: ambiguous redirect
/usr/share/automake-1.14/test-driver: line 115: $trs_file: ambiguous redirect
/usr/share/automake-1.14/test-driver: line 116: $trs_file: ambiguous redirect
/usr/share/automake-1.14/test-driver: line 117: $trs_file: ambiguous redirect
[Inferior 1 (process 9900) exited with code 01]
(gdb) quit

$ gdb --args /usr/bin/sh /usr/share/automake-1.14/test-driver --log-file=/tmp
GNU gdb (GDB) 7.6.50.20130320-cvs
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-cygwin".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/sh...Reading symbols from
/usr/lib/debug/usr/bin/sh.exe.dbg...done.
done.
(gdb) run
Starting program: /usr/bin/sh /usr/share/automake-1.14/test-driver
--log-file=/tmp
[New Thread 2164.0x164c]
[New Thread 2164.0x24a4]
[New Thread 2164.0x2550]
/usr/share/automake-1.14/test-driver: invalid option: '--log-file=/tmp'
[New Thread 2164.0x19d4]
Usage:
  test-driver --test-name=NAME --log-file=PATH --trs-file=PATH
              [--expect-failure={yes|no}] [--color-tests={yes|no}]
              [--enable-hard-errors={yes|no}] [--] TEST-SCRIPT
The '--test-name', '--log-file' and '--trs-file' options are mandatory.

So, there is a problem with 'test-driver' either because a testsuite
does not provide --test-name=NAME or because --log-file=/tmp or
--log-file=/tmp/delme is wrongly considered an invalid option. It
applies to automake 1.13 as well.

Could a Cygwin Team suggest if we could change that behavior,
particularly, make omitting --test-name not so critical?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple