Re: Opening .n extensions
On 8/08/2010 7:23 p.m., Luetta wrote: [..] When my phone said the files were too large and was unable to open the files I downloaded them to my computer to open. Windows said it needed to go to the internet to obtain the program to open the file. I went onto the web and no programs, [save expensive file extension repair] were to be found. When I looked up the extension, every listing had the '.n' extension as yours. I have attached one of the files so you can see it. It has been checked for viruses. I apologize again for my ignorance. I did not know who or where else to ask. Thank you in advance for your Job like patience and understanding. That file does not contain an image, it is only 168 characters long which is far too small to have a useful photo in it. It seems to contain a pointer to a website where you can download the image from, but I don't know the format of the .n file so I'm unsure of the correct link. It will probably be a format specific to that particular cell provider and understood only by their phone software. It looks like the image is supposed to be visible at: http://mmsc.gci.csky.us:6672/m1?4q4rdk4Z_/w4~u9Z4~~~4kc3KHRukT But the server just returns a file not found error. Either I didn't figure out the link format correctly, or the image has now expired from the server. Cheers, Nicholas Sherlock -- 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: Opening .n extensions
Eliot Moss moss at cs.umass.edu writes: On 8/8/2010 4:54 AM, Nicholas Sherlock wrote: On 8/08/2010 7:23 p.m., Luetta wrote: The 168 byte length strongly suggests that it is a 160 byte SMS (text) message with a few extra bytes added by the phone for its own purposes. And the contents suggest that as well, though why they are not more readable lies beyond my knowledge ... I think you're right, it looks like a standardised MMS notification (that would be sent as a text message to tell the phone where to get an image). I found a spec here: http://www.activexperts.com/xmstoolkit/sms/mmsnotification/ That spec says that the URL was correct as I decoded. This message had a relative expiry time that meant it expired 72 hours after being sent, I guess it has expired now. Cheers, Nicholas Sherlock -- 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: Setup.exe don't remember previos settings
On 6/05/2010 5:57 p.m., DEWI - N. Zacharias wrote: Every time I run setup.exe to update the installation I have to fill in the Root Directory ,the Local Package Directory and the Download Site. Because this is annoying and my colleagues which only using Cygwin are irritated by this I want to know if and how this behavior could be changed. That's not how it's supposed to work. On my computer it correctly remembers the root directory, the local package directory, and the download site. I am using the same version of Setup as you. Cheers, Nicholas Sherlock -- 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: Signal support under Cygwin
On 28/04/2010 4:25 p.m., Nicholas Sherlock wrote: Is this supposed to work? Nobody knows if Cygwin signals work? Could anybody reproduce the crash from my example code at least on their machines? Cheers, Nicholas Sherlock -- 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: Signal support under Cygwin
On 6/05/2010 2:23 a.m., Christopher Faylor wrote: On Thu, May 06, 2010 at 02:20:54AM +1200, Nicholas Sherlock wrote: On 28/04/2010 4:25 p.m., Nicholas Sherlock wrote: Is this supposed to work? Nobody knows if Cygwin signals work? Could anybody reproduce the crash from my example code at least on their machines? Investigating this is on my todo list. cgf Okay, thanks :) Cheers, Nicholas Sherlock -- 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
Signal support under Cygwin
/c/Windows/syswow64/KernelBase.dll #3 0x01dc in ?? () #4 0x in ?? () Thread 2 (thread .0x150c): #0 0x77bef8a5 in ntdll!RtlUpdateClonedSRWLock () from /cygdrive/c/Windows/system32/ntdll.dll #1 0x77bef8a5 in ntdll!RtlUpdateClonedSRWLock () from /cygdrive/c/Windows/system32/ntdll.dll #2 0x7748d0c5 in ReadFile () from /cygdrive/c/Windows/syswow64/KernelBase.dll #3 0x0120 in ?? () #4 0x in ?? () Thread 1 (thread .0xa8): #0 0x77bef871 in ntdll!RtlUpdateClonedSRWLock () from /cygdrive/c/Windows/system32/ntdll.dll #1 0x77bef871 in ntdll!RtlUpdateClonedSRWLock () from /cygdrive/c/Windows/system32/ntdll.dll #2 0x77490816 in WaitForSingleObjectEx () from /cygdrive/c/Windows/syswow64/KernelBase.dll #3 0x01cc in ?? () #4 0x in ?? () #0 0x1b4bdb2c in ?? () Is this supposed to work? Cheers, Nicholas Sherlock -- 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: how was debate on _GNU_SOURCE resolved? can't find pthread_getattr_np
On 28/03/2010 4:23 a.m., mike marchywka wrote: I'm now getting this error and don't seem to be able to find the getattr_np thing by grepping through includes, .../JavaScriptCore/runtime/Collector.cpp:683: error: `pthread_getattr_np' was not declared in this scope _np stand for non-portable. You shouldn't expect to find these APIs anywhere except for the exact system the code was written for. Cheers, Nicholas Sherlock -- 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: rm -fr dir causes BSOD
On 3/01/2010 11:08 a.m., Glenn Geers wrote: Hi, I've had a BSOD when doing an rm -fr dir on two different boxes running 1.7.1 under XP (sp3, fully patched). The crash is in ntfs.sys. Any ideas welcome. Bluescreens can't be blamed on Cygwin. Do the two boxes have similar hardware? Try updating your buggy IDE/SATA drivers. Cheers, Nicholas Sherlock -- 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: Slow GCC under 64-bit?
On 11/12/2009 10:59 a.m., Pedro DeKeratry wrote: I experience very slow GCC compilation times on win7 64bit computer as compared to a 3 yr old computer running winXP. The win7 machine has has a much newer/faster CPU and 2x the memory as the XP machine. The slowness exists on Cygwin versions 1.5.x and 1.7. I haven't figured out what the cause is much less a fix. If your new machine is multi-core you might see some benefit if you use the parallel make option with your makefiles - this will run multiple compile steps at the same time, achieving speedup on multi-core systems. On GNU make, for example, you can run 4 jobs at once with: make -j 4 Cheers, Nicholas Sherlock -- 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: R: Segfault with call to pthread_mutexattr_init under GDB
Marco Atzeri wrote: Da: Nicholas Sherlock This GDB was configured as i686-pc-mingw32... Have you tried the cygwin gbd ? $ gcc-4 -o prova prova.c $ gdb prova.exe GNU gdb 6.8.0.20080328-cvs (cygwin-special) Copyright (C) 2008 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 i686-pc-cygwin... (gdb) run Starting program: /tmp/prova/prova.exe Program exited normally. Whoops! I thought that I *was* using Cygwin's GDB, but it turns out that I forgot to reinstall it last time I refreshed my Cygwin installation. I've been using MinGW's GDB without ever realizing it. I've now installed Cygwin's GDB, where it works perfectly. Thanks! Nicholas Sherlock -- 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: cygwin bash and DOS cmd extremely sluggish.
Frank Kim wrote: I then noticed that the DOS cmd window is also very sluggish. How could Cygwin be to blame for the DOS cmd window being sluggish? Cheers, Nicholas Sherlock -- 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: -mnocygwin alternative
Vincent R. wrote: Back in old times it was possible to compile with no cygwin dependencies using something like -mno-cygwin. I hear that a proper cross-compiler is coming to replace -mno-cygwin. Will it be possible to compile again with mingw-4.4 from cygwin console ? You can just install MinGW separately and add the MinGW folders to your path. That's what I do in order to use MinGW's GCC with the Cygwin toolset.. :). Cheers, Nicholas Sherlock -- 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: simple multithread program fails on Cygwin, succeeds on Linux
Bruno Haible wrote: Hi, The attached test program for pthread_once uses the following basic POSIX threads functions: pthread_create pthread_join pthread_mutex_init pthread_mutex_lock pthread_mutex_unlock pthread_once pthread_rwlock_init pthread_rwlock_rdlock pthread_rwlock_unlock pthread_rwlock_wrlock In Cygwin 1.5 there was a bug that meant that you could not lock a rwlock recursively for read (it would just deadlock on the second acquire). I didn't study the code for very long, but this might be the problem you're encountering. In any case, Cygwin 1.7 fixes at least one problem with rwlocks so it's a good upgrade choice. Cheers, Nicholas Sherlock -- 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
Using rand_r
Hey everyone, I'm trying to use the function rand_r with gcc-4 in Cygwin 1.7, all my packages are up to date. It's supposed to be defined in stdlib.h, and I can see it there. But if I compile a program which uses it, I get: warning: implicit declaration of function 'rand_r'. The reason seems to be the check for #ifndef __STRICT_ANSI__ in stdlib.h. Even though I'm compiling with -std=c99, __STRICT_ANSI__ still gets declared, so the definition of rand_r is unavailable. This seems to be the same problem stated here: http://sourceware.org/ml/newlib/2007/msg00783.html Is this a bug or is rand_r supposed to be unavailable with C99? Cheers, Nicholas Sherlock -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Using rand_r
David Billinghurst wrote: Nicholas Sherlock wrote: Hey everyone, I'm trying to use the function rand_r with gcc-4 in Cygwin 1.7, all my packages are up to date. It's supposed to be defined in stdlib.h, and I can see it there. But if I compile a program which uses it, I get: warning: implicit declaration of function 'rand_r'. The reason seems to be the check for #ifndef __STRICT_ANSI__ in stdlib.h. Even though I'm compiling with -std=c99, __STRICT_ANSI__ still gets declared, so the definition of rand_r is unavailable. This seems to be the same problem stated here: Try -std=gnu99. It doesn't define __STRICT_ANSI__ This doesn't answer your question, unfortunately. Thanks, that does solve my immediate problem. But I'm really hoping to compile as vanilla C99 as I can manage, since I'll also be using my code with non-GNU compilers. Cheers, Nicholas Sherlock -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Cygwin PThreads bug?
Hey everyone,
I'm writing a very thread-intensive application using Cygwin and
Cygwin's PThreads implementation, and I'm running into a few problems.
As far as I can tell from the spec:
http://www.opengroup.org/onlinepubs/95399/functions/pthread_rwlock_rdlock.html
This C program:
#include stdio.h
#include pthread.h
#include assert.h
#include errno.h
int main() {
pthread_rwlock_t rw_lock;
pthread_rwlock_init(rw_lock,NULL);
//Lock it once for read...
assert(pthread_rwlock_rdlock(rw_lock)==0);
//Lock it again for read...
int err=pthread_rwlock_rdlock(rw_lock);
printf(Err %d\n, err);
assert (err==EAGAIN || err==0);
if (err!=EAGAIN)
pthread_rwlock_unlock(rw_lock);
pthread_rwlock_unlock(rw_lock);
pthread_rwlock_destroy(rw_lock);
return 0;
}
Should run correctly. That is, the second call to pthread_rwlock_rdlock
should either succeed (returning zero), having acquired the read lock a
second time, or it should fail and return EAGAIN, if the number of
simultaneous allowed read locks has been exceeded. It should not fail
and return EDEADLK (45), which it is currently doing. Am I reading the
spec wrong or is Cygwin non-conforming?
Cheers,
Nicholas Sherlock
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: R: Cygwin PThreads bug?
Marco Atzeri wrote: on $ uname -a CYGWIN_NT-5.1 ITQMOZCAS2NB007 1.7.0(0.200/5/3) 2009-02-20 17:20 i686 Cygwin compiled with gcc-4 $ ./pthread.exe Err 0 That might be making the difference, my uname -a output is: CYGWIN_NT-6.0-WOW64 nick 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin (Vista 64 bit) Can anyone else verify the code as working/not working on their system, along with system details? Expected output is Err 0. Cheers, Nicholas Sherlock -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: R: Cygwin PThreads bug?
Dave Korn wrote: And with gcc3 as well; and neither compiler can make it work on 1.5. So it's a bug that was fixed sometime after 1.5 and before 1.7. Thanks, I'll see if I can work out how to upgrade. Cheers, Nicholas Sherlock -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
