Re: [E-devel] Submit this EWL bug in tracker?

[Peter W. <pet...@we...>]

Terseus schrieb:
> Hi E-developers!!
>
> First of all, sorry for my possible-poor english, I write it very few.
>
> I have found a bug (at least I think it's a bug) in the EWL libraries, but
> don't know if I must submit it, let me explain...
>
> I'm developing a text-editor using EWL, the app have a tabbed bar (an
> Ewl_Notebook widget) and I create and destroy pages without problem, except
> in one special situation: when I destroy the last page of the tabbar and
> create another one, I receive the next EWL messages:
>
> ***** Ewl Developer Warning ***** :
>   
>>  To find where this is occurring set a breakpoint
>>  for the function ewl_print_warning.
>>     This program is calling:
>>
>>     ewl_attach_get();
>>
>>     With the paramter:
>>
>>     w
>>
>>     as the wrong type. (NULL) instead of (widget).
>>     Please fix your program.
>>
>> ***** Ewl Developer Warning ***** :
>>  To find where this is occurring set a breakpoint
>>  for the function ewl_print_warning.
>>     This program is calling:
>>
>>     ewl_widget_hide();
>>
>>     With the paramter:
>>
>>     w
>>
>>     as the wrong type. (NULL) instead of (widget).
>>     Please fix your program.
>>
>>     
>
> I think that EWL doesn't handle very well the void tabbars, but I have no
> problem with it... except when I destroy the last page and create another
> one exactly three times, that when I receive a "Segmentation fault" signal;
> this don't happen if I don't destroy the last page, no matter how much pages
> create and destroy, nor the sort of the pages.
>
> In addition, as you can imagine, I don't have calls to the functions
> ewl_attach_get or ewl_widget_hide in my code.
>
> With a few of gdb I found that the SF signal is raised in the function
> "ewl_widget_type_is" in the file "ewl_widget.c".
> In this function, the parameter "widget" is valid, but not his properties
> "inheritance" and "theme_path", I think that the signal is raised when, in
> the loop, access to "widget->inheritance" (but it's only a supposition).
>
> I don't post it in the tracker because I don't have the latest SVN build,
> that is because I use Enlightenment as my primary (and unique) window
> manager in this PC and now I have it with an almost-stable build (I build it
> from SVN), also I have done some bad builds'n'rollbacks, so I don't have the
> source code of my build (a stupid error, I know...) and don't know how in
> the hell provide you the exactly version of my build; so, I don't know if
> the bug is still present in the actual SVN and don't want full with garbage
> the bug tracker.
>   

It's not such important that you have an uptodate version, as long as we 
know it. There have been some (minor) changes to the notebook, recently, 
but I don't think that they changed/fixed what you are observing. So 
don't hesitate to put into the tracker. Please note, that EWL is still 
using bugzilla (bugs.enlightenment.org).

> If anyone can test this Ewl_Notebook bug with an updated build of EWL would
> be great; if want my code for creation and destroy pages say it to me and
> will send you.
> Or if anyone can say me how can I get the exactly version of my build and if
> I must post this in the tracker I'd be grateful.
>   

The best  would be a small test case to reproduce the bug, in most cases 
this shouldn't be too hard to write and is for you easier, then for us 
to figure out what you are doing in detail.

> Sorry for my noob behavior, but this will be my first bug submited in a free
> software tracker, and don't want post invalid bugs, which I think must be
> very annoying for the developers.

I prefer to have some "invalid" bug reports, then having some unreported 
"real" bugs. And even if it is you using ewl wrongly, we can maybe give 
you some advice to fix it and perhaps improve the documentation, 
although your description sounds more like an actual ewl bug.

Thanks for the report.

Peter