Hi all, i made the clock functions (in m_sched.c) thread-safe so that all multi-threaded programs can use them (e.g. clock_delay(0) to call a worker function) to communicate with the main system thread. Please check if my implementation is waterproof.
And Adam, i stumbled across a compilation problem (Windows only) in s_path.c, function open_via_helppath, where the definition NTOPENFLAG needs a "bin" flag which is not defined. I fixed that, setting "bin" to 0, assuming that the files opened are always pd patches. Could you please review that?
best greetings, Thomas
Thomas Grill said this at Mon, 31 Mar 2003 00:04:39 +0200:
And Adam, i stumbled across a compilation problem (Windows only) in s_path.c, function open_via_helppath, where the definition NTOPENFLAG needs a "bin" flag which is not defined. I fixed that, setting "bin" to 0, assuming that the files opened are always pd patches. Could you please review that?
Hello, Thomas,
I updated my local sources, and re-built. Your NTOPENFLAG doesn't appear to interfere with anything else that I can see (as expected), in compilation or testing. Thanks for noting it to the list. Sorry for my naivety about MSWin programming. (Not sorry for the naivety, but sorry for the side effects. :)
(Ooh, looks like vasp has been updated... I'll try to build again, then...)
Cheers, adam
Thomas Grill said this at Tue, 1 Apr 2003 02:34:59 +0200:
(Ooh, looks like vasp has been updated... I'll try to build again,
then...)
...and up went the download counter. The vasp updates are currently cvs only, i'm sorry....... (anyway, it should be much more stable now)
(I got it from CVS). Well, it builds. However, my copy of pd crashes whenever I try to *load* VASP. I see the following (extract) of a crash log:
Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 0: #0 0x90006ac8 in clock_sleep_trap #1 0x900067cc in nanosleep #2 0x9003e328 in usleep #3 0x0027a29c in flext::Sleep(double) #4 0x0027980c in flext::StartHelper() #5 0x00277498 in flext_obj::lib_init(char const*, void (*)(), bool) #6 0x0004e910 in sys_load_lib #7 0x00042a54 in new_anything #8 0x00042fe0 in pd_typedmess .....
I'll look into it as well, but does this ring any bells? Do I need to run it with the new m_sched you just committed?
Cheers, adam
Hi Adam,
(I got it from CVS). Well, it builds. However, my copy of pd crashes whenever I try to *load* VASP. I see the following (extract) of a crash log:
Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 0: #0 0x90006ac8 in clock_sleep_trap #1 0x900067cc in nanosleep #2 0x9003e328 in usleep #3 0x0027a29c in flext::Sleep(double) #4 0x0027980c in flext::StartHelper() #5 0x00277498 in flext_obj::lib_init(char const*, void (*)(), bool) #6 0x0004e910 in sys_load_lib #7 0x00042a54 in new_anything #8 0x00042fe0 in pd_typedmess .....
I'll look into it as well, but does this ring any bells? Do I need to run it with the new m_sched you just committed?
I'm not sure... this should not be necessary if only one threaded external is running. However, it seems that your excerpt doesn't show the thread that crashed... could you send me the whole crash log?
best greetings, Thomas