Bug 848480 - Arrays as method's input value don't have prober count value
Summary: Arrays as method's input value don't have prober count value
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: konkretcmpi
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Radek Novacek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-15 17:51 UTC by Roman Rakus
Modified: 2016-12-01 00:30 UTC (History)
4 users (show)

Fixed In Version: konkretcmpi-0.8.7-8.fc17
Clone Of:
Environment:
Last Closed: 2013-02-16 00:52:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Roman Rakus 2012-08-15 17:51:23 UTC
Description of problem:
I'm using an array of strings as input value in one method. But the `count' is always set to 0 and thus it is not easy to determine how large the array is.

Version-Release number of selected component (if applicable):
konkretcmpi-0.8.7-3.fc17.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create some method with array of strings as an input
2. Generate provider code
3. print `count'
  
Additional info:
The definition is: const KStringA* values
The testing code is:
printf("Values [%p]:\n", values);
printf("\tExists: %d\n", values->exists);
printf("\tNull: %d\n", values->null);
printf("\tCount: %d\n", values->count);
printf("\tvalue: %p\n", values->value);

The output:
Values [0x7f9fffcc7328]:
        Exists: 1
        Null: 0
        Count: 0
        value: 0x7f9ff8001760

But there is workaround:
arr = values->value;
count = arr->ft->getSize(arr, status);
printf("\tCount2: %d\n", count);

I can provide you testing MOF file and provider code.

Comment 1 Fedora Update System 2013-02-06 08:26:52 UTC
konkretcmpi-0.8.7-8.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/konkretcmpi-0.8.7-8.fc18

Comment 2 John Dennis 2013-02-06 13:52:40 UTC
Thank you for fixing this. Please also build and push the fix for F17 and update the Fixed In field.

I cherry-picked the patch into the f17 branch but I didn't have permission to push it or I would have done this for you.

Comment 3 Fedora Update System 2013-02-06 14:11:07 UTC
konkretcmpi-0.8.7-8.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/konkretcmpi-0.8.7-8.fc17

Comment 4 Radek Novacek 2013-02-06 14:13:52 UTC
Update submitted also for Fedora 17 and Fixed In field filled.

Comment 5 Fedora Update System 2013-02-08 02:06:46 UTC
Package konkretcmpi-0.8.7-8.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing konkretcmpi-0.8.7-8.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-2020/konkretcmpi-0.8.7-8.fc17
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-02-16 00:52:50 UTC
konkretcmpi-0.8.7-8.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2013-02-16 01:04:05 UTC
konkretcmpi-0.8.7-9.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.