[
https://issues.apache.org/jira/browse/XERCESC-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716851#comment-17716851
]
Ilguiz Latypov edited comment on XERCESC-2188 at 4/26/23 8:33 PM
[
https://issues.apache.org/jira/browse/XERCESC-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716908#comment-17716908
]
Ilguiz Latypov commented on XERCESC-2188:
-
Perhaps NVD and scan KBs rely on this ticket's
[
https://issues.apache.org/jira/browse/XERCESC-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716851#comment-17716851
]
Ilguiz Latypov commented on XERCESC-2188:
-
Since year 2019, the NIST record of this bug
[
https://issues.apache.org/jira/browse/SLING-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989033#comment-16989033
]
Ilguiz Latypov edited comment on SLING-8879 at 1/31/20 9:24 PM:
I also
[
https://issues.apache.org/jira/browse/SLING-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989033#comment-16989033
]
Ilguiz Latypov edited comment on SLING-8879 at 12/5/19 6:33 PM:
I also
[
https://issues.apache.org/jira/browse/SLING-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989033#comment-16989033
]
Ilguiz Latypov edited comment on SLING-8879 at 12/5/19 5:58 PM:
I also
[
https://issues.apache.org/jira/browse/SLING-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989033#comment-16989033
]
Ilguiz Latypov edited comment on SLING-8879 at 12/5/19 5:58 PM:
I also
[
https://issues.apache.org/jira/browse/SLING-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989033#comment-16989033
]
Ilguiz Latypov edited comment on SLING-8879 at 12/5/19 5:55 PM:
I also
[
https://issues.apache.org/jira/browse/SLING-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989033#comment-16989033
]
Ilguiz Latypov commented on SLING-8879:
---
I also see a suggestion to fool-proof more characters
[
https://issues.apache.org/jira/browse/SLING-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989011#comment-16989011
]
Ilguiz Latypov edited comment on SLING-8879 at 12/5/19 5:40 PM:
I see
[
https://issues.apache.org/jira/browse/SLING-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989011#comment-16989011
]
Ilguiz Latypov commented on SLING-8879:
---
I see SLING-6679 replaced JSONObject with Johnzon in year
[
https://issues.apache.org/jira/browse/SLING-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988929#comment-16988929
]
Ilguiz Latypov commented on SLING-8879:
---
https://github.com/apache/sling-org-apache-sling-xss/blob
Ilguiz Latypov created SLING-8879:
-
Summary: Make JSONObject#toString and XSSAPI#encodeForJSString
both safe and correct for pasting into a javascript string literal
Key: SLING-8879
URL: https://issues.apache.org
[
https://issues.apache.org/jira/browse/SLING-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988471#comment-16988471
]
Ilguiz Latypov commented on SLING-5946:
---
[~radu], [~rombert], [~vladb]
> XSSAPI#encodeForJSStr
[
https://issues.apache.org/jira/browse/SLING-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988288#comment-16988288
]
Ilguiz Latypov edited comment on SLING-5946 at 12/4/19 11:32 PM:
-
Please
[
https://issues.apache.org/jira/browse/SLING-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988288#comment-16988288
]
Ilguiz Latypov edited comment on SLING-5946 at 12/4/19 11:30 PM:
-
Please
[
https://issues.apache.org/jira/browse/SLING-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988288#comment-16988288
]
Ilguiz Latypov edited comment on SLING-5946 at 12/4/19 11:27 PM:
-
Please
[
https://issues.apache.org/jira/browse/SLING-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988288#comment-16988288
]
Ilguiz Latypov edited comment on SLING-5946 at 12/4/19 11:26 PM:
-
Please
[
https://issues.apache.org/jira/browse/SLING-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988288#comment-16988288
]
Ilguiz Latypov commented on SLING-5946:
---
Please reopen this due to an improper implementation
Sorry it failed even with the padding, so I don't know what is failing
in basez.
Package: basez
Version: 1.6-3
Severity: important
Tags: upstream
Dear Maintainer,
* Decoding a JWT signature showed that omitting the padding (as
required by one of the JWS RFC) causes a failure in base64url -d.
$ echo -n
I contacted the author and he pointed to the "-a" option that controls
the search behaviour. I found the "-A" option to follow my expectation
of a forward and backward search,
-a or --search-skip-screen
By default, forward searches start at the top of the displayed
Ilguiz Latypov created GROOVY-9019:
--
Summary: triple-single and triple-double quotes handle backslash
escapes equally
Key: GROOVY-9019
URL: https://issues.apache.org/jira/browse/GROOVY-9019
Project
[
https://issues.apache.org/jira/browse/GROOVY-9019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilguiz Latypov updated GROOVY-9019:
---
Description:
The documentation implies that triple-single quotes treat only escaping
[
https://issues.apache.org/jira/browse/GROOVY-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilguiz Latypov updated GROOVY-4777:
---
Attachment: GStringTest.java
> GString cannot be cast to java.lang.String while iterat
[
https://issues.apache.org/jira/browse/GROOVY-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilguiz Latypov updated GROOVY-4777:
---
Attachment: build.gradle
> GString cannot be cast to java.lang.String while iterat
[
https://issues.apache.org/jira/browse/GROOVY-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16577040#comment-16577040
]
Ilguiz Latypov commented on GROOVY-4777:
I doubt Groovy 1.7.6 could have an intentional
[
https://issues.apache.org/jira/browse/GROOVY-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16577008#comment-16577008
]
Ilguiz Latypov commented on GROOVY-4777:
GString does not (cannot) extend String. It implements
On Saturday, 11 February 2017 00:49:42 UTC-5, David Karr wrote:
>
> I'm seeing some odd behavior with "println" calls in shared library
> methods, and a perhaps related issue with printing a shared library object
> in a Jenkinsfile.
>
Nice to see an answer to this by Jon S a month later where
On Wed, Apr 04, 2018 at 11:25:30AM +0200, Corinna Vinschen wrote:
> I reshuffled lots of socket code to make room for a new AF_UNIX
> implementation. While at it, I screwed up in a few places, so
> socket code was broken for a bit. The OpenSSH testsuite helped
> a lot to find the bugs, btw :}
>
Hello,
The latest Cygwin 64-bit release with the snapshot cygwin1.dll copied on top of
it shows an "accept: Bad address error" in 3 reproducible cases:
(a) The sshd daemon on receiving a connection request.
(b) The XWin server on receiving a connection request from an X11 client such
as xterm.
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 4:10 PM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 4:06 PM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 3:53 PM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 3:50 PM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 3:44 PM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 3:29 PM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 3:27 PM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 3:25 PM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 3:25 PM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov edited comment on TEXT-42 at 10/29/17 9:56 AM:
--
I wonder
[
https://issues.apache.org/jira/browse/TEXT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223929#comment-16223929
]
Ilguiz Latypov commented on TEXT-42:
I wonder if the escapeEcmaScript()'s use cases can be scrutinized
[
https://issues.apache.org/jira/browse/DERBY-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15000568#comment-15000568
]
Ilguiz Latypov commented on DERBY-2136:
---
Should this be re-opened for the case of the shell script
Ilguiz Latypov created IO-476:
-
Summary: FileUtilsTestCase.testIsFileNewerOlder:987 New File -
Newer - Date
Key: IO-476
URL: https://issues.apache.org/jira/browse/IO-476
Project: Commons IO
[
https://issues.apache.org/jira/browse/IO-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilguiz Latypov updated IO-476:
--
Description:
The test FileUtilsTestCase.testIsFileNewerOlder:987 New File - Newer - Date
failed
Package: smbclient
Version: 2:3.6.13-1
Severity: minor
Dear Maintainer,
* What led up to the situation?
Ran smbclient -A /etc/credentials-USER -L HOST.example.net
* What exactly did you do (or not do) that was effective (or
ineffective)?
Ran the above command.
* What
Package: dosfstools
Version: 3.0.13-1
Followup-For: Bug #691093
Dear Maintainer,
Same here.
* What led up to the situation? Checking the filesystem of a micro SD card.
* What exactly did you do (or not do) that was effective (or
ineffective)? I ran sudo fsck /dev/sdc1 -a.
* What
Running dosfsck -r PARTITION works around the crash.
--
-
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other
On 27/06/12 07:57 PM, Ilguiz Latypov wrote:
I worked around the crash by choosing Open JDK 1.7 to run davmail
compiled by Open JDK 1.6.
sudo update-alternatives --config java
After reporting my work-around I followed advice of the davmail author
and disabled the use of system proxy settings
I worked around the crash by choosing Open JDK 1.7 to run davmail
compiled by Open JDK 1.6.
sudo update-alternatives --config java
I believe it is possible that davmail could compile with Open JDK 1.7
and that its build system prevents higher version numbers by mistake.
I believe changing the
On 27/06/12 07:57 PM, Ilguiz Latypov wrote:
I worked around the crash by choosing Open JDK 1.7 to run davmail
compiled by Open JDK 1.6.
sudo update-alternatives --config java
After reporting my work-around I followed advice of the davmail author
and disabled the use of system proxy settings
I worked around the crash by choosing Open JDK 1.7 to run davmail
compiled by Open JDK 1.6.
sudo update-alternatives --config java
I believe it is possible that davmail could compile with Open JDK 1.7
and that its build system prevents higher version numbers by mistake.
I believe changing the
C:\Users\USER\cygwin\bin\bash.exe
0 [main] bash 6784 C:\cygwin\bin\bash.exe: *** fatal error - add_item
(㽜尿㩃捜杹楷n, /, ...) failed, errno 1
Stack trace:
Frame Function Args
002888D8 6102F96B (002888D8, , , )
00288BC8 6102F96B (6119BD20,
This looks very strange, almost impossible. Did you still have Cygwin
processes running, services maybe, while you updated?
Indeed, I forgot to stop cygrunsrv and sshd. When I saw your question I
ran ProcessExplorer64, turned on the view of all processes but could not
find cygrunsrv, sshd
$ ( export PATH= ; /cygdrive/c/cygwin/bin/gcc-4.exe -v -E - /dev/null )
I figured that cc1 depends on /usr/bin. A user invoking cc1 directly could
figure the missing dependency. Invoking cc1 indirectly from /usr/bin/gcc-4
without /usr/bin in PATH will break cc1 against expectation of
I found that gcc-4 from a recent setup.exe could not start cc1 because the
latter could not find some shared object file.
I confirmed that by running cc1 alone with an empty PATH variable.
$ ( export PATH= ; /cygdrive/c/cygwin/bin/gcc-4.exe -v -E - /dev/null )
Using built-in specs.
Package: gnash
Version: 0.8.10
The --enable-avm2 option causes a warning in the configure script saying that
the script did not recognize the option. I found that configure.ac commented
out its handling by putting dnl at the beginning of each line. Removing the
dnl (delete to new line?)
Package: debian-installer
Version: i386 netinst as of October 5, 2011
Severity: important
Tags: d-i
Dear Maintainer,
* What led up to the situation?
I decided to install Debian on a new disk drive and preserve the Windows
installation on the original drive.
I downloaded the latest
Package: debian-installer
Version: i386 netinst as of October 5, 2011
Severity: important
Tags: d-i
Dear Maintainer,
* What led up to the situation?
I decided to install Debian on a new disk drive and preserve the Windows
installation on the original drive.
I downloaded the latest
Contrary to my earlier conclusion, the upgrade did not delete
older images. It appears a ramdisk generation change may have
included a bad module whose loading crashed the system later.
I could not boot other images because my Grub 2 configuration file
grub.cfg missed the corresponding initrd
Contrary to my earlier conclusion, the upgrade did not delete
older images. It appears a ramdisk generation change may have
included a bad module whose loading crashed the system later.
I could not boot other images because my Grub 2 configuration file
grub.cfg missed the corresponding initrd
Thanks for quashing my hasty conclusion about the timing of the kernel crash.
I now see that the crash occurred after the ramdisk stage succeeded. Probably,
this may have something to do with memory paging to disk. I could boot to the
shell, disable swapping, launch udev, resolvconf,
Thanks for quashing my hasty conclusion about the timing of the kernel crash.
I now see that the crash occurred after the ramdisk stage succeeded. Probably,
this may have something to do with memory paging to disk. I could boot to the
shell, disable swapping, launch udev, resolvconf,
Package: linux-2.6
Version: 2.6.32-30
Severity: critical
Justification: breaks the whole system
Both normal and safe boot modes panicked when running the ram disk
image. Worse, the upgrade DELETED the earlier kernel image and ram disk
image. I managed to boot by editing the safe mode command
Package: linux-2.6
Version: 2.6.38-3
Severity: critical
Justification: breaks the whole system
Booting panics when bringing interfaces up, including a Wi-Fi adm8211
from drivers/net/wireless. The stack trace mentions
ieee80211_rx_handlers in mac80211, net_receive_skb, do_page_fault,
Package: linux-2.6
Version: 2.6.32-30
Severity: critical
Justification: breaks the whole system
Both normal and safe boot modes panicked when running the ram disk
image. Worse, the upgrade DELETED the earlier kernel image and ram disk
image. I managed to boot by editing the safe mode command
Package: linux-2.6
Version: 2.6.38-3
Severity: critical
Justification: breaks the whole system
Booting panics when bringing interfaces up, including a Wi-Fi adm8211
from drivers/net/wireless. The stack trace mentions
ieee80211_rx_handlers in mac80211, net_receive_skb, do_page_fault,
Package: linux-2.6
Version: 2.6.32-30
Severity: critical
Justification: breaks the whole system
Both normal and safe boot modes panicked when running the ram disk
image. Worse, the upgrade DELETED the earlier kernel image and ram disk
image. I managed to boot by editing the safe mode command
Package: linux-2.6
Version: 2.6.38-3
Severity: critical
Justification: breaks the whole system
Booting panics when bringing interfaces up, including a Wi-Fi adm8211
from drivers/net/wireless. The stack trace mentions
ieee80211_rx_handlers in mac80211, net_receive_skb, do_page_fault,
Follow-up Comment #4, bug #28983 (project make):
The GNU make manual both supports and defeats Matt's statement.
A phony target is one that is not really the name of a file.
[..]
Once this is done, `make clean' will run the commands regardless of
whether there is a file named clean.
It
Follow-up Comment #6, bug #28983 (project make):
The following tests show that .PHONY's pre-requisites are normally rebuilt
regardless of existence of a file with the same name.
This works,
$ cat test-force.mak
default: file.o
.PHONY: file.o
file.o:
echo Building $...@... $@
$
Follow-up Comment #7, bug #28983 (project make):
The following tests show that .PHONY's pre-requisites are normally rebuilt
regardless of existence of a file with the same name.
This works,
$ cat test-force.mak
default: file.o
.PHONY: file.o
file.o:
echo Building $...@... $@
$
Package: update-manager-gnome
Version: 0.200.3-1
Severity: grave
File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ui.py
Tags: sid
Justification: renders package unusable
Update Manager crashed on its start.
*** /tmp/update-manager-bugm_Su6p
The information below has been automatically
Package: update-manager-gnome
Version: 0.200.3-1
Severity: grave
File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ui.py
Tags: sid
Justification: renders package unusable
Update Manager crashed on its start.
*** /tmp/update-manager-bugm_Su6p
The information below has been automatically
Thanks for the proposed patch. Anyhow, the right solution is to simply
ignore that extra value in the module that parses them [..]
conffiles = conffiles + [tuple(line.split()[:2])]
Nice. Thanks, Sandro.
--
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Package: python2.5-minimal
Version: 2.5.5-5
Severity: normal
I wonder if this can be fixed with the following change,
--- /usr/lib/python2.5/py_compile.py.orig 2010-04-21 06:00:38.0 -0400
+++ /usr/lib/python2.5/py_compile.py2010-04-21 05:46:52.0 -0400
@@ -153,6 +153,7 @@
Package: reportbug
Version: 4.12
Severity: normal
This appears to be a result of an extra word obsolete in addition to
filename and md5sum fields of a conffiles record. Reproduced when
reporting on python2.5-minimal.
=
Package: reportbug
Version: 4.12
Severity: normal
This appears to be a result of an extra word obsolete in addition to
filename and md5sum fields of a conffiles record. Reproduced when
reporting on python2.5-minimal.
=
Package: python2.5-minimal
Version: 2.5.5-5
Severity: normal
I wonder if this can be fixed with the following change,
--- /usr/lib/python2.5/py_compile.py.orig 2010-04-21 06:00:38.0 -0400
+++ /usr/lib/python2.5/py_compile.py2010-04-21 05:46:52.0 -0400
@@ -153,6 +153,7 @@
[
https://issues.apache.org/jira/browse/NUTCH-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859116#action_12859116
]
Ilguiz Latypov commented on NUTCH-427:
--
I hesitate adding the .zip file because
[
https://issues.apache.org/jira/browse/NUTCH-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilguiz Latypov updated NUTCH-427:
-
Attachment: (was: protocol-smb.zip)
protocol-smb: plugin protocol implementing the CIFS/SMB
[
https://issues.apache.org/jira/browse/NUTCH-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilguiz Latypov updated NUTCH-427:
-
Attachment: protocol-smb-dist.zip
Applied my diff to simplify importing into the Subversion tree
Follow-up Comment #9, bug #27983 (project findutils):
app | d2u | xargs
That is a one-size-fits-all solution - it works no matter the windows app
on the left and no matter the consumer on the right.
This means that the developers should be aware about the newline subtlety
that may be exposed
Follow-up Comment #10, bug #27983 (project findutils):
Cygwin cannot be POSIX-compliant
I meant Cygwin applications cannot rely on POSIX compliance of the system
features they consume.
___
Reply to this item at:
Follow-up Comment #5, bug #27983 (project findutils):
Then you use cat, which preserves binary mode, through a pipe which also
preserves binary mode.
But this is a valid sequence of commands, and Cygwin should preserve the
behavior of this sequence regardless of the input's low-level line
Follow-up Comment #3, bug #27983 (project findutils):
Is the expectation in the test script valid?
mount -t $(cygpath -w ${dir}) /textmode
[..]
tf1=/textmode/file1.txt
tf2=/textmode/file2.txt
[..]
echo foo ${tf1}
echo bar ${tf1}
[..]
cat ${tf1} | xargs -i echo -n =={}== ${tf2}
[..]
Anybody else?
Same here. I am even ruling out any interference with programs I launch from
the terminal. Last time I noticed, even running a couple of Perforce commands
made it impossible to shut the terminal on exit.
Also, during long ant builds I notice that the build would pause. My
The current documentation on Cygwin text mode heuristic relies on a bug in a
GNU tool. That bug was fixed.
http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/doc/textbinary.sgml?rev=1.11content-type=text/x-cvsweb-markupcvsroot=src
The script/para
screen
![CDATA[
#!/bin/sh
# Remove \r
I checked this situation in cmd.exe, and it is not capable of using
paths relativ to %Path%. In other words, if %Path% contains a path
c:\foo and you have two files C:\foo\baz.exe and C:\foo\bar\baz.exe,
then calling baz works, but calling bar\baz fails.
I only meant resolving relative
I check out a module of my repository (located on a remote machine)
and a handful of files do not get downloaded due to the no such file
error described below.
Try cvs up -d or delete everything and cvs co anew. I could not
check out the new directory with a simple cvs up myself.
--
--
This has been changed deliberately, otherwise
the execp functions have a potential security problem. If you omit the
NNF flag, the function returns the original path unchanged, instead of
NULL.
I see that my conjecture about the root cause of the observed inconsistency was
incorrect. But
On Mar 10 10:25, Corinna Vinschen wrote:
execv (argv[1], args);
bash$ gcc -o exec exec.c
bash$ ./exec /bin/echo
abc
bash$ ./exec C:\\cygwin\\bin\\echo
abc
Thanks for trying a test case. I am attaching a new test case that
shows that the trouble was with execvp(), not exec(). Only
constness of pointers
Err, I meant constness of rvalue. But this is not related.
--
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
Package: wodim
Version: 9:1.1.10-1
Severity: normal
Perhaps, my issue is related. I am getting intermittent no error
errors displaying status: 0x02 (CHECK_CONDITION).
I suspect that an extra resid: 28 in addition to a regular resid: 8 is an
early indicator of the trouble.
As a result, the
Package: wodim
Version: 9:1.1.10-1
Severity: normal
Forgot to add the dmesg output that might be related. Also, I just realized
that the sense code error message was logical block address out of range.
[ 4469.846681] hdb: command error: status=0x51 { DriveReady SeekComplete Error }
[
The bottom line is that if you want to use MS-DOS
paths, then use a MinGW or DJGPP version of make.exe. make.exe is not
going to be patched.
The patch was to cygwin1.dll, but I am not insisting.
--
--
Problem reports: http://cygwin.com/problems.html
FAQ:
In particular, mkimport ran objcopy against ftruncate.o in a
temporary directory, but I believe the expected filename argument was
supposed to be t-ftruncate.o. This is only my conjecture as I do not
know the purpose and the intention of the implementation with these
scripts.
While it is very
The attached patch allows executing a path in backslash notation. This can be
tested in the Cygwin builds of GNU make with the DOS compatibility
compile-time option of GNU make enabled, such as those from Cygwin make
packages 3.79 and 3.80.
$ cat dos-compat.mak
default:
..\echo.exe
It isn't clear from your email what you are attempting to accomplish but
it sounds like you are trying to build cygwin using a non-cygwin-aware
version of perl. If that is the case, then this is not of interest to
the project or this mailing list.
The build breaks were exposed by using the
(a) I found that winsup/cygwin/mkimport specified non-existent file names as
arguments to objcopy invocations. I am not sure why this did not cause build
breaks earlier.
(b) It appears perl 5.6 and, possibly, perl 5.10 do not implement the list
form of pipe in calls to open(),
open
1 - 100 of 168 matches
Mail list logo
