Niklaus Giger wrote:
> Hi
>
> Here the reworked patch.
Ok, most of your patch is applied, I changed vxworks msgQLib so that it
behave like vxworks. The only thing I did not apply is :
Index: sim/skins/vxworks/testsuite/t010726-2.c
==
Am Samstag, 17. Juni 2006 20:35 schrieb Gilles Chanteperdrix:
> Niklaus Giger wrote:
> > Am Samstag, 17. Juni 2006 19:53 schrieb Gilles Chanteperdrix:
> > > Niklaus Giger wrote:
> > > > Hi
> > > >
> > > > Here the reworked patch.
> > > >
> > > > vxWorks supports empty messages. Only one
Niklaus Giger wrote:
> Am Samstag, 17. Juni 2006 19:53 schrieb Gilles Chanteperdrix:
> > Niklaus Giger wrote:
> > > Hi
> > >
> > > Here the reworked patch.
> > >
> > > vxWorks supports empty messages. Only one at a time can be received.
> >
> > Could you explain a bit more "Only one a
Am Samstag, 17. Juni 2006 19:53 schrieb Gilles Chanteperdrix:
> Niklaus Giger wrote:
> > Hi
> >
> > Here the reworked patch.
> >
> > vxWorks supports empty messages. Only one at a time can be received.
>
> Could you explain a bit more "Only one at a time can be received" ? I do
> not get it. Y
Niklaus Giger wrote:
> Hi
>
> Here the reworked patch.
>
> vxWorks supports empty messages. Only one at a time can be received.
Could you explain a bit more "Only one at a time can be received" ? I do
not get it. You mean that one message get lost if posting two null
length messages while t
Hi
Here the reworked patch.
vxWorks supports empty messages. Only one at a time can be received.
Test log of running t010726-2 under vxWorks and the simulator are below:
(vxWorks target)
0x1e268a8 (root): t010726-2.c:180: TEST failed: qid == 0 && errno ==
S_msgQLib_INVALID_QUEUE_TYPE
0x1e268a8 (
Am Mittwoch, 14. Juni 2006 15:23 schrieb Gilles Chanteperdrix:
> Niklaus Giger wrote:
> > Is it okay to submit such a patch, which mixes a different test cases
> > or shall I submit the patches in smaller pieces? Should the test that I
> > put into the procedure msgDuringInt better be inlined?
Niklaus Giger wrote:
> Is it okay to submit such a patch, which mixes a different test cases or
> shall I submit the patches in smaller pieces? Should the test that I put
> into
> the procedure msgDuringInt better be inlined? Or should I add a new file for
> these tests?
I think it is a
Hi
First I would like to thanks Gilles a lot! He patiently corrected my mistakes
until we could finally agree on changes in the vxworks testsuite which
allowed me to run (with a few additional files on my windows box running the
vxworks development environment).
The attached patch vx_patch.msg
