Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

euLog Collector crashes after start #29

Closed
RPeschke opened this issue Feb 27, 2014 · 4 comments
Closed

euLog Collector crashes after start #29

RPeschke opened this issue Feb 27, 2014 · 4 comments
Labels
Milestone

Comments

@RPeschke
Copy link
Contributor

I have tried running the newest version of EUDAQ on the NI crate. the GUI version of the log collector crashed immediately with the following error

###### listenaddress=tcp://192.168.2.2:44002
       logfile=../logs/2014-02-23.log
Error: Uncaught exception: Deserialize asked for 1363231829, only have 18
  From ..\..\..\main\lib\src\BufferSerializer.cc:21
  In eudaq::BufferSerializer::Deserialize
LogThread is dying...

i tried the command line version it worked fine.

@hperrey hperrey added this to the Release 1.2 milestone Feb 27, 2014
@hperrey hperrey added the bug label Feb 27, 2014
@RPeschke
Copy link
Contributor Author

the problem is in

status.cc
function
Status::Status(Deserializer & ds){
..
ds.read(m_msg);
..
}

it tries to Deserializer a the status string.

so it just takes 4 letters from this string interprets them as numbers and reserves this much space. but in the Deserializer(ds) ther are only 18 bytes left. this it what causes the problem.

@RPeschke
Copy link
Contributor Author

it seams to be some sort of race condition

I increased the sleep time for the command reciever from 1 ms to 500 and after this the error did not accoured anymore. I am not very happy about this solution but for now it seems to work

void CommandReceiver::OnIdle() {
mSleep(500);
}

@hperrey
Copy link
Contributor

hperrey commented Mar 17, 2014

@RPeschke thanks for looking into this, it really sounds like a serious issue! I've opened up two new issues since this sort of race condition has been seen in other producers as well and is a more general problem.

If you could please make a PR will your workaround, this should do for now; I would then close this issue and move the investigation to issues #35 and #36.

@hperrey
Copy link
Contributor

hperrey commented Mar 19, 2014

This will be "worked-around" with commit 4fba77f that is part of PR #39 -- when we have merged this into master, I will close this issue and we go forward with the release of 1.2; for the next release we should actually fix this (see issues cited above).

@hperrey hperrey closed this as completed Mar 25, 2014
tanmaymudholkar pushed a commit to tanmaymudholkar/eudaq that referenced this issue Jul 12, 2017
Pass TDC error streams to the producer to keep incrementing event numbers
lhuth pushed a commit that referenced this issue Oct 12, 2020
Add trigger mask parameter to precise trigger calculation
airqui pushed a commit to SiWECAL-TestBeam/eudaq that referenced this issue Jun 8, 2022
Longer description on why this is necessary (and if it does the
right thing now) in the corresponding GitHub issue:
SiWECAL-TestBeam/SiWECAL-TB-analysis#29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants