A netman-gtk3 is coming..., whereas we must work also in the backend,
something is wrong in realloc.
Hi Aitor,
realloc was failing because I mistakenly passed active_wifis which is
a pointer to an integer instead of active_wifi_list which is a pointer
to a list of void*. That is why the error reported the use of an
invalid pointer as it doesn't make sense to reallocate an integer of
fixed size.
Edward
On 10/12/2015, Edward Bartolo <edbarx@???> wrote:
> A netman-gtk3 is coming..., whereas we must work also in the backend,
> something is wrong in realloc.
>
> Hi Aitor,
>
> realloc was failing because I mistakenly passed active_wifis which is
> a pointer to an integer instead of active_wifi_list which is a pointer
> to a list of void*. That is why the error reported the use of an
> invalid pointer as it doesn't make sense to reallocate an integer of
> fixed size.
>
> Edward
>
> On 10/12/2015, Edward Bartolo <edbarx@???> wrote:
>> Hi Rainer,
>>
>> Thanks for your help. I will have a deeper look at netman/debian
>> tomorrow. Instead of separating the debianization directory contents ,
>> I can create a debianized netman source tree and an undebianized
>> source tree. That way, users wouldn't need to worry about having to
>> debianize netman. However, I am open to suggestions.
>>
>> Edward
>>
>> On 10/12/2015, Rainer Weikusat <rainerweikusat@???> wrote:
>>> Edward Bartolo <edbarx@???> writes:
>>>> Forwarded to dng.
>>>>
>>>> On 10/12/2015, Edward Bartolo <edbarx@???> wrote:
>>>>> I was using -p together with -f. Now, I succeeded to fully run dh_make
>>>>> as it created the netman/debian directory. These are the file therein:
>>>>>
>>>>> edbarx@edbarx-pc:~/netman-0.1.1/debian$ ls -l
>>>>> total 112
>>>>> -rw-r--r-- 1 edbarx edbarx 178 Dec 10 22:21 changelog
>>>>> -rw-r--r-- 1 edbarx edbarx 2 Dec 10 22:21 compat
>>>>> -rw-r--r-- 1 edbarx edbarx 634 Dec 10 22:21 control
>>>>> -rw-r--r-- 1 edbarx edbarx 1664 Dec 10 22:21 copyright
>>>>> -rwxr-xr-x 1 edbarx edbarx 844 Dec 10 22:21 rules
>>>>> drwxr-xr-x 2 edbarx edbarx 4096 Dec 10 22:21 source
>>>
>>> These are the ones which are required. 'compat' and the source directory
>>> including contents can be left alone. You should edit changelog, control
>>> and copyright. rules is the Makefile actually building the
>>> package. Editing that may be necessary later on.
>>>
>>> You'll also need an install target in the top-level Makefile for this to
>>> work.
>>>
>>> Lastly, in case you want to turn this into a Debian source package,
>>> keeping the debianization stuff on a separate git branch would IMHO be
>>> advisable.
>>> _______________________________________________
>>> Dng mailing list
>>> Dng@???
>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>>>
>>
>