Re^8: Shared variables between threads

It hangs because the catpure thread is at the loop function, my idea is to break that loop using breakloop over the same variable BUT from the main thread.
1- Yes, i've done some tests and looks that 0 is doing exactly the same as -1, but i've changed to -1 now.
2- The callback part works perfectly, i've just remove the contents for the test.
3- Nothing strange at the return codes of the subs.
The problem here is that I can't call breakloop to the same variable at the main thread that is looping at the capture thread and thats why it hangs at the loop function.
I've try it sharing, passing as a parameter to the thread (don't know why it makes a local copy too instead of using the same by reference), i've tried too the last 2 options but using references and found that althoug the references are being copied (as i expected) the content of the references changed too to the copied values inside the thread instead of pointinng to the original variable at the main thread.
I thought it will be easier.

Comment on Re^8: Shared variables between threads

Replies are listed 'Best First'.
Re^9: Shared variables between threads by BrowserUk (Patriarch) on Nov 05, 2007 at 12:51 UTC
Nothing strange at the return codes of the subs. That doesn't make much sense. At the very least, I would expect to see the output from `"$capobj breakloop\n";` [download] If that is not being output, then it suggests that breakloop() is never returning, which is a Pcap issue rather that anything to do with threads. The callback part works perfectly, i've just remove the contents for the test Since you creating $capobj in your main thread and using successfully with the capture thread, it suggests that the sharing is working fine. I've try it sharing, passing as a parameter to the thread (don't know why it makes a local copy too instead of using the same by reference), i've tried too the last 2 options but using references and found that althoug the references are being copied (as i expected) the content of the references changed too to the copied values inside the thread instead of pointinng to the original variable at the main thread. That's a red-herring. The addresses shown in the printout are the addresses of the references not the thing it points to. The way sharing works it to create a clone specific to each thread that acts as a proxy for the real data. The notation `package=TYPE(address)` means that this reference is located in memory at `adddress`, it points to a variable of type `TYPE`, and it is bless'd into `package`. So your output simply means that each of your two threads has it's own reference to the object: `THREAD 1: THREAD 2: pcap_tPtr=SCALAR(0x8ee08f8) pcap_tPtr=SCALAR(0x8f223b4) Ś Ś Ś Ś +-----------> A perl scalar that <<----------------------+ holds the address of the pcap struct: 0xxxxxxxxx Ś +---> Whatever that struct looks like` [download] I still suggest that you print the return codes of the calls, switch to using warn and put some trace in the callback. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply] [d/l] [select]
Re^10: Shared variables between threads by Saladino (Beadle) on Nov 05, 2007 at 13:49 UTC
Couldn't find a solution. Finally i managed to solve my problem using setnonblock on capobj with dispatch and controlling the capture with a shared variable. But that solves my specific problem. Too many time with this, I needed to go forward.	[reply]