Jan Kiszka schrieb:
..
> Yep, correct. Don't know, I must have smoked something while trying to
> fix this bug some weeks ago.
...
Ah, now I know why it always smells a little funny in your office, must
be good stuff. :-)
SCNR.
Cheers
Fu
Anders Blomdell wrote:
> When RTDM is exposed to code like this:
>
> device1 = rt_dev_open("some_device", O_RDWR);
> device2 = rt_dev_open("some_device", O_RDWR);
>
> I get a SEGFAULT, which I attribute to a missing assignment to
> context_ptr in the case when the device is already busy, the
When RTDM is exposed to code like this:
device1 = rt_dev_open("some_device", O_RDWR);
device2 = rt_dev_open("some_device", O_RDWR);
I get a SEGFAULT, which I attribute to a missing assignment to context_ptr in
the case when the device is already busy, the lack of this assignment leads to a
Jan Kiszka schrieb:
..
> Yep, correct. Don't know, I must have smoked something while trying to
> fix this bug some weeks ago.
...
Ah, now I know why it always smells a little funny in your office, must
be good stuff. :-)
SCNR.
Cheers
Fu
Anders Blomdell wrote:
> When RTDM is exposed to code like this:
>
> device1 = rt_dev_open("some_device", O_RDWR);
> device2 = rt_dev_open("some_device", O_RDWR);
>
> I get a SEGFAULT, which I attribute to a missing assignment to
> context_ptr in the case when the device is already busy, the
When RTDM is exposed to code like this:
device1 = rt_dev_open("some_device", O_RDWR);
device2 = rt_dev_open("some_device", O_RDWR);
I get a SEGFAULT, which I attribute to a missing assignment to context_ptr in
the case when the device is already busy, the lack of this assignment leads to a
