Search:

most definitely helpful. it actually coming full circle in that I knew to use the standard int types - but didn't realize their purpose was for exactly the problem I thought I had and was trying to...

got it. makes sense. and actually as I was reading more in the stdint header and the stdint wiki article - stdint is around to solve this exact problem - ensuring the correct width of a type through...

thanks everyone for the help. if anyone has any other suggestions or criticisms please let me know. it's definitely appreciated.

cool thanks. makes sense. and thanks for the reminder about endianness. I did use big endian.

and I think tabstop might have answered my question earlier - that if a machine has uint8,uint16, etc, it's guaranteed to be that size.

I guess maybe I should change my question slightly. or maybe i'm not understanding you correctly. I'm not concerned about sending it. what I'm concerned about is that when the source code is built on...

I see what you mean for network programming - it's up to both programmers to ensure that for example; if some piece of data in the stream is 32 bits the other programming should make sure to read 32...

Thanks. yeah that's what I'm always thinking in the back of my mind. But I can never find any concrete references on dealing with these types of situations.

Thanks - that's kind of what I was thinking but I always run into little snippets that say no machine is guaranteed to have types of the "standard" size - of course I run into that in books from the...

hey renzokuken01,

Sorry if I came off like I was trying to impress. There's always something in C that i'm trying to understand better. In this case I don't quite understand how to make sure that...

Hey All!

I've been working on really really nice c serializer that's just about done. I slightly re-invented the wheel because I didn't like my options, and they didn't have some features I...

I know you're not on a mac, and this might not be 100% useful for you. But another person pointed out what I believe is the problem.

On mac, an unbalanced pthread_rwlock_unlock is actually...

no go.. darn. would it have anything to do with the number of cores on the machine?

I tried your code on my mac, two cores - where it deadlocks. And tried it on a linux box with 3 cores, where it...

yep, I took your compile comment verbatim.

gcc gg.c -Wall -pedantic -std=c99 -pthread -D_XOPEN_SOURCE=700

oh yeah saw that note about readers being recursive. for some reason the combination of recursive read locks with write locks is the problem. If I comment out the stuff that initiates the writers...

ps. are you on a mac? and this is seriously not to throw flames into the fire at all. your code is right on, but on a mac initiating read locks from a thread that already has a read lock creates...

ha. yeah I didn't care about memory. It was a sandboxed example like I mentioned. I think we were onto the same thing. Like I said it was a sandbox example that i've been messing with. not like I was...

what I meant was that what you were pointing out to be an issue wasn't the problem. It was indeed the the write lock.

Here's another version that's fixed. I've run this over and over and have not...

that's definitely not the issue. I've made an even simpler example that still creates the deadlock.





//gcc -Wall rdwr4.c

#include <stdlib.h>
#include <stdbool.h>

Hey All, got a quick question about pthread read/write lock with regards to their recursive abilities.

I'm working on a test to demonstrate how you can lock structures with read/write locks....

nvmnd, I think everything was working as expected, I updated the print statements to help be more identifiable and everything is working as I thought it would...




#include <stdlib.h>...

I'm just messing around with mutex and rwlock in pthreads. I wrote a quick little sample. but what's interesting is that the rwlock behaves much differently.



#include <stdlib.h>
#include...

doh! thanks!

I'm screwing around with the macro offsetof. Just for the sake of screwing around with it. I can't figure out one piece. Here's my code:




#include <stdlib.h>
#include <stdio.h>
#include...

Thanks