"How do you know the 3rd party component is not nesting the calls 200+ deep before returning back to your code?"
Maybe I don't understand correctly, but how can I call a component at, say, level 4 and it returns at another level? I assumed it finally always must return at the same level it starts. Is there a scenario calling a component method at one level and returning at another? Gr, Piotr P.S. I will try to make sample code Op 14 dec. 2017 11:16 a.m. schreef Piotr Chabot Stadhouders <[email protected]>: Hi Tim, It is not really possible to debug this, because a lot of calls are from within a 3rd party component, and thus unable to trace However, I have analyzed the debug log a bit more. For each sequential operation (SEQ_A) I have searched for another (SEQ_B) > SEQ_A with the same stack level Because I know that in the end I return to the original stack level, I also know every SEQ_A must have a SEQ_B Do you think I am right in this? To my surprise (not really, because I already had this gut feeling) there isn’t always a counterpart for project methods in the component and EXECUTE METHOD (in the component) I know they return because else a call to this component would make my application hang, right? Or not? So it looks like the debug logger misses returns from methods called from within in the component. I know and can see in the debug log that the component also uses semaphores, could this be something? So, what could be the reason the debug logger misses returns from method calls from within the component? Gr, Piotr Van: Timothy Penner [mailto:[email protected]] Verzonden: woensdag 13 december 2017 16:05 Aan: Piotr Chabot Stadhouders <[email protected]>; 4D iNug Technical <[email protected]>; Chip Scheide <[email protected]> Onderwerp: Re: Stack level in 4DDebugLog.txt Do you have code that can reproduce this? If so, what does the call chain look like in the debugger if you trace it? Does it show 30 calls deep or 2 calls deep? Can you supply the code and or debug logs that show this? -Tim Sent from my Verizon, Samsung Galaxy smartphone [cid:[email protected]] Timothy Penner Senior Technical Services Engineer Telephone : +1-408-557-4600 Email : [email protected]<mailto:[email protected]> Web : www.4D.com<http://www.4D.com> 4D inc 95 S. Market Street, Suite #240 CA 95113 San Jose - United States Standard : +1-408-557-4600 Fax : +1-408-271-5080 [Banner]<http://bit.ly/2i1gNCl> -------- Original message -------- From: Piotr Chabot Stadhouders <[email protected]<mailto:[email protected]>> Date: 12/13/17 12:23 AM (GMT-08:00) To: 4D iNug Technical <[email protected]<mailto:[email protected]>>, Chip Scheide <[email protected]<mailto:[email protected]>>, Timothy Penner <[email protected]<mailto:[email protected]>> Subject: RE: Stack level in 4DDebugLog.txt Hi Chip, Tim, Could there be some other weird reason why the stack level increases and doesn't decrease? Maybe calling plugin commands, or maybe EXECUTE METHOD? Maybe a bug in the debug log? Maybe something in Windows 10? I know nearly for sure that there is no recursion, and still the stack level increases At some point I am in a method I know it is stack level 2 (for example), but the debug level tells me I am in level 30. How is this possible? Gr, Piotr > -----Oorspronkelijk bericht----- > Van: Chip Scheide [mailto:[email protected]] > Verzonden: maandag 11 december 2017 19:21 > Aan: 4D iNug Technical <[email protected]<mailto:[email protected]>> > Onderwerp: RE: Stack level in 4DDebugLog.txt > > Piotr, > don't forget the possibility of indirect recursion too. > Method_A call Method_B which calls Method_C which calls Method_A > > > On Mon, 11 Dec 2017 18:11:32 +0000, Timothy Penner via 4D_Tech wrote: > > It could be recursion. The debug logs should help you determine > > exactly what is being called. > > > > If method1 calls method1 which calls method1 again (and again and > > again and again), it would increase the stack level each time it > > calls itself. > > > > -Tim > > > > > > > > > > > **************************************************************** > ****** > > 4D Internet Users Group (4D iNUG) > > FAQ: http://lists.4d.com/faqnug.html > > Archive: http://lists.4d.com/archives.html > > Options: http://lists.4d.com/mailman/options/4d_tech > > Unsub: mailto:[email protected] > > > **************************************************************** > ****** > --------------- > Gas is for washing parts > Alcohol is for drinkin' > Nitromethane is for racing ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
