[Paraview-developers] paraview PVSessionCore error

Mon Jul 18 13:38:16 EDT 2016

On Mon, Jul 18, 2016 at 1:05 PM, Chiranjib Sur <sur.chiranjib at gmail.com> wrote:
> Cory,
> Thanks much. It means that except appending all classes by "vtk" nothing
> needs to be changed and is the crash related to "RequestData"
> implementation?

Ah, one problem now that I look at your example again:

Use the 'vtkStandardNewMacro(<myclassname>)' in your .cpp files to
define the New() member functions. I suspect the way you are defining
New() causes the garbage collector to prematurely delete the objects
because the object reference counts are never incremented. This is
likely what leads to the crash.

Cory

> Chiranjib
>
> On Mon, Jul 18, 2016 at 7:44 PM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>>
>> Chiranjib,
>>
>> CC'ing the developer's list so that others may benefit.
>>
>> Please see my modifications to your code attached. I wouldn't stress
>> out about crashes until you more fully implement your plugin.
>>
>> Thanks,
>> Cory
>>
>> On Mon, Jul 18, 2016 at 1:15 AM, Chiranjib Sur <sur.chiranjib at gmail.com>
>> wrote:
>> > Hi Cory,
>> > Sorry to bother you again.
>> >
>> > I started with a clear mind this morning. Here is my modified sources
>> > (prepended the class/file names with vtk ) attached. While building I
>> > can
>> > build the ".so": and can load this as a plugin. However, when I want to
>> > create the source from the menu, I get a seg fault. I think it's  an
>> > issue
>> > with some port. Since  I have not implemented "RequestData" i don't
>> > expect
>> > anyting to be displayed in the PV window, however it landed with a
>> > crash.
>> >
>> > You mentioned that by "appending the names with vtk" you could get it
>> > worked. Could yo you please share the modification you have made it to
>> > work
>> > or have a look at my attachment?
>> >
>> > Thanks,
>> > Chiranjib
>> >
>> > On Fri, Jul 15, 2016 at 12:37 AM, Chiranjib Sur
>> > <sur.chiranjib at gmail.com>
>> > wrote:
>> >>
>> >> Yep! I have access now and have the edit privilege. I will start adding
>> >> things shortly. Let me make a list of things that I have learnt mostly
>> >> via
>> >> discussions using the mailing list.
>> >>
>> >> Chiranjib
>> >>
>> >>
>> >> On Fri, Jul 15, 2016 at 12:28 AM, Cory Quammen
>> >> <cory.quammen at kitware.com>
>> >> wrote:
>> >>>
>> >>> Okay, you should have gotten an email with a randomly generated
>> >>> password that should get you access to the wiki. You should be able to
>> >>> edit it - let me know if you can't.
>> >>>
>> >>> Thanks,
>> >>> Cory
>> >>>
>> >>> On Thu, Jul 14, 2016 at 2:53 PM, Cory Quammen
>> >>> <cory.quammen at kitware.com>
>> >>> wrote:
>> >>> > On Thu, Jul 14, 2016 at 2:46 PM, Chiranjib Sur
>> >>> > <sur.chiranjib at gmail.com> wrote:
>> >>> >> Hi Cory,
>> >>> >> Great! I prefer the user name <chiranjib.sur> for the account and
>> >>> >> atleast
>> >>> >> for first few posts, I want it to be reviewed by you just to make
>> >>> >> sure, I am
>> >>> >> following the standards.
>> >>> >
>> >>> > Sure, no problem. I'm not really sure there are standards :-) You
>> >>> > give
>> >>> > us too much credit.
>> >>> >
>> >>> >> Do you mind for the wiki and edits if I communicate to you directly
>> >>> >> bypassing the PV-developer mailing list?
>> >>> >
>> >>> > Yes, no problem.
>> >>> >
>> >>> > Cory
>> >>> >
>> >>> >> Thanks,
>> >>> >> Chiranjib
>> >>> >>
>> >>> >> On Fri, Jul 15, 2016 at 12:13 AM, Cory Quammen
>> >>> >> <cory.quammen at kitware.com>
>> >>> >> wrote:
>> >>> >>>
>> >>> >>> Chiranjib,
>> >>> >>>
>> >>> >>> > How do I register to the wiki as an author? And how it works -
>> >>> >>> > anybody
>> >>> >>> > reviews the submission before it is published?
>> >>> >>>
>> >>> >>> The wiki suffered from spam attacks recently, so we had to disable
>> >>> >>> user registration. I'll work to get you an account and then get
>> >>> >>> you
>> >>> >>> the login info.
>> >>> >>>
>> >>> >>> No reviews are needed before publishing, but if you want someone
>> >>> >>> to
>> >>> >>> take a look after you post the changes, I'm happy to review.
>> >>> >>>
>> >>> >>> Thanks,
>> >>> >>> Cory
>> >>> >>>
>> >>> >>> > Thanks,
>> >>> >>> > Chiranjib
>> >>> >>> >
>> >>> >>> >
>> >>> >>> >
>> >>> >>> > On Thu, Jul 14, 2016 at 11:43 PM, Cory Quammen
>> >>> >>> > <cory.quammen at kitware.com>
>> >>> >>> > wrote:
>> >>> >>> >>
>> >>> >>> >> > I wish these kind of information is stored in some wiki form
>> >>> >>> >> > somewhere,
>> >>> >>> >> > or
>> >>> >>> >> > posted in your vtk/paraview blog. This will be immensely
>> >>> >>> >> > helpful
>> >>> >>> >> > to
>> >>> >>> >> > the
>> >>> >>> >> > developer community!
>> >>> >>> >>
>> >>> >>> >> Indeed, though a ParaView developer's guide would likely be
>> >>> >>> >> several
>> >>> >>> >> hundred pages long, would no doubt miss an important piece of
>> >>> >>> >> information someone needs, and would be out of date quite
>> >>> >>> >> quickly.
>> >>> >>> >> The
>> >>> >>> >> ParaView code is itself the authoritative source of
>> >>> >>> >> information,
>> >>> >>> >> but I
>> >>> >>> >> know full well - believe me - that it isn't always fast or easy
>> >>> >>> >> to
>> >>> >>> >> go
>> >>> >>> >> that route.
>> >>> >>> >>
>> >>> >>> >> The good news is that you are now part of the developer
>> >>> >>> >> community,
>> >>> >>> >> so
>> >>> >>> >> we have one more person to contribute this documentation! It
>> >>> >>> >> would
>> >>> >>> >> be
>> >>> >>> >> great if you could update the ParaView plugins howto page on
>> >>> >>> >> the
>> >>> >>> >> wiki
>> >>> >>> >> for other developers to benefit:
>> >>> >>> >>
>> >>> >>> >> http://www.paraview.org/Wiki/Plugin_HowTo
>> >>> >>> >>
>> >>> >>> >> Best,
>> >>> >>> >> Cory
>> >>> >>> >>
>> >>> >>> >>
>> >>> >>> >> > Thanks a lot,
>> >>> >>> >> > Chiranjib
>> >>> >>> >> >
>> >>> >>> >> >
>> >>> >>> >> > On Thu, Jul 14, 2016 at 7:37 PM, Cory Quammen
>> >>> >>> >> > <cory.quammen at kitware.com>
>> >>> >>> >> > wrote:
>> >>> >>> >> >>
>> >>> >>> >> >> Chiranjib,
>> >>> >>> >> >>
>> >>> >>> >> >> It's not obvious or probably described anywhere, but the
>> >>> >>> >> >> client/server
>> >>> >>> >> >> code wrapping mechanism wraps member functions that have VTK
>> >>> >>> >> >> objects
>> >>> >>> >> >> as parameters *only* if those VTK objects have names that
>> >>> >>> >> >> start
>> >>> >>> >> >> with
>> >>> >>> >> >> "vtk". If you prepend vtk to all your sph* classes, it
>> >>> >>> >> >> should
>> >>> >>> >> >> work.
>> >>> >>> >> >> In
>> >>> >>> >> >> fact, I tested that locally, and it solves the error you are
>> >>> >>> >> >> seeing.
>> >>> >>> >> >>
>> >>> >>> >> >> HTH,
>> >>> >>> >> >> Cory
>> >>> >>> >> >>
>> >>> >>> >> >> On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur
>> >>> >>> >> >> <sur.chiranjib at gmail.com>
>> >>> >>> >> >> wrote:
>> >>> >>> >> >> > Hi,
>> >>> >>> >> >> > Thanks for your messages the pointers. I still have some
>> >>> >>> >> >> > issues.
>> >>> >>> >> >> > Here
>> >>> >>> >> >> > is
>> >>> >>> >> >> > the
>> >>> >>> >> >> > attached code snippets which throws me error messages. I
>> >>> >>> >> >> > am
>> >>> >>> >> >> > bit
>> >>> >>> >> >> > clueless
>> >>> >>> >> >> > what I am missing here.
>> >>> >>> >> >> >
>> >>> >>> >> >> > Thanks,
>> >>> >>> >> >> > Chiranjib
>> >>> >>> >> >> >
>> >>> >>> >> >> > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge
>> >>> >>> >> >> > Orlando
>> >>> >>> >> >> > <Orlando.RIVERA at mtu.de> wrote:
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Hi,
>> >>> >>> >> >> >>
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Also , check if   "setVariable" is   in  the public
>> >>> >>> >> >> >> section
>> >>> >>> >> >> >> of
>> >>> >>> >> >> >> your
>> >>> >>> >> >> >> class
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Orlando
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> -----Ursprüngliche Nachricht-----
>> >>> >>> >> >> >> Von: Paraview-developers
>> >>> >>> >> >> >> [mailto:paraview-developers-bounces at paraview.org]
>> >>> >>> >> >> >> Im Auftrag von Cory Quammen
>> >>> >>> >> >> >> Gesendet: Tuesday, 12. July 2016 15:37
>> >>> >>> >> >> >> An: Chiranjib Sur
>> >>> >>> >> >> >> Cc: Paraview Developer Mailing list
>> >>> >>> >> >> >> Betreff: Re: [Paraview-developers] paraview PVSessionCore
>> >>> >>> >> >> >> error
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Chiranjib,
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Usually this error means there is a mismatch between the
>> >>> >>> >> >> >> XML
>> >>> >>> >> >> >> used
>> >>> >>> >> >> >> to
>> >>> >>> >> >> >> describe the VTK-side class. Check that your XML name for
>> >>> >>> >> >> >> the
>> >>> >>> >> >> >> member
>> >>> >>> >> >> >> function matches the C++, and that the member function
>> >>> >>> >> >> >> setVariable()
>> >>> >>> >> >> >> takes only one value.
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Cory
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur
>> >>> >>> >> >> >> <sur.chiranjib at gmail.com>
>> >>> >>> >> >> >> wrote:
>> >>> >>> >> >> >> > Hi,
>> >>> >>> >> >> >> > I am trying to implement a new filter in ParaView and I
>> >>> >>> >> >> >> > get the
>> >>> >>> >> >> >> > following
>> >>> >>> >> >> >> > error while executing.
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > vtkPVSessionCore (0x162d180): Object type:
>> >>> >>> >> >> >> > MyObjectSource,
>> >>> >>> >> >> >> > could
>> >>> >>> >> >> >> > not
>> >>> >>> >> >> >> > find
>> >>> >>> >> >> >> > requested method: "setVariable"
>> >>> >>> >> >> >> > or the method was called with incorrect arguments.
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > while processing
>> >>> >>> >> >> >> > Message 0 = Invoke
>> >>> >>> >> >> >> >   Argument 0 = vtk_object_pointer
>> >>> >>> >> >> >> > {MyObjectSource(0x34b3870)}
>> >>> >>> >> >> >> >   Argument 1 = string_value {setVariable}
>> >>> >>> >> >> >> >   Argument 2 = float64_value {0.003}
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > I searched the mailing list and it looks like a very
>> >>> >>> >> >> >> > similar
>> >>> >>> >> >> >> > bug
>> >>> >>> >> >> >> > has
>> >>> >>> >> >> >> > been
>> >>> >>> >> >> >> > reported
>> >>> >>> >> >> >> > http://www.paraview.org/Bug/view.php?id=15593
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > People have faced similar problem and here are the
>> >>> >>> >> >> >> > details
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > http://public.kitware.com/pipermail/paraview/2016-March/036387.html
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > Is there a solution of work-around?
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > Chiranjib
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > _______________________________________________
>> >>> >>> >> >> >> > Powered by www.kitware.com
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > Visit other Kitware open-source projects at
>> >>> >>> >> >> >> > http://www.kitware.com/opensource/opensource.html
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > Search the list archives at:
>> >>> >>> >> >> >> > http://markmail.org/search/?q=Paraview-developers
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > Follow this link to subscribe/unsubscribe:
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>> >>> >> >> >> >
>> >>> >>> >> >> >>
>> >>> >>> >> >> >>
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> --
>> >>> >>> >> >> >> Cory Quammen
>> >>> >>> >> >> >> R&D Engineer
>> >>> >>> >> >> >> Kitware, Inc.
>> >>> >>> >> >> >> _______________________________________________
>> >>> >>> >> >> >> Powered by www.kitware.com
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Visit other Kitware open-source projects at
>> >>> >>> >> >> >> http://www.kitware.com/opensource/opensource.html
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Search the list archives at:
>> >>> >>> >> >> >> http://markmail.org/search/?q=Paraview-developers
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Follow this link to subscribe/unsubscribe:
>> >>> >>> >> >> >>
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>> >>> >> >> >> --
>> >>> >>> >> >> >> MTU Aero Engines AG
>> >>> >>> >> >> >> Vorstand/Board of Management: Reiner Winkler,
>> >>> >>> >> >> >> Vorsitzender/CEO;
>> >>> >>> >> >> >> Dr.
>> >>> >>> >> >> >> Rainer
>> >>> >>> >> >> >> Martens, Michael Schreyoegg
>> >>> >>> >> >> >> Vorsitzender des Aufsichtsrats/Chairman of the
>> >>> >>> >> >> >> Supervisory
>> >>> >>> >> >> >> Board:
>> >>> >>> >> >> >> Klaus
>> >>> >>> >> >> >> Eberhardt
>> >>> >>> >> >> >> Sitz der Gesellschaft/Registered Office: Muenchen
>> >>> >>> >> >> >> Handelsregister/Commercial Register: Muenchen HRB 157206
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene
>> >>> >>> >> >> >> vertrauliche
>> >>> >>> >> >> >> oder
>> >>> >>> >> >> >> rechtlich geschuetzte Informationen.
>> >>> >>> >> >> >> Wenn Sie nicht der beabsichtigte Empfaenger sind,
>> >>> >>> >> >> >> informieren Sie
>> >>> >>> >> >> >> bitte
>> >>> >>> >> >> >> den Absender und loeschen Sie diese
>> >>> >>> >> >> >> E-Mail sowie die Anhaenge. Das unbefugte Speichern,
>> >>> >>> >> >> >> Kopieren
>> >>> >>> >> >> >> oder
>> >>> >>> >> >> >> Weiterleiten ist nicht gestattet.
>> >>> >>> >> >> >>
>> >>> >>> >> >> >> This e-mail and any attached documents are proprietary to
>> >>> >>> >> >> >> MTU,
>> >>> >>> >> >> >> confidential or protected by law.
>> >>> >>> >> >> >> If you are not the intended recipient, please advise the
>> >>> >>> >> >> >> sender
>> >>> >>> >> >> >> and
>> >>> >>> >> >> >> delete
>> >>> >>> >> >> >> this message and its attachments.
>> >>> >>> >> >> >> Any unauthorised storing, copying or distribution is
>> >>> >>> >> >> >> prohibited.
>> >>> >>> >> >> >
>> >>> >>> >> >> >
>> >>> >>> >> >>
>> >>> >>> >> >>
>> >>> >>> >> >>
>> >>> >>> >> >> --
>> >>> >>> >> >> Cory Quammen
>> >>> >>> >> >> R&D Engineer
>> >>> >>> >> >> Kitware, Inc.
>> >>> >>> >> >
>> >>> >>> >> >
>> >>> >>> >>
>> >>> >>> >>
>> >>> >>> >>
>> >>> >>> >> --
>> >>> >>> >> Cory Quammen
>> >>> >>> >> R&D Engineer
>> >>> >>> >> Kitware, Inc.
>> >>> >>> >
>> >>> >>> >
>> >>> >>>
>> >>> >>>
>> >>> >>>
>> >>> >>> --
>> >>> >>> Cory Quammen
>> >>> >>> R&D Engineer
>> >>> >>> Kitware, Inc.
>> >>> >>
>> >>> >>
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> > Cory Quammen
>> >>> > R&D Engineer
>> >>> > Kitware, Inc.
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Cory Quammen
>> >>> R&D Engineer
>> >>> Kitware, Inc.
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>
>

-- 
Cory Quammen
R&D Engineer
Kitware, Inc.