|
The program in question was already loaded into the debugger. When the Run button was hit, I was on a statement in the subordinate program. Kirk Palmer IT Project Manager Walsworth Publishing Company, Inc wdsci-l-bounces@xxxxxxxxxxxx wrote on 08/17/2005 04:15:22 PM: > If you have a very long program it may take some time to load the source. > I don't think they load it all at once, but maybe in 1,000 line > chunks. Thought that shouldn't account for a 15 minute delay... > > Sam > > > > ---------------------------------------------------------------------- > > From: Kirk.Palmer@xxxxxxxxxxxxx > Reply-To: Websphere Development Studio Client for > iSeries<wdsci-l@xxxxxxxxxxxx> > To: wdsci-l@xxxxxxxxxxxx > Subject: [WDSCI-L] Integrated Debugger problem > Date: Wed, 17 Aug 2005 13:36:29 -0500 > >Hi all -- > > > >Version: 5.1.2.5 Build id: 20050622_0933. > > > >The last few days when I've been using the Integrated Debugger, the > >program that I'm debugging will lock up at a point. > > > >1. I start the debugger either manually, or with a Service Entry Point > >2. I set breakpoints (or use ones that I had set in previous sessions) > >3. I step into a subordinate program to debug that program > >4. After stepping a few times, I'll hit the Run button and the program > >will hang at the call to the subordinate program. > > > >Here is the call stack: > > Display Call Stack > > > > Program > > Rqs or > > Lvl Procedure Library Statement Instruction > > QCMD QSYS 0496 > > _CL_PEP CODE400_KP > > SOCI020KCP CODE400_KP 0000000600 > > SOCI022 QGPL 1200 0020 > > SOCI010 OBJLIB 1800 002A > > MNI000M MFGDBLIB 28200 0254 > > 1 QCMD QSYS 01B7 > > < EP_LOC001R CODE400_KP > > LOC001R CODE400_KP 0000017900 > > QTEVSIRF QSYS 0228 > > > >In this example, LOC001R is the program I'm debugging, and statement > 17900 > >is where the call to the subordinate program is. > > > >If I hit the Terminate button, Sys-Req 2 (ENDRQS) the job, and restart > it, > >the program will still hang at the call statement, even if I don't try > to > >run with debug. the only way to get it to run normally again, is to > >signoff and sign back on to my session. > > > >BTW, I was finally able to get it to release a few minutes ago (after > 15 > >minutes of hang time). The only thing I did was click around in the > >source pane, the debug stack pane, and the breakpoints pane. I don't > know > >why it finally released. > > > >I've only noticed this the past 2 days. > > > >Any help would be appreciated. > > > >Thanks, > >Kirk Palmer > >IT Project Manager > >Walsworth Publishing Company, Inc > >-- > >This is the Websphere Development Studio Client for iSeries (WDSCI-L) > mailing list > >To post a message email: WDSCI-L@xxxxxxxxxxxx > >To subscribe, unsubscribe, or change list options, > >visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > >or email: WDSCI-L-request@xxxxxxxxxxxx > >Before posting, please take a moment to review the archives > >at http://archive.midrange.com/wdsci-l. > -- > This is the Websphere Development Studio Client for iSeries (WDSCI- > L) mailing list > To post a message email: WDSCI-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > or email: WDSCI-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
