Re: [ANNOUNCEMENT] Updated: upx-3.09-1 / ucl-1.03-2
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 info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: upx-3.09-1 / ucl-1.03-2
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 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: [ANNOUNCEMENT] Updated: upx-3.09-1 / ucl-1.03-2
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/packaging bug, I think... The upx-debuginfo/setup.hint file was missing. I created one, that should fix it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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
^C and new signal-aware snapshot
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 and sqlite3 are now deadlocked (neither responds to ^c or ^z), you have to kill gdb to escape. I realize that messing with SIGCONT is a good way to confuse the app, but (a) I didn't want to (surprise!) and (b) is there a way to make the penalty for forgetting to ignore SIGCONT a little less draconian? Thanks, Ryan -- 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: [ANNOUNCEMENT] Updated: upx-3.09-1 / ucl-1.03-2
> 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: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: upx-3.09-1 / ucl-1.03-2
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->8--- category: Debug requires: cygwin-debuginfo external-source: upx sdesc: "Debug info for upx" ldesc: "This package contains files necessary for debugging the upx package with gdb." --8<---cut here---end--->8--- It seems that this file went missing during the upload. This has been happening before with a different debuginfo package, maybe there's something wrong with the upload script? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- 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: [ANNOUNCEMENT] Updated: upx-3.09-1 / ucl-1.03-2
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 debuginfo package is created by cygport, so you don't need to do anything extra besides adding it to the RFU (which I find reasonable). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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: problems with COM running native win32 applications through cygwin's bash
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 example below. I'd recommend reporting this to MS if you haven't already. While there may be something in Cygwin that needs tweaking for this, it would be best if MS could diagnose what is failing and why. That would make any Cygwin fix happen quicker. -- Larry _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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: deadlock with busy waiting on sigfe
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 trying to CTRL+C cygwin python process that is executing some >>operation and fell asleep for 60 seconds repeatedly. I'm pretty sure >>that the process was sleeping as i tried interrupt it. >> >>> Are you sure that there are only two threads executing here? It seems like >>> this is a symptom of another thread holding the lock. >>> >>It's unlikely the case because there was two thread running when >>livelock observed. > >How about if you humor me and do a "show threads" rather than just >asserting that it was unlikely? 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 Windows cmd shell? cgf -- 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: deadlock with busy waiting on sigfe
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 Windows cmd shell? cgf It was mintty i was running. and shell command was for i in `seq 1`;do ./hop.py list.txt ;done -- Regards. -- 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: deadlock with busy waiting on sigfe
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 running this under mintty (aka a pty) or in a Windows cmd shell? cgf It was mintty i was running. and shell command was for i in `seq 1`;do ./hop.py list.txt ;done And it would take at least another month to reproduce the busy wait. I forgot to print cygtls::stackptr[-1] at that time. which would be key to identify the cause of the problem. -- Regards. -- 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
