Since this update, every time I run setup, upx-debuginfo always wants to be
installed. And, it's in category Misc, not Debug.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe inf
Andrew Schulman wrote:
Since this update, every time I run setup, upx-debuginfo always wants to be
installed. And, it's in category Misc, not Debug.
Confirmed here too!
I have no *-debuginfo packages installed nor upx!!
A setup.ini/packaging bug, I think...
Ciao,
Angelo.
--
Problem repor
On Mar 15 11:13, Angelo Graziosi wrote:
> Andrew Schulman wrote:
>
> >Since this update, every time I run setup, upx-debuginfo always wants to be
> >installed. And, it's in category Misc, not Debug.
>
> Confirmed here too!
>
> I have no *-debuginfo packages installed nor upx!!
>
> A setup.ini/
Hi all,
I found a problem (or unintended effect? or WJM feature?) with the new
change that makes gdb work with cygwin signals:
1. start sqlite3
2. ^z
3. jobs -p
4. in separate terminal window, gdb -p $PID
5. c
6. in first window, fg
7. in gdb window, gdb should have caught SIGCONT, c
8. gdb an
> The upx-debuginfo/setup.hint file was missing.
I think this is an easy mistake for us package maintainers to make. It's not
obvious at first that we need to create separate setup.hint files for our
debuginfo packages.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Andrew Schulman writes:
> Since this update, every time I run setup, upx-debuginfo always wants to be
> installed. And, it's in category Misc, not Debug.
Sorry for that, but that's the setup.hint that should have been
installed with it:
--8<---cut here---start
Andrew Schulman writes:
> I think this is an easy mistake for us package maintainers to make. It's not
> obvious at first that we need to create separate setup.hint files for our
> debuginfo packages.
I've checked again, the setup.hint file was included in my upload
request. This file and the de
On 3/15/2013 12:07 AM, Edward Peschko wrote:
All,
We are having difficulties running various windows utilities through
bash. Through a regular windows cmd, one can run commands like
diskshadow without issue, but with bash, we are having problems with
COM calls not working. We have posted an exam
On Mon, Mar 11, 2013 at 04:45:54PM -0400, Christopher Faylor wrote:
>On Tue, Mar 12, 2013 at 04:35:41AM +0900, jojelino wrote:
>>On 2013-03-11 PM 11:36, Christopher Faylor wrote:
>>> A "proper bug report" would at least include what you were actually doing
>>> to trigger this problem.
>>>
>>I was t
On 2013-03-16 AM 4:41, Christopher Faylor wrote:
On Mon, Mar 11, 2013 at 04:45:54PM -0400, Christopher Faylor wrote:
Actually, if you are running this on a DOS console, and you hit CTRL-C,
you will have at least one other thread executing.
Were you running this under mintty (aka a pty) or in a W
On 2013-03-16 AM 10:46, jojelino wrote:
On 2013-03-16 AM 4:41, Christopher Faylor wrote:
On Mon, Mar 11, 2013 at 04:45:54PM -0400, Christopher Faylor wrote:
Actually, if you are running this on a DOS console, and you hit CTRL-C,
you will have at least one other thread executing.
Were you runnin
11 matches
Mail list logo
