Hi Christian,
The segmentation violation after unpack is a known bug, fixed in 6.1 and later. I verified today that 6.2 doesn't get the error (don't have 6.1 handy), but 6.01 does get it.
As for the data flow question, I talked with R&D and we believe it's probably a defect in VEE, maybe compiler-related, so when I get a chance I will post it to our defect database. The documentation about when a sequence pin can fire (Adv Techniques, p 263 in the 6.x version of the English-language manual) is a bit loose in its definition of this, taking about data flow completion rather than subthread completion, which is why I say "probably a defect".
*** I just checked using 6.2 with Execution Mode set to VEE 3, removing the compilation step, and it works correctly, so it probably is a compiler-related defect.
Thanks for posting such a complete description and example; because everything I need is there, I won't need to ask you to submit the defect through the ADN.
Best Regards,
Scott Bayes
Software Technical Support
Agilent Technologies, Inc.
815 14th Street S.W.
Loveland, CO, U.S.A. 80537
970 679 3799 Tel
970 635 6867 Fax
> -----Original Message-----
> From: Christian Wienhold [mailto:christian.wienhold@biotronik.de]
> Sent: Wednesday, October 15, 2003 7:48 AM
> To: VEE vrf
> Cc: rainer.Milde@biotronik.de
> Subject: [vrf] VEE 6 bug presentation
>
>
> Hi Vrf,
> attached is a simplified prog that demonstrates a VEE bug we found
> recently. This bug requires a review of all our test sources
> and I don't why
> we haven't found this earlier.
>
> 1. wrong execution flow ( step into the prog )
> 2. segmentation violation ( after paste an unpacked user object )
>
> There are a lot of workarounds to avoid this behaviour, but I
> couldn't see
> why it shouldn't work like it is. It's 'tested' with VEE
> 6.01/03 and you can
> build a similar construct from scratch with the same effect.
>
> What do you think ?
> Best regards
>
> Christian
> BIOTRONIK GmbH & Co.
> EIT-1/CW
> D 12359 Berlin - Neukoelln
> Tel.: +49 30 689 05 - 301
> --------------------------------------
> christian.wienhold@biotronik.de
> --------------------------------------
>
>
>
>
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
The segmentation violation after unpack is a known bug, fixed in 6.1 and later. I verified today that 6.2 doesn't get the error (don't have 6.1 handy), but 6.01 does get it.
As for the data flow question, I talked with R&D and we believe it's probably a defect in VEE, maybe compiler-related, so when I get a chance I will post it to our defect database. The documentation about when a sequence pin can fire (Adv Techniques, p 263 in the 6.x version of the English-language manual) is a bit loose in its definition of this, taking about data flow completion rather than subthread completion, which is why I say "probably a defect".
*** I just checked using 6.2 with Execution Mode set to VEE 3, removing the compilation step, and it works correctly, so it probably is a compiler-related defect.
Thanks for posting such a complete description and example; because everything I need is there, I won't need to ask you to submit the defect through the ADN.
Best Regards,
Scott Bayes
Software Technical Support
Agilent Technologies, Inc.
815 14th Street S.W.
Loveland, CO, U.S.A. 80537
970 679 3799 Tel
970 635 6867 Fax
> -----Original Message-----
> From: Christian Wienhold [mailto:christian.wienhold@biotronik.de]
> Sent: Wednesday, October 15, 2003 7:48 AM
> To: VEE vrf
> Cc: rainer.Milde@biotronik.de
> Subject: [vrf] VEE 6 bug presentation
>
>
> Hi Vrf,
> attached is a simplified prog that demonstrates a VEE bug we found
> recently. This bug requires a review of all our test sources
> and I don't why
> we haven't found this earlier.
>
> 1. wrong execution flow ( step into the prog )
> 2. segmentation violation ( after paste an unpacked user object )
>
> There are a lot of workarounds to avoid this behaviour, but I
> couldn't see
> why it shouldn't work like it is. It's 'tested' with VEE
> 6.01/03 and you can
> build a similar construct from scratch with the same effect.
>
> What do you think ?
> Best regards
>
> Christian
> BIOTRONIK GmbH & Co.
> EIT-1/CW
> D 12359 Berlin - Neukoelln
> Tel.: +49 30 689 05 - 301
> --------------------------------------
> christian.wienhold@biotronik.de
> --------------------------------------
>
>
>
>
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
attached is a simplified prog that demonstrates a VEE bug we found
recently. This bug requires a review of all our test sources and I don't why
we haven't found this earlier.
1. wrong execution flow ( step into the prog )
2. segmentation violation ( after paste an unpacked user object )
There are a lot of workarounds to avoid this behaviour, but I couldn't see
why it shouldn't work like it is. It's 'tested' with VEE 6.01/03 and you can
build a similar construct from scratch with the same effect.
What do you think ?
Best regards
Christian
BIOTRONIK GmbH & Co.
EIT-1/CW
D 12359 Berlin - Neukoelln
Tel.: +49 30 689 05 - 301
--------------------------------------
christian.wienhold@biotronik.de
--------------------------------------