Issues setting up gemtools debugger
Locked
Issues setting up gemtools debugger
 
|
Hello, everyone!
I'm having troubles with debugging... I have one development server where everything works as it should (let's call it "good server"), and now I'm setting up another development server which is not working in the same way (namely, the "bad server")... Both servers have been restored with the same gemstone production DB which runs an application on Seaside. For production environment, I'm using the WAGemStoneProductionErrorHandler. Here are the issues: 1) When I restore that DB to development servers and make an error happen while using WAGemStoneProductionErrorHandler, if I try to debug it in the good server, it shows the debug window just fine, showing all the stak an related values for each stack frame. But if I do the same with the bad server, i get debug window with a different error (not the one i'm trying to debug), like this:  2) If I change the Error handler to WARemoteDebuggingWalkbackErrorHandler, the good server keeps working alright, but the bad server behaves strange... 2.1) When an error occurs and i want to debug it, a good debug window appears and i'm actually able to do it! But when i'm finished debugging, the next gemtools button I press, displays this other window:  2.2) When i try to halt at some point of the code, there's no way to get to that Halt... a debugger window appears, but the stack has nothing to do with the code actually being executed by the application, but by seaside. It's like seaside is producing an error when it reaches a halt. I think this summarises what's wrong with the new server... but I have tried a lot of things and haven't got it to work like the good server... I checked the startFastCGI scripts, the startSeasideAdaptor scrpits... they seem to be the same... is there anything else you see I'm missing?? Thank you very much in advance!!! And sorry for the extense post!! Alejandro |
Re: Issues setting up gemtools debugger
|
|
Hi Alejandro,
The 'different error' seems to be an error that occurs in the gemtools image (and not in gemstone). Are both servers running identical versions of gemstone? Johan |
Re: Issues setting up gemtools debugger
|
|
Hi, Johan! Yes, both servers are running this version:GemStone/S 64 Bit 3.0.1 Build: gss64_3_0_1_branch-27207 Mon Oct 31 15:04:13 2011 Thank you very much!! Alejandro On Tue, Dec 18, 2012 at 3:23 PM, Johan Brichau-2 [via Smalltalk] <[hidden email]> wrote: Hi Alejandro, |
Re: Issues setting up gemtools debugger
|
|
In reply to this post by keropotter
Alejandro,
Please debug the client-side stack on your bad server to find the root cause. First, select 'Popup on debug' in the Admin menu. Then when you get an error you are provided with a dialog box, choose 'debug squeak stack' to bring up the client side debugger. The look at the stack frame labeled GsProcess>>openDebugger, inspect the #tag object in anException. The #message slot will have the error message and we can go from there. Dale ----- Original Message ----- | From: "keropotter" <[hidden email]> | To: [hidden email] | Sent: Tuesday, December 18, 2012 8:17:31 AM | Subject: [GS/SS Beta] Issues setting up gemtools debugger | | Hello, everyone! | | I'm having troubles with debugging... I have one development server | where | everything works as it should (let's call it "good server"), and now | I'm | setting up another development server which is not working in the | same way | (namely, the "bad server")... | | Both servers have been restored with the same gemstone production DB | which | runs an application on Seaside. For production environment, I'm using | the | *WAGemStoneProductionErrorHandler*. | | Here are the issues: | | 1) When I restore that DB to development servers and make an error | happen | while using WAGemStoneProductionErrorHandler, if I try to debug it in | the | good server, it shows the debug window just fine, showing all the | stak an | related values for each stack frame. But if I do the same with the | bad | server, i get debug window with a different error (not the one i'm | trying to | debug), like this: | | <http://forum.world.st/file/n4659840/localMethodAtError.jpg> | | 2) If I change the Error handler to | /WARemoteDebuggingWalkbackErrorHandler/, | the good server keeps working alright, but the bad server behaves | strange... | 2.1) When an error occurs and i want to debug it, a good debug | window | appears and i'm actually able to do it! But when i'm finished | debugging, the | next gemtools button I press, displays this other window: | <http://forum.world.st/file/n4659840/cannotTerminateContinuation.jpg> | 2.2) When i try to halt at some point of the code, there's no way | to get | to that Halt... a debugger window appears, but the stack has nothing | to do | with the code actually being executed by the application, but by | seaside. | It's like seaside is producing an error when it reaches a halt. | | I think this summarises what's wrong with the new server... but I | have tried | a lot of things and haven't got it to work like the good server... I | checked | the startFastCGI scripts, the startSeasideAdaptor scrpits... they | seem to be | the same... is there anything else you see I'm missing?? | | Thank you very much in advance!!! And sorry for the extense post!! | Alejandro | | | | -- | View this message in context: | http://forum.world.st/Issues-setting-up-gemtools-debugger-tp4659840.html | Sent from the GLASS mailing list archive at Nabble.com. | |
Re: Issues setting up gemtools debugger
|
|
Thank you very much, Dale! I set the WAGemStoneProductionErrorHandler in the bad server and produced a message not understood error. Then I debugged the squeak stack as you suggested. The message in tag object is: 'a ThreadError occurred (error 2366), reason:rtErrSchedulerDeadlocked, The ProcessorScheduler is deadlocked'. Thanks again! Alejandro On Tue, Dec 18, 2012 at 4:00 PM, Dale Henrichs [via Smalltalk] <[hidden email]> wrote: Alejandro, |
Re: Issues setting up gemtools debugger
|
|
Hi!
I haven't been able to find a solution to this yet. Has anybody else experienced this issue and has been able to solve it? Thanks in advance! Alejandro |
Re: Issues setting up gemtools debugger
|
|
Alejandro,
Okay I think it is time to reset ... I am afraid that I ended up obsessing on the Client error handling and not the errors that were being raised ... Also as I reread the original message, I see that the context of these errors is the debugging of continuations and the fact that you appear to be able to debug in the "good server" and debugging attempts fail in the "bad server" ... and apparently the error that gets raised in the "bad server" is rtErrSchedulerDeadlocked ... So at this point in time I assume that you are interested in figuring out why debugging attempts fail in the "bad server", so if that's case I have one line of approach. If the "it" in your message is something else, then now is a good time to set me straight ... Perhaps a description (sorry if it is identical to your first message) of your current state will give us a good starting point to resume characterization... Dale ----- Original Message ----- | From: "keropotter" <[hidden email]> | To: [hidden email] | Sent: Friday, January 11, 2013 7:45:57 AM | Subject: Re: [GS/SS Beta] Issues setting up gemtools debugger | | Hi! | | I haven't been able to find a solution to this yet. Has anybody else | experienced this issue and has been able to solve it? | | Thanks in advance! | Alejandro | | | | -- | View this message in context: | http://forum.world.st/Issues-setting-up-gemtools-debugger-tp4659840p4662954.html | Sent from the GLASS mailing list archive at Nabble.com | |
Re: Issues setting up gemtools debugger
|
|
Dale, thank you very much for your time! You're right about I need. I'm trying to figure out why the debug fails on the "bad server" and to make it work fine, since this is stopping us from migrating to the new development servers.Alejandro On Fri, Jan 11, 2013 at 4:46 PM, Dale Henrichs [via Smalltalk] <[hidden email]> wrote: Alejandro, |
Re: Issues setting up gemtools debugger
|
|
In reply to this post by keropotter
Alejandro,
I'm going to start with the very first issue ... You say "But if I do the same with the bad server..." and I'm curious what you are talking about here. Are you trying to debug the same continuation as in the "good server", i.e., the EXACT same stack. Or are you tring to debug a continuation that was produced in the 'bad server" ... I ask, because there are limitations on how you can debug continuations as opposed to debugging errors directly in GemTools. I have not made it possible to do a debugger level for continuations and depending upon where you are in a stack, you may not be able to step either ... So at this point it is important to determine if you are looking at the same EXACT stack (restored from "good server") and that you are doing exactly the same things ... then we'll go from there ... Dale ----- Original Message ----- | From: "keropotter" <[hidden email]> | To: [hidden email] | Sent: Tuesday, December 18, 2012 8:17:31 AM | Subject: [GS/SS Beta] Issues setting up gemtools debugger | | | Here are the issues: | | 1) When I restore that DB to development servers and make an error | happen | while using WAGemStoneProductionErrorHandler, if I try to debug it in | the | good server, it shows the debug window just fine, showing all the | stak an | related values for each stack frame. But if I do the same with the | bad | server, i get debug window with a different error (not the one i'm | trying to | debug), like this: | | <http://forum.world.st/file/n4659840/localMethodAtError.jpg> |
Re: Issues setting up gemtools debugger
|
|
Hi, Dale! I'm not debugging the exact same stack. I've restored a copy of the production database into both servers so I have the same code and objects. After that, I manually produced the exact same error on both servers, so the stacks are different. On Mon, Jan 14, 2013 at 3:24 PM, Dale Henrichs [via Smalltalk] <[hidden email]> wrote: Alejandro, |
Re: Issues setting up gemtools debugger
|
|
Alejandro,
Okay ... and presumably the errors that you are getting can be put down to the limitiations on debugging continuations? Dale ----- Original Message ----- | From: "keropotter" <[hidden email]> | To: [hidden email] | Sent: Monday, January 14, 2013 10:33:31 AM | Subject: Re: [GS/SS Beta] Issues setting up gemtools debugger | | | | | | Hi, Dale! | | I'm not debugging the exact same stack. | | I've restored a copy of the production database into both servers so | I have the same code and objects. | | After that, I manually produced the exact same error on both servers, | so the stacks are different. | | Thank you very much! | Alejandro | | | | | | | | | On Mon, Jan 14, 2013 at 3:24 PM, Dale Henrichs [via Smalltalk] < | [hidden email] > wrote: | | | Alejandro, | | I'm going to start with the very first issue ... | | You say "But if I do the same with the bad server..." and I'm curious | what you are talking about here. | | Are you trying to debug the same continuation as in the "good | server", i.e., the EXACT same stack. | | Or are you tring to debug a continuation that was produced in the | 'bad server" ... | | I ask, because there are limitations on how you can debug | continuations as opposed to debugging errors directly in GemTools. I | have not made it possible to do a debugger level for continuations | and depending upon where you are in a stack, you may not be able to | step either ... | | So at this point it is important to determine if you are looking at | the same EXACT stack (restored from "good server") and that you are | doing exactly the same things ... then we'll go from there ... | | | Dale | | ----- Original Message ----- | | From: "keropotter" < [hidden email] > | | To: [hidden email] | | | Sent: Tuesday, December 18, 2012 8:17:31 AM | | | Subject: [GS/SS Beta] Issues setting up gemtools debugger | | | | | | Here are the issues: | | | | 1) When I restore that DB to development servers and make an error | | happen | | while using WAGemStoneProductionErrorHandler, if I try to debug it | | in | | the | | good server, it shows the debug window just fine, showing all the | | stak an | | related values for each stack frame. But if I do the same with the | | bad | | server, i get debug window with a different error (not the one i'm | | trying to | | debug), like this: | | | | < http://forum.world.st/file/n4659840/localMethodAtError.jpg > | | | | | | | If you reply to this email, your message will be added to the | discussion below: | http://forum.world.st/Issues-setting-up-gemtools-debugger-tp4659840p4663355.html | | | To unsubscribe from Issues setting up gemtools debugger, click here . | NAML | | | View this message in context: Re: Issues setting up gemtools debugger | Sent from the GLASS mailing list archive at Nabble.com. | |
Re: Issues setting up gemtools debugger
|
|
Dale, I'm not 100% sure if I understand you correctly, but I guess they can be put down to the limitations, since i can debug it alright on the "good server". On Mon, Jan 14, 2013 at 4:04 PM, Dale Henrichs [via Smalltalk] <[hidden email]> wrote: Alejandro, |
Re: Issues setting up gemtools debugger
|
|
I guess I'm misunderstanding as well ... I thought your email had claimed that you could reproduce the bad behavior on both servers.
If there is still a "good server" and "bad server" when doing exactly the same operations on exactly the same continuation, then there is a bug we want to characterize .... Sorry about that... Dale ----- Original Message ----- | From: "keropotter" <[hidden email]> | To: [hidden email] | Sent: Monday, January 14, 2013 11:33:25 AM | Subject: Re: [GS/SS Beta] Issues setting up gemtools debugger | | | Dale, | | I'm not 100% sure if I understand you correctly, but I guess they can | be put down to the limitations, since i can debug it alright on the | "good server". | | | | | On Mon, Jan 14, 2013 at 4:04 PM, Dale Henrichs [via Smalltalk] < | [hidden email] > wrote: | | | Alejandro, | | Okay ... and presumably the errors that you are getting can be put | down to the limitiations on debugging continuations? | | | Dale | | ----- Original Message ----- | | From: "keropotter" < [hidden email] > | | To: [hidden email] | | | Sent: Monday, January 14, 2013 10:33:31 AM | | Subject: Re: [GS/SS Beta] Issues setting up gemtools debugger | | | | | | | | | | | | Hi, Dale! | | | | I'm not debugging the exact same stack. | | | | I've restored a copy of the production database into both servers | | so | | I have the same code and objects. | | | | After that, I manually produced the exact same error on both | | servers, | | so the stacks are different. | | | | Thank you very much! | | Alejandro | | | | | | | | | | | | | | | | | | On Mon, Jan 14, 2013 at 3:24 PM, Dale Henrichs [via Smalltalk] < | | | | [hidden email] > wrote: | | | | | | Alejandro, | | | | I'm going to start with the very first issue ... | | | | You say "But if I do the same with the bad server..." and I'm | | curious | | what you are talking about here. | | | | Are you trying to debug the same continuation as in the "good | | server", i.e., the EXACT same stack. | | | | Or are you tring to debug a continuation that was produced in the | | 'bad server" ... | | | | I ask, because there are limitations on how you can debug | | continuations as opposed to debugging errors directly in GemTools. | | I | | have not made it possible to do a debugger level for continuations | | and depending upon where you are in a stack, you may not be able to | | step either ... | | | | So at this point it is important to determine if you are looking at | | the same EXACT stack (restored from "good server") and that you are | | doing exactly the same things ... then we'll go from there ... | | | | | | Dale | | | | ----- Original Message ----- | | | From: "keropotter" < [hidden email] > | | | To: [hidden email] | | | | | Sent: Tuesday, December 18, 2012 8:17:31 AM | | | | | Subject: [GS/SS Beta] Issues setting up gemtools debugger | | | | | | | | | Here are the issues: | | | | | | 1) When I restore that DB to development servers and make an | | | error | | | happen | | | while using WAGemStoneProductionErrorHandler, if I try to debug | | | it | | | in | | | the | | | good server, it shows the debug window just fine, showing all the | | | stak an | | | related values for each stack frame. But if I do the same with | | | the | | | bad | | | server, i get debug window with a different error (not the one | | | i'm | | | trying to | | | debug), like this: | | | | | | < http://forum.world.st/file/n4659840/localMethodAtError.jpg > | | | | | | | | | | | | | | | If you reply to this email, your message will be added to the | | discussion below: | | http://forum.world.st/Issues-setting-up-gemtools-debugger-tp4659840p4663355.html | | | | | | To unsubscribe from Issues setting up gemtools debugger, click here | | . | | NAML | | | | | | View this message in context: Re: Issues setting up gemtools | | debugger | | Sent from the GLASS mailing list archive at Nabble.com. | | | | | | | | | If you reply to this email, your message will be added to the | discussion below: | http://forum.world.st/Issues-setting-up-gemtools-debugger-tp4659840p4663357.html | | | To unsubscribe from Issues setting up gemtools debugger, click here . | NAML | | | View this message in context: Re: Issues setting up gemtools debugger | Sent from the GLASS mailing list archive at Nabble.com. | |
Re: Issues setting up gemtools debugger
|
|
Dale, you're right, i couldn't get both servers to produce the same debug issues. I still have a good and a bad server. I meant that I'm taking the same steps on both servers to produce an error, and I can debug it alright on the good server, but I can't debug it on the bad one. Alejandro On Mon, Jan 14, 2013 at 4:40 PM, Dale Henrichs [via Smalltalk] <[hidden email]> wrote: I guess I'm misunderstanding as well ... I thought your email had claimed that you could reproduce the bad behavior on both servers. |
Re: Issues setting up gemtools debugger
|
|
Alejandro,
Okay, then I'd like to get to the bottom of this ... there really should be no difference between the two ... So if you could describe the process of reproducing and debugging the problems in more detail we'll start from there and move forward ... My first instinct is that you're doing something different on the bad server...my second instinct says that if must be related to how you are producing the bug in the first place ... So I'd like to get a better understanding of how you are reproducing the bug... Dale ----- Original Message ----- | From: "keropotter" <[hidden email]> | To: [hidden email] | Sent: Tuesday, January 15, 2013 11:56:20 AM | Subject: Re: [GS/SS Beta] Issues setting up gemtools debugger | | | | | Dale, you're right, i couldn't get both servers to produce the same | debug issues. I still have a good and a bad server. | | I meant that I'm taking the same steps on both servers to produce an | error, and I can debug it alright on the good server, but I can't | debug it on the bad one. | | Thank you! | Alejandro | | | | | On Mon, Jan 14, 2013 at 4:40 PM, Dale Henrichs [via Smalltalk] < | [hidden email] > wrote: | | | I guess I'm misunderstanding as well ... I thought your email had | claimed that you could reproduce the bad behavior on both servers. | | If there is still a "good server" and "bad server" when doing exactly | the same operations on exactly the same continuation, then there is | a bug we want to characterize .... | | Sorry about that... | | | Dale | | ----- Original Message ----- | | From: "keropotter" < [hidden email] > | | To: [hidden email] | | | Sent: Monday, January 14, 2013 11:33:25 AM | | Subject: Re: [GS/SS Beta] Issues setting up gemtools debugger | | | | | | | Dale, | | | | I'm not 100% sure if I understand you correctly, but I guess they | | can | | be put down to the limitations, since i can debug it alright on the | | "good server". | | | | | | | | | | On Mon, Jan 14, 2013 at 4:04 PM, Dale Henrichs [via Smalltalk] < | | | | [hidden email] > wrote: | | | | | | Alejandro, | | | | Okay ... and presumably the errors that you are getting can be put | | down to the limitiations on debugging continuations? | | | | | | Dale | | | | ----- Original Message ----- | | | From: "keropotter" < [hidden email] > | | | To: [hidden email] | | | | | Sent: Monday, January 14, 2013 10:33:31 AM | | | Subject: Re: [GS/SS Beta] Issues setting up gemtools debugger | | | | | | | | | | | | | | | | | | Hi, Dale! | | | | | | I'm not debugging the exact same stack. | | | | | | I've restored a copy of the production database into both servers | | | so | | | I have the same code and objects. | | | | | | After that, I manually produced the exact same error on both | | | servers, | | | so the stacks are different. | | | | | | Thank you very much! | | | Alejandro | | | | | | | | | | | | | | | | | | | | | | | | | | | On Mon, Jan 14, 2013 at 3:24 PM, Dale Henrichs [via Smalltalk] < | | | | | | | [hidden email] > wrote: | | | | | | | | | Alejandro, | | | | | | I'm going to start with the very first issue ... | | | | | | You say "But if I do the same with the bad server..." and I'm | | | curious | | | what you are talking about here. | | | | | | Are you trying to debug the same continuation as in the "good | | | server", i.e., the EXACT same stack. | | | | | | Or are you tring to debug a continuation that was produced in the | | | 'bad server" ... | | | | | | I ask, because there are limitations on how you can debug | | | continuations as opposed to debugging errors directly in | | | GemTools. | | | I | | | have not made it possible to do a debugger level for | | | continuations | | | and depending upon where you are in a stack, you may not be able | | | to | | | step either ... | | | | | | So at this point it is important to determine if you are looking | | | at | | | the same EXACT stack (restored from "good server") and that you | | | are | | | doing exactly the same things ... then we'll go from there ... | | | | | | | | | Dale | | | | | | ----- Original Message ----- | | | | From: "keropotter" < [hidden email] > | | | | To: [hidden email] | | | | | | | Sent: Tuesday, December 18, 2012 8:17:31 AM | | | | | | | Subject: [GS/SS Beta] Issues setting up gemtools debugger | | | | | | | | | | | | Here are the issues: | | | | | | | | 1) When I restore that DB to development servers and make an | | | | error | | | | happen | | | | while using WAGemStoneProductionErrorHandler, if I try to debug | | | | it | | | | in | | | | the | | | | good server, it shows the debug window just fine, showing all | | | | the | | | | stak an | | | | related values for each stack frame. But if I do the same with | | | | the | | | | bad | | | | server, i get debug window with a different error (not the one | | | | i'm | | | | trying to | | | | debug), like this: | | | | | | | | < http://forum.world.st/file/n4659840/localMethodAtError.jpg > | | | | | | | | | | | | | | | | | | | | | | | If you reply to this email, your message will be added to the | | | discussion below: | | | http://forum.world.st/Issues-setting-up-gemtools-debugger-tp4659840p4663355.html | | | | | | | | | To unsubscribe from Issues setting up gemtools debugger, click | | | here | | | . | | | NAML | | | | | | | | | View this message in context: Re: Issues setting up gemtools | | | debugger | | | Sent from the GLASS mailing list archive at Nabble.com. | | | | | | | | | | | | | | | | | | If you reply to this email, your message will be added to the | | discussion below: | | http://forum.world.st/Issues-setting-up-gemtools-debugger-tp4659840p4663357.html | | | | | | To unsubscribe from Issues setting up gemtools debugger, click here | | . | | NAML | | | | | | View this message in context: Re: Issues setting up gemtools | | debugger | | Sent from the GLASS mailing list archive at Nabble.com. | | | | | | | | | If you reply to this email, your message will be added to the | discussion below: | http://forum.world.st/Issues-setting-up-gemtools-debugger-tp4659840p4663365.html | | | To unsubscribe from Issues setting up gemtools debugger, click here . | NAML | | | View this message in context: Re: Issues setting up gemtools debugger | Sent from the GLASS mailing list archive at Nabble.com. | |
«
Return to GLASS
|
1 view|%1 views
| Free forum by Nabble | Edit this page |