Thanks. This bug seems to be related since in my case there were also some
options that were present more than once. I got around the problem by tweaking
the configuration parameters.
> On 27/08/2010 09:31, Csaba Raduly wrote:
>
> > How odd. It seems to crash only with that exact number of para
Hello again,
I am sorry to bother you again with this, but dbaltex still doesn't work:
peter [~] dhajage2 $ dblatex essai.xml
/usr/lib/python2.6/site-packages/dbtexmf/dblatex/grubber/util.py:8: DeprecationW
arning: the md5 module is deprecated; use hashlib instead
import md5
Build the book set
On Fri, Aug 27 2010, Andy Koppe wrote:
> > So I select "4.3.4-3", and then "next". Then setup.exe crashes with this
> > error:
> > An unhandled win32 exception occurred in setup.exe [1672].
>
> I wasn't able to reproduce this. Were you using the then-latest
> version 2.712 of setup.exe? You could
Hello,
For the last couple of weeks I'm trying to identify the cause for cygwin
slowdown on x64 machines which was reported by David Morgan about 6
months ago.
I wrote a little bash script which prints the result of 'date -s' to a
file in a loop and then counts the number of times the same s
On Aug 29 14:39, Jon TURNEY wrote:
> On 08/08/2010 12:04, Andy Koppe wrote:
> >On 7 August 2010 23:07, Jon TURNEY wrote:
> >>Hmmm, looking again at the implementation of select(), I don't immediately
> >>see that when waiting on /dev/windows, it checks that the message queue has
> >>old messages on
On 30/08/2010 12:23, Corinna Vinschen wrote:
On Aug 29 14:39, Jon TURNEY wrote:
On 08/08/2010 12:04, Andy Koppe wrote:
On 7 August 2010 23:07, Jon TURNEY wrote:
Hmmm, looking again at the implementation of select(), I don't immediately
see that when waiting on /dev/windows, it checks that the
On 27 Aug 2010 19:33:36 +0100, Andy Koppe wrote:
> It will be synced with the POSIX working directory again, except when
> the path is too long or it's a "virtual" directory such as /proc.
Thank you for summarizing the thread. I tried
using the snapshot cygwin1-20100829.dll.bz2 and confirm
On 8/30/2010 7:16 AM, Sagi Ben-Akiva wrote:
For the last couple of weeks I'm trying to identify the cause for
cygwin slowdown on x64 machines which was reported by David Morgan
about 6 months ago.
You're my new hero. :)
I then applied the changes one by one and built cygwin1.dll for each
chan
Hi,
In looking at slowdown problem on x64 systems by Sagi Ben-Akiva, I found
some puzzling code that perhaps someone could enlighten me on. I must be
reading it wrong.
Here's the code path that I'm tracing using cygwin-src-20100829.tar.bz2:
- In dcrt0.cc, if dynamically_loaded is true, then
On Aug 30 10:26, Edward Lam wrote:
> Hi,
>
> In looking at slowdown problem on x64 systems by Sagi Ben-Akiva, I
> found some puzzling code that perhaps someone could enlighten me on.
> I must be reading it wrong.
>
> Here's the code path that I'm tracing using cygwin-src-20100829.tar.bz2:
>
> -
On Fri, Aug 27, 2010 at 2:59 PM, Jeremy Bopp wrote:
> On 8/27/2010 1:28 PM, Tim Visher wrote:
>> Hello Everyone,
>>
>> I recently switched from setting up environment variables within my
>> bash_profile/bashrc file and instead started setting them on the box
>> I'm on. This works great for PATH.
On 8/30/2010 10:45 AM, Corinna Vinschen wrote:
What am I missing?
cygthread::operator new(size_t)
Thanks!
-Edward
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
On 8/30/2010 7:16 AM, Sagi Ben-Akiva wrote:
2. a. Moving the call to wait_for_sigthread from dll_crt0_1 to _dll_crt0
which calls dll_crt0_1.
b. Deleting the call to WaitForSingleObject,
i.e. : "Don't worry about sync_startup"
I can confirm that the 2nd sub-change is the cause for the slowdown.
Hello all,
I've used the US-International keyboard layout for ages without issues.
Recently, I fired cygwin and noticed the "s" key was unresponsive.
Restarting Vista didn't help.
Changing to standard US layout before starting Cygwin didn't help.
Restarting Cygwin didn't help.
Scrapping the Cygwin
On 08/30/2010 10:52 AM, Eric Vautier wrote:
Hello all,
I've used the US-International keyboard layout for ages without issues.
Recently, I fired cygwin and noticed the "s" key was unresponsive.
Did you check whether ~/.inputrc has DOS line endings? If so, run d2u
on it, and see if that fixes
I checked the following below. The user's home directory has the proper
permissions (755), the .ssh directory is 700, and the files underneath the .ssh
directory is 600. By default StrictModes is set to no.
I still can't log in.
Any help will be greatly appreciated.
Thanks, and regards,
Mr. Au
On Mon, Aug 30, 2010 at 18:03, Auteria W. Winzer Jr. wrote:
> I checked the following below. The user's home directory has the proper
> permissions (755), the .ssh directory is 700, and the files underneath the
> .ssh
> directory is 600. By default StrictModes is set to no.
>
> I still can't log i
$ /bin/test -d && echo ok
ok
$ /bin/test -d '' && echo ok || echo must_be_error
must_be_error
POSIX require argument for -d, so behavior implementation
depend.
I can not check another 'test' implementation now.
For me get error is more convenient,
because this not break this code if $dir no
On 08/30/2010 11:27 AM, Oleksandr Gavenko wrote:
$ /bin/test -d && echo ok
ok
$ /bin/test -d '' && echo ok || echo must_be_error
must_be_error
Both of these results match POSIX. Remember, POSIX describes different
behaviors for one argument than for two arguments (for the one-argument
case
On 2010-08-30 20:31, Eric Blake wrote:
On 08/30/2010 11:27 AM, Oleksandr Gavenko wrote:
$ /bin/test -d && echo ok
ok
$ /bin/test -d '' && echo ok || echo must_be_error
must_be_error
Both of these results match POSIX. Remember, POSIX describes different
behaviors for one argument than for two a
On Mon, 30 Aug 2010, Corinna Vinschen wrote:
> I applied a patch to Cygwin which should make select on /dev/windows
> fully functional.
>
> The blessed solution is to replace the call to MsgWaitForMultipleObjects
> with a call to MsgWaitForMultipleObjectsEx with the MWMO_INPUTAVAILABLE
> flag set.
On Aug 30 12:49, Brian Ford wrote:
> On Mon, 30 Aug 2010, Corinna Vinschen wrote:
>
> > I applied a patch to Cygwin which should make select on /dev/windows
> > fully functional.
> >
> > The blessed solution is to replace the call to MsgWaitForMultipleObjects
> > with a call to MsgWaitForMultipleO
With grep 2.6.3-1, the following produces no output:
echo "Hello world" > hi
/bin/grep --include='*' 'world' *
With grep 2.5.4-2, the output is "Hello world".
Rob
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
The mutt mail reader shipping with Cygwin does not have SMTP enabled,
which I'd like to give a try. So I tried to build mutt, but encountered
problems.
The machine is 64-Bit PC running Win7/64/Pro, and Cygwin, of course.
I have both gcc 3 and 4 installed.
./configure --prefix=/usr/local/mutt -
On 30.08.2010 23:52, Michael Ludwig wrote:
The mutt mail reader shipping with Cygwin does not have SMTP enabled,
which I'd like to give a try. So I tried to build mutt, but encountered
problems.
[... long whine about non-working build snipped ...]
Did you use the ./prepare script first if buil
On Mon, Aug 30, 2010 at 01:22:48PM -0700, Robert Ross wrote:
>With grep 2.6.3-1, the following produces no output:
>
>echo "Hello world" > hi
>/bin/grep --include='*' 'world' *
>
>With grep 2.5.4-2, the output is "Hello world".
It does seem strange but, if it's a bug, it's also evident
on linux.
On 08/30/2010 05:08 PM, Christopher Faylor wrote:
On Mon, Aug 30, 2010 at 01:22:48PM -0700, Robert Ross wrote:
With grep 2.6.3-1, the following produces no output:
echo "Hello world"> hi
/bin/grep --include='*' 'world' *
With grep 2.5.4-2, the output is "Hello world".
It does seem strange b
Hi--
After updating to the latest version of xfig, I got the following error
message from xfig when I ran (countr.fig is a new figure I am building):
xfig countr.fig &
-error message
The app-defaults file (version: 3.2.4) is older
than this version of x
On Mon, Aug 30 2010, Peter Münster wrote:
> - it seems, that it crashes now, whatever I do...
Hello,
I've found "the solution": instead of using mirror rz.ruhr-uni-bochum.de I
switched to mirror tu-dresden.de. Now there is no more crash!
Cheers, Peter
--
Contact information: http://pmrb.free.
On 30 August 2010 13:43, Peter Münster wrote:
>> - it seems, that it crashes now, whatever I do...
>
> Hello,
>
> I've found "the solution": instead of using mirror rz.ruhr-uni-bochum.de I
> switched to mirror tu-dresden.de. Now there is no more crash!
Good.
The Bochum http mirror works fine for
Hi Sagi and all others,
Thanks Sagi for your investigation!
This is great news that it could finally be tracked down. I am also
suffering badly here from this
speed drop. I haven't yet tried myself to revert this change to see
whether it brings back speed
but will certainly try to do so soon.
31 matches
Mail list logo
