Bug#743098: passing NULL argv to gtestutils.

[Emilio Pozuelo Monfort]

reassign 743098 ekg2 1:0.4~pre+20120506.1-3
thanks

On 06/04/14 21:31, Marcin Owsiany wrote:
> 2014-04-06 19:19 GMT+02:00 Andreas Henriksson <andreas at fatal.se>:
> 
>> Hello Marcin Owsiany!
>>
>> In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743098
>> you wrote:
>>
>>> This seems to be a regression in glib, which used to support passing an
>>> empty argv:
>>
>> Looks to me like it at best used to work by chance.
>>
>> Could you please explain what you mean by supported
> 
> 
> Only that it used to be accepted, and now crashes the program.
> 
> 
>> and
>> why you think passing an empty argv is a sane thing to do?
>>
> 
> It's just one way of passing "nothing". Unless the semantics are
> documented, this way is as sane as any other :-)

They are:

Docs for 2.40 which we currently have in unstable:

https://developer.gnome.org/glib/2.40/glib-Testing.html#g-test-init

And for really-old 2.26:

https://developer.gnome.org/glib/2.26/glib-Testing.html#g-test-init

As you can see both say:

"argc: Address of the argc parameter of the main() function. Changed if any
arguments were handled."
"argv: Address of the argv parameter of main(). Any parameters understood by
g_test_init() stripped before return."

And none have the common "[allow-none]" annotation which would mean passing NULL
is supported.

Cheers,
Emilio