kX>X>by nameby namevabldd kJ[AX>X>X>'8Y./r/lib/A k<XX>X>X>';X./lpp_names/msg/4 R I xlfcmp.idebug.html.en_US { xlfcmp.idebug.html.en_US 8.1.1.0000 01 N U en_US Distributed Debugger Documentation for XL Fortran - U.S. English [ % /etc/vatools/xlf 16 /usr/lib/objrepos 72 /usr/share/man/info/en_US/xlf/html/debugger 320 /usr/share/man/info/en_US/xlf/html/debugger/concepts 144 /usr/share/man/info/en_US/xlf/html/debugger/ref 168 /usr/share/man/info/en_US/xlf/html/debugger/tasks 336 /usr/share/man/info/en_US/xlf/html/debugger/ui 848 /usr/share/man/info/en_US/xlf/html/debugger/images 400 INSTWORK 192 152 /lpp/xlfcmp.idebug.html.en_US 24 % % % IY35608,IY37280,IY37809,IY37954,IY38175,IY38462,IY38483,IY38498,IY39359,IY39446,IY39739,IY39858,IY39897,IY39898,IY40212,IY40286,IY40711,IY40877,IY41052,IY41071,IY41099,IY41147,IY41310,IY41452,IY41467,IY41658,IY41837,IY41838,IY43238,IY43332,IY43718,IY45718,IY45719,IY45720,IY43616 12 % ] } k:_AX>X>X>'8Y./usrna/A k`AX>X>X>'8Y./usr/lpps/msg/A kaAX>X>X>';=./usr/lpp/xlfcmp.idebug.html.en_US/A lbm X>X>X>';>./usr/lpp/xlfcmp.idebug.html.en_US/liblpp.ap/m   /e ghilmnrstu.4=abcdfop",SU_xy0123567:EFILkvwz89$#-CR>DOTY[]`j|&;ABMPW^!#T-)  XK@;`i,x붢i!!0]?{ï}g8B$? ĀuQ4붢i<d46; H]OQ8j&8KOĞĦ2XAA0@01 P`0oF3dÀ0R9HadBo0^  !a@@I'``PB0 _89?)>9HadBo0Y x}H@xSW#h< cCxJ2c@` H,IZ\c-)9HadBo0ZSW#h< cC}.ډef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?V J١ћ dxTV\.[= .4\:̚p O VcT9YzyX@02CѼ@ @)?kKrE1!4\ :̚\-F JjqEežЫxтsOͣɩW 1@d.N O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт`` WfFnĂĥ58¢tLyUht9dԫi@B'}+1OM=?IOz7'iqVZ(x<>$ '6&\(sO88%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł75vhtfI 8TV\.[= .4\:̚p<Bef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?V ']+q)MN0]8zo0]i9u5*Cy( )pcG+1O+$SaaIZ\c-)9HadBo0Z,`ptC7ebIbRaQYpqo<*4`rsh2jU‡4P) S>ᕘǧ&Vcr^VI$=B洸+-Z$ '6&\(sO88%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł75vhtfH 0PO# ˅Ӌ}1VKGYR9bD.N O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт``iWfFnăTV\.[= .4\:̚p<!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+O4:3vV$RaQYpqo<*4`rsh2jU‡4P! S>ᕘǧ&Vcr^VI$=B洸+-Z'6&\(sO88%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7']+ H ĥ58¢tLyUht9dԫiR'}+1OM=?IOz7'iqVZ(x<>$ '6&\(sO88%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł75vhtfH(JSS*+.N-Ǟ[ƌC}.NmfMJPq!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+]+JjqEežЫxтsOͣɩW 1A.N O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт`d]+  bRaQYpqo<*4`rsh2jU‡4P)pcG+1O+$SaaIZ\c-)9HadBo0Z,O4:3vV$0rA\JSS*+.N-Ǟ[ƌC}.NmfMJPq8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7]+ĥ58¢tLyUht9dԫʹeef1A ǧ܁ו'=a@X洸+-Z$ $ '6&\(m(ѦM\@A =?!4r:I%?!V59Yh|CyDfMD.Ni@IWfFnĂดTV\.[= .4\:̚pPyF9\ Bef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?V']+)MN0]8zo0]i9u5*FmF0ӌr!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+ݕRaQYpqo<*4`rsh2jUA2a|\@A =?!4r:I%?!V59Yh|CyDfMD.NiiWfFnāดTV\.[= .4\:̚pPyFi"[\@A =?!4r:I%?!V59Yh|CyDfMD.NiAݕ$ JjqEežЫxтsOͣɩW 5h4i@98%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7ݕ$ RaQYpqo<*4`rsh2jUA2`##H\@A =?!4r:I%?!V59Yh|CyDfMD.Ni`ħ]+ ดTV\.[= .4\:̚pPyF!c'}+1OM=?IOz7'iqVZ(x<>$ '6&\(m(Ѧ\@A =?!4r:I%?!V59Yh|CyDfMD.NiIO4:3vV$ 1)MN0]8zo0]i9u5*FmF0AeD.N O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт``a]+  bRaQYpqo<*4`rsh2jUA2`-Bef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?V ']+H #' ˅Ӌ}1VKGYRj6єh">2'}+1OM=?IOz7'iqVZ(x<>$ $ $ $ $ '6&\*}@OB"Bef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?VO4:3vV$ #ĥ58¢tLyUht9dԫBϨkBef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?V 5vhtfI 0 _0LJSS*+.N-Ǟ[ƌC}.NmfMJT,8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7ݕLJSS*+.N-Ǟ[ƌC}.NmfMJT,"\Bef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?V J١ћ 0`? ˅Ӌ}1VKGYR >`@8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7ݕTV\.[= .4\:̚pY'}+1OM=?IOz7'iqVZ(x<>$ '6&\*}@<֐8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7ݕxTV\.[= .4\:̚pY!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+O4:3vV$   ˅Ӌ}1VKGYR >`%d.N O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт```@`IWfFnĂRaQYpqo<*4`rsh2jU¡g '}+1OM=?IOz7'iqVZ(x<>$ ᕘǧ&Vcr^VI$=B洸+-Z'6&\*E:5# p,'}+1OM=?IOz7'iqVZ(x<>$ '6&\*E:5#"Bef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?VO4:3vV$1)MN0]8zo0]i9u5*R.!ѩlnFBef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?V 5vhtfI &%) cBF >'6&\*E:5##+xy S>ᕘǧ&Vcr^VI$=B洸+-Z'6&\*E:5# ɯ!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+$C7eb@q)MN0]8zo0]i9u5*R.!ѩ!5H\@A =?!4r:I%?!V59Yh|CyDfMD.NiiWfFnĂTV\.[= .4\:̚pԌ67&Bef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?VO4:3vV$8 ĥ58¢tLyUht9dԫHF`eH)pcG+1O+$SaaIZ\c-)9HadBo0Z,O4:3vV$@0N%) cBF >'6&\*E:5# @'}+1OM=?IOz7'iqVZ(x<>$ ᕘǧ&Vcr^VI$=B洸+-Z'6&\*E:5# 1'}+1OM=?IOz7'iqVZ(x<>$ ᕘǧ&Vcr^VI$=B洸+-Zᕘǧ&Vcr^VI$=B洸+-Z'6&\*E:5# Z(8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7Sݕ$ bRaQYpqo<*4`rsh2jU¤\CR0@ը<8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7']+ 1)MN0]8zo0]i9u5*R.!ѩ j(8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7']+H@1?&%) cBF >'6&\*E:5# r'Bef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?V 5vhtfH( 7 JjqEežЫxтsOͣɩW qH8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7']+H bRaQYpqo<*4`rsh2jU¤\CR0Ab$.N O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт``$C7ebAAA\JSS*+.N-Ǟ[ƌC}.NmfMJT@A =?!4r:`dyX,( R֗eGcBiu59[ƌ ˅Ӌ}1VKGYR6T89'}+1OM=?IOz7'iqVZ(x<>$ $ '6&\*lq:!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+ݕดTV\.[= .4\:̚pa!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+$?jXrAB?\JSS*+.N-Ǟ[ƌC}.NmfMJTS0!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+O4:3vV$A?\JSS*+.N-Ǟ[ƌC}.NmfMJTS0Z$.N O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт``d5vhtfI$TV\.[= .4\:̚pa8bBef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?V 5vhtfH9 @.%) cBF >'6&\*lqic\@A =?!4r:I%?!V59Yh|CyDfMD.Ni O4:3vV$#ĥ58¢tLyUht9dԫM31A'}+1OM=?IOz7'iqVZ(x<>$ '6&\*lq!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+O4:3vV$7 JjqEežЫxтsOͣɩW *fdah8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7ݕ\JSS*+.N-Ǟ[ƌC}.NmfMJTS1 S>ᕘǧ&Vcr^VI$=B洸+-Zᕘǧ&Vcr^VI$=B洸+-Zᕘǧ&Vcr^VI$=B洸+-Zᕘǧ&Vcr^VI$=B洸+-Z$ '6&\*lq4H\@A =?!4r:I%?!V59Yh|CyDfMD.Nidݕĥ58¢tLyUht9dԫM31 S>ᕘǧ&Vcr^VI$=B洸+-Z$ ᕘǧ&Vcr^VI$=B洸+-Z$ P!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+']+H JjqEežЫxтsOͣɩW *f"*2!rpJ2c@$yXX`hR֗eGcBiu59[ƌo+']+HON%) cBF >'6&\*l 萹8%?YzPBhf1 udJCѼ,04)?kKrE1!4\ :̚\-F Oł7 5vhtfH@  ˅Ӌ}1VKGYR6TEBef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?VH١ћ @_`xTV\.[= .4\:̚pa])pcG+1O+$SaaIZ\c-)9HadBo0Z, O4:3vV$ ĥ58¢tLyUht9dԫ1Ū@A =?!4r:`dyX,( R֗eGcBiu59[ƌ ˅Ӌ}1VKGYR=FHS O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт`` @TC7ebAA@%) cBF >'6&\)-Wz@A =?!4r:I%?!V59Yh|CyDfMD.Ni@SݕxTV\.[= .4\:̚p8\ia`䐦@A =?!4r:I%?!V59Yh|CyDfMD.NiIO4:3vV$ RaQYpqo<*4`rsh2jU˜q8"ef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?VH (B١ћ `  ˅Ӌ}1VKGYR=PS O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт``"Sݕ$ĥ58¢tLyUht9dԫ1ŪOTq a)pcG+1O+$SaaIZ\c-)9HadBo0Z,١ћ P/ ˅Ӌ}1VKGYR=AHS O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт````0DC7eb@'ĥ58¢tLyUht9dԫ1ŪOP|,S>ᕘǧ&Vcr^VI$=B洸+-Zᕘǧ&Vcr^VI$=B洸+-Z$ '6&\)-WzES>ᕘǧ&Vcr^VI$=B洸+-Z'6&\)-WzXyd)}+1OM=?IOz7'iqVZ(x<>$ '6&\)-Wz! a)pcG+1O+$SaaIZ\c-)9HadBo0Z, ?jX A_%) cBF >'6&\)-Wz @D)}+1OM=?IOz7'iqVZ(x<>$ '6&\)-Wzm40ef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?VH ?jX``@pJjqEežЫxтsOͣɩW cUƞ[`BxJ2c@$yXX`hR֗eGcBiu59[ƌo+O4:3vV$OJjqEežЫxтsOͣɩW cUƞ[dBxJ2c@$yXX`hR֗eGcBiu59[ƌo+O4:3vV$ RaQYpqo<*4`rsh2jU˜q0ef1A ǧ܁וI)FФ.1ELJr$02j!rsH-?VO4:3vV$ P ˅Ӌ}1VKGYR=QA)}+1OM=?IOz7'iqVZ(x<>$ '6&\)-Wy,|S O VcT9YzyY$o+ OQhLx}H@x<"C&'4xт````IWfFnĂ$ $ '6&\(sO89$T ˅Ӌ}1VKGYR9b\*qEežЫxтsOͣɩW 1@.NI8¢tLyUht9dԫiBH\*qEežЫxтsOͣɩW 1@.NI8¢tLyUht9dԫ1X'$aQYpqo<*4`rsh2jU–ڋi EN0]8zo0]i9u5*Cy( "TV\.[= .4\:̚p<BS*+.N-Ǟ[ƌC}.NmfMJPq!rrH cBF >'6&\(sO89$T ˅Ӌ}1VKGYR9bH\*qEežЫxтsOͣɩW 1@d9$T ˅Ӌ}1VKGYR9b\*qEežЫxтsOͣɩW 1@`.NI8¢tLyUht9dԫi0'$aQYpqo<*4`rsh2jU‡4P"TV\.[= .4\:̚p<!rrH cBF >'6&\(sO89$T ˅Ӌ}1VKGYR9b\*qEežЫxтsOͣɩW 1@.NI8¢tLyUht9dԫiH\*qEežЫxтsOͣɩW 1@.NI8¢tLyUht9dԫir'$aQYpqo<*4`rsh2jU‡4PA EN0]8zo0]i9u5*Cy(BS*+.N-Ǟ[ƌC}.NmfMJPq9$T ˅Ӌ}1VKGYRj6єREN0]8zo0]i9u5*FmF2BS*+.N-Ǟ[ƌC}.NmfMJQ.NI8¢tLyUht9dԫʹe4N1BS*+.N-Ǟ[ƌC}.NmfMJQ'6&\*zH cBF >'6&\*}@N1 BS*+.N-Ǟ[ƌC}.NmfMJT,#"BS*+.N-Ǟ[ƌC}.NmfMJT,b!rrH cBF >'6&\*}@N1dBS*+.N-Ǟ[ƌC}.NmfMJT,8"TV\.[= .4\:̚pY = EN0]8zo0]i9u5*Pì9$T ˅Ӌ}1VKGYR >a5.NI8¢tLyUht9dԫBϨ r%d.NI8¢tLyUht9dԫBϨ z:D.NI8¢tLyUht9dԫBϨ |$9$T ˅Ӌ}1VKGYR >`kH\*qEežЫxтsOͣɩW P0A1'$aQYpqo<*4`rsh2jU¡g D,"TV\.[= .4\:̚pY#+D"TV\.[= .4\:̚pY$0'$aQYpqo<*4`rsh2jU¡g 4 EN0]8zo0]i9u5*Pd!rrH cBF >'6&\*E:)"TV\.[= .4\:̚pԌ:nE.NI8¢tLyUht9dԫHFat-D.NI8¢tLyUht9dԫHFapyp!rrH cBF >'6&\*E:5# 1.NI8¢tLyUht9dԫHFa EN0]8zo0]i9u5*R.!ѩig9$T ˅Ӌ}1VKGYR"]"TV\.[= .4\:̚pԌ4@<"TV\.[= .4\:̚pԌ4[9$T ˅Ӌ}1VKGYR"uq EN0]8zo0]i9u5*R.!ѩ! BS*+.N-Ǟ[ƌC}.NmfMJTtjFBS*+.N-Ǟ[ƌC}.NmfMJTtjFFY.NI8¢tLyUht9dԫHFayh"TV\.[= .4\:̚pԌr q EN0]8zo0]i9u5*R.!ѩlnFBS*+.N-Ǟ[ƌC}.NmfMJTtjFFV'$aQYpqo<*4`rsh2jU¤\CR0ܚ'$aQYpqo<*4`rsh2jU¤\CR0B2j9$T ˅Ӌ}1VKGYR"\*qEežЫxтsOͣɩW qH EN0]8zo0]i9u5*R.!ѩlnB9$T ˅Ӌ}1VKGYR"9$T ˅Ӌ}1VKGYR"9'$aQYpqo<*4`rsh2jU¤\CR0!rrH cBF >'6&\*E:5# .NI8¢tLyUht9dԫHFa󅨅"TV\.[= .4\:̚pԌ4>a"TV\.[= .4\:̚pԌ4<@H\*qEežЫxтsOͣɩW qH !rrH cBF >'6&\*E:5# "'$aQYpqo<*4`rsh2jU¤\CR0@N\*qEežЫxтsOͣɩW qHq9$T ˅Ӌ}1VKGYR"P9$T ˅Ӌ}1VKGYR"Q\*qEežЫxтsOͣɩW qHVBS*+.N-Ǟ[ƌC}.NmfMJTtjF.NI8¢tLyUht9dԫHF`D\*qEežЫxтsOͣɩW qH9$T ˅Ӌ}1VKGYR"!rrH cBF >'6&\*lI8¢tLyUht9dԫM30D"TV\.[= .4\:̚paǐ9$T ˅Ӌ}1VKGYR6T8ãr!rrH cBF >'6&\*lq:!rrH cBF >'6&\*lq\*qEežЫxтsOͣɩW *f`2$.NI8¢tLyUht9dԫM31ŢBS*+.N-Ǟ[ƌC}.NmfMJTS0Z1!rrH cBF >'6&\*lqic\*qEežЫxтsOͣɩW *fc΂$.NI8¢tLyUht9dԫM315.NI8¢tLyUht9dԫM320H\*qEežЫxтsOͣɩW *f"!rrH cBF >'6&\*lqb$.NI8¢tLyUht9dԫM30BS*+.N-Ǟ[ƌC}.NmfMJTS0 Y!rrH cBF >'6&\*lq0!rrH cBF >'6&\*lq(9$T ˅Ӌ}1VKGYR6T8.NI8¢tLyUht9dԫM30<'$aQYpqo<*4`rsh2jU¦ʙ{D"TV\.[= .4\:̚pa\*qEežЫxтsOͣɩW *fay.NI8¢tLyUht9dԫM31vH\*qEežЫxтsOͣɩW *fc^b$.NI8¢tLyUht9dԫM31q EN0]8zo0]i9u5*SeLÌ"BS*+.N-Ǟ[ƌC}.NmfMJTS09$T ˅Ӌ}1VKGYR6T8ț9$T ˅Ӌ}1VKGYR6T8>9$T ˅Ӌ}1VKGYR6T8Ƞ\*qEežЫxтsOͣɩW *fc..NI8¢tLyUht9dԫM3204'$aQYpqo<*4`rsh2jU¦ʙ EN0]8zo0]i9u5*SeLÌ D"TV\.[= .4\:̚pa# <"TV\.[= .4\:̚pb/099$T ˅Ӌ}1VKGYR6TE@֐9$T ˅Ӌ}1VKGYR6TE9!rrH cBF >'6&\*l@"TV\.[= .4\:̚pb/"'$aQYpqo<*4`rsh2jU¦ʙ2 EN0]8zo0]i9u5*SeL_AD.NI8¢tLyUht9dԫM30.NI8¢tLyUht9dԫ1Ū*qEežЫxтsOͣɩW cUƞPy)aQYpqo<*4`rsh2jU˜qhq a"TV\.[= .4\:̚p8\ia`䐦*qEežЫxтsOͣɩW cUƞEN0]8zo0]i9u5*Lqj <0S*+.N-Ǟ[ƌC}.NmfMJSZ4H*qEežЫxтsOͣɩW cUƞPy)aQYpqo<*4`rsh2jU˜q>y a"TV\.[= .4\:̚p8\iq!L=$T ˅Ӌ}1VKGYR<Ù!L=$T ˅Ӌ}1VKGYR<ÙBzH cBF >'6&\)-Wy!L=$T ˅Ӌ}1VKGYR'6&\)-Wz @D)aQYpqo<*4`rsh2jU˜q0S*+.N-Ǟ[ƌC}.NmfMJSZ4Bi a"TV\.[= .4\:̚p8\iꅶ)aQYpqo<*4`rsh2jU˜q*qEežЫxтsOͣɩW cUƞ"EN0]8zo0]i9u5*LqjBzH cBF >'6&\)-Wy(0S*+.N-Ǟ[ƌC}.NmfMJSZ4#$N1D)aQYpqo<*4`rsh2jU˜q#c!L=$T ˅Ӌ}1VKGYR<>D)aQYpqo<*4`rsh2jU˜q́p!L=$T ˅Ӌ}1VKGYR=F BzH cBF >'6&\)-Wz@EN0]8zo0]i9u5*Lqjj#SH@/A (07~9HadBo0Y``FyrAƇ4 58š) E cBF >'6&\0P@$ ˅Ӌ}1VKGYRj6єp2IMN0]8zo0]i9u5*P0pjqEežЫxтsOͣɩW q aQYpqo<*4`rsh2jU¦H 58¢tLyUht9dԫ1Ū/D  HOI?('iu59[ƌAqr,$_R䃓``_D8@ p k!YQ Ehd#.@sO5Ȑìɨ"4`B2 9HadBo0Yz(FCXL0 9HadBo0Y x}H@xr$02j!rsH,4\ :̚\-F ", 9HadBo0YqȰ  U kcAX>X>X>';P./usr/lpp/xlfcmp.idebug.html.en_US/inst_rootp/A knJdm|f>{f>X>';Q./usr/lpp/xlfcmp.idebug.html.en_US/inst_root/liblpp.a/m 580 0 68 68 0 386 580 0 1054842339 1703 8100 640 35 xlfcmp.idebug.html.en_US.cfgfiles.S` # 10/16/01 1.1 # # COMPONENT_NAME: xlf.pkg # # FUNCTIONS: none # # ORIGINS: 27 # # # (C) COPYRIGHT International Business Machines Corp. 1999 # All Rights Reserved # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # /etc/vatools/xlf/help.cfg user_merge 60 0 68 0 0 0 0 0 ` 1 68 xlfcmp.idebug.html.en_US.cfgfiles.S4\: k gAX>X>X>';T./etc/vatools/xlfdebug./A kfh$yf> `>X>';U./etc/vatools/xlf/help.cfgl.en_/$HTML_HOSTNAME=file:///usr/share/man/info/en_US/xlf/html/ CGI_BIN_DIR=cgi-bin HELP=/usr/share/man/info/en_US/xlf/html/ HELP_EXE=vahwebx.exe #The following should be changed to something else for a second instance, e.g. vajava3a. INSTALL_INSTANCE=der8 #Variables used by the help client code itself START_NETQ_DAEMON=0 START_LITE_DAEMON=0 START_DBCSNETQ_DAEMON=0 ZIPPED_WEB=0 #Uncomment the following to point to a specific browser: #HTML_BROWSER="H:\Programs\Netscape\Communicator\Netscape.exe" HTMLHELP_HIDDEN=1 le Con kWoAX>X>X>';k./usr/share/man/info/en_US/xlf/html/debuggerlib/A kNp$' yf>_>X>';l' ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg21.htm/$
ExpandConcepts
ExpandTasks
ContractReference
  Documentidebug command
  Documentirmtdbgc command
  DocumentStep commands
  DocumentOptional breakpoint parameters
  DocumentProgram profiles
  ContractSupported expressions
   ExpandFortran expressions supported
  ExpandCompiler options for debugging
  ExpandEnvironment variables
  ExpandLimitations
 kƑq$ yf>_>X>';m ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg22.htm/$
ExpandConcepts
ExpandTasks
ContractReference
  Documentidebug command
  Documentirmtdbgc command
  DocumentStep commands
  DocumentOptional breakpoint parameters
  DocumentProgram profiles
  ExpandSupported expressions
  ContractCompiler options for debugging
   DocumentFortran compiler options
  ExpandEnvironment variables
  ExpandLimitations
imit lr$|yf>_>X>';n% ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg23.htm/$     "<=>at/cdegilnoprs bfmv.012h&,45;ADEHuz#3BFT_wx67CGIPRSk9LNU8VyOS6rHQC( A MK/( (P@MIl[@0BA5C$:L0T,d_[UcBڬGf_1jnW's"n oZd_>.oV"$Ӕ?V)%0KN7l <ߣAD^fh3~/7+7NPHPYJ&*c,Rbf8,g%[~/7+7mb)O9A_0 =,->mAIH$$@ !BFUBHTE7G37vٽ<ߢK-M>d_{}-ⓔVT!0S)er5Hqĩd?(5)-I|ũ^ԝ̋3l7+N x aio OF$A$(FU^y;+7mѶo foѠ"/ z4yDZ}Iȿ['($[k)RCL`|LL!S@o%{Rw2/Ͳ\ߘE82I(2 ~)?w7ߩh FUWwW5vٽfhf"7GI|ũ^ԝ̋/oRr@0RA K+C%K&A8IoߢK-M>d_d1XpdNPdK O[}?R(oR6 '* $ !#|?$'mCOvٽfhf"7GI|ũ^ԝ̋/oRr@A$:L0TY\Rq*Y5< q K~_1jnW's"n %S$:r `@zXZ}gGs}-I9PI&A@9Pq+bcfz64EvoF37Srϩ;p^Kx y a(!C !Ba0>R&&jLJ@JMO3򃁯梶~/7+7mb)O9A_0 =,->h JAcz64EvoF37Srϩ;p^Kx GI9@0`P`YJ&*c,Rbfxtd?(8j+lݷSrϩ;pf.oV"$Ӕ?V)ba.͌J@7G37vٽ<ߢK-M>d_{}-ⓔ,Uh3376 '(PBD$:L0TY\Q o@JMO3W77m$bܯsNEKImAIH$$@bv V`4:fmGh;HލF.f_1jnW's"n o+me*Ht`I8Tjym$bܯsNEKId_{}-ⓔ0!Ba0>R&&jRɩ~Pk R[Srϩ;p^.oV"$Ӕ?VO;oԍIʂI4~DCCXh Ppu7G37vٽ~ix]ѣ$bܯsNE)9A@q$:L0TY\Rq*Y5< q K~_1jnW's"n %S$:r `@zXZ}gGs}-I9PI&V @ `P(8( fz64EvoFߣAD^fh3~/7+7NPP!Ba0>R&&jRɩ~Pk R[Srϩ;p^.oV"$Ӕ?VO;oԍIʂI4!DCCXh 7mѶo foѠ"/ z6"7GI|ũ^ԝ̋/oRrEVT!0S)er5Hqĩd?(5)-I|ũ^ԝ̋/l7+N x aio OF$A$ A@Uhhp P`"fmGh;HލF.f_1jnW's"n oYJ&*c,Rbf8,g%[~/7+7b)O9A_0 =,->mAIH$$@g @Uhhp P` @p7mѶo foѠ"/ z4yDZ}Iȿy a(!CDkme*Ht`ISkvߢK-M>d_d1XpdNPdK OZRnllލ|4{7 Nوrl|h@l> kĒs$Fyf>_>X>';pF./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg24.htm/$
ExpandConcepts
ExpandTasks
ContractReference
  Documentidebug command
  Documentirmtdbgc command
  DocumentStep commands
  DocumentOptional breakpoint parameters
  DocumentProgram profiles
  ExpandSupported expressions
  ExpandCompiler options for debugging
  ExpandEnvironment variables
  ContractLimitations
   DocumentRemote debug limitations
   DocumentFortran debug limitations
> l>ut$yf>_>X>';q ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg25.htm/$    "<>aent=cdgiloprs /bfmv.02h&,134;AFHuxz#5DE67Ckw89yLORSTP~Rb,lq0p i $HX\kWƐ "D !F`urL&[qW$ljX4DW ũ Q34Û.^-IOb]z >BX(f&Vqt?ƯuDEz ZƟcfŽ+M!cDDDV@i&咂 _!Fa9EbuOv8BTL/ p"n˯DRxlط8D0'+ /}GɰǀϡCjX4DW ũ{stK; pi r`|'|vw|i&i#@*mN+BOaEg"ˡCjX^КcDEz ZƟcfŽ+M!4( r5q*+BTL/ f4DRxlط8D0'+ /}Gɺrw'g~ viv;lt?u^"+`CC,hDRxlط8Yi &E&c0{iQXx0f1~i0o|z ZƟcfŽ%A8}49XPY{>MG㓾i;;`[KACS`S;;pk a[t?u^"+`CC,hDRxlط8Yi 7J)0CqsJ䡇1H +{Ԟ40v-0=,?L* )łjQn?I߽ݤ]MKkJE4DW8&X^/كonq; H@͍YݤCJH@~PP4( r5q*+t1H an˯DRxlط8D0'+ /}Gɰ kXF5t?ƯuN! ^КcDEz ZƟcfŽ+M! L-I9d/ ҊL#\a0Ң:'@ Q34v|Ax'>{s*wbC5e6{C{|<5cQC.X" =4?`CC. =4?ƈAx'>{s uVBnR`9 ׏C!*&c3Vע ũ{s uVB 7J)0CqsJ䡇1H +{Ԟ40v-05,?L* )łjQn?I߽ݤ]KƈMxkZ~49׽Lcus|t?ƯuN! 4DW ũ{s uV@Y""+ [HrA  _7J)0CqsJp_@D^/كonqg|=AaPNM!NV,3V^`~-Ng^9XB?u^"+`CC,hDRxlط84DDEd viY(!" 򀂂&E&c0{iQXxݎ1H9țԞ40v-0=,?L* )łjQlTR=L5Br t8)v kKu$yf>_>X>';s./usr/share/man/info/en_US/xlf/html/debugger/index.htmt/$ Distributed Debugger for XL Fortran <body> <p>This page uses frames, but your browser does not support them.</p> </body> ~P"n kvv$yf>_>X>';t./usr/share/man/info/en_US/xlf/html/debugger/hglegal.htm/$ Legal Notices

Notices

Note to U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this Documentation in other countries. (In this notice, Documentation includes the product, in whole or in part, (including but not limited to source code files and object code files) and its associated materials whether in electronic or print form.) Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this Documentation. The furnishing of this Documentation does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Lab Director
IBM Canada Ltd. Laboratory
8200 Warden Avenue
Markham, Ontario, Canada L6G 1C7

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this Documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. 1997, 2002. All rights reserved.

Programming interface information

Programming interface information is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Trademarks and service marks

The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, or other countries, or both:

  • AFS
  • DB2
  • DB2 Extenders
  • DB2 Universal Database
  • CICS
  • IBM
  • IMS
  • OS/390
  • OS/400
  • VisualAge
  • WebSphere
  • WorkPad

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

ActiveX, Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States, or other countries, or both.

UNIX is a registered trademark of The Open Group

Linux is a registered trademark of Linus Torvalds.

Other company, product, and service names, which may be denoted by a double asterisk(**), may be trademarks or service marks of others.

(c) Copyright IBM Corp. 2000, 2002. All Rights Reserved.

Th kFtw$yf>_>X>';v./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg1.htm/$
ExpandConcepts
ExpandTasks
ExpandReference
u kx$yf>_>X>';w./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg10.htm/$
ExpandConcepts
ContractTasks
  ExpandEstablishing a debugging environment
  ExpandPreparing a program for debugging
  ContractStarting the debugger
   DocumentStarting the debugger for local debugging
   ExpandStarting the debugger for remote debugging
   DocumentStarting the debugger user interface daemon
   DocumentAttaching to a local running process
   DocumentAttaching to a remote running process
  ExpandWorking with breakpoints
  ExpandControlling program execution
  ExpandInspecting data
  ExpandPostmortem debugging
ExpandReference
ava ky$yf>_>X>';x./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg11.htm/$
ExpandConcepts
ContractTasks
  ExpandEstablishing a debugging environment
  ExpandPreparing a program for debugging
  ExpandStarting the debugger
  ContractWorking with breakpoints
   ExpandSetting breakpoints
   DocumentViewing set breakpoints
   DocumentModifying breakpoint properties
   DocumentEnabling and disabling breakpoints
   DocumentDeleting a breakpoint
  ExpandControlling program execution
  ExpandInspecting data
  ExpandPostmortem debugging
ExpandReference
iz lꂒz$yf>_>X>';yR ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg12.htm/$    "<=>antcdegiloprs /bfmv.012h&,3;AHuxz#4EFk589CDSw7PRy6ITWj~Ra,1lu7 Q& Zr @@"rHZ 8u!k{t؈2ήM݃D@^x/VϱbR.@PphrNBEENRLEjP&;\*&cW prܯ<Rzك1onzQb2.B\X0RZ=Fd7C` h<Rzك1on) ( 84DDEl r Y'!"C󔢓1CD=ƹQZ<~I:TLƯ@fwM>yZ>{w(wrj6^ }݃W/P|"+Ԟ6`[۽br;JEȑ"'nA7!$$/1CD=ƹQZ<~IJ1ǜ+Ԟ6`[۽bg|=APN!.V) -l-OLl*89R;>P4DWx"^x/VϱbR.DSDDDV Œr@YQI"\J?$gkDjPjO\0f-ޱYDX'L+V Qp + s* c -)W&݃DEy{B(> jO\0f-ޱ9["HDDDV Œr$@q~PHQI"\J?$gkDjPjO\0f-ޱYDX'L+V Qpw-t?(v ^"+πCCh<Rzك1on)"-&1d_&rR`8u*+R6Q37x>yZ>{wVQ,5* "%Ճ!em  W&x!KX|5{h>hE"^Icf Ž'+c\DDDV Œr_*rR`8u*+R1J irܯ<Rzك1on%A:d\Z`,z3;ŭ\kiP/ΡCj`^|Њϕ^!4DW թ=slzlvq'nA7!$$H/S1CD=ƹQZ<~IJ1ǜ+Ԟ6`[۽brg|=APN!.V) -lr`#A-bC`" =?+πCCh<Rzك1on) 9QI"\J?$0t_܀0YH<Rzك1on%A:d\Z`,zLw r x%wkR_8ɍvCP|5{h>hE/P|"+Ԟ6`[۽br;JE81CD=ƹQZ<~I`Q3`9^x/VϱbK; Etȹ r`HYhg+cGܙsK CCCZLx0-"ab]P?(v ^"+πCC =?z'}3Xґr$)E&cX{r(xҢf5re#r^Icf Ž'(wrj6V뒏3;0-&/EN5 C7a11.Ҩ}ϔ?v ^!^|ЊσDEyZ>{wNViH*rR`8u*+R; *&cW ; R;+Ԟ6`[۽brg|=APN!.V) -ll~(3܂n^ x@/WSZW&cab]P?(v ^"+πCC =?z'}3Xґr(NRLEjP'aDjaG|yZ>{wNQ,5* "%Ճ!em%rfw`[M/\"W&6%UC`" =?+πCCh<Rzك1on) 󔢓1CD=ƹQZ<~I`Q3`9^x/VϱbK; Etȹ r`HYhg+cGܙsK xcC-r` -)C3 AC}L?(v ^"+πCCh<Rzك1on) `pphrNBDDRLEjP&;\*&cW prܯ<Rzك1on%A:d\Z`,zj ݃DEy{B(> jO\0f-ޱ9[" N [܂nCIH0q~PHrR`8u*+R6Q37x>yZ>{wVQ,5* "%Ճ!emlz \ϔ?v DEyZ>{wN [܂nCIH8( !:b!5ʊԡMv:TLƯ@<^x/Vϱb%A:d\Z`,z"a.P"Arial lx{$yf>_>X>';{ ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg13.htm/$    "<>at=cdegilnoprs /bfmv.012h#&,3;AHxz48EFku59CI67DPwySTWRzS.r?!GsH(ض -h @pyȿ`\XjL+I* V|ӥQt>ƭZ^1ji\s"ignH M!%(HqzP(D,r&VV)1:3rԲg49 >uuϞw2/Ƙ"7|V i iai՟& "acV֢D^C,oj9xũs̋uRM"DM!%( ^ C<`sJ&#G K&~3M `Q7C֣Zi>yȿaWDԘW'HT K N6 \EВ*Rڮ9%C.XհfZ^1ji\s"ignH@loI408(C<`sJ&#G K&~3M `Q7C֣Zi>yȿaWDԘW'HT K N6`| +t$J]acQ`"/ 7bNE )&  67Y$CJP@DMW!B`a09ebڣ?0c񨛡Q-M4֣Zi>yȿa7Yۅ$67Y$CJPA@EMW!B`a09ebڣ?0c񨛡Q-M4uuϞw2/ƘU.n5&äӫ>M}[Uћ>}[ ZixMX3Hh}EG/4Ӯ|~4n I  M!%(H8(HnR++ u,4DZ^1ji\s"iRa\:M!P^0-,-:ؽ'յ\&4>}[ ZixMX3Hh}EG/4Ӯ|~4n I 67Y$CJP8(H 7K)\A x敕LGj@:Lf@Ƣn˭G/4Ӯ|~4nswa0N&/Yll^گq4>}[ ZixMX3Hh}EG/4Ӯ|~4n I$M!%(PQB&e+!00ҲIQRɟH1MuuϞw2/ƘM.n5&äӫ>M}[U㮆)4>}[ ZixMX3Hh}EG/4Ӯ|~4n I(T,r&VV)1CK&~3M j9xũs̋tK+ Irp4Axpϓur NN[$w"A N 8*l !j5 ŵ_9NjJ:C+sh|Qt>ƭE4&]j,E4>֣Zi>yȿa7Yۅ$C<`sJ&#Hqédi8ݛG/4Ӯ|~4nswa0N&/YnAIIKvx$NAH9,,8*l !j&4>]acV֢D^C. "QcQ-M4M}):i;ni܈"#8%S`0j} [s{9CԷcC5l,oj,E4>֣Zi>yȿa7Yۅ$&8$Hc A /JC<`sJ&#G K&~3M `Q7C֣Zi>yȿaWDԘW'HT K N6])ԕВ*RڪQt>ƭZ^1ji\s"igi a(!@@P$,r&VV)1>Y3i?.bNE]Ra\:M!P^0-,-:J`4>}CC2!e k6r|$+ yf>_>X>';}+ ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg14.htm/$
ExpandConcepts
ContractTasks
  ExpandEstablishing a debugging environment
  ExpandPreparing a program for debugging
  ExpandStarting the debugger
  ExpandWorking with breakpoints
  ExpandControlling program execution
  ExpandInspecting data
  ContractPostmortem debugging
   DocumentDebugging dump files
ExpandReference
Z`, lꀑ}$0yf>_>X>';~ ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg15.htm/$    "<>aent=cdgiloprs /bfm.012hv#&,34;AHuxz5DEFkw689CSy7PITWRZbx%'bH( W D Zi$H8n ^,r5խëa0}ZۈB&c׺Lj"7كonq]dv 6MG㓾i;;`cO#È̀ߎrcl#I JuS ap$5)W&ˢ=D{zX^^Ъ#un% =MG㓾i;;`cO#_̀ߎrcl#I JuSCRr`-^N`=Dz.X" ĽTG`KDz,xD ũ{s.wab5cw|'|vw|iFǂGtf g6~;ɏ$5)@kЮqX}f΢2E{s*#4ҋL#\a0Ң:9(a%ELbaK@ZƟcfŽtS; i r`ᚱ>MG㓾i;;`cO#筇3˛ ÌW&= W&^#.]cEz,{BEע*X^Rxlط8®; H%Fa9EurPÈJ Æu聸'>{s.wab5cw|'|vw|iFǂG q~ g6L{#![?a\De=={xEq/hU"7كonq]dva I""+ cHrA)(@,PQiXk&T^'^G$wc%ELbnr&茺@ZƟcfŽ)X}4XpX& +x%ۀ]=D{zX^^Ъ#cEz n-IOb /M!cDDV@iF唂R(XX(stL=4NIJ Mu聸'>{stS; i r`ᚱ>Msrab]Ƈi}L#tGǯun% ={stS; i r`ᚱ>MJohE%{tA,@t@-vface=" lꈡ~$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg16.htm/$   "<>aent=cdgiloprs /bfm&.012;hv,AHkuz#34DEFSwx89C567yPIMTVWRZb,lqD&V 4 WKqAk{pDVIX xD ũAܬX0Fn`DŽ]cEz,7=QS4mD^Rxlط8KP^TH;ՍQlVW&2%*9^=={xE^tGLj@ZƟcfŽu^DcDDV@iFZA)`$(,r5q*/#|;Ң1~iۜ#.7كonqE30+w+ [W&2%\B4\#tGǯuK.X^Rxlط8n; H͏YAk)H<tD=4NIJ nr&茺@ZƟcfŽ]z >AܬX0Fn`z16%:#tGǯuK.X^Rxlط8n; H*lx( YH% @<3tD=4NI pt_@VwtF]z n-IOb.g|=AzaPVM V,#V7}Gɰ*)^2 vKX=={xE^tGa]"7كonqdv ͏YAk)H<7J-0KqCsJJg{7DeעԞ40v-0P^TH;ՍQl. k#tGǯuK.]z,7=^ ĽE聸'>{sҋL#\aҢ:9(aåELba‹@ZƟcfŽtS; ir`>MG㓾i;;`cO^Gw﯃;Ld-]KZwtGu^"+a]Xn%Dz.{E"+qjO};MGaziIQiXk"T^'^G% 8t_@8Q{7^Rxlط8ng|=AzaPVM V,#V7}Gɺrw'g~ vixKAMqhq\'Ɍ;`n2EMG㓾i;;`cO^G ~ 8.ltb{n2EMG㓾i;;`cO^G %҃;Ld#J;Qp%W}Dz.X"{EE^tGa]"7كonqdvB@$(,r5q*/#:TT/ f(D ũAܬX0FnuN(䜖Vg6䀘p%W}Dz.X"{E"+qjO};MGazicDDV@iFZA)(8,$T(,r5q*/#|;Ң1~iۜ#.7كonqE30+w+  1kW&%\h/NgQ=={xE^tGLj@ZƟcfŽu^@@6{s@Y""+ cH-e āfE c0{iQxyݎ1HMu聸'>{s)AX}4X`X& HRRM#c׺Lj"7كonq1QJ@y`0,(,r5q*/#|;Ң1~iۜ#.7كonqE30+w+ VxDz.XG+ۢ b-< tr> < kN$\yf>_>X>';\./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg17.htm/$
ExpandConcepts
ContractTasks
  ExpandEstablishing a debugging environment
  ExpandPreparing a program for debugging
  ExpandStarting the debugger
  ExpandWorking with breakpoints
  ContractControlling program execution
   ContractSetting breakpoints
    DocumentSetting a line breakpoint
    DocumentSetting a procedure breakpoint
    DocumentSetting an address breakpoint
    DocumentSetting a storage change breakpoint
    DocumentSetting a load occurrence breakpoint
    DocumentSetting a deferred breakpoint
    DocumentSetting a conditional breakpoint
    DocumentSetting multiple breakpoints
   DocumentRunning a program
   DocumentStepping through a program
   DocumentSkipping over sections of a program
   DocumentHalting execution of a program
   DocumentRestarting a program
   DocumentSelecting debugger recognized exceptions
  ExpandInspecting data
  ExpandPostmortem debugging
ExpandReference
2 fa l$yf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg18.htm/$   "<>ant/=cdegiloprs bfmv&.012;hx#,34AHz8CEFku59DIw7y6MPSTVWRSrr@,9zQKk8z @8HjA*Jr"Pq=0yfo%X={R6/8Ҕz:ffoddIkII g *RA*L` ժ&Q uo_6dkǯsP%⤝BA0f)M-^m`܅?ff2^׹(sb)G X<쌂= i)!bCA-.HtD=0ZnZ:MN@WwQmz/^ԡ͋K, QI:`h0RZ؂#fn"/f3~/Z9~Б"+Q'%$,g !Jq µjhC`l&[0&͹~/Z9~w|Łj8'PL SKWX dF3;)QW;W}Ӗo foӁ]ӃdkǯsPRBEJffoddIkII @JaK1L+VD6juz ~k,ۗ_ϩC,wXu =`4{?`\\4%ДJ]Ӗo foӁ]ӃdkǯsPRB@ X<쌂= i)!bDYl)rC@&0AjrѨ:MN@aMer2^׹(sbqRNG3Z b6?aόTDVB737D^.f2^׹(sb)GA`3372 $5g $MeUTMFa5:=y5mz/^ԡ͋K, QI:`h0RZt $AZ{7, <ߧqx7z/^ԡ͋'/gQ'%$,Hl_p|]1`Z*I(kAF]5J R>uӖo foӁ]ӃdkǯsPR@yzRBÌD[ \%P8zaZDܴ$uo,ۗ_ϩC,wXu =`4{7EG)7, <ߧqx7/Ӂ]ӃdkǯsPR@kQ'%$,H8qP(%eUTMB@~[ j>͹~/Z9~eqRNG3Z b6Hr佃46oNY=0yN"voN_qx7/Ӂ]ӃdkǯsPR@JaK1L+V :MN@+ )]_ϩCNY.-G$z 5Jij#k/g WwԌ=~yԤqU`JR\연fK**1c} g*͹fn"/fp7zr8ٽ8<ߦKֱ|z>l_q9{=(u—$: T"cVQ7-.@uoW R/%X={R6/8]1`Z*I(kAF^=!z"&X$qU`1@;9s(wz.&vK3HjЕ |fܳzrp7zr8ٽ9~ Eޜfo%X={R6/8Ҕz5—$: T"cVQ7-.@uoW R/%X={R6/8]1`Z*I(kAF^=!z"&t Y{<(峗>1Rw2gd4͹fn"/fp7zpyLb}Jؿxr{JQX<쌂= i)!b@@l_qYdbTQ& փ)؍-^zCR2 $DM! VFo-)TU߾t)t%W|lۖoNY=0yN"voN37_ϩCN^iJ=V333{# OCZJHXY.-G$z 5Jij#k QR Z˳zr3~/Z9~3372 $5V[ \%P8zaZDܴj!SkYfܿLb}JؿxdbTQ& փ)؍TUӖof!1H0)a lr0$gyf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg19.htm/$   "<>aent=cdgiloprs /bfmv.012h#&,3;AHxz4EFku5789CDIw6yPMSTVWR~RblqyQ Zi @8n^ r5խëa}ZۈB&cWƈ"^-IOb +M (64DDEd vi Y(!"EMҊL#\aҢ:'û*&c0cs7Cע ũ{s͍YݤCJH _ ҊL#\aҢ:'û*&c0cs7Cע ũ{sscDDDV@i&Œ_ $"nR`9׏:Jg{7Cע ũ{sbfE&c0{iQXx0Ңf1~ipI[7^/كonqzt >BX8^(-IK!S`V*Nj;;c!ڕ?>]cWƈX7EqhMX7"+Ԟ40v-0´st1D=4N~JpQ348$DRxlط8ng|=AaPNM!NV,/V^uN$CK!S`0䫓/` jTPt?u^"+`CC. =4?`CC,hDRxlط8n; H@7J)0CqCsJ䡇1HÂJAx'>{s&wbe7YNnM?< ;R_6+ԩdxsC5{hEqhMX7"+Ԟ40v-0´MYݤCJH@MҊL#\aҢ:'û*&c0cs7Cע ũ{sE !F!9EbuPÇJa%o|z ZƟcfŽtK; pi r`z|'|vw|i&ǂ?r7_6!jr! ~rc rF5C5{hEqhMX7"+Ԟ40v-0´MҊL#\aҢ:(aåDbn^-IOb %A8}49XpY{>MG㓾i;;`[O9+l,8*l BɏcƗ穝^9XB>]cWƈX7EqhM豢"^-IOb +M P nR`9׏C*&cujO};U,7L* )ŃQn?I߽ݤxA-^rUɏkߞt0)ct?u^"+`CC,hDRxlط8n; H """I4, PQ YQIk"TV'^?$wcDb nr&|Ax'>{stK; pi r`z|6?cJi\t?ƯuDEz ZƟcfŽcDDDV@i&Œ/ҊL#\aҢ:'û*&c0cs7Cע ũ_>X>';] ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg2.htm/$
ContractConcepts
  ExpandDistributed Debugger
  DocumentWhen to attach
  DocumentRemote debugging
  DocumentOptimized code debugging
  DocumentBreakpoints
  DocumentException handling
  Expand UNIX call handling during debugging
  ExpandPostmortem debugging
ExpandTasks
ExpandReference
 lꖀ$yf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg20.htm/$    "<>ant/=cdegiloprs bfmv&.012;h#,34AHuxz8CEFkw579DI6SyMPTVWRSrr@,9zQ"DKk8z$H8HjA*r&Pq8=0yfo%X={R6/8Ҕz@:ffodlI17Yl)rC@f0AjrѨBMN@`&͹~/Z9~2w|Ł8'PL SKWXw!Oٽ9f`dyLb}Jؿx{JQV333{#`OA%$,PP(=eUTMBA=S}er2^׹(sbeTqrNG3Z b6 ٽ9f`f8Y8<ߦKֱ|z>l_qY{=((PffodlI1 @—$: T&cVQ7-l-| ~k,ۗ_ϩC,wXu =`4{hDk9s*qJzrp?zpyLb}Jؿx{JQPyz i)!`(P( Yl)rC@f0AjrѨBMN@`&͹~/Z9~w|Ł8'PL SKWXPS J] J Z˳zrp?zpyLb}Jؿx{JQPV333{#`OA%$,P|QBk-.HtL=0ZnZ5[ Y/%X={R6/8>Y.5G$z 5Jij#k'=񪔨Pzrp?zpyLb}Jؿx{JQX@X<썂=4B E !Jq3 µjhC`!l&[0cYfܿLb}Jؿxdb\Q& փ)؍W@\Yd+As;f~"/f3~/Z9~e88=`3376 $RB 7.RA*` ժ&Q oMer2^׹(sbTqrNG3Z b6 9g._.T1H ;ޜ|0{`3~E,ޜfo%X={R6/8Ҕz+Q'ƒ o (RA*` ժ& [ j>͹~/Z9~w|Ł8'PL SKWX^{9rzrp?zr8Y8<ߦKֱ|z>l_qY{=(V333{#`OA%$,P@(PRA*` ժ&Q oMer2^׹(sb%BA0f)M-^m`z{i Tlޜ|0{`3~E,ޜN"oN37_ϩCV^iJ=Q'ƒ(7[ \%P8zaZDܴj!S1ɬn_Kֱ|z>l_qydb\Q& փ)؍/R=7, <ߧx7/ӁeӃdkǯsPR@@yz i)!b E!Jq3 µjhH'juzn_Kֱ|z>l_qydb\Q& փ)؍/R=Y9f`f8Y9~E,ޜN"oN37_ϩCV^iJ=—$: T&cVQ7-.@og ,w_Kֱ|z>l_qYdb\Q& փ)؍-^zCR6 $DM PU`1@reFΘUr737D^2~"/fp?zpyLb}Jؿx{JQ HaK1L+V BMN@3R/%X={R6/8]1`j.I(kAF^=!z"&(U`n˟E]wKTr737D^2~"/fp?zpyLb}Jؿx{JQ H Yl)rC@f0Ajr[ rW}edkǯsPK, Q:`h0RZ;]#`O_D@%WU`n˟Cq3t5jwY,ޜ|0{`3~E,ޜN"oN_x7z/^ԡ͋+/gu—$: T&cVQ7-.@og ,w_Kֱ|z>l_qYdb\Q& փ)؍-^zCR6 $DM# @*%)g.vy@j gI.JF,wK0RT,ۖoNY=0yN"oN_x7z/^ԡ͋+/g!Jq3 µjir-|9e+2^׹(sb%BA0f)M-^mejޮQ'؂"o!+R oX!e,rds=ReA;ۖoNY=0yN"oN_x7z/^ԡ͋+/g+-.HtL=0ZnZ\ a5:=@YJ﬿Lb}Jؿxw|Ł8'PL SKWY{?ZwlI A-,@* CY˟s>ʋօ$^CU6Ӗo foӁeӗD^2f2^׹(sb)GpRA*` ժ&S z/^ԡ͋/,wXu =`4{HwzFDb l|(峗>5S> %;r737D^2f2^׹(sb)GffodlI17Yl)rC@f0AjrѨBMN@`&͹~/Z9~w|Ł8'PL SKWXNz7, <̏37_ϩCV333{#`OA%$, @("RA*` ժ&Q oMer2^׹(sbeTqrNG3Z b6 %PW!VoNY=,9 ,|@size= kdp$ yf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg3.htm/$
ExpandConcepts
ContractTasks
  ExpandEstablishing a debugging environment
  ExpandPreparing a program for debugging
  ExpandStarting the debugger
  ExpandWorking with breakpoints
  ExpandControlling program execution
  ExpandInspecting data
  ExpandPostmortem debugging
ExpandReference
- kd$ yf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg4.htm/$
ExpandConcepts
ExpandTasks
ContractReference
  Documentidebug command
  Documentirmtdbgc command
  DocumentStep commands
  DocumentOptional breakpoint parameters
  DocumentProgram profiles
  ExpandSupported expressions
  ExpandCompiler options for debugging
  ExpandEnvironment variables
  ExpandLimitations
& kd$ yf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg5.htm/$
ContractConcepts
  ContractDistributed Debugger
   DocumentSource and Control Panes
   DocumentValue Panes
  DocumentWhen to attach
  DocumentRemote debugging
  DocumentOptimized code debugging
  DocumentBreakpoints
  DocumentException handling
  Expand UNIX call handling during debugging
  ExpandPostmortem debugging
ExpandTasks
ExpandReference
TqrN k$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg6.htm/$
ContractConcepts
  ExpandDistributed Debugger
  DocumentWhen to attach
  DocumentRemote debugging
  DocumentOptimized code debugging
  DocumentBreakpoints
  DocumentException handling
  Contract UNIX call handling during debugging
   Documentexec() handling
   Documentfork() handling
   Documentsystem() handling
  ExpandPostmortem debugging
ExpandTasks
ExpandReference
>_>X>';7 ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg7.htm/$   "<>aent=cdgiloprs /bfmv.02hu&,1;AHxz#34DFw56CEIXk78NPRUy9BOTWL^RbLlq @TY @TkWf0SuBc0>on\B04D jO};"#4&ƈNM!%$ 8( &nR`9׏:}1Han˯DRxlط8{YPnLHS ՗>C.X" =4?ƈAx'>{suVD""";I4,8( ҊL#\aҢ:'û*&c 1țԞ40v-0YPnLHS ՗d~9;擳{;I4}ostW6 S _  Ju>]cWƈX7"+Ԟ40v-0EGaZiҊL#\aҢ:(aåDb aŕujO};M,7L& )ŃQn?I߽N>9⼩8.]cDEz,{BhEjO};"#4MҊL#\aҢ:(aåDb aŕujO};M,7L& )ŃQn?I߽N>9JAyS`Jg#HC5{hEqhM豢"^-IOb]dv8 7J)0CqCsJ䡇1H%Vע ũMG㓾i;;`SI9Ê ۀ[Xt?u^"+`CC,hDRxlط8YiMҊL#\aҢ:(aåDb aŕujO};M,7L& )ŃQn?I߽N>9÷8*l >΁YZ4>]cWƈX7"+Ԟ40v-0EGaZii""+ SHbA 4( r5q*+|;Ңf1~i.^-IOb %8}49XpY{>MHŮg!j\F-)W&]cDEz,{BhEjO};"#41cDDDV@i&Œ$8( E&c0{iQXxQ34v|Ax'>{s&wbe6)* JUɡCjX^Кun! 4DW ũBX8^()I}㜀[JC31ߥB4iJ0΀$ E4DW&]z,{BhEjO};"#4A3t1D=4N~JpQ34Xqeo|z ZƟcfŽ%8}49XpY{>MG㓾i;;`SI9|-ÊG x\#H렍t UC.X" =4?`CC,hDRxlط8YiIQIk"TV'^?% 8t_A,8n^-IOb]zt`>BX8^()I}㜀ZƇME+| [ɆST#HC5{hEqhMX7"+Ԟ40v-0EGaZinR`9׏C*&cK,DRxlط8D0'+/}Gɺrw'g~ vi;8x 1kW69sܮL P cz?cJiҕrh|t?ƯuDEz ZƟcfŽ+M @"lh$PB@y@`<( r5q*+|;Ңf1~i.^-IObg|=Aa0NM!NV,/V^` C.X hDRxlط84DDEd vi Y(! ⼠0"nR`9׏>Q34D^/كonqD0'+/}Gɰ뷏?uC +]n kN$F yf>_>X>';F ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg8.htm/$
ExpandConcepts
ContractTasks
  ContractEstablishing a debugging environment
   DocumentSetting environment variables for the debugger
  ExpandPreparing a program for debugging
  ExpandStarting the debugger
  ExpandWorking with breakpoints
  ExpandControlling program execution
  ExpandInspecting data
  ExpandPostmortem debugging
ExpandReference
cu kk$[ yf>_>X>';[ ./usr/share/man/info/en_US/xlf/html/debugger/xlfdbg9.htm/$
ExpandConcepts
ContractTasks
  ExpandEstablishing a debugging environment
  ContractPreparing a program for debugging
   DocumentWriting a program for debugging
   DocumentCompiling a program for debugging
  ExpandStarting the debugger
  ExpandWorking with breakpoints
  ExpandControlling program execution
  ExpandInspecting data
  ExpandPostmortem debugging
ExpandReference
gcacr kBXAX>X>X>'E./usr/share/man/info/en_US/xlf/html/debugger/conceptstm/A kY$ yf>_>X>'G ./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbexcptn.htm/$ Exception Handling

Exception Handling

The Distributed Debugger allows you to investigate exceptions that occur while you are debugging your program.

You can choose the types of exception or the level of exception you want the debugger to recognize in the Exception Filter Preferences Setting field in Applications Preferences dialog box. The types of exception or level of exception you can select varies with the platform where you are running the program that you are debugging. For example, the exceptions the debugger can handle for a C++ program running on Windows NT are different from the exceptions the debugger can handle for a C++ program running on AIX.

When the debugger encounters an exception that matches one of the exceptions that are specified in the Exception Filter Preferences Settings dialog box, a dialog box opens to warn you an exception occurred. Also, the line where the exception occurred is highlighted in the Source pane.

After a program exception is encountered and the Application Exception Occurred dialog box is closed, the following actions are available:

Step exception
Step exception causes the debugger to step into the first registered exception handler (tracked by the operating system). Execution stops at the first executable line of code in the exception handler. If your application does not have a registered exception handler, the exception remains "unhandled" and the application may be terminated.

Run exception
Run exception causes the debugger to run the exception handler that is registered to handle the type of exception encountered. If your application does not have a registered exception handler, the exception remains "unhandled," and the application may be terminated.

Examine/Retry exception

Examine/Retry exception discards the exception and allows you to investigate the cause of the exception and, if desired, retry program execution at the statement that triggered the exception. The debugger begins at this statement and attempts to continue.

Copyright IBM Corporation 1999, 2002

c=" l7Z$yf>_>X>'Y'./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwheapr.htm/$  eanortchilpsu <>dfgmy,./bkw"CSv=AHIPT-01DEFLMRWx()+29:BGNOXYjq'68;U_!453 ` p@@x4'"@ ~p( xbm3@âQ :;@Ù."ԅf/Ł W1/ł/v!bL K$ @@Ag4,Ay`h 0%ą-  a6@3f"@0 4@X4gp$&EL( 8M0ܒq2I 0w^SLBu84x( !&9} H&`x< ZԞs`@@D$8Ŧ0,kZٮp$&E u0YeOi#ed`zMZٮq34n1xS`fyVGuF8%gR|˚rhLgy%%gĽz BNzgh&j98Iu*N/=`6va}JR9 Aδ|Kᰴ$f$hdѸLJ/MfqU|˚r]J(-1Ou*N˚r| +-]&|yVeOm;BūM6/\lbIRwN-Y qf ϙt/&.uVqN+IYԩ;'2朾CkGǘdSF=c%T'<sqݬ0y籗R]9OCkp%kGĽz%izΥI8J♞!~nBa@"Zq}kGJ"bم6[50^ʓުi$q aY`);zim$h%q ,,d;zq1ť_-9; :9& ~ %c9Fg6i`| #6[.s1ť\-6hK40w:;Z>34n1xS`wk;3w^:9k'*hN֏;Uc#z̎G8 cR`hR˦]ΥI8Jⴔ3.iZm h<1/ZL|-٤/кM߀Vxުk%xrIah;jLƓ\%Jx')14> u$̷2|h?%_<`Y BNh̚7z-ى|Y :S tsL򝪼NG`u0YY :w^:9& fQÉW'5v;5$mpVqZ^ 3IZɣq_33:&u^GuSWie2ҥf5u"U '0^rIMaՑlSWin;-/5_VyN^Gu 79$ u)Z>SGu˩#OFkl%$+lť^2v1MqMY :SL.S/#fBcZ>'ieC. q aY>[\/Z>;IY;zUIZm h%6]HZIGb`hMd  STјcedau0Y(0U˩0X캘,3icedc<46R/Z>aIXmfw8@ed4fGu㣜V̹^1\zǒSU42`uMfs-'u(ܘc}%kG̷8$!~m0^[(kCzѓl̷8U9>ū+>;\S`^Ph&*NoIq*ᵡ*NoIq*yl_9ĉWTԤc=`6x'=&_ Sf|sSYM֏W'=c%DސB7~0s4K8ou(>H6IXnKߟ_^mǓ x'RfqW'=c BU캘,w(0U˩fU #:9& 6if;\ 1j1U&kGu+l0<f\ӗ1|sWrr1~nC']&n|sS#:9& 6i80ìu0YEMx3.W~1q ,,d;i&5x_f|!~ܜye⦳/L1yݬZ>Gu9ʿ[љ}a4l=|Z`hihz/sfy'k\Ũ˕0^{kb<x詣*EFmL0캘,w(0U˩ 7&5Yvceb=qb`ުiu;. Mi2`6au0YEMׂQ+L`!S;. !S8vI ֏ފ3;VW+D\sBceGu'G8x/0%c9Fg6i`|6[XbүZ^Mc&L4cf!I mRH%_Z> G8 1WIx'Sc-Zwk{LlN|Zwc[# #+%&O6ⵣw^ e<щ )򝗔JhmuI;f!I mRH築ZYiJ6.s39rahJ& Ɍy1iWg2hc×xOև ȕ/>34ng1։Z>Gu㣜VK4M*hHq)$ Iҵ\iML 0$Jlm_>X>'H./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwlmtxp.htm/$ Limitations during postmortem debugging

Limitations during postmortem debugging

Once you have started debugging a dump file, you can use a subset of debugger features to examine registers, storage (if available), and code for the executable that caused the trap. You can access only the following debugger monitors:

  • Registers monitor
  • Storage monitor
  • Call Stack monitor
  • Local Variables monitor

You cannot change the contents of items in these monitors (for example, registers in the registers monitor). Where the core file does not contain appropriate information, question marks or messages such as "expression evaluation failed" may appear in place of data. For example, if stack information was not saved, local variable values may not be displayed, even though the names of those variables are.

The following debugger commands are disabled, and icons for them are hidden or greyed out, when you are debugging a dump file:

  • Run and stop commands
  • Step commands
  • Commands to set, clear, disable, enable, or delete breakpoints.

Copyright IBM Corporation 1999, 2002

 k\$yf>_>X>'./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwpmdo.htm/$ Postmortem debugging on AIX

Postmortem debugging on AIX

Postmortem debugging is intended to help you isolate the causes of unanticipated traps or unhandled exceptions, in programs that are already in production or widespread use. There are three stages to the postmortem debugging process:

  1. You compile the program with debug information, and ship the resulting object code.
  2. When the end user experiences a trap or unanticipated exception, AIX automatically creates a core dump file with the name core, in the current directory (provided that directory is writable).
  3. You debug the core file instead of a live object code. Because the core file contains information about the state of the application at the time of the trap or exception, and is not a live object file, only a subset of debugger features are available. For example, you can view memory and register contents, but you cannot step or run the program or set breakpoints.

Copyright IBM Corporation 1999, 2002

f=".. k%]$ yf>_>X>' ./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwunusu.htm/$ Unusual bebugger behavior (AIX only)

Unusual debugger behavior

Applies to AIXIf the debugger behaves in unexpected ways when you are debugging core files, it is usually an indication that the core file is missing necessary information, or that modules cannot be located.

There are limitations during postmortem debugging regarding what subset of debugging features and actions is normally available for core files. Missing core file information and missing modules can further limit the debugger in the following ways:

  • The contents of local variables cannot be displayed or used in expression evaluation. This indicates that the program stack is absent from the core file.
  • No entries appear in the Call Stack monitor. This also indicates that the program stack is absent from the core file. If some entries appear in the Call Stack monitor but others are missing, this indicates that the process call stack has an entry for a function contained within a module that is not available. This situation causes the call stack to be truncated in the monitor; that is, only the entries in the stack up to that entry are shown.
  • Threads are missing. This indicates that the current execution location of a thread is contained in a module that is not available. The debugger handles this situation as if the thread never existed.
  • You cannot use a variable of static storage duration in an expression (for example, in the Monitor Expression dialog). This indicates that data segments are missing from the core file.
  • Memory in the storage window shows "??????" instead of the expected contents. This indicates that the core file was missing those memory locations (for the stack, data segments, and memory-mapped regions), or that the debugger could not locate necessary modules (for code segment regions).

Related reference
Limitations during postmortem debugging

Copyright IBM Corporation 1999, 2002

ou( k:^$(yf>_>X>'1(./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbxpmerr.htm/$ Errors during UNIX workstation postmortem debugging

Errors during UNIX workstation postmortem debugging

You may experience two kinds of problems while debugging core files:

  • Errors that prevent you from debugging the core file
  • Unusual debugger behavior.

Related reference
Unusual debugger behavior

Copyright IBM Corporation 1999, 2002

 k_$yf>_>X>'2./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbcdbmon.htm/$ Distributed Debugger: Value Panes

Distributed Debugger: Value Panes

Depending on the language you are debugging, the Distributed Debugger provides you with value panes to observe various aspects of your program. The following value panes are available in the Distributed Debugger user interface:

Variables and Expressions (Monitors pane)

The Monitors pane shows variables and expressions that you have selected to monitor. You can enter the variables or expressions in a dialog box or select them from the Source pane. Use the Monitors pane to monitor global variables or variables you want to see at all times during your debugging session. From the Monitors pane you can also modify the content of variables, or change the representation of values.

Tip: Enabling tool tip evaluation for variables provides a quick way to view the contents of variables in the Source pane. When you point at a variable, a pop-up appears displaying the contents of that variable. If hover help for variables is disabled and you want to enable it, see the related topic below.

Local Variables (Locals pane)

The Locals pane helps you monitor all local variables in scope at the current execution point of your program. The Locals pane is updated after each Step or Run command to show what variables are currently in scope and the contents of those variables. It is also used to modify the content of variables or change the representation of values.

Registers (Registers pane)

The Registers pane allows you to view and change the contents of processor registers for the threads in your program. Registers values are unique for each thread of your program. The registers are categorized, so you only need to expand the category of registers that you wish to view.

Storage (Storage pane and Storage Monitor panes)

The Storage pane and Storage Monitor panes let you view and change the contents of storage areas used by your program. You can also change the address range to view and modify the contents of storage, and change the representation the debug engine uses to display storage.

The initial Storage pane shows the storage areas used by your program at its starting address.

You can add additional Storage Monitor panes that start at the address of storage allocated to a register, variable, array, class object or expression.

Applies to Fortran Storage pane and Storage Monitor panes are not available when debugging Fortran programs.

Note: When viewing a Value pane with expandable items, choosing the Expand All option from the pane's menu in the debugger main menu bar will expand one level of the tree at a time. You must choose Expand All for each subsequent level of the tree that you wish to expand. Choosing Collapse All will collapse all levels of the tree.

Related concepts
Distributed Debugger: Overview
Distributed Debugger: Source and Control Panes

Related tasks
Enabling Tool Tip Evaluation for Variables

Copyright IBM Corporation 1999, 2002

i kP`$E yf>_>X>'3E ./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbcdbovr.htm/$ Distributed Debugger: Overview

Distributed Debugger

The Distributed Debugger is a client/server application that enables you to detect and diagnose errors in your programs. This client/server design makes it possible to debug programs running on systems accessible through a network connection as well as debug programs running on your workstation.

The debugger server, also known as a debug engine, runs on the same system where the program you want to debug runs. This system can be your workstation or a system accessible through a network. If you debug a program running on your workstation, you are performing local debugging. If you debug a program running on a system accessible through a network connection, you are performing remote debugging.

The Distributed Debugger client is a graphical user interface where you can issue commands used by the debug engine to control the execution of your program. For example, you can set breakpoints, step through your code and examine the contents of variables. The Distributed Debugger user interface lets you debug multiple applications, which may be written in different languages, from a single debugger session. Each program you debug is shown on a separate program page with a tab on each page displaying program identification information such as the name of the program being debugged. The type of information displayed depends on the debug engine that you are connected to.

Each program page is divided into different sections, called panes. Each pane displays different information about your program. There are panes to display your source code, breakpoints, the program's call stack and various monitors. The types of control and value panes available on a program page depend on the program you are debugging.

For more information on the control and value panes available in the Distributed Debugger user interface, see the related topics below.

Related concepts
Distributed Debugger: Source and Control Panes
Distributed Debugger: Value Panes
Remote debugging

Copyright IBM Corporation 1999, 2002

nes ka$ yf>_>X>'B ./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbcdbpan.htm/$ Distributed Debugger: Panes

Distributed Debugger: Source and Control Panes

Selected entries in the Control Panes have a direct relationship with what is displayed in the Source Pane. For example, if you expand the stack view and click on one of the entries, the source pane displays the source for the selected entry. Similarly, if you click on a source file in the modules pane, that source file appears in the source pane.

The types of control panes displayed when debugging a program depend on the programming language used. The following control panes are available in the Distributed Debugger user interface:

Stacks pane

The Stacks pane provides a view of the call stack for each thread in the program you are debugging. Each thread in your program appears as a node in a tree list. Expanding a node will display the names of active functions for that thread. The thread you are debugging is highlighted. When debugging interpreted Java, the name of the thread will be displayed.

Breakpoints pane

The Breakpoints pane contains a view of information about the breakpoints you have set in the program you are debugging. Use the Breakpoints pane to view breakpoints set in your program, modify their properties, enable or disable breakpoints, delete them, or add new ones.

Source pane

The Source pane provides a view of the source code for the program you are debugging. If your program was compiled with debugging information, you have three choices as to how to view it: by its source code, its disassembled machine code, or a combination of the two. To view source code, the source code must be accessible to the debugger engine or the debugger user interface, either on a local or network drive. If the source code file is not found, or your program was not compiled with debugging information, only a disassembled machine code view is available.

Note: Disassembly is only shown for compiled language programs.

Object Modules pane

Applies to FortranThis pane is displayed when debugging Fortran programs.

The Object Modules pane displays a list of object modules loaded while running your program. The items in the list can be expanded to show object files, source files, main programs, modules, procedures and ENTRY statements.

The remaining panes are value panes. For more information on value panes, see the related topics below.

Note: When viewing a Control pane with expandable items, choosing the Expand All option from the pane's menu in the debugger main menu bar will expand one level of the tree at a time. You must choose Expand All for each subsequent level of the tree that you wish to expand. Choosing Collapse All will collapse all levels of the tree.

Related concepts
Distributed Debugger: Value Panes
Distributed Debugger: Overview

Copyright IBM Corporation 1999, 2002

href=". kb$( yf>_>X>'C( ./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwbrkpt.htm/$ Breakpoints

Breakpoints

Breakpoints are temporary markers you place in your executable program to tell the Distributed Debugger to stop your program whenever execution reaches that point. For example, if a particular statement in your program is causing problems, you could set a breakpoint on the line containing the statement, then run your program. Execution stops at the breakpoint before the statement is executed. You can check the contents of variables, registers, storage, and the stack. You can then step over (execute) the statement to see how the problem arises or you can choose to skip the execution of the statement in question.

The Distributed Debugger supports the following types of breakpoints:

  • Line breakpoints are triggered before the code at a particular line in a program is executed.
  • Applies to FortranProcedure breakpoints are triggered when the procedure they apply to is reached.
  • Storage change breakpoints are triggered when storage at a specified address is changed. Applies to AIXStorage change breakpoints are not available when debugging programs running on AIX.
  • Load occurrence breakpoints are triggered when a DLL is loaded.
  • Applies to AIXApplies to Windows Address breakpoints are triggered before the disassembly instruction at a particular address is executed.

Related tasks
Setting a line breakpoint
 Setting a storage change breakpoint
Setting a load occurrence breakpoint
 Stepping through a program
 Skipping over sections of a program
 Setting a conditional breakpoint
Applies to FortranSetting a procedure breakpoint
Applies to AIXApplies to WindowsSetting an address breakpoint

Copyright IBM Corporation 1999, 2002

 kc$ yf>_>X>'D ./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwdoptc.htm/$ Optimized code debugging

Optimized code debugging

Problems that only surface during optimization are often an indication of logic errors or compile errors that are exposed by optimization, for example using a variable that has not been initialized. If you encounter an error in your program that only occurs in the optimized version, you can usually find the cause of the error using a binary search technique to find the failing module:

  1. Begin by optimizing half the modules and see if the error persists.
  2. After each change in the number of optimized modules, if the error persists, optimize fewer modules; if the error goes away, optimize more modules. Eventually you will have narrowed the error down to a single module or a small number of modules.
  3. Debug the failing module. If possible, turn off the instruction scheduling optimizations for that module. Look for problems such as reading from a variable before it has been written to, and pointers or array indices exceeding the bounds of storage allocated for the pointer or array.

When you debug optimized code, information in debugger panes may lead you to suspect logic problems that do not actually exist. You should bear in mind the points below:

Local variables are not always current

Do not rely on the Local variables monitor to show the current values of variables. Numeric values, character values and pointers may be kept in processor registers. In the optimized program, these values and pointers are not always written out to memory; in some cases, they may be discarded because they are not needed.

Static and external variables are not always current

Within an optimized function, the values of static or external variables are not always written out to memory.

Registers and Storage monitors are always current

The Registers and Storage monitors are correct. Unlike a monitor that shows actual variables, such as the Locals Variables monitor, the Registers and Storage monitors are always up-to-date as of the last time execution stopped.

Source statements may be optimized away

Using the disassembly view or mixed view to see the machine code for your program, you may find, for example, that an assignment to a variable in your source code does not result in any disassembly code being produced; this may indicate that the variable's value is never used after the assignment.

Copyright IBM Corporation 1999, 2002

ption  kh3d$yf>_>X>'u./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwexec.htm/$ exec() handling (AIX)

exec() handling

When a process calls exec(), a new program is loaded to replace the current program.

The debugger suspends program execution at this point and opens a dialog, which allows you to choose whether to debug program initialization or whether to use a program profile. The name of the new program is shown, but, you cannot change the name. After you select OK, the debugger stops at the first instruction of the new program's runtime (if you asked to debug program initialization), or at the first instruction or statement in the new program.

Related reference
fork() handling
system() handling

Copyright IBM Corporation 1999, 2002

prob kPe$yf>_>X>'{./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwfork.htm/$ fork() handling (AIX and OS/390)

fork() handling

When a process calls fork(), an exact copy of that process is created. The process that forked is called the parent, and the new process is called the child. If a process being debugged forks, the Distributed Debugger stops both the parent and child processes, and opens a dialog box that lets you choose whether to continue debugging the parent process or switch to the child process.

Whichever choice you make (Parent or Child), the Distributed Debugger ignores the process you did not choose, and allows it to continue running. The debugger will halt the selected process, which then allows you to perform debugging activities, such as adding a breakpoint. The process remains halted until explicitly restarted .Breakpoints set in the process you did not choose are ignored. Execution stops in the process that you chose to debug.

If the process you did not choose performs an exec(), the Distributed Debugger will allow
you to debug the new process. Look under the exec() handling related reference for additional information.

Related reference
exec() handling
system() handling

Copyright IBM Corporation 1999, 2002

rs k f$yf>_>X>'./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwhatt.htm/$ When to attach (AIX, Solaris, and Windows only)

When to attach

There are two main reasons for attaching the Debugger to a process or JVM:

  • You anticipate a problem at a particular point in your program, and you do not want to step through the program or set breakpoints. In this situation, you can run your program, and during a program pause shortly before the anticipated failure (for example, while the program is waiting for keyboard input), you attach the Debugger. You can then provide the input, and debug from that point on.
  • You are developing or maintaining a program that hangs sporadically, and you want to find out why it is hanging. In this situation, you can attach the Debugger, and look for infinite loops or other problems that might be causing your program to hang.

Note: You can attach the Debugger to an already running program or a running Java Virtual Machine (JVM) where an error or failure has occurred.

Related tasks
Applies to AIXApplies to WindowsAttaching to a local running process
Attaching to a remote running process

Copyright IBM Corporation 1999, 2002

 k0Ug$ryf>_>X>'r./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwremdb.htm/$ Remote debugging

Remote debugging

Debugging a program running on one system while controlling the program from another system is known as remote debugging. The debugger supports remote debugging by allowing you to run the debugger user interface on one system, while running the debug engine on another system. The system running the debugger user interface is known as the local system. The system where the debug engine runs is known as the remote system.

When debugging a program remotely, you can start the debugger in one of two ways:

  • Start a debug engine daemon, then start the debugger user interface.
  • Start a debugger user interface daemon, then start a debug engine.

In both cases, a daemon will listen for a connection. Once a connection is made you can begin to debug your program.

Why use remote debugging
You might want to use remote debugging for the following reasons:

  • The program you are debugging is running on another user's system, and is behaving differently on that system than on your own.

    You can use the remote debug feature to debug this program on the other system, from your system. The user on the system running that program interacts with the program as usual (except where breakpoints or step commands introduce delays) and you are able to control the program and observe the program's internal behavior from your system.

  • You want to debug a program that uses graphics or has a graphical user interface.

    It is easier to debug an application that uses graphics or has a graphical user interface when you keep the debugger user interface separate from that of the application. Your interaction (or another user's interaction) with the application occurs on the remote system, while your interaction with the debugger occurs on the local system.

  • The program you are debugging was compiled for a platform that the debugger user interface does not run on.

    You can use the remote debug feature to take advantage of the debugger user interface while debugging the remote application.

Applies to OS/390Applies to OS/400 Restriction: This information applies to remote debugging between workstation platforms only. For information for debugging an OS/390 or AS/400 program from a workstation, see the online for help for the Distributed Debugger shipped with products that support OS/390 or AS/400.

Related tasks
Applies to AIXApplies to WindowsApplies to HP-UXApplies to SolarisStarting the debugger for debugging compiled languages remotely
Starting the debugger user interface daemon

Related reference
Remote debugging limits

Copyright IBM Corporation 1999, 2002

images k겍h$w yf>_>X>'w ./usr/share/man/info/en_US/xlf/html/debugger/concepts/cbwsyste.htm/$ system() handling (AIX only)

system() handling

Applies to AIXApplies to SolarisRestriction: This is supported on AIX and Solaris only.

When a program running in a UNIX environment starts another program using a call to system(), the system() function calls both fork() and exec(). The following describes the Distributed Debugger's behavior after you perform a Step Over command on a line containing a system() call, and tells you what actions you should take to begin debugging the child process.

  1. The system() function calls fork(). The Distributed Debugger stops execution and raises a Process fork action dialog.
  2. At this point you should choose to debug the child process. Once the Process fork action dialog closes, issue the Run command to continue debugging the child process.
  3. The new child process calls exec() to load /bin/sh, and the debugger opens a New process dialog and the active Distributed debugger Source pane shows a disassembly view of the initial runtime entry point of /bin/sh.
  4. Click OK to start debugging the child process.
  5. The Distributed Debugger stops in the main function of /bin/sh.
  6. Issue the Run command.
  7. Applies to AIXThe /bin/sh process calls exec() to load the program specified in the call to system() in the original program. The Distributed Debugger opens a New process dialog and the active Distributed Debugger Source pane shows a disassembly view of the initial runtime entry point of the program specified in the call to system().
  8. Click OK. The Distributed Debugger stops at main(). From here you can continue debugging.

Related reference
exec() handling
fork() handling

Copyright IBM Corporation 1999, 2002

 k<0iAX>X>X>'./usr/share/man/info/en_US/xlf/html/debugger/refepts/cb/A k|j$qyf>_>X>'q./usr/share/man/info/en_US/xlf/html/debugger/ref/rbcdbpro.htm.h/$ Program profiles

Program profiles

Applies to AIX If you are debugging on AIX, user profiles are stored in the workstation, in $HOME/.DbgProf.

Using program profiles means that the Distributed Debugger will restore debugger fonts, monitor settings, and breakpoints for your program from the last time you debugged the program. If you are debugging the program for the first time, the debugger windows start up with their default appearance, and no breakpoints are set.

When you use program profiles, any changes you make to the exception filter settings, monitor settings, and breakpoints are saved. If the debugger has saved a profile containing information on window, breakpoint, and monitor settings from a previous debug session for a program, the profile is used to restore those settings. To delete them you can use the Application Preferences dialog.

Attention: If you add or delete lines in your source file, recompile it, and then debug the program again with a saved program profile, line breakpoints may no longer match the code they were initially set for because line breakpoint information is saved by line number, not by the content of the line.

Copyright IBM Corporation 1999, 2002

rocess. kk$ yf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/ref/rbvdpstp.htm.h/$ DER_DBG_DEEP_STEP_DEBUG

DER_DBG_DEEP_STEP_DEBUG

The environment variable DER_DBG_DEEP_STEP_DEBUG allows you to bias the step-debug behavior to favor either performance or function. The default step-debug behavior favors better stepping performance by having the debugger step over calls made to shared libraries that do not have any debug information. This improves performance by ignoring libraries that are unlikely to lead to debuggable code.

If the value of this environment variable is set to 1, step-debug will follow such calls. This allows step-debug to reach callbacks from libraries that have no debug information, at the cost of somewhat degraded stepping performance.

For example:

Modules A and C contain debug information, B does not.

line module A line module B line module C
100 call B()
5 call C()
500 do some stuff
510 return
6 do some stuff
20 return
101 do some stuff

A default step-debug executed at line 100 in module A will cause the debugger to stop next at line 101 in module A. If the DER_DBG_DEEP_STEP_DEBUG environment variable is set, then the debugger will stop at line 500 in module C.

Related tasks
Stepping through a program

Related reference
Step commands

Copyright IBM Corporation 1999, 2002


 k l$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbcdbgc.htm.h/$ irmtdbgc command

irmtdbgc command

Applies to AIXApplies to SolarisApplies to WindowsRestriction: This is supported on AIX, Solaris, and Windows only.

Requirement: You must have the debug engine installed on the remote system in order to use this command. Check the install documentation for instructions on how to install the debug engine on a remote system. This command can also be used on the local system.

The irmtdbgc command starts the debug engine on the remote system. If the debug engine detects a Debugger user interface daemon, then you can start debugging your program immediately. If no Debugger user interface daemon is detected, the debug engine will run as a daemon until you start the Debugger user interface on the local system with the idebug command.

Note: The Debugger can operate in the remote manner when the UI and engine are on the same machine.

The irmtdbgc command has the following syntax:

irmtdbgc [irmtdbgc_parameters] [--] [program_name [program_parameters]]

where irmtdbgc_parameters are:

Parameter Description
-qport=<port> Specifies the TCP/IP port used for the connection.

If you do not use the default port, specify the same port number you use here in the -qport parameter of the idebug command. The default port is 8000.

Note: Do not use this parameter when connecting to a Debugger user interface daemon. You must use the -quiport option.
-quiport=<ui_daemon_port> Specifies the TCP/IP port used for connecting to a Debugger user interface daemon listening on another machine.

This port number must match the port number used in the -quiport parameter of the idebug command.
-qhost=<ui_daemon_host> Specifies the TCP/IP name or address of the machine where the Debugger user interface daemon is listening.
-qdaemon Tells the debug engine to run as a daemon. The debug engine re-initializes itself and waits for a new connection when the program you are debugging runs to completion or is terminated manually. The debug engine must be terminated manually on the remote system.

Without this option, the debug engine terminates when the program you are debugging runs to completion or is terminated manually.

Use the "--" parameter to separate irmtdbgc parameters from the program name and parameters. Use this option if your program name or parameters include forward slashes ("/") or dashes ("-"). If you do not use this option, anything preceded by a slash or a dash will be interpreted as a Debugger option.

If you do not specify program_name when issuing the irmtdbgc command, the Debugger will prompt you for the required information in the Load Program dialog of the Debugger user interface.

Related reference
idebug command

Copyright IBM Corporation 1999, 2002

s/ngd km$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbcdbopt.htm.h/$ Optional breakpoint parameters

Optional breakpoint parameters

Optional breakpoint parameters are used to control the behavior of breakpoints. You can set the following parameters when you set a breakpoint:

Optional breakpoint parameter Description Type of breakpoint supported
Threads This parameter is supported by all breakpoint types.
Frequency This parameter is supported by all breakpoint types.
Expression You can enter an expression into this field. The execution of the program stops at the breakpoint only if the condition specified in this field tests true.

Line, function or method
Defer Select this check box if you want to set a breakpoint in a program module that is not currently loaded.

If you enter an incorrect source, file, function, or program unit, the debugger will not be able to activate the breakpoint when the program is loaded, and the breakpoint will remain in the deferred state.

Restriction: You cannot set a deferred breakpoint in a preloaded DLL or dynamically called routine, but you can set one in a program that has some preloaded DLLs or dynamically called routines and some dynamically loaded ones.

 Line, function or method

Related reference

Copyright IBM Corporation 1999, 2002

Do n kn$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbcforod.htm.h/$ Fortran supported expression operands

Fortran supported expression operands

You can monitor an expression that includes the following expression operands:

Operand Description
Constant Named constants and literal constants are supported.

Literal constants can be of intrinsic type, but can only appear as a subscript or substring bounds.
Named Variable A named variable can be a scalar variable name or an array variable name.
Subobject A subobject of a constant is a portion of the constant. The referenced part may depend on a variable value. A subobject of a constant or a named variable can be an array element, an array section, a character substring, or a structure component.

A subobject of a constant or name variable can be:

  • an array element
  • an array section
  • a character substring
  • a structure component

Subscripts and substring bounds must be of type INTEGER(4).

Copyright IBM Corporation 1999, 2002

 k[o$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbcforop.htm.h/$ Fortran supported expression operators

Fortran supported expression operators

You can monitor an expression that uses the following operators in array subscripts and substring bounds only:

Operator Code
unary minus -a
unary plus +a

Copyright IBM Corporation 1999, 2002

e a sc lp$,yf>_>X>';z./usr/share/man/info/en_US/xlf/html/debugger/ref/rbcidebg.htm.h/$   aert /<>dghilmnops".bcfu=w-0ACDIST_qy,45:GLMPRv&+1;UWXkx#9BEHO[]()28FNVYz|!?j3@C@X`OBo`  9p ( Pu8 2Lkܓ RLflHE mBDcrc h;5,!  D)(`` p a14P  >L&F]ijɋPRZLI1DT& RYJLdI(8x@0PÎvs<M[JD )9?ah@p8smiCph'6< ls&eN$VAkAOy1{ 4gȎ/{ p xU~ p Z4+tI8L~2d oۄ>\_cɌ!d _-=|oN{oϱAk].w¨?]Uo|񀌫)%^SaO%^SeYO h=%sRoٖP3M8dbM;-~UɠICWfYBo[d*}zJߡJ+,Cb"$YOY|6-kxU~몭IAԛ9Eve(` ,Oȯ)MjL OCSi#$TOjYOIA I$A:|YF2AO}e w/įT\l AD:^  ntD 0PܛsJS`Cڭ`@oѸ5Pβd{孌yF JINj(gYZ2Q=i`ěq&7T>IDZt%$RBh}_e҄6 ȓsDL$" #}RM~ěѪHM ѪHt1/,m:+o}ěn$RBfoF" le958O|ڻaɌ\ [u:|Hli`q/VKJ>I J:|-l`ȯ)[\y1|ztIAIߠ7Tx Iru [ʎ}eN$VAkAOy1{ $ߠ7I$RC~mZy19 ӚU91UeiYdڮY|s/pa_EyO$ߠ7IAI7T.w^S%5l`?e k7#lF]ҋa.Nq%-'"Qx/gSޫ ~W~ֶY~Y?7'Z}e -TEk7.-ϬUE}JWYP&2[ ;$Oʂf8@u_|`ݎOˠ:Ql6~#jMQ=ixyF O+ĿJWu[oÉļxM|b5۠A_Yp __EyOl8=yF^S%5l/@tlO&F %Y|u 򣜋&6ˠ:Ql7GZöfFl/x17įA$⾲mZyS󠍫זDJe( 70nȯ),Muϗ;W؛u\AD/ʢݾw/Ak]M7oF!2 AI7TGys,)}kc/wro dW,Mu[=A_Y|6-kD\yr۬nuYT[RT G+<g/ Ӝ'z:IAoѸ5I ->&j\9<˸ql}e k6c̹K.se Z:qtltWŲ˝n/t$$IUoyPWDHHmsPykc o}ěn$RBDbscT5I͟ d;|eT>Ysl[tT~$ߣq&j%l+m$RC@Op`dry *.w¨|a1}RM D:c!)(gDpĚwUZ)A(;)1$sDp#*}y-'d ^Sa^wDw?+וe>~9Y-)}e>-?So&2$_DKM8EVAke>h&k=9eh 0>&IFM'8 C9]]4m(n 0\Dž%g qgŶ  ۟1TEd:T5I uAboJ¡.,]D+%6 ȯ)lPYt\ Zf4櫄ie"CnZ$ѴCUࡀ6NTK`C ɷ:T6 0(n-  &ѸY\ +FHSXY\ +FH;- X-$IѪI(>&F!Y>h>&}ěFMRI}RMRC#"$o75I*9PAI75IhC"$oAuo} D:c!)(lld- _e>h=%`%&2$.w:|툪-b2M>Ipq/oؘN |a_-zv;+%6k/G_UE{gs-y$D >I|vUdVSo&Ο$I| ɷ:r[(nMҥ)XCqmVPHP7INj(gYZ2Q=iSoyF JINj(gYZ2Q=i 0A-(>&IFM%g qgxiCph'6<,8 (8x@0PÎvs<-m(n 0\ǁ.c%g qg7  .RsncnDqW (8x@0PÎvs<7  .RsncP<$ FGx(`$P}RM$$I{)`ޜlED"ۖ*}ViMeyÁJV\W_}^__UZm? AIAoѸ5I@p8sh:P, (`I͹ FJ 0㝯l[JD )9?c` sP}RM$$JQzY茣oH|۟_s| y0X_ _-ٛAXAeQn(π(PPPAs| y{Ig_s| yڻ`o_DHHΟ$VSoIn?TBAOy1{ M>&IFM$$IѪHH zU uAe$Y-)?oEyO{`˥|UZ,~ 75\#N./͑}e|tEy$| ɷ:r[(nMҥ)XCqmVPHP7ěNj(gYZ2@"]ěNj(gYZ2@ˇUZ,oIn$$TT,4T>Mq&F$H>&F!@^SoO7ěܨ 4sr^SoO7D:oAI7>LIRءh }e>c˝e ;mTM=%`%&2$_DImU[VSo&Ο$Ų絚//{ p xU~몭 ep`SV[=Ɛ^ڸmZy˝ *n9Y-)G7yʎz _- 7BX ᭞H/m\6-kxU~++ľMCkl:ֶ|N%EyO "2M>I AD:^  ntD 0PܛsJS`Cڭ`@oѸ5Pβd{ ܌X5Pβd{s'-l`r0ZP}bM~ěѪHH ѪH᭞H/m\6-kxUcz }M'OBDlΟ$[qlyiBm'OBDV>IHq_X[v;+%6᭞H/m\6-k7#͞9QLa '[O Z=mtI7q&7T'ToF!"N,R-T^T4EKޓCd¡Y= .c˝VAk[`,Fp86D\;au- A6u#07&ʉl(`6Jb ŵZC!C$7ojzsWCpF HS{҃ojzsWCpF H;p ZyF JIq&ѸTP}RMRC<+|}RM7ě) GEyOIq<7ojTsrojʇEyOIq<I$ߠ7IG5$RBDlF H{ҋzeޓCd[ȼ᭞H/m\6-kxUfU0dKr=r l,~1/P҄y uG7;vN(sˇ&/kdl ; s@uΟ$=_L^ Unڻ=7į(/&:$D Zö,H嫋e×6Y}!"J|`Ο$[oA?YT[9y'}RM~ěѪHH=T5I tgs? mZy˝l6&㜹vo oAI7>LIRء\)2A?Ÿ~UɠȒ@_ċH>I AO@q"QYO;em Z~*}YedW }*}\?kcҸK,OO_*8.^n`ċGċ@U6\E@Hc⸜Kꏄw;ZzfY6W Oכl]U6qms ^ڽO ZH=tI//wiVAk[`2I@p8sh:P, (`I͹ FJ 0㝯l[JD )9?c`@p8sH_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbcremlm.htm.h/$ Remote debug limitations

Remote debug limitations

Remote debugging imposes the following limitations:

  • Browse only displays the file system on the local system. The file system on the remote system cannot be displayed.

Related concepts
Remote debugging

Related tasks
Applies to AIXApplies to WindowsApplies to HP-UXApplies to SolarisStarting the debugger for debugging compiled languages remotely

Copyright IBM Corporation 1999, 2002

 k*r$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwdpath.htm.h/$ DER_DBG_PATH environment variable

DER_DBG_PATH environment variable

The DER_DBG_PATH environment variable is used by the debug engine, the debugger user interface, or both to locate debug source files on your client workstation that are not stored in the same location as the executable being debugged. For example, if your debug executable is stored in F:\BUILDS\SANDDUNE\TEST but your source code is stored in F:\SOURCE and F:\SOURCE\INCLUDE, you should set your DER_DBG_PATH variable as follows:

Applies to AIX set DER_DBG_PATH=F:\SOURCE:F:\SOURCE\INCLUDE

You can set the DER_DBG_PATH environment variable on both client and server systems. The search for source files starts on the server first.

Note: When using the DER_DBG_PATH environment variable with the Distributed Debugger user interface or engine daemon, be sure to set the variable before starting the daemon.

Related tasks
Setting environment variables for the Debugger

Copyright IBM Corporation 1999, 2002

jzs k0s$7yf>_>X>';7./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwfordt.htm.h/$ Fortran supported data types

Fortran supported data types

You can monitor an expression that includes the following data types:

  • BYTE
  • CHARACTER
  • COMPLEX(4)
  • COMPLEX(8)
  • COMPLEX(16)
  • INTEGER(1)
  • INTEGER(2)
  • INTEGER(4)
  • INTEGER(8)
  • LOGICAL(1)
  • LOGICAL(2)
  • LOGICAL(4)
  • LOGICAL(8)
  • REAL(4)
  • REAL(8)
  • REAL(16)

Derived types can also be monitored.

CRAY pointers (INTEGER pointers) can be monitored.

Copyright IBM Corporation 1999, 2002

 k_t$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwfrtlm.htm.h/$ Fortran debug limitations

Fortran debug limitations

Monitored expression limits

  • The following may not appear in a monitored expression:
    • array constructors
    • assignments
    • function references
    • pointer assignments
    • recursion
    • registers
    • storage monitors
    • structure constructors
    • subroutine references
    • vector subscripts
    • literal constants used outside of array subscripts or substring bounds context
    • subscripts and substring bounds that are of types other than INTEGER(4)
  • Some compile options affect the evaluation of expressions. In these cases, the default settings are assumed.
  • Variables from previous invocations of a recursive procedure cannot be monitored. Only the copy of the variable from the last instance can be monitored.

Copyright IBM Corporation 1999, 2002

zs ku$"yf>_>X>';"./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwincl.htm.h/$ INCLUDE environment variable

INCLUDE environment variable

The INCLUDE environment variable is used by the debugger to locate include files on the workstation.

The environment variable does not apply to languages that do not support include files.

Related tasks
Setting environment variables for the Debugger

Copyright IBM Corporation 1999, 2002

utine  kꂱv$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwlibp.htm.h/$ LIBPATH environment variable (AIX and OS/2)

LIBPATH environment variable

Applies to AIXApplies to OS/2Restriction: This is supported on AIX and OS/2 only.

The LIBPATH environment variable tells the debug engine where to look for debugger DLLs on the workstation.

Copyright IBM Corporation 1999, 2002

2" bor kTw$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwpath.htm.h/$ PATH environment variable

PATH environment variable

The PATH environment variable is used to locate the debugger executable and the executable programs to be debugged, as well as any other executables being run on the workstation.

Related tasks
Setting environment variables for the debugger

Related reference
Applies to AIX Applies to OS/2 LIBPATH environment variable

Copyright IBM Corporation 1999, 2002

of typ kx$ yf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwstep.htm.h/$ Step commands

Step commands

You can use step commands to step through your program a single line or, on AIX or Windows, one disassembly instruction at a time.

The following types of step commands are available:

Step Command Button Shortcut Description
Step Over Step Over push button F8 Executes the current line, without stopping in any functions or routines called within the line.
Step Into Step Into push button F11 Executes the current line. If the current line contains a call to a function or routine, execution stops in the first line or disassembly instruction of the called function or routine. If the called function or routine was not compiled with debug information, the function or routine is shown in a disassembly view.
Step Debug Step Debug push button F7 Executes the current line. Execution stops at the next line encountered for which debug information is available. This could be in the current function or routine, in the called function or routine, or in a function or routine called within the called function or routine.
Step Return Step Return push button Shift+F11 Executes from the current execution point up to the line immediately following the line that called this function or routine. If you issue a Step Return command from the main entry point (in C++, the main() program), the program runs to completion.

Execution of your program may stop earlier than indicated in the step command descriptions, if the Distributed Debugger encounters a breakpoint or an exception occurs.

Tip: You can use combinations of step commands to step through multiple calls on a single line.

Related tasks
Stepping through a program
Skipping over sections of a program

Related reference
DER_DBG_DEEP_STEP_DEBUG

Copyright IBM Corporation 1999, 2002

$ ky$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwtgrid.htm.h/$ DER_DBG_TABGRID environment variable

DER_DBG_TABGRID environment variable

The DER_DBG_TABGRID environment variable affects how the debugger uses tab characters to align tabs to columns in a source or mixed view within a Source pane. The value of this variable is an integer indicating the starting position and frequency of the tab. For example, if you set DER_DBG_TABGRID=6, the debugger sets tab stops at 6, 12, 18, 24, and so on. If DER_DBG_TABGRID is set to a nonzero value, the setting of DER_DBG_TAB has no effect.

Related tasks
Setting environment variables for the debugger

Related reference
DER_DBG_TAB environment variable

Copyright IBM Corporation 1999, 2002

nter kz$yf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwvcase.htm.h/$ DER_DBG_CASESENSITIVE environment variable

DER_DBG_CASESENSITIVE environment variable

The DER_DBG_CASESENSITIVE environment variable, if set to a non-null value (for example, "yes", 1, "true", etc.) tells the debugger to compare part names and module names on a case-sensitive basis. By default the debugger converts all names to uppercase for comparison purposes. Note that this does not affect filesystem accesses which are operating system dependent and not affected by DER_DBG_CASESENSITIVE.

Related tasks
Setting environment variables for the debugger

Copyright IBM Corporation 1999, 2002

/a>_>X>';0./usr/share/man/info/en_US/xlf/html/debugger/ref/rbwvdbtb.htm.h/$ DER_DBG_TAB environment variable

DER_DBG_TAB environment variable

The DER_DBG_TAB environment variable affects how the debugger expands tab characters in a source or mixed view within a Source pane. The value for this variable is an integer, indicating the number of spaces to convert a tab character into. Unlike DER_DBG_TABGRID, DER_DBG_TAB does not cause the debugger to place tabbed information in specific columns; it simply results in each tab in the displayed files being converted to the indicated number of spaces.

Note: If DER_DBG_TABGRID has been set to a nonzero value, the setting of DER_DBG_TAB has no effect.

Related tasks
Setting environment variables for the debugger

Related reference
DER_DBG_TABGRID environment variable

Copyright IBM Corporation 1999, 2002

 k|AX>X>X>';./usr/share/man/info/en_US/xlf/html/debugger/taskswvdbt/A k}$+yf>_>X>';+./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwdumpi.htm/$ Debugging Dump Files

Debugging Dump Files

Applies to AIXApplies to OS/2 Note: Postmortem debugging is available on AIX and OS/2 only.

To start debugging a dump file, from the command shell type:

idebug [path]dumpfilename

where dumpfilename is the name of the dump file you want to debug. You can also enter the dump file name from the Startup dialog, by starting the debugger without parameters, or by choosing File->Startup from the Source or Session Control windows.

Once you have started debugging a dump file, you can use a subset of debugger features to examine registers, storage, and code for the executable that caused the trap. You can access all the debugger monitors (registers, call stack, storage, local variables, program, private and popup), but you cannot change the contents of items in these monitors (for example, registers in the registers monitor).

The following debugger commands are disabled, and icons for them are hidden or greyed out, when you are debugging a dump file:

  • Halt command
  • Step commands
  • Commands to set, clear, disable, enable, or delete breakpoints.

The Run command is available, but its only effect is to cause a redisplay of the exception that caused the trap.

Copyright IBM Corporation 1999, 2002

which k~$ yf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcaddreg.htmm/$ Adding a register to the Monitors pane

Adding a register to the Monitors pane

Applies to Fortran Restriction: Registers are not supported as expressions, and cannot be added to the Monitors pane.

You can add a register to the Monitors pane if you want to monitor only a few registers during the execution of your program. Registers can also be monitored in the Registers pane and Storage Monitor panes. To monitor all registers during program execution, use the Registers pane.

To add a register to the Monitors pane:

  1. Do one of the following:
    • Select Source > Monitor Expression from the menu bar.
    • Press Shift+F9.
    • Click on the Monitors tab and select Monitors > Monitor Expression from the menu bar.
  2. In the dialog, enter the name of the register you want to monitor. Check the Registers pane to see a valid Registers name.
  3. Select Program Monitor.
  4. Click OK to add the register to the Expressions monitor and dismiss the dialog.

To add multiple registers to the Monitors pane:

  1. Click on the Monitors tab and do one of the following:
    • Select Source > Monitor Expression from the menu bar.
    • Click on the Monitors tab and select Monitors > Monitor Expression from the menu bar.
    • Press Shift+F9.
  2. In the dialog, enter the register you want to monitor.
  3. Click Monitor to add the register to the monitor.
  4. Repeat steps 2 and 3 until you have added all the registers you want to monitor.
  5. Click Cancel to dismiss the dialog.

Related tasks
Viewing the contents of a register
Adding a new Storage Monitor pane for an expression or register

Copyright IBM Corporation 1999, 2002

your k.<$ zf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcaddvar.htmm/$ Adding a variable or expression to the Monitors pane

Adding a variable or expression to the Monitors pane

If you want to keep track of the contents of variables and expressions during program execution, add them to the Monitors pane. You can add variables and expressions to the Monitors pane from the Source Pane or the Monitors menu.

Local variables that are in scope can also be monitored in the Locals pane. By default, all local variables in scope are added to the Locals pane.

To add a variable or expression to the Monitors pane from the Source pane:

  1. Ensure that the Source pane is set to source view. To set the Source pane to a source view, select Source > Source View from the menu bar.
  2. Do one of the following:
    • Ensure that Add to program monitor in the Preferences > Debug menu is selected and then double-click the variable or expression you want to monitor.
    • Double-click or highlight the variable or expression you want to monitor and then right-click on the highlighted variable, and select Add to Program Monitor from the pop-up menu.

To add a variable or expression to the Monitors pane from the Monitors menu:

  1. Select Monitors > Monitor Expression from the menu bar.
  2. In the dialog, enter the variable or expression you want to monitor.
  3. Select the Program monitor radio button.
  4. Click OK to add the variable or expression to the monitor and dismiss the dialog.

To add multiple variables or expressions to the Monitors pane from the Monitors menu:

  1. Select Monitors > Monitor Expression from the menu bar.
  2. In the dialog, enter the variable or expression you want to monitor.
  3. Select the Program monitor radio button.
  4. Click Monitor to add the variable to the monitor.
  5. Repeat steps 2 to 4 until you have added all the variables or expressions you want to monitor.
  6. Click Cancel to close the dialog.

Related reference
Fortran supported data types
Fortran supported expression operands
Fortran supported expression operators

Copyright IBM Corporation 1999, 2002

p k8O$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcbpdel.htm/$ Deleting a breakpoint

Deleting a breakpoint

You can delete single breakpoints from the Source pane and the Breakpoints pane. All breakpoints can be deleted at once from the Breakpoints menu. If you delete a breakpoint, all information on it is lost. If you do not want to lose your breakpoint information, but do not want the breakpoint to stop execution, disable the breakpoint instead. For information on disabling breakpoints, see the related topic below.

To delete a single breakpoint in the Source pane:

  1. Scroll to the line which contains the breakpoint you want to delete.
  2. Do one of the following to delete the breakpoint:
    • Double-click on the line number in the prefix area of the line to delete the breakpoint.
    • Right-click on the breakpoint and select Delete Breakpoint from the pop-up menu.

To delete a single breakpoint in the Breakpoints pane:

  1. Click on the Breakpoints tab to bring the Breakpoints pane to the foreground.
  2. In the Breakpoints pane, expand the list of breakpoints by clicking on the plus icons (Plus icon - click to expand one level of a list) until you see the breakpoint you want to delete.
  3. Right-click on the breakpoint you want to delete.
  4. Select Delete Breakpoint from the pop-up menu.

To delete all breakpoints, select Breakpoints > Delete All Breakpoints from the menu bar.

If you want to temporarily prevent all breakpoints from stopping execution, disable them instead by selecting Breakpoints > Disable All Breakpoints.

Related tasks
Enabling and disabling breakpoints

Copyright IBM Corporation 1999, 2002

< k"t$N zf>_>X>';N ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcchrep.htm/$ Changing the representation of monitor contents

Changing the representation of monitor contents

You can change the representation of variables and expressions in the Monitors or Locals panes. You can change the representation for existing entries or the default representation for future entries in the Applications Preferences dialog.

To change the representation of a variable or expression:

  1. Right-click on the variable or expression for which you want to change the representation.
  2. Select Representation from the pop-up menu. The Monitor Representation dialog appears.
  3. Select the representation you want from the list of available representations.
  4. Click OK to change the representation and dismiss the Monitor Representation dialog.

To change the default representation of variables or expressions:

  1. Select File > Preferences from the main menu bar. The Application Preferences dialog appears.
  2. In the left-hand pane of the Application Preferences dialog, go to Debug > program > language: Default Monitor Representation, where program is the name of a program loaded in the Distributed Debugger you want to change the default representation for and language is the language the program you are debugging was written in.
  3. Change the representations for variable types by clicking on the representation associated with a variable type and selecting a representation from the list.
  4. If you want these representations to become the default for the Distributed Debugger to use when no program profile is available, select the Debugger Defaults checkbox. If you want to restore the Debugger factory default settings, click on the Default push button.
  5. Click OK to change the default representations and dismiss the Application Preferences dialog.

The default representations of variables and expressions in programs you have previously debugged will not be affected by these changes.

Copyright IBM Corporation 1999, 2002

po k]$ zf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcbpead.htm/$ Enabling and disabling breakpoints

Enabling and disabling breakpoints

You can disable a breakpoint so that it does not stop execution, and then later enable it again. Information about the breakpoint (such as type, location, condition, and frequency) is saved by the Distributed Debugger when the breakpoint is disabled. Since this is not true when the breakpoint is deleted, the advantage of disabling a breakpoint instead of deleting it is that it is easier to enable a breakpoint than to recreate it. Enabled breakpoints are indicated with a red dot (Brakpt.gif (97 bytes)). Disabled breakpoints are indicated with a gray dot (BrkptDis.gif (97 bytes)).

You can enable or disable breakpoints from the Breakpoints pane. Also, you can enable or disable breakpoints from the Source pane.

To enable or disable a single breakpoint from the Breakpoints pane:

  1. Click on the Breakpoints tab to bring the Breakpoints pane to the foreground.
  2. In the Breakpoints pane, expand the list of breakpoints until you see the breakpoint you want to enable or disable.
  3. Right-click on the breakpoint you want to enable or disable.
  4. Select Enable Breakpoint or Disable Breakpoint from the pop-up menu.

To enable or disable a breakpoint from the Source pane:

  1. Scroll to the line which contains the breakpoint you want to enable or disable.
  2. Right-click on the line which contains the breakpoint you want to enable or disable.
  3. Select Enable Breakpoint or Disable Breakpoint from the pop-up menu.

To enable all breakpoints, select Breakpoints > Enable All Breakpoints from the menu bar.

To disable all breakpoints, select Breakpoints > Disable All Breakpoints from the menu bar.

Related tasks
Deleting a breakpoint

Copyright IBM Corporation 1999, 2002

 kꖀ$p zf>_>X>';p ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcdaem.htm/$ Starting the Distributed Debugger user interface daemon

Starting the Distributed Debugger user interface daemon

Start the Distributed Debugger user interface in daemon mode if you want the Distributed Debugger user interface to appear only after you have started a debug engine.

To start the Distributed Debugger user interface daemon, issue the following command at a command line prompt:

idebug -qdaemon -quiport=<port>

where <port> is the port number where you want the Distributed Debugger user interface daemon to listen for a debug engine.

Applies to AIXApplies to SolarisApplies to WindowsWhen you start the debug engine that will connect to this daemon, the port specified with the -quiport option to the irmtdbgc command must be the same as the one specified with the -quiport option to the idebug command.

Related tasks
Applies to AIXApplies to WindowsStarting the debugger for local debugging
Applies to AIXApplies to WindowsApplies to HP-UXApplies to SolarisStarting the debugger for debugging compiled languages remotely

Related reference
idebug command
Applies to AIXApplies to SolarisApplies to Windowsirmtdbgc command

Copyright IBM Corporation 1999, 2002

 k* $#zf>_>X>';#./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcflyov.htm/$ Enabling tool tip evaluation for variables

Enabling tool tip evaluation for variables

Tool tip evaluation of variables ("hover help for variables") provides you with a quick way to view the value of a variable in the Source pane. When you point at a variable in the Source pane, the variable is evaluated and its value displays in a manner similar to a tool tip. This feature is enabled by default when you first start the debugger.

To enable tool tip evaluation of a variable, select Source > Allow Tool Tip Evaluation from the menu bar.

A check mark appears next to the Allow Tool Tip Evaluation menu item when tool tip evaluation for variables is enabled.

To enable tool tip evaluation for variables as the default:

  1. Select File > Preferences from the main menu.
  2. Select Debug from the list of preferences to set.
  3. Select Allow Tool Tip Evaluation from the Debugger Defaults section.
  4. Click OK to enable the tool tip monitor and dismiss the dialog.

Note: Tool tip evaluation uses spaces and punctuation to parse source and, therefore, will only evaluate identifiers and not expressions. If you wish to evaluate more complicated expressions with tool tip, highlight the entire expression in the Source view and then position the mouse pointer to hover over the highlighted expression and see the evaluation.

Related concepts
Distributed Debugger: Value Panes

Copyright IBM Corporation 1999, 2002

plies kx$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcbplst.htm/$ Setting multiple breakpoints

Setting multiple breakpoints

You can set several breakpoints with the same optional parameters from any of the breakpoint dialogs.

To set multiple occurrences of a type of breakpoint:

  1. Select the type of breakpoints you want to set from the Breakpoints menu.
  2. From the Breakpoint dialog, enter the required information for the first breakpoint. Change any fields in the Optional Parameters section of the dialog, as desired.
  3. Click on Set. The settings are saved for the current breakpoint.
  4. For each additional breakpoint, change the information for the new breakpoint (for example, new line number, new function , or new address) and click on Set.
  5. After you have set the last breakpoint, click on Cancel to dismiss the dialog.

Related concepts
Breakpoints

Related tasks
Modifying breakpoint properties
Enabling and disabling breakpoints
Setting a conditional breakpoint
Deleting a breakpoint
Viewing breakpoints

Copyright IBM Corporation 1999, 2002

 k9$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcmxead.htm/$ Enabling and disabling a monitored variable, expression, or register

Enabling and disabling a monitored variable, expression or register

You can disable the monitoring of a variable, expression or register. The advantage of disabling a monitored expression instead of deleting it is that it is easier to enable a monitored expression than to recreate it.

You can enable or disable monitored variables, expressions or registers from either the Monitor pane or Locals pane.

To enable or disable a monitored expression:

  1. Locate the variable, expression or register you want to disable or enable in the Monitors pane or Locals pane.
  2. Right-click on the variable, expression or register you want to enable or disable.
  3. Select Enable or Disable from the pop-up menu.

Copyright IBM Corporation 1999, 2002

. kꦏ$L zf>_>X>';L ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwrestr.htm/$ Restarting a program

Restarting a program

Applies to AIX Applies to Windows Restriction: Restarting a program is supported on AIX and Windows only. It is not supported if you have attached to a process or JVM.

To start debugging your program from the beginning when your program is stopped, do one of the following:

  • Click Restart push button in the toolbar.
  • Select Debug > Restart from the menu bar.
  • Press Ctrl+Shift+F5.

To start debugging your program again from the beginning when your program is running:

  1. Issue a Halt command by doing one of the following:
    • Click Halt push button in the toolbar.
    • Press Ctrl+F5.
    • Select Debug > Halt from the menu bar, if the program is currently executing within the debugger.
  2. Set a breakpoint at the location you want to run to, if it is not the beginning of your program and you have not already set a breakpoint there.
  3. Click Restart push button in the toolbar or select Debug > Restart from the menu bar.

If the previous run of your program produced side effects such as the creation of an output file and the program logic will be changed by the existence of such files from a previous debug session, you may want to erase these files before restarting.

Related tasks
Applies to AIX Applies to Windows Halting execution of a program
Running a program

Copyright IBM Corporation 1999, 2002

orde k ;$wzf>_>X>';w./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcnewstr.htmm/$ Adding a new Storage monitor pane for an expression or register

Adding a new Storage Monitor pane for an expression or register

Applies to Fortran Restriction: Storage Monitor panes are not available when debugging Fortran programs.

Registers can also be monitored in the Registers pane and the Monitors pane. To monitor all registers during program execution, use the Registers pane.

You may wish to add a new Storage Monitor pane for an expression or a register if you want to monitor specific locations in storage or only a few registers during the execution. To monitor all locations in storage during program execution, use the Storage pane.

You can also monitor all storage locations in a storage monitor, but it follows a specific variable, expression, or register as it changes. Warning: If there is a variable in scope which has the same name as the register that you are trying to use, the variable will be used first.

To add a new Storage Monitor pane for an expression or register from the Registers pane:

  1. Highlight the expression or register for which you want to add a new Storage Monitor pane.
  2. Right-click the highlighted expression or register and select Add to Storage Monitor from the pop-up menu. A new Storage Monitor pane will appear with the expression or register appearing as the monitor's tab title. The current value of the expression or register will be highlighted.

To add a new Storage Monitor pane for an expression or register from the Monitors pane:

  1. Do one of the following:
    • Select Source > Monitor Expression from the menu bar.
    • Press Shift+F9.
    • Click on the Monitors tab and select Monitors > Monitor Expression from the menu bar.
  2. In the dialog, enter the expression or register that you want to monitor.
  3. Select the Storage Monitor radio button.
  4. Click OK to add the new Storage Monitor pane.
  5. A new Storage Monitor pane will appear with the expression or register appearing in the monitor's tab.

To add multiple new Storage Monitor panes from the Monitors pane:

  1. Do one of the following:
    • Select Source > Monitor Expression from the menu bar.
    • Press Shift+F9.
    • Click on the Monitors tab and select Monitors > Monitor Expression from the menu bar.
  2. In the dialog, enter the first expression or the name of the register that you want to monitor.
  3. Select the Storage Monitor radio button.
  4. Click Monitor to add the new Storage Monitor pane for the expression or register entered.
  5. Repeat steps 2 to 4 until you have added all the storage locations or registers that you want to monitor.
  6. Click Cancel to close the dialog.

Tip: Check the Registers pane to see a valid register name.

Related tasks
Changing the representation of storage contents
Changing the contents of a storage location
Viewing a location in storage

Copyright IBM Corporation 1999, 2002

g k$ zf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwsetad.htm/$ Setting an address breakpoint

Setting an address breakpoint

Applies to AIXApplies to WindowsRestriction: This is supported for AIX and Windows only.

You can set an address breakpoint from the Source pane, and from the Breakpoints menu.

To set an address breakpoint from the Source pane:

  1. Ensure the Source pane is set to a disassembly or mixed view. To set the Source pane to a disassembly view, select Source > Disassembly View. To set the Source pane to a mixed view, select Source > Mixed View.
  2. Make sure the appropriate line is visible in the pane by using the scroll bar or cursor keys to locate the line.
  3. Double-click on the address in the prefix area of the line, or right-click on the Disassembly or Mixed view and select Set Breakpoint from the pop-up menu.

To set an address breakpoint from the Breakpoints menu:

  1. Select Breakpoints > Set Address from the menu bar.
  2. Enter either the address where you want to set the breakpoint or an expression that evaluates to an address. The address must be entered in hexadecimal notation.
  3. Set any optional parameters that you want for the breakpoint.
  4. Click OK to set the breakpoint and dismiss the Address Breakpoint dialog. Alternatively, use the Set button to set the breakpoint without dismissing the Address Breakpoint dialog.

Related concepts
Breakpoints

Related tasks
Setting multiple breakpoints
Setting a conditional breakpoint
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints

Copyright IBM Corporation 1999, 2002

._>X>';. ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcrnapg.htm/$ Running a program

Running a program

You can have a program run until one of the following occurs:

  • end of program is reached
  • an active breakpoint is hit
  • a specific line number is reached
  • an exception occurs.
  • Applies to AIX Applies to Solaris a fork(), exec(), or system() call is reached.

If you select Debug > Run, the program will run until the end of the program is reached, an active breakpoint is hit, or an exception occurs if exception filtering is set to a level other than NONE.

To run a program until an active breakpoint is hit, do one of the following:

  • Click the run button (Run push button).
  • Select Debug > Run from the menu bar.
  • Press F5.

If you select Run to Location, the program will run to the statement selected unless an active breakpoint is hit, an exception occurs or the end of the program is reached.

To run a program to a specific line number:

  1. Make sure the line to run to is visible in the Source pane by using the scroll bar or cursor keys to locate the line.
  2. Run the program to the line by doing one of the following:
    • Right-click on the line to bring up the pop-up menu, then select Run To Location.
    • Click on the line to select it, then select Debug > Run To Location from the menu bar.

Related concepts
Breakpoints

Related tasks
Stepping through a program
Setting multiple breakpoints
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints

Copyright IBM Corporation 1999, 2002

ew kH$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwskpjm.htm/$ Skipping over sections of a program

Skipping over sections of a program

Restriction: When debugging interpreted Java programs, you cannot skip sections of a program.

You can skip over sections of code to avoid executing certain statements or to move to a position that certain statements can be executed again.

To skip over a section of code:

  1. Scroll to the line where there are statements that you want to avoid executing or you want to execute again.
  2. Jump to the line by doing one of the following:
    • Right-click on the line and select Jump to Location from the pop-up menu.
    • Click on the line to select it, then select Debug > Jump to Location from the menu bar.

Using Jump to Location can cause unpredictable results if you jump outside the current function, jump over code that has side-effects (for example, calls to functions whose results are assigned to variables, or functions that change the contents of variables passed by reference), or jump into the middle of a block such as a for loop.

Related tasks
Running a program

Copyright IBM Corporation 1999, 2002

 k$Czf>_>X>';C./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcsetcd.htm/$ Setting a conditional breakpoint

Setting a conditional breakpoint

When you set a breakpoint, you can specify the parameters or conditions for that breakpoint.

To set a conditional breakpoint:

  1. Ensure the Source pane is set to source view. To set the Source pane to a source view, select Source > Source View.
  2. Use the Breakpoints menu to select the type of breakpoint that you want to set.
  3. On the Breakpoint dialog complete any or all optional parameters that you want as conditions for your breakpoint.
  4. Click OK to set the conditional breakpoint and dismiss the dialog.

Related concepts
Breakpoints

Related tasks
Setting multiple breakpoints
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints
 Optional breakpoint parameters

Copyright IBM Corporation 1999, 2002

glega k$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwstenv.htm/$ Setting environment variables for the Debugger

Setting environment variables for the Debugger

The Distributed Debugger user interface running on a workstation uses environment variables to specify the settings for a variety of factors, such as the location of source files for the client application, the location of the executable for that application, and case-sensitivity when doing particular name comparisons.

You may want to set environment variables for the debug engine and Distributed Debugger client. You can set the environment variables based on your operating system. For instructions on setting environment variables refer to your operating system manuals.

All variables listed in the related references below can be set on the host where the debug engine is located. The following variables are also used by the Distributed Debugger client: DER_DBG_PATH, CLASSPATH, and PATH.

Related reference
DER_DBG_CASESENSITIVE
DER_DBG_PATH
DER_DBG_TAB
DER_DBG_TABGRID
INCLUDE
LIBPATH
PATH

Copyright IBM Corporation 1999, 2002

To Loc kBq$ zf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcsetln.htm/$ Setting a line breakpoint

Setting a line breakpoint

Line breakpoints can be set from either of the following:

To set a line breakpoint in the Source pane:

  1. Ensure the Source pane is set to source view. To set the Source pane to a source view, select Source > Source View.
  2. Make sure the appropriate line is visible in the Source pane by using the scroll bar or cursor keys to locate the line.
  3. Do one of the following:
    • Double-click on the line number in the prefix area of the line.
    • Right-click on the line you want to set a breakpoint on, and select Set Breakpoint from the pop-up menu.

To set a line breakpoint from the Breakpoints menu:

  1. Select Breakpoints > Set Line from the menu bar.
  2. Enter the name of the module or routine in which you want to set a breakpoint in the Executable or Package entry field in the Line Breakpoint dialog. If this module or routine is loaded, you can select it from the pulldown list in the Executable or Package entry field.
  3. Choose or enter the object, class or source file that is associated with the module or routine specified in the Executable or Package entry field and contains the line where the breakpoint is to be set from the Object pulldown list.
  4. Choose the source file containing the code for the object or class file from the Source pulldown list. (This step is optional if you have not selected to defer the breakpoint.)
  5. Enter the line number within the source file where you want to place a breakpoint in the Line entry field
  6. If the module or routine you entered in the Executable or Package entry field is not currently loaded, click on the Defer breakpoint check box.
  7. Set any optional parameters that you want for the breakpoint.
  8. Click OK to set the breakpoint and dismiss the Line Breakpoint dialog. Alternatively, use the Set button to set the breakpoint without dismissing the Line Breakpoint dialog.

Related concepts
Breakpoints

Related tasks
Setting multiple breakpoints
Setting a conditional breakpoint
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints

Copyright IBM Corporation 1999, 2002

 kj$Szf>_>X>';S./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwstloc.htm/$ Starting the debugger for local debugging (AIX and Windows only)

Starting the debugger for local debugging

Applies to AIXApplies to Windows Restriction: Local debugging is supported on AIX and Windows only.

To start debugging a program locally from the command line, issue the idebug command with local debug parameters at a command line prompt.

If you issue the idebug command without any options, the debugger will prompt you for the required information in the Load Program dialog.

Tip: If you have debugged a specific program before and do not want to use the previous profile options, make sure that Use program profile is not selected or use the -p- option of the idebug command.

Once the debugger user interface is running, you can debug other programs using the same debugger session by selecting File > Load Program from the main menubar.

Related reference
idebug command

Copyright IBM Corporation 1999, 2002

ong>E kꔕ$ zf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcsetlo.htm/$ Setting a load occurrence breakpoint

Setting a load occurrence breakpoint

Load occurrence breakpoints halt execution of your program when the DLL or dynamically loaded module specified is loaded into memory. You can set load occurrence breakpoints from the Breakpoints menu.

To set a load occurrence breakpoint from the Breakpoints menu:

  1. Select Breakpoints > Set Load Occurrence from the menu bar.
  2. Enter the name of the DLL or dynamically loaded module to set the breakpoint for.
  3. Set any optional parameters that you want for the breakpoint.
  4. Click OK to set the breakpoint and dismiss the Load Occurrence Breakpoint dialog. Alternatively, use the Set button to set the breakpoint without dismissing the Load Occurrence Breakpoint dialog.

Related concepts
Breakpoints

Related tasks
Setting multiple breakpoints
Setting a conditional breakpoint
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints

Copyright IBM Corporation 1999, 2002

ed in t k($ zf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwstrmt.htm/$ Starting the debugger for debugging compiled languages remotely

Starting the debugger for debugging compiled languages remotely

Applies to AIXApplies to WindowsApplies to Solaris Restriction: Remote debugging is only supported on AIX, Solaris, HP-UX, and Windows.

The debugger allows you to run the debugger user interface and the debug engine on separate machines. These separate machines can be running different operating systems. When you start the debugger for remote debugging, you first start a debug engine daemon. This daemon waits for a connection from the debugger user interface. Once a connection is established, you can begin to debug your program.

To start debugging a remote program from the command line:

  1. On the remote system, start the debug engine with the irmtdbgc command at a command line prompt. For information on irmtdbgc command parameters, see the related topic below.
  2. On the local system, use the idebug command to start the Debugger user interface and then select TCP/IP connection in the Load Program dialog and enter the name of the host where you started the debug engine to make the connection.

Alternatively, you can use a command line after starting the debug engine to issue the idebug command, using the remote debug parameters. If you use this method to make the connection, you must specify the -qhost parameter and the -qlang parameter for the language you are debugging. For information on the idebug command parameters, see the related topic below.

Tip: The debug engine is terminated if the debugger cannot load the program you want to debug. Also, the debug engine is terminated when the program you are debugging runs to completion or is terminated manually. To prevent the debug engine from being terminated in these situations, use the -qdaemon option of the irmtdbgc command.

Related concepts
Remote debugging

Related reference
Applies to AIXApplies to WindowsApplies to Solarisirmtdbgc command
idebug command

Copyright IBM Corporation 1999, 2002

/a>_>X>';F ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcsetwa.htm/$ Setting a storage change breakpoint

Setting a storage change breakpoint

Restrictions: Storage change breakpoints are not supported on Solaris or when debugging AIX data types other than 64-bit.

Storage change breakpoints halt execution of your program whenever storage at a specific address is changed. For example, if a byte being watched contains X'40' and the program writes X'40' to that byte, the storage change breakpoint is not triggered. If the program writes X'41', the storage change breakpoint is triggered.

To set a storage change breakpoint from the Breakpoints menu:

  1. Select Breakpoints > Set Storage Change from the menu bar.
  2. Enter an address or expression that evaluates to an address in the Address or Expression field.
  3. Specify the number of bytes to be monitored in the Bytes to Monitor field.
  4. Set any optional parameters that you want for the breakpoint.
  5. Click OK to set the breakpoint and dismiss the Storage Change Breakpoint dialog. Alternatively, use the Set button to set the breakpoint without dismissing the Storage Change Breakpoint dialog.

Caution: If you set a storage change breakpoint for any address that is on the call stack, be sure to remove the breakpoint before leaving the routine associated with it. Otherwise, when you return from the routine, the routine's stack frame will be removed from the stack, but the breakpoint will still be active. Any other routine that gets loaded on the stack will then contain the breakpoint.

Related concepts
Breakpoints

Related tasks
Setting multiple breakpoints
Setting a conditional breakpoint
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints

Copyright IBM Corporation 1999, 2002

=" k$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwwrtdb.htm/$ Writing a program for debugging

Writing a program for debugging

You can make your programs easier to debug by following these simple guidelines:

  • Do not hand-tune your source code for performance until you have fully debugged and tested the untuned version. Hand-tuning may make the logic of your code harder to understand.
  • Where possible, do not put multiple statements on a single line, because some Distributed Debugger features operate on a line basis. For example, you cannot step over or set line breakpoints on more than one statement on the same line.
  • Assign intermediate expression values to temporary variables to make it easier to verify intermediate results by monitoring the temporary variables.

To debug programs at the level of source code statements, you must specify the compiler options that generate debug information. In some cases, you must specify additional options that enable the debug engine to work properly with your code.

Copyright IBM Corporation 1999, 2002

str k$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcsetxp.htm/$ Selecting debugger recognized exceptions

Selecting debugger recognized exceptions

You can choose the type of exceptions the Distributed Debugger recognizes for processes you are debugging, so that stepping or execution will stop when one of the selected exceptions is thrown. By default, all unhandled exceptions are recognized by the Distributed Debugger.

To select the exceptions recognized by the Distributed Debugger:

  1. Select File > Preferences from the menu bar.
  2. Expand the Debug item in the left-hand window of the Application Preferences dialog.
  3. Locate the process you want to set the exceptions recognized for.
  4. Click on Exception Filter Preferences Settings.
  5. Check the type of exceptions you want the Distributed Debugger to recognize or uncheck exceptions you want the Distributed Debugger to ignore.
  6. Click OK to close the Application Preferences dialog.

To undo changes that you have made to the exception filter, click Reset.

To restore the exception filter preferences factory default settings, click Default.

To set your new exception filter preferences as the default for that programming language, check the Debugger Defaults box before clicking OK.

Copyright IBM Corporation 1999, 2002

k, k$Wzf>_>X>';W./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcstep.htm/$ Stepping through a program

Stepping through a program

You can use step commands to step through your program a single statement at a time. The statements can be source code or disassembly instructions. For an explanation of the step commands, see the related topic below.

To execute a Step Over command, do one of the following:

  • Click the step over button (Step Over) on the toolbar.
  • Select Debug > Step Over from the menu bar.
  • Press F8.

To execute a Step Into command, do one of the following:

  • Click the step into button (Step Into) on the toolbar.
  • Select Debug > Step Into from the menu bar.
  • Press F11.

To execute a Step Debug command, do one of the following:

  • Click the step debug button (Step Debug) on the toolbar.
  • Select Debug > Step Debug from the menu bar.
  • Press F7.

To execute a Step Return command, do one of the following:

  • Click the set return button (Step Print) on the toolbar.
  • Select Debug > Step Return from the menu bar.
  • Press Shift+F11.

Related tasks
Running a program

Related reference
Step commands
DER_DBG_DEEP_STEP_DEBUG

Copyright IBM Corporation 1999, 2002

h kV$ zf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcvumem.htm/$ Viewing a location in storage

Viewing a location in storage

Applies to Fortran Restriction: Storage information is not available when debugging Fortran programs.

You can view the contents of storage from the Storage pane or from a new Storage Monitor pane that you have created.

To view the contents of storage from the Storage pane:

  1. If desired, change the representation of the storage contents in the Storage pane.
  2. If necessary, use the scroll bar in the Storage pane to view storage locations above or below the starting address of the Storage pane.
  3. You can jump directly to an address in the Storage pane by doing the following:
    • Double-click on any address field in the Storage pane.
    • Enter the address you want to view. This address can be an expression, for example &x.
    • Press Enter. The storage contents now shown in the Storage pane are centered around the address you just entered.

To view the contents of storage from a Storage Monitor pane that you have created:

  1. If desired, change the representation of the storage contents in the Storage Monitor pane.
  2. If necessary, use the scroll bar in the Storage Monitor pane to view storage locations above or below the starting address of the Storage Monitor pane.
  3. Use the Go to Address button to return to the starting address of the Storage Monitor pane.

Related tasks
Changing the representation of storage contents
Changing the contents of a storage location
Creating a new Storage monitor for an expression or register

Copyright IBM Corporation 1999, 2002

es_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcvureg.htm/$ Viewing the contents of a register

Viewing the contents of a register

You can view the contents of a register from the Registers pane, the Monitors pane if you have added the register there, or a Storage Monitor pane if you have added the register there.

To view the contents of a register in the Registers pane:

  1. Expand the thread for which you want to view the registers.
  2. Expand the register category that contains the register you want to view.
  3. If desired, use the scroll to scroll the pane until the register is visible.

To view the contents of a register you have already added to the Monitors pane:

  1. If necessary, use the scroll bars to scroll the Monitors pane until the register is visible.
  2. If desired, change the representation of the register: right-click on the register and select Representation from the pop-up menu. Then select the desired representation from the Monitor Representation dialog box.

To view the contents of a register you have already added to a Storage pane:

  1. If necessary, use the scroll bars or PageUp and PageDown keys to scroll the Storage pane until the register is visible.
  2. If desired, change the representation of the register: right-click on the register and select Representation from the pop-up menu. Then select the desired representation from the Monitor Representation dialog box.

Related tasks
Adding a new Storage Monitor pane for an expression or register
Adding a register to the Monitors pane

Copyright IBM Corporation 1999, 2002

/b k$_ zf>_>X>';_ ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcvuvar.htm/$ Viewing the contents of a variable or expression

Viewing the contents of a variable or expression

You can view the contents of a variable or expression in the Locals pane or the Monitors pane, if you have added the variable there. By default, all local variables in scope for the selected stack entry are added to the Locals pane. Call stack entries can be viewed or selected in the Stacks pane, and they include threads and, depending on the language you are debugging, functions, methods, procedures, or entry points.

To view the contents of a variable or expression in the Locals pane:

  1. If the variable that you want to view is associated with a function, method, procedure, or entry point call of a particular thread, go to the Stacks pane and choose the appropriate call stack entry. This will update the Locals pane with the value of the local variables of that particular call.

    Selecting a thread in the Stacks pane is equivalent to selecting the top or first entry for that thread (for example, the first function, method, procedure, or entry point call). If the debug engine does not support locals monitoring for secondary entries (entries other than the top entry), then the Locals pane thread nodes for those secondary entries displays "Locals not available" when they are selected.

  2. Expand the thread in the Locals pane where the local variable you want to view appears.
  3. If necessary, use the scroll bars to scroll the pane until the variable is visible.
  4. If your variable is a class, struct or array, it can be expanded to show its individual elements.
  5. If desired, change the representation of the variable: right-click on the variable and select Representation from the pop-up menu. Then select the desired representation from the Monitor Representation dialog box.

To view the contents of a variable or expression you have already added to the Monitors pane:

  1. Use the scroll bars to scroll the pane until the variable is visible.
  2. If your variable is a class, struct or array, it can be expanded to show its individual elements.
  3. If desired, change the representation of the variable: right-click on the variable and select Representation from the pop-up menu. Then select the desired representation from the Monitor Representation dialog box.

If a variable or expression is not in scope, a message displays in the Monitors pane instead of a value.

You can also view the contents of variables in the Source pane with Tool-tip evaluation. To enable Tool-tip evaluation, see the related topic below.

Related tasks
Enabling Tool-tip evaluation for variables
Adding a variable or expression to the Monitors pane
Viewing a location in storage

Copyright IBM Corporation 1999, 2002

a k$jzf>_>X>';j./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbcvwbp.htm/$ Viewing set breakpoints

Viewing set breakpoints

A list of breakpoints you have set is kept in the Breakpoints pane for the process you are debugging. This list is originally collapsed and can be expanded to show your installed breakpoints. The list of breakpoints is divided into the types of breakpoints you may have set. Expanding each type of breakpoint will provide you with a list of breakpoints for that type.

To view the list of breakpoints:

  1. Click on the Breakpoints tab for the process or program you are debugging.
  2. Expand or collapse the list of breakpoints to display the breakpoints you want to see.

To view the properties of a breakpoint, right-click on the desired breakpoint and select Properties from the pop-up menu.

Related concepts
Breakpoints

Related tasks
Setting multiple breakpoints
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint

Copyright IBM Corporation 1999, 2002

cals p k$ zf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwatloc.htm/$ Attaching to a local running process

Attaching to a local running process

Applies to AIXApplies to WindowsRestriction: Attaching to a local running process is only supported on AIX and Windows.

You can attach the debugger to a running process either by using the Attach dialog or from a command line by using the -a option of the idebug command. See the related topic below on when to attach to a running process.

To attach the debugger to a running process with the Attach dialog:

  1. Select File > Attach to invoke the Attach dialog.
  2. Select the Compiled tab.
  3. Select the Local radio button.
  4. Select the dominant language of the program.
  5. Optionally, enter the full path name to the executable associated with the process you want to attach, in the Process Path field.
  6. If you do not know the Process ID of the process you want to attach to, click Get Process List. The Process List dialog provides a list of the processes running on the local machine. Select a process in the Process Path field and click OK to close the Process List dialog.

    or

    If you know the Process ID, click the Enter Process ID radio button and enter the Process ID in the Process ID field.

  7. Click Use program profile if you want to use this feature.
  8. Click Attach to attach to the process and close the Attach dialog.

To attach the debugger to a running process from a command line, enter the following command:

Applies to AIXApplies to Windowsidebug -a<process_id>

where <process_id> is a valid process id on your system.

Important: Do not attach to operating system processes or to the debugger's own processes. Attaching to such processes can cause unpredictable results.

Applies to AIXThe debugger detaches from the process on debugger exit. The Terminate button can be used to terminate an attached process. To detach without exiting the debugger, use the Detach button or select Debug> Detach from the menu bar.

You cannot restart a program that you have attached to.

Related concepts
When to attach

Related tasks
Attaching to a remote running process

Related reference
idebug command

Copyright IBM Corporation 1999, 2002

 l$tzf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwatrmt.htm/$     aeost<>cghilmnpr "./bdu=ATfy&;CILMPRSw,-0DEGkx189:OWY_qv'2BHNUX[]!35FK48``p3aa8P@$ (X_C8 \eeZQ@B:@u& sz` 8H ?A"ˆ?DҗhOJ9Z%`0  +]BH80476隺,o7}]+vRc%q#nnt>cyǫ%@&NVKp[t(Tr]s*igۃ˦؏ߝJߟ^=^a'*sW\,*8ۼ۝/3$Aqm@@u|N|َ]s(Uc뛌z]2. RNVKslߐ`߫|A:9Y.=Yo}uwױO,"Ʒ흨?]s(dfp SX;X)W]oGG댶Xt۝/0 9q@|A 25\.D7BcN5w (BB+6V /PI>_e6UA А2 m5hItrrs+>KLi״B'+%Gf}]}]qaAw˫|dk3ϫusi/3%@Ct&`#A <k3o^NT8z\v_I͍H)_ sieg̢R =6̬'ݔWjWMfVtdܮk1-Xkw 9P@~we+QfU׽Wm5|i׵nm;Wt8J1Pr8綠 BI|Ԁck+BxJVlmGk%C Wt:Jډ9Mbb)͍H AVlmG,  BI߫ϛzNz&2fƸ7@Ԙ7v1O?j?W]w./3渺]F=L}vgk3iz9Mbb)[~l2NSX;X*|A0ַu}W^vKmy̴v,]87ݔ|Ԁk3NfޤqIk?k3y{ϱMfp_W^gf~;@ |Ԁmo8c3NVlmAgwk3|Ζ |Ԁ(NVlmGm}]Ѵg fo1Q'.('.(qo>~tm5` 﫮|Ԁcãi 9Y2c/nQѴg ?66 :6`z2a')@@SXw>lm@26VlmG`62|ܯfq:lh  )H;66 Vg+66#ݔ]xFY^gKo+)_1Q')@*ځ<po A$J zTqAĐ*k+>HAA@<(IS*)i*`8bH5o[f,9w*"HŮYUG[)]gwׄm5,*']sޤ z9fe\חݔ [)_f@ku̢R nW>lm@.Rz7v?)͍Hf!ZuԁFuO71$Ax zeَ2﫝l޹tg$Ax rE"H$UaOTi%LG鳴gM5 r=qH$oMCp"%zVr*sc)A$J zMTyn >;F}a9q@ $ILtX%LG,IA`$,4„I%1Ҫž<0aP`$ Ϸ<y F#:I+[~{m2^=^aʔ qWȤIS*)6$@}6vzhs\h` $¢ZXeW! 25]6K9R\h`4I^Aˊ8Xh7 JcU=Ry*`8bH5o $ a $I)V䩃 T V}XxxP $:UXSՖTqAĐ*k+>Yr&TD !zCI%FajI+EajOMTA<Ɔ JZJq;H $:UXSܘ %LGb/xX W\gYo0@G.eDIr*s]5뚁can be  k $|zf>_>X>';|./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwbpdef.htm/$ Setting a deferred breakpoint

Setting a deferred breakpoint

A deferred breakpoint is a breakpoint set in a DLL, dynamically called routine, executable, or package that is not currently loaded. You can defer the following types of breakpoints:

  • line breakpoints
  • function breakpoints

To set a deferred breakpoint, click on the Defer breakpoint check box when setting one of the above types of breakpoints. When you restart a program, the breakpoints that were set in the previous debug session for classes not currently loaded will be set as deferred breakpoints. These deferred breakpoints will be enabled when the classes corresponding to the breakpoints are loaded.

Related concepts
Breakpoints

Related tasks
Setting multiple breakpoints
Setting a conditional breakpoint
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints

Copyright IBM Corporation 1999, 2002

Q k&$2 zf>_>X>';2 ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwbpmdb.htm/$ Modifying breakpoint properties

Modifying breakpoint properties

You can change the following properties of a breakpoint:

  • Which threads the breakpoint applies to.
  • How often the debugger should skip the breakpoint (the frequency).
  • Whether to stop on the breakpoint only when a given expression is true. Expressions can only be applied to the following breakpoints:
    • line breakpoints
    • procedure breakpoints
    • address breakpoints
  • Whether to defer the breakpoint. Only the following breakpoints can be deferred:
    • line breakpoints
    • procedure breakpoints

You can also change the Required parameters fields for a breakpoint. Changing these fields results in the existing breakpoint being deleted and a new breakpoint being set.

To change a breakpoint's properties:

  1. Click on the Breakpoints tab to bring the Breakpoints pane to the foreground.
  2. In the Breakpoints pane, expand the list of breakpoints until you see the breakpoint you want to modify.
  3. Right-click on the breakpoint you want to modify.
  4. Select Modify Breakpoint from the pop-up menu. A Breakpoint dialog corresponding to the breakpoint type appears displaying the current settings for the breakpoint.
  5. Change the breakpoint's properties in the Breakpoint dialog.

Related concepts
Breakpoints

Related tasks
Setting multiple breakpoints
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints

Copyright IBM Corporation 1999, 2002

6$ k&$9zf>_>X>';9./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwchgreg.htmm/$ Changing the contents of a register

Changing the contents of a register

To change the contents of a register in the Registers pane, Monitors pane or Storage Monitor pane:

  1. In the Registers pane, or Monitors pane expand the entry which contains the register whose value you to want to change.
  2. Scroll to the register you want to change and do one of the following:
    • Double-click on the register.
    • Select Edit from the pop-up menu.
  3. Enter a value that is valid for the current representation of that register.
  4. Press Enter to submit the change. The Distributed Debugger checks for a valid value.

Related tasks
Viewing the contents of a register
Adding a register to the Monitors pane

Copyright IBM Corporation 1999, 2002

 k$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwchgstr.htmm/$ Changing the contents of a storage location

Changing the contents of a storage location

Applies to FortranRestriction: Storage information is not available when debugging Fortran programs.

To change the contents of a storage location in a Storage pane or Storage Monitor pane:

  1. Select the Storage pane or Storage Monitor pane where you want to make the change.
  2. Scroll down to the storage location you want to change.
  3. Right click and select Edit or double-click on the value you want to change.
  4. Enter a valid value for that storage location.
  5. Press Enter to submit the change. The Distributed Debugger checks for a valid value.

Copyright IBM Corporation 1999, 2002

>

< k$A$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwchgvar.htmm/$ Changing the contents of a variable

Changing the contents of a variable

To change the contents of a variable in the Locals or Monitors pane:

  1. Expand the monitor containing the variable whose value you want to modify.
  2. If your variable is a class, struct or array, expand it to show its individual elements.
  3. Scroll down to the variable you want to change and do one of the following:
    • Double-click on the variable or variable element.
    • Right-click on the variable and select Edit from the pop-up menu.
  4. Enter a new value for the variable or variable element.

Related tasks
Adding a variable or expression to the Monitors pane

Copyright IBM Corporation 1999, 2002

"> k$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwchstr.htm/$ Changing the representation of storage contents

Changing the representation of storage contents

For each Storage or Storage Monitor pane you have, you can change the representation of the storage and the number of columns shown in each pane.

These settings affect only the Storage or Storage Monitor pane you are viewing, so you can have multiple Storage Monitor panes with different settings.

  • Select the representation of storage for the Storage pane or Storage Monitor pane you are viewing from the Content style pulldown list. The Content Style pulldown list is at the bottom of the pane.
  • Select the number of columns shown in a Storage pane or Storage Monitor pane from the Columns Per Line pulldown list. The Columns Per Line pulldown list is at the bottom of the pane.

Copyright IBM Corporation 1999, 2002

or k`$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwcmpdb.htm/$ Compiling a program for debugging

Compiling a program for debugging

In order to debug your program at the source code level, you need to compile your program with certain compiler options that instruct the compiler to generate symbolic information and debug hooks in the object file. See your compiler reference documentation on how to compile your program with debug information.

Related concepts
Applies to AIXApplies to WindowsOptimized code debugging

Related tasks
Writing a program for debugging

Copyright IBM Corporation 1999, 2002

/ul>  kJr$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwhalt.htm/$ Halting execution of a program

Halting execution of a program

Halting a program stops the execution of the program without terminating the execution of the program. It allows you to pause and examine the program's internal state and then continue execution without restarting the program.

To halt execution of a program that is currently running in the debugger, do one of the following:

  • Click on Halt push button.
  • Select Debug > Halt from the menu bar.
  • Press Ctrl-F5.

You may find that execution halts in a function other than the one you are debugging (for example, a system library routine). To run to the end of that routine and stop in your own code, do one of the following:

  • Issue a Step Return command.
  • If the previous technique results in the debugger displaying the message "Cannot determine return address", issue the Step Debug command until execution returns to your code
  • If you know what line in your program will be the next to execute after the current function returns, go to the source pane containing that line, set a breakpoint on it, and issue the Run command.

Related concepts
Step commands

Related tasks
Running a program
Stepping through a program
Setting a line breakpoint

Copyright IBM Corporation 1999, 2002

in kx$ zf>_>X>'; ./usr/share/man/info/en_US/xlf/html/debugger/tasks/tbwprcbp.htm/$ Setting a procedure breakpoint

Setting a procedure breakpoint

Applies to FortranRestriction: This section applies to debugging Fortran programs only.

You can set procedure breakpoints from the Object Modules pane and from the Breakpoints menu.

To set a procedure breakpoint from the Object Modules pane:

  1. Expand the list in the Object Modules pane until you see the procedure you want to set a procedure breakpoint on.
  2. Right-click on that entry and select Set Procedure breakpoint from the pop-up menu.

To set a procedure breakpoint from the Breakpoints menu:

  1. Select Breakpoints > Set Procedure from the menu bar.
  2. Enter the name of the procedure you want to debug in the Procedure entry field in the Procedure Breakpoint dialog. If this executable is loaded, you can select it from the pulldown list in the Procedure entry field.
  3. Choose or enter the object or source file that is associated with the module or routine specified in the Executable entry field and contains the line where the breakpoint is to be set from the Source pulldown list.
  4. Set any optional parameters that you want for the breakpoint.
  5. Click OK to set the breakpoint and dismiss the Procedure Breakpoint dialog. Alternatively, use the Set button to set the breakpoint without dismissing the Procedure Breakpoint dialog.

Related concepts
Breakpoints

Related tasks
Setting multiple breakpoints
Setting a conditional breakpoint
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints

Copyright IBM Corporation 1999, 2002

OM k8AX>X>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/A kL$ zf>_>X>' ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbaddp.htmtm/$ Add Program dialog box

Add Program dialog box

Restriction: This dialog box applies only when debugging on the AS/400.

Use the Add Program dialog box to specify the type and the name of the program, service program, or Java class that you want to add to the list of programs under debug mode. Programs under debug mode must include at least one module that has been compiled with debug data. Java classes must be compiled with debug data.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Program Name Specify the name of the program or service program that you want to add to the list of programs or service programs being debugged. The program or service program name can be in any of the following formats:
  • Library/program
  • *LIBL/program
  • *CURLIB/program
  • Program (same as *LIBL/program)

Alternatively, specify the Java class that you want to add to the list of programs being debugged. The Java class can be in any of the following formats:

  • Partial path/Java class (if the partial path is in the CLASSPATH as defined in the Debugger Settings dialog box)
  • Java class (if the class is in the CLASSPATH as defined in the Debugger Settings dialog box)

Adding a program that has multiple modules with the same name is not supported and will result in an error message.

Program Type Specify the type of program you want to add by selecting one of the following choices.
Program Select this choice if you are adding a program (*PGM).
Service Program Select this choice if you are adding a service program (*SRVPGM).
Java Class Select this choice if you are adding a Java class.
Push buttons
OK Adds the program you specified and closes the Add Program dialog box.
Cancel Closes the Add Program dialog box without adding a program.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

" k_$ zf>_>X>' ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbalay.htmtm/$ Add Layout dialog box

Add Layout dialog box

Restriction: This dialog box applies to debugging OS/390 C/C++ programs only. It does not apply when debugging OS/390 interpreted Java programs or OS/390 Java program objects.

Use the Add Layout dialog box to specify an address and XML layout file name for the layout element you wish to add to the Mapping pane.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

HEX Address Enter the HEX address for the storage that you want to map.
Layout File Name Enter the path and name of the layout file you want to use to map storage. If you do not know the path and name of the layout file name, you can locate it through Browse.
Push buttons
OK Creates the layout element you specified and closes the Add Layout dialog box.
Browse Opens a file-selection window so you can locate and select the XML layout file.
Cancel Closes the Add Layout dialog box without loading an XML layout file.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

d>  l΍$.zf>_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbdset.htmtm/$   aert<>dilnops "/bcgh.=fmuvy,0STw4ACDIJLMVkx-125BEPj():;FHNU&9RWz8OY!3KQqG8 C x p0@X' $I VC(*ZY$`(slR86a(64 -C k.Y`0`Ime,A!$lS)0$`ppA( 0 F[Yr@, ` %٩ZT9V@*JaX\ݩ?Jm3)j9&%rs% 0ɬ.nPЉ4@;jk1}Xb0T*̦xs~,nlL,6dp@Y p%s-ٳf5ژc2BF钅d,kK/|ݩ<$pd pNp5L1<19QePJP$p5eũ7jar\; iO͜H(+.;Y;DlZ5L0 8H栻P֔4o< \-39j.-Mf4yu2Lp%9Z?֤Qe)Jԁε ,BJU8 )8i,*ydOm[8ژL9j.-M`|-Eũ~7yu2Lp%ymOB٩P$(9Z?֤ iOrV$Z8r 2P ˆqwxZ~8Ҟce֋O#9j.-M`O kJEEZvg 8,ƴ^x22xO2FUXX,2p .vg r\; dS 9fJu2Ԯ.SM0LJg'2 .^;0tB2k|ݩ<'w .5͝r&E^=#f5ژc2r\;7ja̦rcxbr˦T闗J*S+hh|]5yn2- T:b3 >.!;]-{ySe) ƴ^lo "\a;6wSL*_Ggf%K:dL ]xm[;]ĩr&ҁ == QE k @5𶋢"9/k Aɴq[\Bl?ZBq -BFln%ũoh.Gu5tT\bT1I 1E,Yt~7)Em`|6 rgrJKC]hH%*.C@F]:,Ӓ Ι{L3S5P?@!j1Ma-ȳNKrm(d-F0AIj7g|nq-m.-L3{Es8 ,8PV ciC$'S {V~ _fT1L3h͜JiCCr訹Ĩb.b7tYR5Vom[X #܃9RH4kEI#Z.i| rK?܀gLkvrm(M97.P?ɴ97HtiBcmqm[ @Bm i@rn?ӌ"y`<jbasv"rm(d-F0A?2-ݷ{ ٳA0qJ8f S0TYk_bfBT܇  TĨmpᦨpX Ҫm1Emvlk^.rI@F\ot 2kt%*aHT4AH(?ӌ"w5  r_ti@!j1٪~%Rt#{6pH4Hs @` E* \x⡉m Lkܐx 9܌2B7U+HP[\n-,TlasU+Hsi@rn?ɸ)rMɺ@{{N2 kj`skzDMɺ@{{N2 kARv SYژc`28T|RLAɴq[\B[Thv$o ^ $*RE* \ٳ] @XX 8fLMQfl=Ubx: 5L5K_Bٵ8 ,8PPs*RE* \E;6p|R NZ*DlbPQFrlS]JYtx|1%<%*5dRwT#-!#vgHқۗS=45C"._%@cyJ)sK2.^Φ=KZbr͆=#+^[Yrxsw 1ess2)PR'U !;r]lS]J+49r;RLM`e"._ˆeORLԧ(n S 49L38rd‚`SX*YxȥAK*_k.\0 a*RE* \!b.TE:S ?܀pڜM`e".yeҥDlSO;*RPڜJSOfθ}d˚~-&ҁ == QEeot0AA9@"@&ҁ == QE )x;ũL10`x5ETPɑH96{N2 k@ |jM۽Z֢)R͝2P kE#b7iqse@gf $ 5O̦v"E 6YJaa2@-Eũf!82F2p[.hL8X˅%Td-Id‚T Rו#S)85ETPsw 1%j5OZ*' Φ#./7VETR;^͜^Yٳ$iMOm˩Ķ~*7ZK~59p̩[I Paa1#)tׇ9.@r*Rcyme™`A19p62 6* 9.@)sLЂr2k{0+[)S @F٢@D == QE k @$]Tj%Ma96{N2 kF-BFlSOfXeQU7( [ÜJtMKrm(M q[\F[VC[ rm(M q[\B" MLZ.nkR"rm(d-F0AIj7u5V7d !bkʝ{of=Ubx: 5LaˆeOSt)ٳ dnP+lbfvl@AAs8֋#KK*Yqjk1-Sju0KhTZ@cxJxMtՍ ZlAK 9rU+KZy0ըnSCxbqP͞kQs./7VT'uKٲ?7k;6p)Iu1sC_mpT0nkRh5O79.@w# nY'u5V7d d,\'-j,!ٳÝMu*.{9r 2{6rkk.Yor\@ctMXVd,\wٳÝMu*.zhhO NꗿdJH%lTS;6wS]5j.rSԶ5)8bG\0Κ%@MtՍ18X~\1L\0 a?Xˆ1<3Nw -v.wS]5cyeҥDlSO;*R ]ˑJSOf%T5)[!Mɺ@{{N2 kj`siJtHd-F0AȤQeV SYژcLAɴq[\B *v7-jߩ0SEL0>rm(M q[\F[VC[ rm(M q[\B"En iX&-Mf7ja [*RJ/92)&ҁiBcmqoS)wKP-x ,8PW,kK/)rUc!bfTYf*R֕ٱzS)͜H((P͜ i[*kS;6pka8M2VBfSB:ZRGKPiSٳÜijg RFKr; nB?5چOr\ZgQePJZPsw 1%<3 U5T ZvlAK 9rU+KLU Z6=47' ΦkĪVT'g:T\,T>Z^QJ{6p[5xBFgf6)=..zhk`j*/֋T{o Hsw 1WETPݐ*^Φ=KZbr͆=9r[Yrxsw 1essƵQCq4]85ETPN\}<9R禆{6GJH%@˥K3gZ \2m&jS7MA)pďkC^Km嵗 fR"\p+,ب. \64 Z-L0ADeJT6h8Q== QE k @$]Tj%Ma96{N2 kF-BFlSOfXeQU7M2P\-oE`P$)Mɺ@&96&?8Z`-#-{Aͤrm(M q[\B" d7jao7(]X"rm(d-F0Am&hA9rZ`˕Д # Rl p?ӌ"w5 5 P?8Z`-!p2_h+SeJwژc{6Y_ٲ?*JaX\ݩ?Jm3)\ݩ?Y.Smvl勪^(YSY?Jq-HS^5; h$nک.r͝*̦p-{ykk8Z*i,ܶL6-ySJu3H|1^XX5j 3p 6YhzMgfX{khɮ͜Jik.0͞Yt49ɴ97HtiBcmq; +9/k Aɴq[\B+k8*JaX\ݩ?Jm3)5VkEY8`2P vɴ97HtiBcmq;en9/k Aɴq[\BJ{_٪~d9ɴ97H@&ҁ spR_>X>'4 ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbexec.htmtm/$ New Process dialog box

New Process dialog box

Restriction: This dialog box only applies when debugging on AIX or Solaris.

This dialog box appears when a new process has been created as the result of an exec() function call in the program you are debugging. While in the New Process dialog box, you can choose to debug program initialization. When you close the dialog box, you will be debugging the new process rather than the calling process.

Controls and control groupings are described below. Control group and subgroup names appear in italics, and control names appear in bold.

Debug program initialization Select this checkbox to debug code that executes before the main program entry point is called. You might wish to do this if you are debugging C++ code and you need to debug the constructors for your globally-declared C++ class objects (because such objects are constructed before main is entered). If unchecked, the program will run to the main entry point.

By default, this checkbox is unchecked if you are debugging the program for the first time. If you select the checkbox and debug program initialization, then this will become a setting in the program profile and this checkbox will be checked the next time you debug the program. At that time, you can choose to deselect the checkbox or clear the checkbox by clicking Default.
Push buttons
OK Closes the New Process dialog box. The Debugger will be stopped in the new process.
Default If the Debug program initialization checkbox is selected, clicking Default causes the checkbox to return to its default state (which is unchecked).
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

 kQ$' zf>_>X>'' ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbfnod.htmtm/$ Find Node dialog box

Find Node dialog box

Restriction: This dialog box applies to debugging OS/390 C/C++ programs only. It does not apply when debugging OS/390 interpreted Java programs.

Use the Find Node dialog box to locate a layout element or sub-element displayed in the Mapping pane. If found, the matching node is highlighted.

Controls and control groupings are described below. Group names appear in italics, and control names appear in bold.

Name If selected, enter the layout element or sub-element you want to locate into this field.
Offset If selected, enter the offset value you want to locate into this field. If a hexadecimal offset value is specified, the 0x prefix must be used. Otherwise, the offset value is read as a decimal number and converted to a hexadecimal number. The offset is calculated within the currently selected layout element.
Push buttons
OK Starts the search using the name or offset specified. If found, the matching node is highlighted in the Mapping pane. If the node is not found, an information message displays.
Cancel Cancels the find operation and closes the Find Node dialog box.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

t k꾏$ zf>_>X>' ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbjobs.htmtm/$ Job List dialog box

Job List dialog box

Restriction: This dialog box applies only when debugging on the AS/400.

Use the Job List dialog box to select the job you will be debugging.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Select Job Select the job you want to use for debugging from the list of jobs currently available on the AS/400.

The list of jobs is presented in fully qualified AS/400 job name format (job/user/number), where:

  • job is the name of the job as identified to the system
  • user is the user profile under which the job is running
  • number is the system-assigned job number
Push buttons
OK Closes the Job List dialog box and replaces any existing entry in the Job to debug field of the Load Program dialog box with the job you selected.
Refresh Refreshes the list, removing AS/400 jobs that have terminated, and adding ones that started since the Job List dialog box opened or since the last refresh.
Cancel Closes the Job List dialog box without altering the Job to debug field in the Load Program dialog box.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

(which k f$zf>_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbmap.htmtm/$ Mapping pane

Mapping pane

Restriction: The Mapping pane applies to debugging OS/390 C/C++ and COBOL programs only. It does not apply when debugging OS/390 interpreted Java programs or OS/390 Java program objects.

Use the Mapping pane to view a set of elements representing blocks of storage mapped according to a selected storage layout. The top most element represents the layout information (layout name, address, and XML file name). Each sub-element represents a layout element or a nested layout according to the definition from the custom XML layout file.

If an element in the Mapping pane has sub-elements, that element can be expanded to display the sub-elements.

On the Mapping pane, pop-up menu options let you add another layout or expand and collapse layout elements.

On a layout element, pop-up menu options let you refresh, modify, remove or find a layout element.

On a layout sub-element, pop-up menu options let you change the representation and edit the selected element.

Copyright IBM Corporation 1999, 2002

strong kDc$izf>_>X>'i./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbmaps.htmtm/$ Map Storage dialog box

Map Storage dialog box

Restrictions: This dialog box applies to debugging OS/390 C/C++ programs only. It does not apply when debugging OS/390 interpreted Java programs or OS/390 Java program objects.

Use the Map Storage dialog box to select a storage mapping layout of an item selected in the Monitors pane, Locals pane, Registers pane, Storage pane or Storage Monitors pane.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Item selected This group appears for the item selected, where Item selected is the item you have selected in the pane. This group contains a radio button list of available storage mappings for the item selected. From this list, select the desired storage mapping of the item.
Push buttons
OK Adds the storage layout of the item you selected to the Mapping pane and closes the Map Storage dialog box.
Cancel Closes the Map Storage dialog box without selecting the storage mapping of the item.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

the Loa kا $~ zf>_>X>'~ ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbmlay.htmtm/$ Modify Layout dialog box

Modify Layout dialog box

Restrictions: This dialog box applies to debugging OS/390 C/C++ programs only. It does not apply when debugging OS/390 interpreted Java programs or OS/390 Java program objects.

Use the Modify Layout dialog box to change the address or XML layout file name for the selected layout element in the Mapping pane.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

HEX Address Enter the HEX address for the storage map that you want to change.
Layout File Name Enter the path and name of the new layout file you want the storage map to use. If you do not know the path and name of the layout file, you can locate it through Browse.
Push buttons
OK Changes the HEX address or layout file name or both the HEX address and layout file name for the selected layout element and closes the Modify Layout dialog box.
Browse Opens a file-selection window so you can locate and select the XML layout file.
Cancel Closes the Modify Layout dialog box without changing the layout element.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

f" kf $| zf>_>X>'| ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbndrp.htmtm/$ Monitor Representation dialog box

Monitor Representation dialog box

Use the Monitor Representation dialog box to change the representation of an item selected in the Monitors pane or the Locals pane. The representation of only the selected expression will be changed. This dialog box is available for programs written in the C++ and COBOL programming languages.

To modify the default representation, select File > Preferences.... In the Application Preferences dialog box, expand Debug in the navigation tree. Expand the program you are debugging, and select Default Monitor Representations.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Item selected This group appears for the item selected, where Item selected is the name of the expression or variable selected for change in the Monitor Representation dialog box. This group contains a radio button list of available representations for the item selected. From this list, select the desired representation of the item.
Push buttons
OK Changes the representation of the item you selected and closes the Monitor Representation dialog box.
Reset Changes the selection you have made in the Monitor Representation dialog box back to the current representation of the item.
Cancel Closes the Monitor Representation dialog box without changing the representation of the item.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

 k긭 $zf>_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbprli.htmtm/$ Process List dialog box

Process List dialog box

Use the Process List dialog box to select a running process to which the Debugger should attach. The Select Process textbox is a table that displays the process ID and executable name of all processes running on the host system specified in the Attach dialog. Select the process you want to debug from this table.

Controls and control groupings are described below. Control group and subgroup names appear in italics, and control names appear in bold.

Push buttons
OK Sets the selected process ID in the Attach dialog box.
Refresh Refreshes the list of running processes.
Cancel Closes the Process List dialog box.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbsrep.htmtm/$ Representation dialog box

Representation dialog box

Restriction: This dialog box applies to OS/390 C/C++ programs only.

Use the Representation dialog box to change the representation of an item selected in the Mapping pane.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Selection list This group appears for the layout element selected, where the Selection list is the list of format choices. This group contains a radio button list of available representations for the layout element selected. From this list, select the desired representation.
Push buttons
OK Changes the representation of the item you selected and closes the Representation dialog box.
Reset Changes the selection you have made in the Representation dialog box to the present representation of the item.
Cancel Closes Representation dialog box without changing the representation of the item.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

lign= l $:0zf>_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubpnsrce.htmtm/$   aeinot<>cdhlprs "/bfgmu.=kvwy,STx0ACILMR()149DEGOPWj-35;BY_#28:NUVX!FHq8@83 ( xh0`Ya@_P8#:- 0@^ 10 s'cu@6zBGٽ>^1#p·@P@@pd  x9{7w$]<'MU`Z@OQ&쫁rI.Ղ8k=rr6B98hc@Nl\cKL;_W<' rg.zW\[6_k#JmYW= / M,pd~|5ƺgc^05xtp$!U纋^ 2p$ex/_\Ɉk 郑& 7Z*٦.I_ΌK7*=8t1j@RUtU=oCK;ׂ˧ ʽO|n ufpA EȲfhb(p2J.ܫITxst%K7* ]2|rx p`8 Xq"Y*CP4(8]> d ʽVLls1OY*`Cr^._=Yy2éZ1.]<^6:0_|K7*#nF].]=y S߸)sW# ʽ66]* 5/ 6ӵo\/ ʽpwLga/~*쫟t⧊]_(N_ypܫN(XGL#jmk/޸_nUT —y.ܫ{5*Wqr5 v)s\80x,8FAr, b(pm\RcqàW#5UtǫU&6_.]>LJvUjݱr}\.MP\ie˼5|^T~|9+ժ/ͩ/.x7çaK'T8@2=Î X•VXq8U+VpG@ߟ\ ޖRD|Zѫv W<' rg.{]%P_Lv^o 1ՠoF~}r긘eahQWsv!rr5HϪa]qW=sTL rmk/Rk7 o>Qv}ƎNxND?.NF\L24tj粮~ӊɟ!rvUB\'W9 oϮ@}W 8LO; ع9 q0.ÏѫʹWN*~&|MW WsLI oF~}r긘eahz}W$Cbj7U(>GF{*]8)7e^/}_ϛ ʽ9 oϮ@}W 8t^]0!W틟r6ӵ̝^(#ؙQz|LnU%zعOީ*\W9 q0.ÏѫLme+ ʽ|^TRk7 o>Qv}Ǝ2S'\v(Kbj7U(>GF{ \O+q e;ʦI oF~}r긘eahQWsأY/틓@}W 8v+mk/r5H@ߟ\&Eq:#x bj7U(>GF{ \O+q,L@ߜr q0.Ï_" l\R긘eah~÷_W<8|j7#\>\L24tE$*>Ă2Q o>Qv}Ǝ\;~s߆3ӊV;~wL@ߜr q0.ÏʍtwF_'#T&Eq:5s߰Wk2]\L24tEpܫWsأY/틓@}W 8v+ rgVϢm&ӌ4xnt[0-z2qaR܅e\+?s>B&赲^ʃpd8LUi˟q8KۖsW/WN*}_ueKI[ӌ4^ IT"L@n vUϳL&\./ LnU:zqPc 1ڀk 鎪{Ẏ?wqKO%z*17a 2 d͒CP4(8e,r]0!W:Z1㹘pK%]st^ aKO[_Vo $ 8`Q\%TZ(~  ,r]0!W:qIf:zK%]st^7 \]0!WTwU>ه?\ڹ`Cr}?Y;* r;P OǾdθ,N9Rj8$~c UYaTXq8 ~}r +zYI r5hϫF|9+\5ɞعtA~1ەz0c@ߜr "> Nݮʍt틓@}R5sW? OϐI*!{~ 9 oϮ@}R# ʽW<`Cr_Hf(OtWsan'#Tja𯫞5ɞTWCr5H@ߟ\Gk2]?̝^+\=[ o>v+ؙQN 9 cK% v\{͟- Ww|^an>|9+3*}\sTL WTΪ|𝬷K'8&B9D}\w@>^ܵ} c8/2N[Ce6o=_ \MaxH<p yX!hPqMk*_8@#xHq G@N͋9e 1ڀ|\5ɞعMH߅qxk] / M/ֆK23b窞@\L)V_R+_W=qxoOTieՖ.{&FN*~;e ~ .2.oyT xoTi|^anτan;6Lt_]?]D&\Et e+<%8cYO_>zcwմW=8ciOT.̢׾y3r6:wLV;\HG{] fot/{#qReF|i>zp%_W.2.ozct7XoL_`&Pڹ\OvSV;]-g5ݮqP1WZ$ƫ+dme9 @ \5ɞع}Li0Μa[p>ه?\Qkѓ4 —>/{*]8)7e^EZT.{$eUFL&\:^ܵ}ϫʹºqS{N0,7 ]?Jޜa_"Uzxc<5!{*쫟t⧊]_(N_',#o&_JQK!ѵ.F%{IuS᭘s\]0!W,9 @oD~\ f:~/%{l_ʹWN*@@R&\/ϫU&7S᭘w ߹qr.y.ܫVLn;0eS᭘w`)s|^gY;*}\]0!Wj6UV{*1j@RÝ p`8 Xq"Y2-CP4(8ڹj@Fk VLl\}l/ 3,˻b ]?]D$˗xkf58 \sWU&6_-S_l\xoO5e9 @`O'pqe{a5e?L*qV8 >h,a9 գW>xNl\Jʽ 1ՠoF~}r긘eahQWsv!rr5HϪa]qW=sTL rmk/Rk7 o>Qv}Ǝ`Cr}_.ܫRTҮʹm;Y|LnU9 q0.ÏѫLme+ ʽ|^TRk7 o>Qv}Ǝ2S'\v(Kbj7U(>GF{ \OvSV;~wL@ߜr q0.Ïm;Y~烱F_'#T&Eq:5s߰W(N_',j7#\>\L24tGK!S'\>" o>Qv}Ǝ\;~s߆3ӊY|wU2NF~r57U(>GDs'WW<rr5HϪa]qW=߅}\'W@ߜr q0.ÏFSdwF_'#T&Eq:5s߰W~N*~;eWFSdRk7 o>Qv}Ǝv&Tk\8FS5ع9 q0.Ïѫo¾{]9 oϮ@}W 8݆\틓@}W 8쫟trg\ݕ{W=n oFY(c7loNdZ;v ts\U1Ws܅̫trg\ݕ¸7uSOτe\Y> 2ʹR#c]Zp^^ Jvr-ɳ}lxN2la:%0b[$`e郠a}Hq"YtIhCf-{$xk/Pp@ ~N9RGAȄaA8h/Lbzro~ lw$zf>_>X>' ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbabbp.htmtm/$    eot<>adgilnprs "/bchu.=fmvwy,0Tkx&15;ACDEq-49BFIMOPS()2:GHLNRUW!+38VY|6JKXj8pX /pv@I <AĒ (,x(.-䴒B0s,SP82RqSi̻x!X,Auˬ #.rEmeh3,3b`P !w$T `@BF]: 4 %/2a8#fB=(P) }1שm/*NM()RRq`)*\%!:1-Pi0;x)@ ]Ln 1ĶA#H)2]J5kcӻ2G$!A]Cc`MʰZw—s9ހT&1JCLub[Kʠޝ3*}CDӥ܆6/*cى7O!Yv0v/%R1dcl9 ʹ#m/*vGH)2]J5kcӻ2ph0 N$({O&Qr^;\)eӮp^.:a:%J0>aFKҗ 5*ccȤ2":\u›":^L6;Dӌ2a=9P>Ir̝"^(ծT9UL #.Zؽ%@Qrֽ*S1V``HQp@b-yrmHMIMrmHMZZŸAO!Hl% $T'&E ڐ?Xp.BP*tRu›й0vJCLux. lm9UL #.Zؽ%@Qrֽ*S1V``HQp@b-ylz{2`h? ٓ,Ʊf_fOfBRѸĺ3}# Hc鎰YFGH)Ӛ7ojlM@T{17׾x[l!)T|)pHMɸ =ՋKX" )d$"l&E ڐ?Xp.Btg'!!eō˧\)'Fs avʄ1^+dYV2МKSRYP>Ѯ>dY-Tv;2]ܵ8>J5kta,\]t'HBRc'Fs&QV%xNe M˶_(֫t];c 0qtkaٓV(֫um.ai)PTA2孋[-kҥ1@,cf {V--b NZP9h96{V--b aٓd#yP>ѮNѸĺ2G|j0<8eCԊ{d'`mK'FscйfNT%!:2q,osLvX..u%A<$"mX0`&ԁ?jť[tx)@])Aɵ ڱik]<s̝BRcF7_fNZPCR)퐝qn1.q-9}9P>&8 9qtk`ˮ`?$"mX0B&ՃusbFǍwfNT%!:yu0HDڰ`,s,h$"mX0>rmHMZZŸAO!œ)Aɵ ڱik]<s̜L$"lYY7_fNZ̑ʄ1X| rOlquwNhޝ=} \n&\]D'\M `&ԁ?ɴ@&ԁ?jť[tx)@@5Ŕ9h96{V--b rƾtcS:K%:o'*}9v ˧)wlVvc#d]n=?ހ2jE=N6 %Ӄ7—ѹtkUfN&,H@P$p A6 H)fC @,S?[E%\6ax)RFNleXYm )Mɸ i)Mɸ =ՋKX" )3(ۺtNLAɵ ڱik]<Sg*De[9b #.ZץJc Y*@, !ZZŸAO!œ91Sj@b-yBSs̝*T&1ʄ1^lXd9qѼ_%K%A=.f=85J8 Hc鎽LKiyTڐ??Xp.B9hfLnڐ?Xp.BДdz'J r) }1כ9}ĶA>]ƱnZ] M*9P>sj@rnp@b-y_>X>'0 ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbaval.htmtm/$    aeinot "<>dglprs/=bch.fmuvxy0ACMTw145EFLPS,-9DGHIORU#()28BKNW!:;Yq3@ hP`| p`W88,C< HpG t[k.8t$As I&v9{EPz lzAFh(sH8(I d@ C8{KOV&FֲR.)K'Y[Yo.tS0'5&2 $$\S O 8\xT3BLd5!ϸ?}.P_'r\[6knY%o窡N \o.rw~Ȑ21& 9ndVV[ä$\S O P_' xJe$ߡG- 0qLY<.tSä$\S O /b81P;)& 9nd T3HHA, pʽUC1|( qLI&2G$$\S O P_'(~-i %T3쵥P;Rc!?K.)K'Y[Yof/>|Jߥ*pW ߹U:jLd5!YzcZYzg[SjyNe\fSS|Z`2 lý_DMl2z)V^5}e$߮ZCvF,N9R?*XǶ Y?*X•V ? id :M57U)vAt쵤ɇ|J@+k-]}RMqp]}Ɲ d8VV_2 d@IF&je.>NHN?]E,@e(TU)vAt3/\qLY<*UC1|kK[U~,oŠM/7\% oo.Kӥe \쵥oje.>N&@.˖7.Xoo@Ro@I>,jPvZ҈ddsP_'!"x\xT3߮ZP;Rc!?K.)K'ΗUC1|;V.x\n {8@I+/]W+/]v mZ/)L, v oWxVp&_᭘w)QO@% 1c=aޯ쵤b;kHtԘ%*\AKUk KRAGᴭ,!IF&je.>N?]0I[㉝/߮ZP>&je.>N|JLx!'sO߂< dgK<:$ߠ}rM57U)vAtD)EnȔ}RMqp]}Ɲ(%*\AKUk KRAGᴭ,!Ikoje.>N?]%]}RMW i\&>&ѮIѪᔻ :PvZT]}RMW i|sE2 dOf/8mix+xUōQB鲥KxOI77rMW i҇֐.XvZҁI75\\2dqHOk kO,I77}Y)7}RM$`JLd5(p&H8HA, pʽUC1|t쵤$\S O޸oe^N @e(ړ H\qLY<zzb83w$\pܫ7pؽEZvCR?ūu6oꗔ&Uɖ`h~;7ūQ+v o/;H(yje뱞L[0WvZN1H쵤:jLdl. {`pl)Uk VA@ߣ\5\\2dqJZA̘|$~o\7*]}RMqp]}Ɲ d/^?K~\S O 7ܫׇ@IF&je.>NHo\7*>&>&ѮIѪᔻ :PvZ߮ZP>&FR4id c{b>&>&K%&I@It ÎZ+/D(+qD8qL.^=SF]?i ƍu,` Xk/ . Jv@↤Ę  l6+$"zf>_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbchfl.htmtm/$  einot <>adghlprs"/=bcfu.0mvwxy,CFST45AEILOk#-139BDGHMNPRW_:;KUXjz&'28!JYq@@PhoC@0qb@  UƶnrNt6TgUۺ@68V^ 5?//fFi .&0(, qtg Gx4y{7 IAlxftmk!MUxlNS6ғʖbƤC@t5V3x]:zNrbhHkg-P|3g5V3x]:zNrg-Lzkgr̀ۺ}l pިO\kV2]%S |)[=V΃\RPIH0xf9PׂIC(Wl$GAH00P!IA:vL$p "H@0 IAI·=':3!D9%LlU 0~ 81uL~8 t0 $pȡ*dċdqFG=B?+ #(g B8r(J1".;(0Hǽ1^  t 2Hp*҈2ؐ<6Fo O])V Ae(!IAI·F~xSUl#7ӧg+}κܡ]ta `\)xfUtzC0L lF-[1e!%NfCa d$? y/tp 'J68l ^.~UkPS<]k~|T&}L2a7u /r1 뒍c&]9Z~y[<ʄw%@o2g궲تX QNAL Lkg5V3x]:zNrgSqo|F !%N_]BK܀!9e1adz=sEJR_k4C  =z:) :|;ڄzT=_DvlIX堈2ؐ!9Ѫ).`H8sVG?.\ka#zGOJu2qe هϵ }l0.t2ؔI)NY#J#bBGaĠZO_S,:Ag şOK*Wk#1MUxlNg+AAF'FSH(-("; %jj:d|z.pZ VώN7 z3/yx# @4d-("; '^ y鏄ƗVϗyu[Y-~CNjYsNq*{~E=pRAAF'FSH(- U.Ae(#VW)$}ǎdf?[<)O Jv38jl`\)UtIIlj:d҈2ؐ6\[5i?5|RLGx/rj=F'F')ғդN5E:RsDvlH Ga jdftҝ`μr/a.{r|-OϑY;*X~DvlH]:x3@'c ("; ':o\kVΫlþ(HtzPCs@88`"HÑBTɉ̈(@xi#Tpad0$q; % 2HP)O uҝ`2ؔz@4gg5V3x]:zNrg먽F062>ga.N\mOByg `\U"yjzVT7<Ɇl rzw#l.n'k8)\*1[<)O Jv3:7 >0ov}l^nVώN궲àCGc!K+KX~C Uҙ 5&cʡ$JkT.("D$j1{P}e%c#bCFO+ #΋][ @s I :O6 ?W)$}ǎGaăof[>&~Ts)҂#bPF'j:d }l[k3ϭBWS:դO6 ?W)$}ǎHżwr$JPF'j:dҍQNVAsG˝8r=K][ ?K֒8, tF'FSH(-T[5i?5|RLGx62HAqSKׂsyj-[?[>8l e:x7Us̽ @ GHkg; $ 2؞.x/S>][>_1me e:cިOQecE:~kĩ…Htf^jl)NY#J#b@sDvlJդJu2q ˟ޫAAFJO#V6 :I·e ~l4[[<)O Jv3:c7['g,QN5l뒍c%a87 {0e:}Lo;Nw*ztӕ PEW >;/*'3%L8VϭYU~0 >zXɀǕ-Pz[+[~,BoO62!=Vڏ*ZUg/oώN!9CҀppD(Ç"-@ ;(0Hǽ1 @= 2H :Q[[$3x]:zNrb-A JzNt= 3šd.=tc9X3u^ MNW0'zCCghLgJ5wajُϫ/! /|pC s궲z}gPu /r|_%ѕ+|^@#V_P7RJ)h" `P 4? l<6Fo IJv3:7 /[<$[>C şOU%@htzBZy{ wd0ղ=Pp|v aS!ڄzT=_DMjEHV^^Bf=O|; $rDvlHtd0$p~\za#.sԵհcti#BIF'j:d҈2ؐmgڄ>~ BVe:PDvlJդ_S,:Akz~&~Sx^AIF'j:d҉@طn\PDJդ_S,:Q).`H8sVG?.\ka#zG$Ju2qe! #bPF'FSH RS|_%ѕ+ݑl<6Fo IJv3ZOO`W)$}ǎGaāPq[5i?5|RLGx>n=\tїI{Y|]Z_qo-W݅gg şOjv@Q 2H@ lGaāPq[կTvHS3['t;]kpVʶ}l.y?_ `\:դ$6 ?5|RLGxDvlH.z-A)NY#C['g,QNTճJ587g[92J9*ztT%A^'bl쿗D_\k0pU[>yfzwU~0 뒍c&TB!>l}l̈́&@"Ke:B}ϭl!78l e:Bz~9TB!Ĩoȟ_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbchsr.htmtm/$ Choose Source File dialog box

Choose Source File dialog box

Restrictions: This dialog box does not apply when debugging on the AS/400 or on OS/390.

Use the Choose Source File dialog box to select the correct source file for your program. If more than one source file for your program exists in different locations, this dialog box will appear. The dialog box is available when debugging on the AIX, Solaris, and Windows NT platforms.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Push buttons
OK Opens the selected source file, then closes the Choose Source File dialog box.
Cancel Closes the Choose Source File dialog box without opening the new source file.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

tI kzh$zf>_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbclsp.htmtm/$ Browse for Class file dialog box

Browse for Class file dialog box

Use this window to select an interpreted Java class to load into the Debugger. This dialog is available when debugging programs on the AIX, Solaris, or Windows NT operating systems.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Select the classpath component This field incorporates a selection list containing paths and jar or zip files preset by the CLASSPATH environment variable (indicated by a red dot) with a list of those set by the user (green dot). From this list, select the path, jar or zip file that contains the class you want to load into the Debugger.

To select a directory, jar or zip file not named in this list, do one of the following:

  • Click Add directory. A directory-selection window opens so that you can browse for the desired directory. Use the controls in the resulting directory-selection window to find and select a directory.
  • Click Add jar/zip file. A file-selection window opens so that you can browse for the jar or zip file containing the desired class. Use the controls in the resulting file-selection window to find and select a jar or zip file.

The additional list item displays with a green dot. Use the Delete push button to maintain the user-specified list items (green dots); the paths and files (red dots) that are preset by the CLASSPATH cannot be deleted.

Expand the directory, JAR or zip file, then select the class After a classpath component has been selected, this field displays its subdirectories and classes. Select the class you want to load into the debugger.

If only subdirectories are displayed in this field, double-click to expand the one which contains the class to be loaded into the Debugger. The class to be loaded into the debugger can then be selected.
Class selected Displays the class that has been selected to be loaded into the Debugger.
Push buttons
OK Accepts the selected class to the Load Program dialog box.
Cancel Cancels the Browse for Class file operation and closes the window. All selections are discarded.
Help Displays this help.

Copyright IBM Corporation 1999, 2002

U~ l$@&zf>_>X>'A./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbexoc.htmtm/$   einot<>acdghlprs "./bmux=fvy,0AESTw5CDILMORWk&-1349:;GJFHNPX_j#()68BKY!2Uq8A@HpX'H@ H(80p4kk-.$:;t aJ1˝Ony pN^-?V^M[ jaX  @p` eވ^ل1ucko{IjY! _]%VrvҁKe+@X 1 -u);Y|0K9J2]a%BAb+k, 91e9R Tk/! _]%}GoHӒSoJ1gaAADc͞T"!O {JN_ 5RR%}tc9XoSSlVϗ3ܝ/˺}l0(2p]%V="NINٱ%UlX @,(' OpZ><w:' Y%cVl“蜁`gc H:{a"DA`qɅD*ׁ`qɅD'8BxR=" phpi HrR@$ aa h< r&K&$F? -uL~ pX4H -,l8PX08@o{c8n90.` ppX4H -,l!$~ 8[^t Οi.D  (7T@PBxx2؀ԤejY|J.rюLvlAJK0z<-u);Y|0K9J2]a7ٰ!Vc *3k,'ƓU/62a+-:~\KޘOT&~d`U/!"fjݫdz.r8sgx{fK)FBQƺݕARx2؃[ޛK0z9{ tzm}Y{ wd0ղ=0EJR#k0C 1{0|Z+RTNLkcK)-+[Az<:/J pzV?D@ߟ`).X:%ˉɒruhϫeq<:/J pzV?D@).X:[[ruh).X:.~x[Rvaerd!+mXeWko{Iᆪ_Q`a쌬'g;ҭzE& az<:/J pzV?D@ߟ`).X:[jYg&; 7W%>@sj=*te|}NjE 9El?K@U/:=_˥[Vx2؀Tc8 xnae2؁L0\ٜ'9B1[8R˥[Vϭk/&Fc%L>ϭ&Tva+jY}a`e|[?0Nճ\vKB8a6>=;#M)W?bl5R0#xd:^R7&>{R*z|%J[Y}`ՖWy-[SkthMgu);Y|OفuiY%;pX4H -,liBG`zE$tpfʶ {0|'e|H&_Ojmnl07Hr%7˥[VjY}I23(2axw:9&F~:76L~|~_֧xzc#*3k/q߭&lIN$oV.}_RuM;#l5RQԓ t'k,'gɪeWy-[Skthl'k/|0.;+ 7'`>|R]L灗ԝSyN~:76L~~|Kڰل@ߜ Iu2x2؀R]\jYg&; 7W%>@sj=*te|}NjE 9Eleɪ!$~hԗW$v*egcL>C/]*ڶsafh7|U/91eL0\ٜVճj=*s><^S'gg&F~ jY}6Bz5 XOQY};7S\jw)J|~Y9%L9Rʸ|u;%MvK~oڳ$@ ɉ6e ?s  -2؎l\cVϗqɅD'О/ Jj?yf;k[ Jc2 ,'g5RNwٿfէf!=6/ ri)՗fO\cVϭc 9: c)ҁ;r^;pX4H -,l@BG`@,(t>\aCeo{I0K9J2]a&; %c͞jY|J.rߏlOYg|1I~McIeV{0jw3sOϓU/-jY}*\4_*5+#6{燶a?[>MTk/d!+c]Ln_ K }ǎUEHmG\N'`Jto9: c)ҁ;'f=A%5RQj/f_ {JN_ 5RR%}tc+ dea?[gɪe'!y1ڑS,WՖM_h2ڛ[g&K@_&bY<2T2˛ZEVԤer^@ ɉ6I!$~ 8[RGG6oJ1`WvWO|1Iq jYq_ c~Y*NK/*jnYlUl/ᆪ_ԓ#1뒌c&sesgGzoSdgSSktgɪejw?[ 8a6wj&ʌԔFbl'TSA8,OϓU/yI1P/ KRv~|~X -5qe6JL_&bY<2T2˛ZEVԤeruh@ߟ`).X:[2ae2؃@}_S,@ͨk/|eҭ:g=(@MLIeɪ!$~he5RQclqIr˥[Vx2؀Tc8 x< Tk,aq0ysfr˥[Vϭk/&Fc%L>灖7gɪe֧}GYQلv-OU/j/fK78,px$@MLII #`pTp=":8A}rQe[>RB|eҭgzUԓ#1뒌c&sNb?Zڛ[?[?E~ jY~mXeVAՠoN~}bxvae2؎&_.lR`Aހtjme/ Xԓ#?l5R8I𝀾c *3k/~FvK߭N1 _ϓU/#+[tk,'gɪeV\is Xʞ+ 뒌ge\c7/j̟0V9;>!Ջ8sdoTvQ+(2a՗fLzwgS\dwN>~\jw)JF5RK7:lʕaseD 2 /ɲ6ɏ*Ej=W !ԖHOU/ˏ-"v[&In7~a>ԝSz#_>X>' ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbfind.htmtm/$ Find dialog box

Find dialog box

Use the Find dialog box to locate text in the program code displayed in the Source pane.

Applies to OS/400 When using the Find dialog box to locate text, the first occurrence of matching text is highlighted. Using the Find dialog box again to locate the same text will cause the same occurrence of the text to be found. To locate subsequent occurrences of the text, select Source > Find Next from the menu bar. After the last string of matching text is found in the source, using the Find dialog box or Find Next will cause the Source pane to wrap to the top of the source and to the first instance in the source of the string.

Controls and control groupings are described below. Group names appear in italics, and control names appear in bold.

Text to find In this field, enter the text you want to locate.
Case sensitive search If you select this check box, text is found only if both text string and character case are matched.
Push buttons
OK Starts the search using the text and character case option specified. If found, text that matches the search string is highlighted in the Source pane. If the text is not found, an information message displays.
Cancel Cancels the search request and closes the Find dialog box.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

gJ1 lꎑ$\zf>_>X>'PR./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbfnbp.htmtm/$   enot<>adilrs "/bcghpu.=fkmvwy,x05ADFIOPSTq&14;BCEGLMNV9:RUWYj()+23X_#-6|!8HK@ xA3 $@@p8 $$`;@|$KlSI$ H65#aKH۳3,9]MCN2n&Ñpdb嚧>,;@ PBG@|T 0@F]MrP("q6zD$t[-i] u2l2mp)С'S&M2--IqU,jG%*B2mB>,XWNg0)С'S&M2-qrPuIs TduIFئљT5E61낏0IOf A!ItʅF^Tlt#XlSh̪ 5RdkV3ک0QPmѮ <&jlg5V"+^s(V>e`l$lkbFeP^5E6lN( dl`pajDž` A!Zx d?]UL5qrBF22mL: `DS*SvlkbFeP_f,^:$d޶)fU>,^:$d޶)fU%% t@g0)С'S&M2/1rHA\,F:$d޶)fU%Ԏ:HHE623\<0fq7(jQBu59T٬~)fUF*F]M<<GG vSX[L HV^]MʅCt)'C&$jK&$2 9#Sc*prr2y-`r$eZrIbI nH!Ⱥ8$ {>&%?-x5Hr.!#-E62ˇ #.ל& F\5)kdQ.@(nH^-MaJn1 %mikũ2Ctq  ~TYBL{$͍v1<C!a]|?XlSh̪ miے?-kũ2Ctq C&$#_n1(&֑Z$9G-Ыlbͥ:$d{&vloI- >1?c[3*:'}chHqFSBNM2 nH$EE%TdQuIA6!Ⱥ8T.ٱ.&?dlhIlSpQp砘uv"p!G$ ] BL miے?-kũ2Ctq C&$ T A/TkH^-MaH|?XlSh̪ 2ͣ IN :6? $[?׋SXd"۪LHpӐK&%?׋SXd" cjXiʘhdkH&ܑڊl$kHmڊl$qrPI$t7p,9J2L1`pH9k! A @8pÐ1,!ɏ1`pH9k!yTà !(nXr%d<0c$1F AsY] y T+ O SBNMpH di]p)С'S&M2,t۪LJ 9#䀇f >KTSBNMbFeP_u/W03)С'S&5V;~s(WpYʜa=Nj%*v?.Bv\d$A])С'S&T~ZS_[΂ ofpY{caaэle:$ddrGA@8pÐ1,!Ʌpc  8`X) ;61vʑ΂ nꞅÛJ\/qvʜu ˩2_تt .Rc,͍Tez D:&Uxj-Ljl`eKM2,ut) ǜ dk}\9eHl 6ٱBǩCWf> :HSnT.Mus$tk ʆv`gpYTA6m!Ⱥ8(v_n1(&֑Z$9Gyʕ46wٱ@. C0ofSBNMk!P͎p]B'X.S>͇ c(jtP *M#rGE#-x5Hr.!(}ăO(%mikũ2Ctq `%*{a,͌BLqd?ٱ>KTP٬~lllfÆ1?Mõs1vʞT* ZGA6rGZjk ]BPuI@vSBNM۪LJ EE$# X`9TF6*o|lBL:F9BTjsmvҗ ?H8F6nvItAwqqc`+|l ΣY ͌aQMQvjt(Iɼa=\}.WٱP{R/=D9бj NH9(}ĂpK&'T~Zj!΅:$d?Άҗ . >S`+(j}LlYΣ]SШCiKj)R*5 ajkF. ?Jx@8`&L,`8$Y5HN??|^p"^ .SP}N P%*BJ5V?eN.Ra]2 Sccҗ buOpYqq~jZD9мBL‡c)С'S&ڮ2T:kBElٰ?gڊll~! t(IɽU&CX\:? $[?׋SXd"۪LH2 <&lJT-_n1(&֑Z$9G6 c͂P^?hb\].1QPj5B\y2L")•l miے?-kũ2Ctq C&$ S|Kl%mikũ2Ctq 6  mq f.j|. ZGA6&Sa#ZGnHrGEE%) *nS*.miZ$9G[[*Tܺu7pa9N :6N Bʧ.k^rdIp֜`rDc49 BGE#-x5Hr.!(}Ąt)h%mikũ2Ctq vʝ}~665Wٮ-t(Iɽ Vlz5Хf!+ckaC k 66;5Х F6*oٱPa~>c SKF9U fqeRyΣO miے?-kũ2Ctq D H5>$&%?׋SXd"5>$u6kQ?YN :7W6'%lHQ,OB3hf)R7 t(IɽKаH2?|l͌ak 7.t#VSBNMf 0vh>C:q;/y{WR񆰳xwf 0vhRd;}EU9peZ[$Hˆ-l #١?ܑkũ2Ctq C&$_n1(&֑kũ2Ctq &ݛ9P|It|;G6?ٱ 2o; iQ̀1~1S}2 R( ZGA6&Sa#ZGnH&Sa#䠓:Jx@8`&Lp crgC$($rPi] t(Iɼp ! eN:$d޶)fU%RbPItvʜ t(IɽlSh̪ e:$df}u . >S6'c}ЍXeONu ϖ^Ǐ]7Uٱ\}Ʃ^=! F6*l{}N :6Am۩dNp¡yP]GWuw*G vSX[L HV^]MʅCt)'C&$jK&$2 9#Sc*prr2y-`r$eZrIbI nH!Ⱥ8$L: =ZGEE$>2mcGk ͌BL樸^u ʆI2EU9peZ[$Hˆ-l #١?-kũ2Ctq C&$ ϵA/TkH^-MaHSct(Iɱqd?ٱ1ʅCOf]ka}P7 . >Sc &֑M#ܑZ$9G>RbA.K&%?׋SXd":R0.6:(wcct(Iɱqd?ٱ@. CT?dk*vٰ|p\Ίp]B2 nH$EE%Ti]RbPM#-x5Hr.!!l}eOu5ٱPz9B61vʞT*{5 ;X p>v`f .Sʅ@dkH&ܑnH^-MaJn1 t(IɴuIA6!Ⱥ8a]kl'*M[b#P{'Vs(V*{cU{^YtMnRaAMõN...1 lb!];9c+>YaCٱ 2)j.-WN :76'` ϵµJ62 u2ot S%'c\:?WI%TB2 }*T^ZD9мBL:9R|gڊlex?-S/9c+Uy~m)pE6WFL-MhݴxdkH&ܑnH^-MaJn1 ( dDS*SԴj }ĠZGZjk ]BB0.56 A{chqҗqp?tSF9B٪ pQ3d U2 nH$EE%T-O/e\ ۪LJ EE$#,,L,+ 2te(e?^` miے?QMmiM#-Z$9G@ζTANPsL J Zjk ]BBl\jZlSrmޅñ:$d:s 2 ?Sc*prr2y-`r$eZrIbI !Ⱥ85Х۪LJ EE$$k*v-?,ڧ0_fC/c)С'S&Hl%[]BP͍}k 50B6?|_fSBNMFX-Ljlu-5V")yS{mkK:r<2 nH$EE%) @LƠkH^-MaH|vl`@L۩cAGd;lH[ue:$dީ^0؞xa#cAGd;s(=͡H*‹7)С'S&?.Ba#cj?'X]k{60dyCa,$>nЍYN :6?2 T?ex]7q7``H``HdkHmnH!Ⱥ8uIA6^-MaH7ڧSBNM%pmTf 0wu6 pG6M}?ɧ2Lt(IɽB.ٱ0&K\MÇ&}X&}X VjъGu=N :6?;gՁ egՁ!M# $E#׋SXd"۪LH.5RbPM#׋SXd"Mû61%2Ml`( [{5t(Iɰ6Z #G6?Gu=KF1ЎÆ(l$>n& > ``HdkHmڊl$A6m!Ⱥ8{R_n1(&֑Z$9GG{tjt=7] Xl 1?g*wWٱP}KFٱR[*wC!{$52|$N-Bll:5Gc$X 1??.jtvlb)2 9#r@ À Ā&(QH G88(K(䠓?Jn1 \duI9).lT{Sث1nA])С'S&G}_Nm(3C$͌5A]668 9-S5yu6N-MJS miے?QMmiM#QMNH9#Da  Qd0,1F AsYX8Jx@8`&L}41F AsY5Ncʧ.I @8pÐ1,!Ƀ!`0X@,uJcH}ġ\T p)С'S&X8$HH6PcmAc%RbPI$>;602mp)С'S&M2/P}ts9c+,eN0؝SۆS&?.Bv\dl}LmG)С'S&T~ZS_[΂ ofpY{66?le:$ddrGAm۩dNp¡yP]GWuw*G vSX[L HV^]MʅCt)'C&$jK&$2 9#Sc*prr2y-`r$eZrIbI nH!Ⱥ8$L: =ZGEE$>2mcGk ͌BL樸^u ʆI2EU9peZ[$Hˆ-l #١?-kũ2Ctq C&$ ϵA/TkH^-MaHSct(Iɱqd?ٱ1ʅCOf]ka}P7 . >Sc &֑M#ܑZ$9G>RbA.K&%?׋SXd":R0.6:(wcct(Iɱqd?ٱ@. CT?dk*vٰ|p\Ίp]B2 nH$EE%T2mp2mRbPM#-x5Hr.!!l}Mnu2ot(Iɱqd?ٱۆS&P~?|6 Tc6a &ڹMnu2o &֑M#ܑZ$9G>RbA"Ph%mikũ2Ctq `?,,NU&4 u2odu Rlvjc=ΉJ\,09 ?v%ӝ=!&7:6ӳF9B>Ya]2 Sa{Tk*֍J\/A6m!Ⱥ8 0I$E8R=KF۪LJ EE$# X`9TF6Z7m){KE;9c)Pa6Hp[*C ZGA6rGZjk ]BPuI[ }ĠZGZjk ]BA2͂¸pC!~FYrvZ% &֑M# H&֑ے?ܑkũ2Ctq D Hnٱ 2=ԙtpaj)N\899pּ0929K[$1vhr@@$$Zjk ]BPuI ۪LJ Zjk ]B@ɸwf!}:$d]7Ml`( w[C`wjs`+`mTf 0puK\;c)С'S&61 sqC^Ǐ%pXWp V VA6&ܑ^-MaJn1!*A/TkH!Ⱥ8p͍}:$d]7Ml`( w[C`wjs`+`mTڝc s$͌BL"ݛl$>n8gՁ gՁ!f\lMtwSٱPaCMð&}X X&}X?rG[?-x5Hr.!(}āPK&%?-x5Hr.! d;c Xc,a,mTf 0puXBL iQ̀1~1Sc/twSԴoS}\8n"vK n?3  VA6&ܑMGkH&ܑnH^-MaJn1 `Y·(%mikũ2Ctq T~ZF,Cʝu٬~!ՆC\}}}N :7Դnu+ey[2GXC!odkH&ܑڊl$kHmڊl$trGA@8pÐ1,!ɀA!`0X@,u$8ЮT*MhPx<"BPuI&4p)С'S&M2-RbPJNH9 !ٱnN :7mA}\̧BL^9Σ\g*qljt / ΦM]7U: `gڊlj\jcf! F6*oٰ9N :6r@u5yu6nc&?S\<0^T6Qj<GʅCQBt@WSnPG vuI*uI NHʧ.k^rdIp֜`rDc49 BG[?-x5Hr.!(I=9BA0)(&֑kũ2Ctq u5'XQwZC&1ãc)С'S&?9.{63F9Bf( j)N\899pּ0929K[$1vhr@@$rGZjk ]BPuIE6K&%?׋SXd":R0.68 ϵ{62 u2lsY:vlg:rrP٬~lllfÆ1?Mõs8 ϵB2 nH$EE%Ty@. uIA6!Ⱥ8ζT6 ͎p]{62 u2lsY:vltP *=vʝ}l8cC;W03\x69P miے?-kũ2Ctq C&$ p!LA/TkH^-MaHFfnL{62 u2lsY:vlq6ɾT*{5 ;X p>v`gnLB2 nH$EE%Tde:$d }ĠZGZjk ]BB0.56 A{chbz BL:F9BTjsmvҗ ?H8F6nvItAwqqc`+ ΦMtE66AGd;cSc]Z;62 u2llpj)iKjle:$dKOfBڮ ?Jn1 \duIUzsyN :7us ϵ >~Z|_S'Vs(WfT*9R|gڊl?T} ceBZѻiK0&֑M#ܑZ$9G>RbAQ3d UhuIA6!Ⱥ8a]kl'*KF7m/}qg:r?Uy1fNeHdkH&ܑnH^-MaJn1 Z^`A/TkH^-MaH8FYXXWnd5o5NQwSĽp? $A6 ?rG[?-x5Hr.!(IlSpQp砘kH!Ⱥ8BظԵR۩ c t(Iɷtd:EU9peZ[$Hˆ-l #١?-kũ2Ctq C&$$kKA/TkH^-MaHH?|6 Tcl[~YOat)o|_fSBNMJ`ٮ/1]X kXaٱٮ/l:1~1S}͌BL c?ZZ7jE8S5W^(,B u xdkH&ܑnH^-MaJ RA%A0)(&֑Z$9G%˩S_w of 0v0ؑt(IɽRa=,;eF 0v& nQbzC1JT?nSBNM]7F!ռOfeOpl`( u8XYIt|; u2l60dyCGx9Ћ{ͣڽGj#5ėGû60dyCG|ړ! ?-E62ˇ #.ל& F\5)kdQ.@(^-MaJn1 PuIA6^-MaH71ϼBLK?͌a}HlN-BllQa vle:$df!}.;`~$>n n33&֑ے?ܑkũ2Ctq C&$%H%miZ$9G2nٱOBLK?͌a}HlN-Bll}SaNdٱPz\;c`MėGÂ0L$ 0L$6 5{62 u2l(vϫA!ϫC ZGnHrGEE%T0\8j }ĠZGEE$ vlb3Ke5QkPam; 9F6*le[zc Q|It|9\MÇ&}X3&֑ے? Hmiے?QMmiM#QM:Hx@8`&LS`8$Y5 Da  QdC`8$Y5T,^:$d޶)fU>,^:$d޶)fU%RbPI$>;60>,^:$d޶)fU[s2 u2oU{~s(WpYʜa=i{B6ӷBC&8 cf*,^SBNM6ٱ6@ݏ= 6^*,^jjS%F*,[{67TrP9G޶2UgZSm-ئљTNxV!+k 4q~Z|6 ͍p:6u յvlt.Rxio NH9 ]MRu71y̓Ѯ[T/*C`kJQB:>Z`RuJmʅCt)'C&$jK&$2 9#Sc*prr2y-`r$eZrIbI nH!Ⱥ8$L: =ZGEE$>2mcGk ͌BL樸^u ʆI2EU9peZ[$Hˆ-l #١?-kũ2Ctq C&$ ĨA/TkH^-MaHĨxlfÆ1?Mõs3XTA6m!Ⱥ8Oz }ĠZGZjk ]BA[*TFf[TXXYN :6?9B67`eN>=>͇ c(jeO*M#rGE#-x5Hr.!(}āfK&%?׋SXd"wٱ6c afle:$d8u EKB'X.S>͇ c(jbͥP? $[?׋SXd"۪LH2C u2mRbPM#-x5Hr.!!l}ʠ1~1S}XiyN :7ug:rbg;5WDF.lN8XY?5B|^p"^SBNM~Ra]WЎ͌BL5Rd?C llOf[T~|XWf:$dUY!J,OuC ch&ڧdNty,J بia]2 `61&ë\}*M#rG䎋^p  C&$P RbPM#^p  lSCal}1c afle:$d8u !T*{5 ;X p>`gE. lrP: $qnH,p< >RbBgK&%8,p< 6 ͌A]t(IɽGCCٱ.{ c`eN>`61&ڹ΢g &֑M#rGEA`p8  BLA/TkHׂ 8@B0.56 A{chbzEte:$dYΣXYU5yg6ѻiK$#G7;$sG1.{+pj)ٰ82 RbAQ3d UhuIA6:-x" h $$# X`9TF6Z7m){tE;9c)Pa6Hp[*C ZGA6:-4۪LH.K&%8,p< p`0&7jߩіj. ZGA6䎂mE6: tnHܑkXA xA(IlSpQp砘kHׂ 8@Bl\jZlSrmޅñ:$d:;s 2 :-E62ˇ #.ל& F\5)kdQ.@(nH,p< >RbBFuIA6:-x" h $$$k*v-?,ڧ0_f[dzc)С'S&Hl%[]BP͍}fZ ͎t)c6?|_fSBNMFXBƨRѽNsUb)ž=yS{mkK:r<2 tnHܑkXA xA(IgĖ5ZG45>$u6kQYN :7W6'%lHQܢ#6)R7 t(IɽKаH2cvʞ͌ak 7.t#VSBNMl`( o6j swC:q;/y{WRk 7.vl`( o6jǚRd;}EU9peZ[$Hˆ-l #١:-4۪LH5)RbPM#^p  &ݛ9P|It|;G7ٱ 2=6Z #G7ٱ 2oút(Iɱ1ϼCl{ėGáa\Mò@dkH&ܑE#ׂ 8@PuI R }ĠZG4Mû66P|It|;G7ٱ 2=6Z #G7^&3c)С'S&Pvl` xpWp VjъGu=N :6_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbfork.htmtm/$ Fork Occurred dialog box

Fork Occurred dialog box

Restrictions: This dialog box is not available when debugging on Windows or on the AS/400. It also does not apply to interpreted Java programs.

Use this dialog box to specify the process to debug when the debugger encounters a fork() call. The debugger will halt inside the fork() runtime function, where the call to the kernel is made, and the Source pane will display disassembled machine code. After selecting the process to debug, you can use Step Return to return to the caller of the fork() function. While the debugger is halted, you can perform debugging activities, such as adding a breakpoint. The process remains halted until explicitly restarted.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Push buttons
Parent Tells the Debugger to keep control of the parent process. The child process will then run.
Child Tells the Debugger to take control of the child process and release control of the parent process. The parent process will then run.
Help Displays this help.

Copyright IBM Corporation 1999, 2002

afle: lV$(zf>_>X>'N./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbfunc.htmtm/$   enot<>adgilrs "/bchpu.=fmvyFwx,05CDEILMPST14AGOk#()-HRUj9BKNW28:!3;XYq8 ( @D (N8 A+p7l"lKH àcbZ9p cN]ـAMp |ؖZ\}p` L 0,(Sq6p`B!f:= d 6JT.@=T(A ɽLKiy4r-@ J0&- rdU%[*HEJ *k\ۅdަ% 9 "\r1Ўc1-^QiA*d‹M.PI[%aC`ĶA|Lb)Ql(]BHp*@ 1j:rY*M:h,tU%[*u1-YJCXb@@JtYtLKiy4:Y*eҵ1-YJCXb@@J{QLKiy4:Y*F51-YJCXb@@J\ۅdަ% ,` ɽLKiy4r ckP1A1RbS d 6JTb[KɠWeKqVʝ\1"C`T_D* l< ׁvV乐M\`$ծBe&rc|% K[XKC( N^!Zo c[IkaC/1Է$N.WmE*9NJYIɁ qEƒ1@&M~VUMiKT<0VL6`K4ʷJFDIB]s2P*ʩSyH~ d}h&uJi%NT880PּĔXqCZbTJÎ bp8n@b.Ct`;+@IU2TrnZEՊKX=у","cdeN.“7o"ԁ[7܁j%\w۪VJ_^` qE۪Vj@b.Ct`?(( ɠ ӈ6JT~"u-@MYxdeO)eYE*I|itbSe r-HEyRZq}hA&l)T-rnZEՊKX=у#/&?|6 PhCʩY+WDSS1ɍ\(1ȵ o9 oڱIk!Ǻ0tk6"Z7X:Ildӕ8 >T51%2Vp8P֘)˜,8:=X:uJ)}h9 b.Ct`weD* leTY,\ lpAUc2&{.013e]Y07U6K%}6U6JT~S M²E.u`pH$8)\<& Y1T“td\f:0/K!qU%[*u1-^Siꕠ!ꕣ5.c;vJ)m"%6ʝ),jIllˎpUʩY+AU UꕠWDSSԴY}h͒PN=/| %LtH Ʒ&:2&{.Q*30'KAX80 8`0JW"I2-hD8Ll08ta= OB;.013Sݒˍ_B;.ll r-H[7j%\w۪VJdi}h9 b.Ct`Y*M:h/ eFK-SȾ(:$B;.1Vʐ"ԁE܁RZq}hC+Aȵ o=r{@)1cf&aEri%Eyȷ ci%b;.0Tj2TI%[*_2ޑ1D%I-M/ĶA}6>+ /Z\_eH !U\ { %[*q=cb99 cRT5%Jd8*8  {V)-b8FR˥wXJC+Aȵ oڱIk!Ǻ0tELt#]+FI\Qxpcj@r-n@b.Ct`;+@%//eToC+Aȵ oڱIk!Ǻ0tv[\^W iŗJE*Z/`1eҹH*-.IWKK(Pcj@r-n@b.Ct`;+@* 5kdd MhuJr-HRZqy4U€KE5/|?f$-+TY,MZ+")Sl˜K.v\bb˥9 "܁ {V)-b8Fyy&Լ@R=r{@{I-rʆ$JÎ*2Vp@Se@ o=r{AnZ9T"ԁRZqQ/FS.2UM_eW ŗJ=BqQ2\mdUMX\b(V&,VH3Πp 0b%+$\a@4"pk&6JRn:0ˌ@t$6.0JtYtLKiy4|<1ȵ on@ o=r{AnZ)!ꕠZ7ՊKX=у|? dEJĶAxS,6\Ql"EQF%Cq.Z7ȷ oې7ՊKX=уT"a}h9 b.Ct`15"l~\441ȵ on@r-$7ȵ o9 r-$1@0Ge MZ؆J5O™eH"` qƤ.ĶA}6>+b˥?yis%}"`6WqB]+i}9 cb9;+ADqY*F51-X dĶAg!(9T sK%X=T(F% v\o1T(FѮRܑ!A SnL*M4JߥѪSL+&AA%ie[%nL"a$!.9Jik yȁ(ieT۩L?IB]sRMQ}h r @Ǵɧ*p|k^bJd8q1*S%a1VXq8t oڱIk!Ǻ0tꕠ*k2TrnZEՊKX=у","cF1tn|%9 "܁ {V)-b8FRR[FK,>RR=r{@0GeE@^M~lp6QP]e]KE7V^cQR&4ʲKUòĦ.Z7rې7X:uJ MZ+")SlZ,>RR=r{@0GeE@^M~lp7Ry"_SidV7 5kdd M c[.(V"q*k1ȵ o9 oڱIk!Ǻ0tk6"Z7X:Ildӕ8 >T51%2Vp8P֘)˜,8:=X:uJ)}h9 b.Ct`e5F"q['*do`f:=BqQ2\mdTY,\b(VcQzgKAX80 8`0JW"I2-hD8Ll08ta= Hl"\a,`QP]h/)xcj@"܁n@{V)-b8FRS%CNC+Aȵ o=r{@%eVu 5ѩm/&YtmK-E;L袍sJ#1T(@cj@"܁n@{V)-b8FRi!ꕠZ7ՊKX=уǘԋep30"ԁEȴ@"ԁ[1ȴ@1* 5kb*~$ lf:~/zD)nˌ5$~% ȗ^1T(C2WiR&alcYqBEBtbB{-7 sr @1}h:yH8K%X.m}2oS^MJ\ۅdަ% 9 A}h9 cY*snzh/2UxpdѮu-b56kʲmnLd]9²a]FUV4R&2L2퓞6VUMDd%';+A4۪V {I-rʆ$JÎ*2Vp@Se@{r=r{AnZspˎ&/27dK.۪Vj@b.Ct`2;.9HGenLѸRf^"Z7rې7X:uJ K|Kl.(uJr-HRZqy4U€g ̦M~"u-7FMY|M^e2o2p줾41)9 "܁ {V)-b8FRVJHp*z9T"ԁj%\ l~QpPA{\( Դ^cnHTY,MZ+")Sl˜K.v\q6yɰ"ԁ[7܁j%\xy/$ۺj@b.Ct`i%NT880PּĔXqCZbTJÎ bp8 b.Ct`;+@!ꕠZ7ՊKX=у 2%wecnHK%ˁ ۅS&Oe\Tf&cLd&Y07U6K%}6UۅS&E.u`pH$8)\<& Y1T“td\f:0/K!qU/&1-^Si"ԁE܁RZq}hJ۪Vj@{V)-b8FKiˌ%6x>7m/&YtmK-E;L袍sJ#㉷ ̦M9 r- b.Ct`;+@rnZEX:LyH[ 313 r-H- r-HEI- s qVv!MmnL~/zD)nˌ5$͸^MS^MdKXdK[*kK+)6 c\M^e2oi}9 ab@ Akl-- ]`qA  JJHl>q4`1e @v NM 4C!(9 aA4hc]j= k~$ zf>_>X>' ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbhelp.htmtm/$ Select product context dialog box

Select Product Context dialog box

Use the Select Product Context dialog box to switch the Distributed Debugger's help.

The Distributed Debugger ships with many different IBM products. In order to access the help appropriate for a product from the Debugger, you need to select the product from this dialog box.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Available product contexts Select the product name used to compile the program you are debugging. This ensures that the help you see for the debugger is appropriate. It will also ensure the Help home page item from the Help menu will display the proper product's help home page.
Push buttons
OK Changes the source of online help for the Distributed Debugger and closes the Select Product Context dialog box.
Reset Restores the Distributed Debugger's product context to the context that was set when you first opened the Select product context dialog box.
Cancel Closes the Select product context dialog box without changing the current product context.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

e lb$?kzf>_>X>'=./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdblnbp.htmtm/$   eot<>adgilnprs "/bchu.=fkmvwy,x&05;CDLOSTq()14ABEFIP29:GMRUYj!#+-36HJNWX_|K8V8А@@, 4 ܀$ Pi$@@,a@V][)i$B9)s)R8]$&k Nu Hk䌺uˬ9!vI)̳͇dh ! 3rEHrP p AF]:@ xIA0#fB=(Ӂ}1שm/*M()RRq`{8 Hz, q1"PGfNca)cS^U嘗.c_.SٓC9_fNRX7L'Tj,6wٓ> MTqkP?Aә  50d@0PȐ0#MLS9 0"D G%(9-b:s!"AQIP 9)Ak95s%sX 0`bK[rǽXY8 V K%s\C-xH9cL{#ML2  B@`49I\ė,clFAc`*D;*Cj`Ȁ`1ʡ!œ K鎽LKiyTrcp-%(9/@̜NR%^% #2)ci-^:zt<%R!.-9{XʄK鎰r-q|{2y ʹfO6!0mK7ٓ HaK8z6:\u›kL'Tĸ0VTi"r^9@v}C.=mKjW1 39 JlQ $1k?F6:ܫH꒍ZqΜHI%6pB0JlKXI@z0 5\&QܑS/|E!eӮ1ap-STrcp-K8z9h:w$T $8BI)G%( rcp-6pKNSu{*J5kcBʶ5+9/@Sg*r2孋[˖R F1 D =ՋKX" )2BfL*na"rmHZZŸ9O!63NScݘTcd{2r)cdw%ʶ82w—ʖ9zVPcJlT0@F\zKcQrֽ*S1V`r`X( ڱik]<7 rfJl)Aɵ ڱik]<e]d%i)c afvdBR%^1nq];KE䊘wf2NK@9h96{V--b@GfO6]*rdn=" n!E:t UBGv8̘bوr2.08Ѱ.q ldBR%_(֫*x͏b!B1-dc#!\wH͎-q lH rmHMZZŸ9O!œ91Sj@b-Ⱥys ;Tc12Zb{2vӌ2a=9P}1?51-*F1ڐ??Xpr.B9hHT%"_Lu)Aɵ ڱik]<e]c#d'*Ѹĺ3zvӕ H{|)pHRlbodwUKvU* wyu4cBKBm%6BѰ.BE. lvd(ծac[*tl̜JD. \+dvU* .WfNT%"_LuIc;'TBUr:l2r)c4n9t2N-*dq Ǹ!}C{d+`mJ5kc. r̜֫E51X 9/@zz8nā8%" S$CzK?ɵ 97rm%6P?ɵ 97 ڱik]<E 6&ewNɑH96{V--bJlT0@F\zKcQrֽ*S1V`r`X( ڱik]<7 r ɍœR=nE@6dc*/:b/'ݱˎ6-* v[j3tl%"_Lub[Kʠ&ԁ?jť[tx)@FlNZMՋKX"  M{2vӕ HycٓnF| ex2p{8 Hz/˸6K)T'*/:ڐ??Xpr.B9hH91Sj@b-Ⱥy\dz'ݱˎvdH>NKpE0HNLFQT3c:b?BMm9q.ѻ.#2)c1ɵ 97 ڱik]<7 r K)Aɵ ڱik]<[Qd:p6/:1-P^1eyp;fT%"_Lu96&{V--bNZZ9h96{V--bs"l{1̖z]- rmHMIMrmHMIMwA`+hr%.XH[rǽX$ZHʨ*`QΝ! $Ap-$)AJ9h rcp-6pKNSu{"0|&X$ZuIFlrsJlT0@F\zKcQrֽ*S1V`r`X( ڱik]<E HLBU)EM"rdRMՋKX" r lv;p_j t OfNT%"_LuVfNRYR/Tj* {IM˖/IlrÐ #.ZץJcY*@, {V--bNZ%+9h96{V--bK̝,JW=0gfNT%"_Lu{7 ٓ$PHvc#[%)Y ,ɀFBu4Xw$T96&{V--bNZLbrcp-&ԁjť[twٓ=0gfNT%"_Lu{7 ْ?;*cݘvvFa 2`1]s ;f[SH rmHMZZŸ9O!œh8OS$NZMՋKX" #- ٓ[%)kUCٓƍscdc0;2r)ckUNKpE0HNLAɵ ڱik]<0lTRl%t7s aJD뎘Opb09UL-l^ F\J,91UX !ZZŸ9O!œG&7 rrmHZZŸ9O!#2.Nٸhܳ*8Y JqʄK鎱Jdِ؈P̝f1f522{2lv0f6%qJD dv7:EIMѽ;{Sb*ى& e J[KED6rmHMZZŸ9O!H!3eō92)&ԁjť[tc=8 .,n]:Muܵ8:J5kc w\nӴT%"_LurK"X 8:J5kbf_#2bὰTǔfT%"_Lu\T 8KUGlw-ofNZ;c 3F?P}1ٓV(֫F<+2t"/kUZ\1?50Q\ÉkUӗ0tǴʨ*`(kb,92zT9abQ=ՋKX" S>(NZMՋKX" u;2q o*/:qtkaӱ01n1.̑%;tP-" #FQ\ú%\ó'*/:2q or?Te..u%A\$&mX0!3jMɸ =ՋKX" S)Aɵ ڱik]<ιfN)cF7_fNZPB)퐭1n1.q-9}9P}1פE;2p 9qtk`ˮ`?$&mX0!3jf$\-tٓ Ha\$&mX0p94696&{V--bNZs&7 rrmHZZŸ9O!saٓ͗73c 3FQ\tْ?P}1S![chb]{/tӚ7OFB90aF 0!3jX$&mX01ɵ 97rm%6P?ɵ 97 ڱik]<7 rrcp-&ԁjť[tܴ.-Ŕ펺Gj`)pHBm7O̜JDGfN]9LSK`J;C%cql@P-" #F꒍Z{KEchܺ5k'Mm cNK?ރ"!Á@N<8q N H)f $"rmHMIMrmHMZZŸ9O!HMFӢrdRMՋKX" 9UL-l^ F\J,91UX !ZZŸ9O!œrcp-&ԁjť[t =;XʄK鎼ر7lr㍣xK`J2]ڌ2p{8 Hz,1ɵ 97 ڱik]<7 r91Sj@b-ȺySs̝tBR%^lXd9qѼ_%C%AYF&e̜NR%^% 5rJnqU ʄK鎸96&{V--bNZ!&Lnڐ?Xpr.B)17lrݙ9RSL*na"k Θ[|f\qKn 3zwH̨JD rmHMZZŸ9O!œR&7 rrmHZZŸ9O!f=8= K鎽LKiyTeF\%6/N HaMɸ =ՋKX" SNZMՋKX" Ƚds%ޗKCRp@&SeRp@&Seww XDC1,Ir X(lFAca X(B3rEHr NZtR%^% 91SqfNca)cS^U\fP}1Ӵ| /k=CNrJD 7-.l7',IM.W6!a mK7ٓ HaK8zF2:/dv8] c ch2.NZ3x Hg&7 r7 rt)@Vx)@Flp{8 Hg&7 r3NZ])l%"_Lu)F*\nˑQ 7-.7tʄK鎱2]ٌ% BeYCxdc7 rJD91SScNZgœf{8 Hg&7 rъTC`:KT*/:sF vc":/dv8] e -^SJ` Hg&7 rъPc9ހm:M+.p9q 1. *U- 5\&QܑS/|E!eӮ1ap-STrcp-K8純ʨ*`(kb,92zT9abQp@b-Ⱥy<@ SDȤR=nE@ Ӯwf2:F"0̜JDIr̝"^(ծT9UL-l^ F\J,91UX !ZZŸ9O!œ0"Lnڐ?Xpr.B2.2p0"H o. c afvdBR%^1nq]#$V䊘wf26\Xܺu›k{2ptj0.?iJDc w\D,62ptj0̾=%Fe %{`),̨JDѮ62q ;ٌ.NZ̜%:v0g..u:)c'IFs&QV!xVe E˶_(֫´];c 0qtkaٓV(֫um.ai)PT9Qr-XrDeZLrÐ #Y`8{=nEAp-|(QɍœR=nE@vdT%"_Lu\çc afchb]}#:J5kwC>ZE=F6%ٓVuKйfNT%"_Lud!`\]Ju0HLڰ`BfՃRp@{=nEAp-*91Sj@b-Ⱥys̝BR%_..u1n1.̜%7O>?S![chb]{/i[ r2r)cHvdfr\+\HLڰ`BfՃa*HzZ1#c;'*/:¹u0HLڰ` s,h$&mX06rmHMZZŸ9O!œNLnڐ?Xpr.B\ó' .,n1f0f6%ٓVu;ʄK鎰P-" #F}ѽ:z6ȹE ?50W. V !3jMɸ i)Mɸ =ՋKX" S8-Ŕ9h96{V--bFݍ|w!o,luf28KTaKEr%lq|tdBR%_Nh݂;2re[2Uݘ-Wsp6Cgz!iV7L'Tj/N 0 \(+FѭWc_=8khcr^)  p ÉpJE< H0 H'&)g&ԁ?ɴ@&ԁ?jť[tyDؙm:'&E ڐ?Xpr.Bi)PT9Qr-XrDeZLrÐ #Y`?jť[tx)@@'&7 rrmHZZŸ9O!JncٓJD̞͋3v.87d+%mG'Ӂ}1שm/*Rp@{=nEAp-9h96{V--bl%71NT%"_LuŎ_fOcm[2Tmf_tl%"_Lub[Kʠ.X7-.˄PJDcj@rnp@b-ȺyKC;*CRp@{=nEAp-6S 91Sj@b-Ⱥyvd`\ҧ.FЎ2.`َY #OPT$ lciɆ!!X7-.-c 3fNT%"_Lu2jv"+2.Nl!fL22ˮatj䊐&ԁ?jť[tx)@=9h96{V--b90ӸEL6:C%*]l7'k8&ٓ Hcc[̞/!4l C!Mɸ =ՋKX" SteBR%YɍœR=nE@F[%f29fIbr/`mK7k9P}1ױw—U(f&Gu^Y7m%Rz7\K8$.K6Sd+!̜%1kwUN=֒sٓ Hx%ݙ;KElJACʄK鎼c),vvdJnCœM\9hu:ޝR"a VT%"_LuvU*.K6Sd(mqӱw—bcƅNKi*r%i).W:"ZZѣWN96&M96&{V--bȤl%"$T'&E ڐ?Xpr.BP*tLSܺu›й0vT%"_LuL'1kJ6\Xܺu›k{2ptj0.?iJDc w\D,62ptj0̾=%Fe %{`),̨JDѮ62q ;ٌ.NZ̜%:v0g..u:)c'IFs&QV!xVe E˶_(֫´];c 0qtkaٓV(֫um.ai)PT9Qr-XrDeZLrÐ #Y`8{=nEAp-|(QɍœR=nE@vdT%"_Lu\çc afchb]}#:J5kwC>ZE=F6%ٓVuKйfNT%"_Lud!`\]Ju0HLڰ`BfՃRp@{=nEAp-*91Sj@b-Ⱥys̝BR%_..u1n1.̜%7O>?S![chb]{/i[ r2r)cHvdfr\+\HLڰ`BfՃa*HzZ1#c;'*/:¹u0HLڰ` s,h$&mX06rmHMZZŸ9O!œNLnڐ?Xpr.B\ó' .,n1f0f6%ٓVu;ʄK鎰P-" #F}ѽ:z6ȹE ?50W. V !3jMɸ i)Mɸ =ՋKX" S8-Ŕ9h96{V--bFݍ|w!o,luf28KTaKEr%lq|tdBR%_Nh݂;2re[2Uݘ-Wsp6Cgz!iV7L'Tj/N 0 \+FѭWc_=8khcr^)  p ÉpJE< H0 H'&)X 0`bK]M # {Y1h@ Fx)@ 91ScS}BX%ڤV9x4 ;IP r^7 r5rNLn1%6creLbvƋbnUek# HxcySl/km$q.2rʱe862GcSUӭ,v--Max)&ԁ?ɴ@&ԁ?jť[tyDؙm:'&E ڐ?Xpr.Bi)PT9Qr-XrDeZLrÐ #Y`?jť[tx)@@'&7 rrmHZZŸ9O!JncٓJD̞͋3v.87d+%mG'Ӂ}1שm/*Rp@{=nEAp-9h96{V--bl%71NT%"_LuŎ_fOcm[2Tmf_tl%"_Lub[Kʠ.X7-.˄PJDcj@rnp@b-Ⱥy_>X>'.8./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbload.htmtm/$    eot <>adgilnrs"/bchmpu.=fvwy,0Sk45ACDIPTx1:ELM-9BGHJORUWY()+FVX_jqz#2678N'3;Q!@,D,40 8, X8 08`'AOm8q-9Ti: VUـ@0։0*rfH4qA9V[)Pvƀ8  '@;\`p$@p4q$ aS ¬նImJ@Rl)QzڧS2(I9RAi9P2S NdP=1 2^?2(nSj:*T GeNd)Qx7T'\kװ#IʝF 2 UDb*ILSOSɧ)!F8DG&;*N"׳%W,6cЌS kٹOadǧUѱrE@GAIjPHEJ ׀P$#$EJ)5Lu%?J `s!7+^@`c`d&{LP:ԟ ʄ0!@p Ԕ$1 ⧵ȗPs`&=9Ĭn^ Ck*p2 dY:@8ޢ=ɧ)!FO_Hd(#%PZ[jsIɧ)\QJ#p$Sp!9:-D:r*  &\蘢Z$lsRװ8M]`@$dpIkĩcÍt`Di+ ۺ|P<kIkĩcÍt`?C"qeΉ%`qFɗ8-m{AFIpIJ<8F FOb@Rck`lokorT? ky .nWOad@\E55у%SؐJĩ7I^DNZ?a+P֓$C'kI='E'Z*sX]2Q% xž\*TC8eNd)Q}DrAdi@kĩcÍt`?-D:r*  &\蘢Z$lsRװ8M]`@$dpIkJ#p >3h-fMZS^l)ObP='E!R&)m?͌T[ yrGeNMZS^@pIkJ#p >3M sIU s!"[F[O[ yr@SؔkIkHTIlz2Oc='xž\S 68.H5qŴEC1%VxdkIE'E(žĀeN׶ڧ` 2`HڡfKaO._h7 {i?-i I7MF[ilg]x.H5r-<}6=meN]gˤm?1ʄF[i i?{OD:R@\E55у%ZBMTKAIB;*s!L@ZP='Z*sX]2BMGeN"׳-ZC_='um?kE4*s!LȖX^)w^Ȩ.``$lsbk`e1K[^5vPqpE'E55у%Sؐ2SNؘ %ODE0F.*3M1tnY 6\V r5R]?T%q/6-{;*tEEY %E,=a#F67ѬP{*qP^"ZAm{;*O爸ܖj!ӑP\8H2Dװ8#d˜b j#$$^%NkkJ#p .h7 {i?׉SLJ)6\&eAW1]$i?4S^׳z#W9U &_n^@SXɀl*]$ާ%UFBll6 SKR}lglwQr?;YSEB;)WQr {ZO ?. ?׉SLJ)H6h7 {i?׉SLJ9 idL;*xIusH5jc{^ΞѺ}_$T,#\Q̨^`֓{OC'%ι 1f̨unim[i_JSؐ @S؜S\zgE*\kxeOq/x7T'uP[^VYy.5rk9Ձt*8\mV~)VQJf!#p &*2p'Ms{lLrTTC]3SS NdP?*32(C]=ԥ}eN c&#F"T$L9xž\b׳3-(ׯk):@t}6Ѹ>rABtm} ܯZtT006L1D0H2`qb(88H?. ?׉SLJ)HvTQ94S^׳-Mu;^&h7 {bO֓-x9xq CejTs\eM}k*wB3!L &_n^vT 2` I78Q}loJ_e*!Lʜ$L$\eM̅2 /}^+lw66|#)ΡM{$5 7 } ޢSט+9AEv,^'Sט+k)6\IjANi!z#p &*2p!/͌TeI15׳%ʌ@3h-fMZS^l)ObP='E!R&)m?͌T[ yrGeNMZS^@pIkJ#p >3M sIU s!"[F[O[ yr@SؔkIkHTIlz2Oc='xž\S 68.H5qŴEC1%VxdkIE'E(žĀeN׶ڧ` 2`HڡfKaO._h7 {i?-i I7MF[ilg]x.H5r-<}6=meN]gˤm?1ʄF[i i?{OD:R@\E55у%ZBMTKAIB;*s!L@ZP='Z*sX]2BMGeN"׳-ZC_='um?kE4*s!LȖX^)w^Ȩ.``$lsbk`e1K[^5vPqpE'E55у%Sؐ2SNؘ %ODE0F.*3M1tnY 6\V r5R]?T%q/6-{;*tEEY brheh125KTO701!F67ѬP{*qP^"ZAm{;*O爸ܖj!ӑP\8H2Dװ8#d˜b j#$$^%NkkJ#p .h7 {i?׉SLJ)6\PcI66igeN1G .r7L/62gTIOKQsMl#W9UѸ>ޢ{^*w66س'zvR*{_uM!@\E55у%SؐmBzS:5T U @$\H%0k!M$Q@`sR ʨ\i%mFueTo?V';QM$] i%j-/Qr.C=Ebh%?s\ N uhp]|eMTQsЃSQD(ʝSؐQ=6\p5Чll#SI+&jkH5Uޢ )OdTtZO^UFQs BD}IJ{'ukQsʨ\⊗ѹlz2O I='pIJ<8F FObA idLF=eOtr d^vSc܃r`Ptma d^؟s넩z tQsތ*s70?U9}Q!`m\!)K\ŀj2rDar׉SLJ)HB JžĠ{ZO^%NkkH($/qJ}YʓM}euO^ 04[i6"a/&cnGgS -UMtl3!LlbnTof1m<6 uBO 1f.d)QxeN!# {*uȅ?L1%V~ Kɘ񛶽6[^j|fBTe51 P?;SZ%Py%)*ru=yM}+F2(QR]׋`3 J#p } x)N u-}C\nw5?aƍ3k#ENT\k;*s!L?kMqP^d)Qy tnk")^?ɆZ*risR/0mNp3xDc;? PY׈m?lxL ^wYy*O_}dkI='E'E55у%Sؐ0c'KD6W:ڧS2(ѭԥz*p2S N亣1 i?{O$Tƺ0d7 { Sɗ x)JTƺ0deJ_FLmz]QTe)yAEjLȠxlqI6|uBu$ @='\Z*sX]2Q=r_>X>'&./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbscbp.htmtm/$  eot<>adghilnprs "/bcu.=fmvw,kxy05CDTq&14;ABEFILOPRSUW29GM+-6H#38:KN!JY'0 8 p7 $  A pp7\:,S92KN0\'fѮ (8uˬAo.܅Y -Fl;#@ @(cp(n@8@8ʧ\Î ENieql!S*He/a( }1@&)o: dQ[dq14181hrMR&dhcKVMc< vGKVMe-TL\9];^EKRl}FKVMv^G˥=; .7"@ bq1m8fFH81hra( }1ץm+&8#u*pbNPcKVM5 ph06ACE %^! 19k79 8e-^! ,6AYACXqAm8 g< 1sFNQ̍!nN ZJ_LubJɠA 9S06AF!1Ss1pJ3nN ZJ_LubJɠލ/&}1*J.N?t !Sq| +BS r*b7ONh^qHis9S`#EgJ-#RT脠#L%/:u_pb0lrh\B0/CcYqbJɠ넦D1ӡ܅26+&aC0y9GOlxLDnat_nNRNL%/: Дc֋ݮr|CKE{CX L&1 g`"1 LHrAA@8AC`"1 LHri@8HqMr2IjS pӰ8 `7q-Ouˮa1w L1"qkN) b{sFNQX2"7 rb-'֜R88Og8KSq|z1Hisw-ok$L;\,I3 H]p/^4]@6b`qL79sCXrL\=>`c.7"qkNEKRat\7• Ip8"KdIp8k5N=9I)n70'1kN) b{p>) K-7*p*a\&q Rƴɨ&`p|kb(8z9Abma0k5N=9p(P9G1kN) b{pr2*Nٸt^R8\% uoL%/:c`-Gk8 BF)mb}{\% Ůa8]C7oa( }1-5zsBvTǵ/[mJ) T&!i8b.p8)Ǻx48 .(,HI5N=8%spyr l{sdԩ-rvɄ%^'wu%ar%S &e('^% fTz cpPRֽ Kű6`Po5ӊCXѸSp.$FNQEӊCX u;\L%/:qT[ax:\$*aqN 7P)^# huIjTú*a&}q oSvX.*u%!.`]XZN7\785pq99GQœI5N=8vڈL%/:qT[ax:\$*aqN u)^# hu덢N1s @K鎽.a_.*u9uՀ˫`ցS4Z;L%/:9u0]X8C Հi8b.p8)Ǻx4n 0 1Ssi8)Ǻxs8H-8֜R88OœAO,)9oZqHkd-R!r ,Nr}r7>86Rs3`0l  B$9E42 |Ac`4|f|`"1 LHri@8HPL81D0b% A pqX aj 9.Ќ p0FrLbvhǵ h" A-!9D0b% 9A@8PL8`0l  B$9E=@8 PL87P4;cSG h" A-}Z>|&4Sq:Lb K!4$D\T}10)Ŕ"q\7qi!Sth)8s]@FNQEӊCXWqbIt#$.=ъD[=CcS/_uEu:dB m+(t{Z/Ι)r}sD[;"7YK1"qE1"qkN) b{sH϶SD&na"Nb-'֜R88O|(S:NU:MTvJ_Lu~R-8k5N=9p(pDnZN785pq9\ǵ-Ra( }1ח9]xt_LHGk Sj38&)x @K鎽,CiY4ZN7\785pq99GfDnZN785pq9\ǵ:ra( }1ח9]xt_LHFIw̾#e/a( }1ץm+&|at^R E&90ci8b.p8)Ǻx4n"[lFNQEӊCXǵ) .cݮsH϶SD&na"O[ SD CIp8k5N=9p(8iœI5N=81kE %^! ŲET%+F @K鎰"q\7qi!Sth)8^b#p("qi!St d^ǵ:އKCIp8"KdIp8"Kd4n܁2pMRLubJɠ [鎽,CiY4bs9G18(kEzXҲh+7tŢ[鎰ZR\f-8k5N=9p(BS z>b#p("qi!St F{[#d=.rLbwkE) -1 5!Ԇ1"qE1"qkN) b{sH϶SD&na"Nb-'֜R88O|(S:NU:MTvZ,űtAy S s7z 3s) j l.$1>r$ FR1 7rj *Zؽ18(|k^Pqc؛Xq`0(soZqHk1hcdx͍֋xζ^hp_k!-h Bv^E@1o1oZqHkTz cpPRֽ Kű6`Pp8)Ǻx4n1œI5N=82Ţ[鎼snG J`JB˲Q4YK}1ץm+&Ip8k5N=9p(وœI5N=82Ţ[鎼snG J`JB$f_8&)o: dWOq.C(')o:ZN7\785pq99GȄ1Ssi8)ǺxP*cݱʎv"N>NCp=@LD>QoT2:"7dB m9QŮ]{*"hc1o1oZqHk_>X>'m./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdblobp.htmtm/$   eot<>adgilnprs "/bchu.=fmvwy,0LTk5ABCDOSqx&-149;EFIMPRUW23GHN8:XY!6KJ8A``Vмa``3 $D $ 0`€l2 tYl%r9̱M@J9M2, `).0k䌺uˬA!$',3b@ @ A"PP`8#.r@ pFJɄ5L9@]%X8̈́% 5^%eP92R9ʥ @t`68.z"rL8z9h7lDLn 1ĶAWZXԔ.%ݙ#AA=CdTj/c`Mʰ-;KED9z@!*Ŗl!..p\%!:1-PG7tʄ5_f&>2!:\cC"87KcYdu1-PG*,tʄ5Xs9ރhx0AÒI\ė,*lF @)k&= d# 1w—f&rʵ rE0ye0Q3'*]lɆvd奭c;KEu t)k̜r—2 @n] {0ps9ހe:M+.p9q 1. *U- 5\&QܑS/|E!eӮ1ap-STrcp-K8純ʨ*` kb,ADeZLr #YD =ՋKX" )| d%X$T'&E ڐ?Xp.B]:Mvc#kR%a ʄ5^jKlpd. ,rIFr純ʨ*` kb,ADeZLr #YD =ՋKX" ShX^t9h96{V--b )0ܑSО̜cC#B9&&* ݎGj`1 Lgc.->p91 Lg, ހ'䊜*yu%XYC2K]86@Xde;*qmmsٓBn1.]%̜e@66e;4hsj@rnp@b-y_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbscrl.htmtm/$ Scroll To Line dialog box

Scroll To Line dialog box

Use the Scroll To Line dialog box to move to a specific line in the source file displayed in the Source pane. The dialog can also be launched whenever the Source View has focus by simply starting to type in a line number, for example, 123.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Enter the line to scroll to Enter the line number you want the Source pane to scroll to. If you enter a number greater than the number of lines in the source file displayed, an error message displays, and you will need to enter a valid line number.
Push buttons
OK Scrolls the Source pane to the line number entered and closes the Scroll to Line dialog box.
Cancel Cancels the scroll-to-line operation and closes the Scroll to Line dialog box.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

<50 lP$#zf>_>X>'H./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbmnex.htmtm/$   einort "<>adglps/=chm.MSbuvx0AETfwy,45CIR19DGJLOP-3:BHNUWX_#2FKY[]jk!()8;q@@8xOAB|qh8p G SfMptimIKI\j[Aw[(5~Mi"_` :L!A\p,$Bi7[DptZΓ#g[ u;yF!SmU@:I9P@XjLd$E 쇾nMqV5$CTqPRM簿Gu;yF!SmU䔪d?{GsUwM3QݖQ|6duld0'~Nv[Uh]`#ԛ6Rr8pmVKx ]<GmVK٥c:)7l dp :B @Jlߡ+A s8A:)2ԘrP;c!B( Ufa:P  Yy-LLT ?B8Cه I  Yy-LL};$, sfj^t_ pǒxɠ쐳4(9͘6ivܺbD]Np{TgcP;.w$CJ"vvC7]r85|}Gu;xT0weYsLU0ZF})U1 b(l_%UT˕6X߷VW vL"vU. vC7A;c!n[_Kn[{2źi뇓*Cl0?Ż,S2Żҋ9Ь]ZgT% H ʥn-\?΅g~*ڴ˦$:rLdj68p k^4~L5R4 ? D :M7oFSeAtLHMlgңd=u1Mw]1(V5|b,( j7VNly7Z}*=( vC7OkCywSL6 ު 5|p/NCf`]׫J.澕/#kQkm*_V~oѸ5|b,ܺb@bN w]1(V5|b,L6 ߥK)s|PۯԵ*< vC7_oQ]N?U>&$ߣq&j6YDmJtĉ28˦%oFSeAt;.ou9 N)]Nw*}*^o{?C`/8pjdێ?rP w]1(VW) n:@{*_ʆU i7o@M>&$T)JrLd9(~zQpAAΔ|H4AÇKS!-pp쐳4(9͘p AΞ"vvC7F\*Ơu%r@I$>>E 쇾nMqV7-}UkJ"vʨܓH.r_&rٖ-LVG\!Ghl-r@ѫe}!EK\W扼u vneɺMM3QEk l</P##u;y wx@A1Z],? w| vC7\/,KewSY'zdScx쇾n^Qp5lAC]J]ץsN7m*^o jáC.{!rbd˺ꮬQnJޢܟ/Tuf(7d=uKzr@!C`7B(-1M вFpϥGVbC5E7LTuf(7-Ph%E<2ZJ>!GC[ Q˺oi]C`i7q&7W) n:P˦$f(]~i7W) n:D`T7 ݺ}K_ңd=uEPo>M7oFSeAtLHS#u;x߹tĠ}ZMl>ێ0'~/Bn'![\N)ܪyyPsrP  Yy-LL PvHY@A?1CtLI6$˦'\xgɦynu b*]~)溌bR*ka|PoWX0:դߠ}ěn$_(D<[=i@ѫe}( lqW A0ֽ&ik\i~+҈8(tFM_(C.8;.Iѫe} ]1 ~[1Eo;./; u-oTx쇾nңr𢣈#]\Jotĉ29wSLO`99 Wdw**8dS`? *85|uʛl7Km7դIn$l>ێ?ru;x߹tĠ}ZM_(Z5|}Gu;xT{NBoʨwJ1Y*qB\C.o8Hd=toʛloEw |W.vy!]~)o9w+%Bi7o75|b,ܺbAjaLJդl>ێ[mGu;yF!SmUᓥXNM3M vC7Ox@tIIѫe}(~@ܺbP>&FSeAtR5AT wro$B 7}ZMI>Sa&2rP˦% @8t A8Zp쐳4(9͘p8~*q.o8Hd=teʛljRP;.r@cQ]Np{Tgc~R+%Bd=uET{ϷVW vL"vU. vC7A;c!n[_Kn[{2źi뇓*Cl0?Ż,S2Żҋ9Ь]ZgT% H ʥn-\?΅g~*ڴ˦$:rLdj68p k^4~L5R4 ? D :M7oFSeAtLHMlg{Qb-[ @ܺbP>&j6YDmHQR0oxw`~nSSLTzQpaf쇾n ֆo!alTkye*_/߷˺$*;^!W\/}*_/GGңd=uE\ [JV~oѸ5|b,ܺb@bN w]1(V5|b,L6 ߥK)s|PۯԵ*< vC7_oQ]N?U>&$ߣq&j6YDmJtĉ28˦%oFSeAt;.ou9 N)]Nw*}*^o{?C]1 ~䓳t;./NB8S# *(-gdl/bxtI@7I1MQq҈- x ݺzҁi7W) n:QAa{L890ֹK\8(2WpP$7ě1MQq҇]1 p w]1(VW) n:B*< vC7_oQ]N?U󓐭z'o.o TEGu;yF!SmUTW%xtIIѫe}(~"vr@1MQqQkJ"vʨl?q;xGu;xo*? *85|uʛlo-SO/Nr#d=tA/9 i7o75|b,ܺbAjaLJդl>ێ[mGu;yF!SmUᓥXNM3M]à}ZM}ěFM_(C. r~i75|b, ҥkPVq&Io>LB 2+AÇ6+K:Q% Ï%(\~ۃrXV` wV$ pCW JRP;c qVԙ& kt$6zf>_>X>'6./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbsona.htmtm/$ Source Filename dialog box

Source Filename dialog box

The behavior of the Source Filename dialog box changes depending on the platform running the program you are debugging. Select the appropriate platform:

Applies to AIXApplies to SolarisApplies to Windows Source Filename dialog box

The Source Filename dialog box opens when the debugger cannot locate the source code.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Specify another file name or path Enter the path and name of the source file that the debugger has indicated cannot be found, or enter the path and name of another source file. If you do not know the path and name of the source file, and the file is located on the
workstation, you can locate it through Browse.
Push buttons
OK Loads the source file you specified and closes the Source Filename dialog box.
Browse Opens a file-selection window so you can locate and select the source file. The Browse window lists only files residing on the workstation or files that are accessible through a mapped network drive.
Cancel Closes the Source Filename dialog box without loading a source file.
Help Displays this help panel.

Applies to OS/400 Source Filename dialog box

The Source Filename dialog box opens when the debugger cannot locate the source. You can use the Source Filename dialog box for files that are located on the workstation or a mapped IFS drive.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Specify another file name or path Enter the path and name of the source file. If you do not know the path and name of the source file, and the file is located on the workstation, you can locate it through Browse.
Push buttons
OK Loads the source file you specified and closes the Source Filename dialog box.
Browse Opens a file-selection window so you can locate and select the source file. The Browse window lists only files residing on the workstation or files that are accessible through a mapped network drive.
Cancel Closes the Source Filename dialog box without loading a source file.

The Source pane will show a Listing view, if one is available. If a Listing view is not available, the Source pane will show a Statement view.
Help Displays this help panel.

Applies to OS/390 Source Filename dialog box

The Source Filename dialog box opens when the debugger cannot locate the source code.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Specify another file name or path Enter the location of the source file. This could be specified as a PDS and member, a sequential file, an HFS file name, or a workstation path and file. If you do not know the path and name of the source file, and the file is located on the workstation, you can locate it through Browse.
Push buttons
OK Loads the source file you specified and closes the Source Filename dialog box.
Browse Opens a file-selection window so you can locate and select the source file.
Cancel Closes the Source Filename dialog box without loading a source file.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

"> kr $X zf>_>X>'X ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbndar.htmtm/$ Array/Struct/Class Element Expansion dialog box

Array/Structure/Class Element Expansion dialog box

Restriction: This dialog box is not available when debugging on the AS/400.

Use the Array/Structure/Class Element Expansion dialog box to change the way program elements containing subelements (for example, arrays) are displayed when you expand them in the Monitors pane or Locals pane. This dialog changes the representation of only the selected array. The dialog box is available on the AIX, Solaris, OS/390, and Windows NT operating systems.

To modify the default representation, select File > Preferences.... In the Application Preferences dialog box, expand Debug in the navigation tree. Expand the program you are debugging, and select Array/Structure/Class Element Expansion Defaults.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Maximum number of elements displayed Enter the maximum number of subelements you want displayed.
Starting element Enter the number of the subelement position you want display of the elements to start from.
Push buttons
OK Changes the way the subelements are displayed and closes the Array/Structure/Class Element Expansion dialog box.
Cancel Closes the Array/Structure/Class Element Expansion dialog box without changing the way the element is displayed.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

 kB!!$zf>_>X>'./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbsrcf.htmtm/$ Open New Source/Module dialog box

Open New Source/Module dialog box

The name of this dialog box changes depending on the program you are debugging. The name of this dialog box may be Open New Source or Open New Module. The prompts for the Open New Source dialog box differ depending on the language you are debugging. Select the appropriate dialog box:

Open New Source dialog box (compiled languages)

Use the Open New Source dialog box to load additional source files for the program you are debugging.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Select the module that contains the source: Select the executable to which the source file you wish to load belongs from the program names in this selection list. The default selection is All modules which indicates all known executables are searched.

This field is optional. If left blank, all known executables are searched. This is similar to specifying All modules.
Select the source or object file: Select the source file you wish to load from the source file names in this selection list.

This selection list only contains items related to the executable specified in the first selection box, if any. If the first selection box contains All modules, all source and object files are listed.
Only show items with debug information Select this check box if you only want to load source code for programs that have debugging information. This is enabled by default.
Push buttons
OK Loads the source file you specified, then closes the Open New Source dialog box.
Cancel Closes the Open New Source dialog box without loading any new source files.
Help Displays this help panel.

Open New Source dialog box (interpreted Java)

Use the Open New Source dialog box to load additional source files for the program you are debugging.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Select the package that contains the class:

Select the package that contains the loaded class for which you wish to see the source. If the package name does not appear in the selection list, type the package name in this entry field. The default selection is All packages, which indicates that all known packages will be searched.

This field is optional. Leaving it blank will search all known packages for the class. This is similar to specifying All packages.
Select the class: Select the loaded class file from the class file names in this selection list.

This selection list only contains items related to the package specified in the first selection box, if any. If the first selection box contains All packages, all class files are listed.
Only show items with debug information Select this check box if you only want to load source code for classes that have debugging information.
Push buttons
OK Loads the source file you specified, then closes the Open New Source dialog box.
Cancel Closes the Open New Source dialog box without loading any new source files.
Help Displays this help panel.

Open New Module dialog box

Use the Open New Module dialog box to display the source of the various modules of your program.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Select the module that contains the source: From the program names in this selection list, select the program to which the module source you wish to display belongs.
Select the source or object file: Select the module of which you wish to show the source from the modules in this selection list. If the module is not available in this list, type its name and path directly into this field.
Only show items with debug information Select this check box if you only want to load source code for programs that have debugging information.
Push buttons
OK Loads the source file you specified, then closes the Open New Module dialog box.
Cancel Closes the Open New Module dialog box without loading any new source files.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

 l"$Wizf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbprcs.htmtm/$    eot<>adghilnrs "/bcmpu.=fy,0AISvw4CDJLMPTjkx15EGRV*-9:BHOUWY237NQXq#&()8;F_'+6K!8$<`, apA8 p8#A/m[0dHͧeـ@,և O}pp$|}H!![3b[08:80 Ir$p, ( 0|}H($4L' Tnݤjj]KɠȶۥJT94hc@]JfԼcL/S^'2$KjW:^&T WlRtnN$խXOt}td(57#ZIT4ꘕm+NU>N*pkdD`Oi&9T00s=^RnWPlǡY%ׯr^ROÓѱrlU@b ʧ)eSpLNPi2LLsI*J`&u} ̅. ,{OÓѱrlU@eUa ܍i' /N*kNAc sPt섊8Yt:Ytr^RJCjBGc`d&] V HrNBPr sPt섊8@AC,48PQJCA@ v1^ A -+ hX8Hf{,0ɨ*`$pp`#CKJ$=q[EG 06ca&‡A^ A -+C`p1͘XkA&‡Aӽ%ȑYt:YtkI#098]JfԼ\eUzݤwZs!ELb5C؛.BC6$ʄ016=͌Pvׯʢk[d(f< {,0F & Nz>"0ƽ}֗d6ׯܗ *cixv̅1j'&s p)&s^d%M*K\t\YF]a"&uSA1 sצ̅1* \\p6_TYtr^RdM|Zm̜U9ׯL'}\TĨ4{(?N MZ1/S:nS%Y1B- 1r sc=pt79ř&{dILfBl{צBCj 0$qii\ć-[EG 06caa>MAS#4  @ZW1!8B(|,8Y9 & 5L:2pLj061B퓙 *cE#nR_Ѭl67ř&l$3c0 ISjILɑU "k 9/ G Hz hX8Hf{5PTHC2_yd MZ:^/MJd2T;b5 kr!@ ab::^}izbTL&]A0.i^&QoIs&)KTNDeS.c%0Sւi9Sց 1$rj *\蘒(|sJ׬HH{Ul8 y9.j${AˤE%CWT1%58PR)X$p$:p@asV#:=hu9Sփj@asV#:lqM+kʨPMtIV~_l.cЮ]\ʍDŽ/ ͌$_l$a*_ .vTozKT(llF+HeFtnu{\kdll'fOl.z{*7]SeRp@{=Kx)@6g"7 zr-H9.j${@v̨^K&a'W:WΤtܽ_O |L)ʅ 1ʄRp@"KRp@"KRp@{=Ky-IM/N-Kr^R퓂dV;62r$R=K.N 2$KjW8Q} 0߹9E$^;cAȵ o9 oڰ乫xžaELcfJ2OK r#p"ԁjÒG0tOlQS&V}@sdd6ׯܗꛘlQS&ي'2T8`'K7;HN.%4Pxi7ˤ*mdwOT;dͲdle]$h91"Ai%ӓPTH@RDĔ׬HCKbTbGGګ`8P ZeUB /scg"KAȵ o=K=$c'N*pkc^ꘕ*ɗPx fi\IJa6%$dYT;zK0L6[‡@{=Ky-*ͲiILd4r$R=K{I.Gʗ:&$bG *\58>[‡@{=Kx)@";=h9 {V5o=у0Wtr:W_'uqan$խ^U>NjlLrE9%OO퓺Kb0l)pI|dmcT5pP kׯQ"rXeFyI~Ln"rX <$.7%bbܦUF{ccіxN.67ѬPsU=qTP{^Um k'͕.7%b=NMAS#KS^#.qR jG@Co=Շ%[ďt`T%Jk$p$|=   {V5o=уZř&r$R=K{I.Gʗ:&$bG *\58>[‡@{=Kx)@]JaȍžR=Kv1d2Jhʳ!ELc0P r-HE9.j${ApqȍžR=KuFc' ILԺ`[^ko**O +Kň9 " {V5o=уSր.0FOZEՇ%[ďt`&9"3pj@r.ZItoj@r.ZItabA i%ӓPTH@RDĔ׬HCKbTbGGګ`8Pp@asV#::w8Xh((t0` Hҹ]D!m>  ,ُuACo<AG"KAJEՇ%[ďt`8]JfԼZnS;/"^D/HTLzl,48PVR_=>z'Nu#r;%[C1 ҙK]_L1)6~`20" !@sPe31r w5)6S6\LBp4iWu퐔T7ғm1)6|p8 ymmeoɞok(!@sP A>o9@[س&= Lrv*E2I\A1@dFILki!a‚}'&X:$oTjb~SuI5{&0totyp&a9S֍퍎ԼP˨N 3'TĨ4m?]sOZnLtr#p4`bE>N*pkdv6:FVΠbIt08>T1%58PR)X$p$:=Շ%[ďt`idqU"tA@@0AsP75 0Wl"rXLbվULlp==_){^7qUy),<ɘdB潠l'K7L)&OVxNDRYgK1`r"F;}^L*cXb9nR_Ю8s=^\)QM:xLfsc} 퓃K\]=?N@(+ܖ#plL'-*9p'$=h6\/WlD 2M9%]ׇPB{d'7u/& $o sP> z @4((r.ӹ`&8{m>ޒo @4((q!@w5S`ׯ hh]sc} Lp3c0̅ ko`P 9 }(:c{d'LbվUD4fCA@1>K5)~I57*N"0s'NuU@txa b=NMAS#KS^#.qR jG@Co=Շ%[ďt`8 r\EՇ%[ďt` s(a yS0U9 " {V5o=у$EՇ%[ďt` s(a yS6[^=9LLU$0U9 " {V5o=у$r-H9.j${@ {IW)vb`aׯI% רAȵ o9 r-$P7@9:If:c6763&31 JkdžTjDnr]pUb̓ncw[^A 퓂ަԼk7@5$ Р `Y1Ѻw67Э.wlDkhX$ Br sP> z!zdžTjDnr\[C87N퓃vN{bo=8 9 s+N+)0Vש&:sc0=7{㧋^NB{do%4P}pYI68˕I؛Ou#P|Lsbׯk*=ש&,[Lt&;ck_uka'sc} LpKd'7lYm?lFJP2_xˤ퓞7 zvr#př&yp#蜳cy3iIWPa Խؘ䋕9 r. asV#:=hQ8-=h9 asV#:iA SրU9S֎kè!=pU7-MKy4"_lDscr퍎ԼIW$o}tu^TjR9 {ڰ乫xž%4P;\+Nd)pI}MYȍžRڰ乫x97i)z/"^D/H$ׯNd)pI{\F[ivI1퓊:U<:^yS7r2s!KKdΕ*U:_86$%# 7Ժ sOZnLtr#p4.e2JJ{d$ծ`7{\7Fi87I5kI.63D&IMPo;s'Tjb~;mznttZm%_$o!KKؘ5UcO 퓙 \^;co%4SeA=uI&-ɞVZ^j\bCA@1>K};dB%lZWlU9׬oUq# o;[I`,!KK8̜$8`S&=x%4Se[Lcv̅. ,F+m꩎S^9%ldMni0L0C.cvSbc.T 9P,!KK8̜$8`S&:\v`6c'sI`/scxlD2JhʶNx)@*TjDn.WBdJl)pIzRh#kmGN)f*'SE6U \^"0[loT}^)WlRN^tB1W#:r!@w5@X` Rs'&s {dKsI`/P8>dMmlSրUjMYȍžr6\vt`R5.GE&Nd)pIb0CuV;Lz-[Zc'(B_{La;lo`S&8`^* zc׫Nd)pIa:_!PRMHPo;l)pIxd_lR&IMPOl2M62%ΘleXa(A%9j91"CA@1E&N HrrǶ&LZOr' @h5Abam6xN)(!7 zA=h댺J9NLcd%[ Phtl/Ժ74r @r-H\79.j${Ap63 \^d(S]'"7 zr-H9.j${@!PC694+F}Y#0 rN 04i6*a/*cnǶ&hX{m6%6 ztl7&7dV[O Ѻa#I5kk׋a \^*'Fir'&s {dI57cRm 017mzپԹ͍R2C$^Gkѭ1z:t^Sqth!=l{n/VL%!)bfB_yztlLj01iAb=h i$FOZ0X7J5Ks_1]4l S]!<$,ƺvNKI&Nd)pIcVmOJ!KK̅ k's_90 㖑{ou=s L퓕J"{msT2dL%!)P-6~Ht$^wY3y"dS_} 퓹"ԁE9.j${Ap$इ$FOZEXr\ռHFt}dɠX7lYiILo6ׯD8Xip"ԁE9.j${Ap$ծa^)Aȵ o=KsJgždV7mzr#pFKd$ծ`7lݵ뎦Լ̜$0ٻkMKy4P|qtot7L(^ MZm'3LxѰ*slr-H\79.j${Ap&a9Sփj@asV#:X7J9p&a9S֌IA =vLBUqtl0AZL1)6~W0sJ5퓞7 zvr#př&7 Ѻ}_t}sOZnLtr#pL4 ѣ{\KÛ!xѰ*Bt[?2$ &1Va:^3y0 U2҂ zdžݤ)@afIt`]퓞7 z=h6,6F$ծa9ss̅e덦`7 aiIawk'Fs̫Ol&攛m?Hm; k׬FTaiIǁ{^4lRԺ sOZ`=h6#2tcRm=w4lSaɄ e5rR Ei%ҁEyȸ ci%ҁb̜b̓nWl.%3SR^MtuLJImlU9׬kI."poIs&)žNQȍž9 o=NMAS#KS^#.qR jG@Co7Շ%[ďt`j@r.p@asV#:=hrDnZ7Xr\ռHFKbc.=.31/9 "EJj@"ZItcd$P!t.,t 84bCK(bCuF VP3T &O@NA@ >MAS#0 P re!z k8\#$( zf>_>X>'%( ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbsrcp.htmtm/$ Source Search Path dialog box

Source Search Path dialog box

Restriction: This dialog box is not available when debugging on the AS/400.

Use the Source Search Path dialog box to tell the Debugger where to look for source files associated with the program you are debugging. The Debugger can only search the local system for these source files. The dialog box is available when debugging on the AIX, Solaris, OS/390, and Windows NT platforms.

Each time this dialog appears, it will display the previously entered paths, so if you do not type over the previous path, and instead add another path, both search paths will remain for the Debugger to search.

To remove all search paths, erase the paths in the dialog and click OK.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Enter source search path Enter the paths on which the Distributed Debugger user interface should look for source files. This should be done on the workstation associated with the program you are debugging.

Applies to AIXApplies to Solaris Separate multiple paths with a colon (:).
Applies to OS/390Applies to Windows Separate multiple paths with a semicolon (;).
Push buttons
OK Sets the paths on the local system to be searched for source files associated with the program you are debugging and closes the Source Search Path dialog box.
Cancel Closes the Source Search Path dialog box and discards any path information entered.
Help Displays this help panel.

Copyright IBM Corporation 1999, 2002

 lؖ$$ ]zf>_>X>';25./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbpref.htmtm/$   eot"<>adgilnprs /=chu.bfmv0ADSTwy,5CIx-14EGLMPRkz&29;BFHOUW()3:Y8NXq+K!7J8 p8 PX`p `0p PX`Hpp# ][)h@29V)c)R8]dNuadӮ]dcbJL#6C#@8 8d p4 ܑRA(`PdӮ]dȀ0*S(l!k MБ3 q31U{eP1*R 1RP0(@Ce;"ff8c 8c23S=a)S:&a.&c1ʠ$ `#8L-ki{0K.V$lwCp28@ s3v.:a:eL%[uZk9q.VI&cKZ31`ΘJcМt)mO ץZq,osSV&+Be&.F2R U5 WH&XܒqITL$>S#[i֖:=#,BE:\u›=CgPTɖ/I,r09ezT9dl10( 27XqyyZ08)RdJKmȤ{R=n O2dg%\(ZK:JKm$eCPdAk\9"86LzIcA͓-kҥ1 aUA@H90{=n O29hkh3 nP)7 rqHZZŸ]< 7LOS\ .[BlꛅBlo b8m2Ӏa lʜuˮ= Ŧ Hv;q@紈l* ` 2%Y6LJ,1VQ @{=n O2"-,lȤ{R=n O2iT0 AeK lk^)Y b Á {V--bAd7 rI7P 8Sj@b-@YL JzsCq,S"6=;emSllvS +|)pH,l%.N&rqH=ZZŸ]<I) cn`q@t$L\L 9q8)ԁjť[5̃NZ @(``b;QAíMd!k&=‡A͈*`Ã9hdu‹~/{Cp¥ڤAk[S8 &_l`%BD%Fcpߥ_uKTBy/S;*y/Sȹhe&/ K s넓KsʝJ—BKEvRo uHֶ9y)vREˏA7lr㉨r &_l Xۘ1qށ>I`ʞA_1I)d\8酰ژo.  *IT$(vT7Оʑi2e; |ꘓ>N13v.:acu eOlrA.[4}k=eH%$@4TcZJKm9ǵ o8 q"(ڐ7{7Xqyiz\A)r=yǸ o=ՋKXkH ". vA!\ &˄ژ l^^E&DNS#C5H Ǒ"d aXJ. a0/)"u^R3zw— | 6/|)pH,l c[9oRnTڐ7{7Xqyx)@LIm9h8 {V--bAdK1BxK1Zm]_>X>'& ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubpnbkpt.htmtm/$    aeinopthlrs "./<>bcdgmu=ASfkwy,-0BCITvx349DEGLMORWY#'1NPUX_28:HJq!;j50A  < @  X@ Y`Ogp=6vne 4,1PAFV@NDuZ? }hvtjK.z- 4^(H,y[I / /SBlH3gWe9=8&Mat;pC˚z Z4 :iC˚z P i9ЧgU1r浿aȤ&_U2ؗbuSHTXqvGBMf+Q1іĀ' Y~b0I ( kvK@9(8 nhOp9Z?1ri$P8XY&X,, \G.M1dXaniM YfcuH0.7&M#Q7.k[yl?U.4#HqKYYt^lq>=@ ޔR~k꣡&0Γt;8Z:BEȎpMUce&q)k0.7xsCS9ӊ޸QT|t_o= W Uf7Yt6[uHJϵk[}Ȃ/ 0 H 4.4h/$it频@$\~M!cO:؄0I!d`p4ŃDQEN4E@$\~kvKI[ $,LxhJ(IцH'$Vb(u`B4ӥIbnhB4C7.k[ -0.43 [U1r浿@搜s!kxO#7q>2cQ;. >쏌l!N\}?!s7.kZW|8=DN^k꥽r}Ur3qsZ>q+|}r'GUhe& Z>5C˚5Q-Пe_Uc dd?U]y$odyM>Џs!oƔ@&Cs7.k[ztvW6 H 4=Qd8ܹZɆneJ|tN}Ts7.kZlJ^'(ap~u7Pf7tY΄k04 @ٺo\oi ?qs[͘hOsЖ˂d8ܹhOzC s!kJ04 L/ 0,$.Rta68XYHx`xEf.ao 'lB$M7Yt?J(X,,C7.k[ -0.43 [U1r浿@搜2n\ַ8d8ܹo> q\}όXêv]k} CW~nQ~C} C˚֕6==!WKzUc:g9r浼}BB;cJEq=rxu߮j9̇5k꣮[?U澪>2HvCF8MǨHI9P_U}UC˚-+c栃7.k[zGlEy.a 04 CC˚oX}Nji$gG9r浠)f4+RyҊOwZsxO U l|E F H 4 O:QI͛[o7S΄\s7.k[ސBcqsZ҈|m ?j9̇5y ن4IJ)?5RߏPQfaxi `$Qr .FFĒ+1s |,0 ,y]"iҁ$dqsZ1 -0.43 [U1r浿@搜s!kxO#7q>2cQ;. >쏌l!N\}?!s7.kZW|8=DN^k꥽r}Ur3qsZ>q+|}z"+X<'Nٺ ι2n\nTwc,w"=gA6!'xC#}Tvl>9{g\f2n\oli\!9r浼GlEy.a 04 CC˚oX}Nji$gG9r浠)f4+RyҊOwZsxO U l|E F H 4 O:QI͛sЖˎs!k{\ls7.kZQf`p4ŃDQEN4DAFFĒ+1s |8o #i޺Vd8ܹf7yc#aA2cߪe O:QI͛mCouv;qsZ߷΂$dTM}T| O:QIaxi^Aa?S `J("ER"M2RG$it_>X>'%+./usr/share/man/info/en_US/xlf/html/debugger/ui/ubpnlocl.htmtm/$ Distributed Debugger window - Locals pane

Locals pane

The behavior of the Locals pane changes depending on the platform running the program you are debugging. Select the appropriate platform:

Note: When viewing the Locals pane, choosing the Expand All option from the pane's menu in the debugger main menu bar will expand one level of the tree at a time. You must choose Expand All for each subsequent level of the tree that you wish to expand. Choosing Collapse All will collapse all levels of the tree.

Applies to WindowsApplies to AIXApplies to Solaris Locals pane

Use the Locals pane to view the contents of local variables that are in scope where your program has halted or that are associated with a selected function, method, procedure, or entry point call of a particular thread in the Stacks pane. The Locals pane displays variables for this program thread or variables for the thread that is in scope where your program has halted. You can expand thread entries in the Locals pane to display all variables in scope for that thread. You can expand variables with subelements, such as arrays or classes, to display these subelements.

Pop-up menu options allow you to enable or disable, edit, delete and change the representation of variables in this list.

When you enable, disable or delete a variable in the list, the action only affects the variable while you are in the present scope. When the scope changes, the list of variables will be updated with all the variables now in scope.

Enabled variables are indicated with a red diamond (Enabled variable icon). Disabled variables are indicated with a gray diamond (Disabled variable icon ).

Leaving a thread expanded in the Locals pane may adversely affect the performance of the Distributed Debugger. The local variables associated with a thread may need to be updated during program execution. For example, a change in scope, a program step, the function or entry point on the top of the call stack may all cause the variables to be updated. If you find that performance of the Distributed Debugger is slow while stepping through your program, completely collapse the thread in the Locals pane.

Applies to OS/400 Locals pane

Use the Locals pane to view the contents of local variables that are in scope where your program has halted or that are associated with a selected call stack entry of a particular thread in the Stacks pane. The Locals pane displays this program's thread or the thread that is in scope where your program has halted. You can then expand the *LOCALVARS data structure to display all local variables in scope for that thread. You can expand local variables with subelements, such as arrays or classes, to display these subelements.

By default, all local variables in scope for the selected stack entry are added to the Locals pane, if debug information for the stack entry is available. If debug information for a selected entry is unavailable, a debugger message will indicate that debug information is unavailable and the Locals pane will be empty.

Pointers and Java object references can be dereferenced, which causes a new expression to be added to the Locals pane.

Pop-up menu options allow you to enable, disable, edit, and delete variables in this list.

Enabled variables are indicated with a red diamond (Enabled variable icon). Disabled variables are indicated with a gray diamond (Disabled variable icon ).

Leaving a thread expanded in the Locals pane will affect the performance of the Distributed Debugger. The local variables associated with a thread may be updated during program execution if the thread is expanded. Variables can be updated from a change in scope or a program execution. If you find performance of the Distributed Debugger is slow while stepping through your program, completely collapse the thread in the Locals pane.

Applies to OS/390 Locals pane

Restriction: Local variables are not supported by TPF Assembler Debugger for VisualAge Client.

Use the Locals pane to view the contents of local variables that are in scope where your program has halted or that are associated with a selected function, method, procedure, or entry point call of a particular thread in the Stacks pane. The Locals pane displays variables for this program thread or variables for the thread that is in scope where your program has halted. The thread entries can be expanded to display all variables in scope for that thread. You can expand variables with subelements, such as arrays or classes, to display these subelements.

Pop-up menu options allow you to enable, disable, edit, delete, and change the representation of variables in this list.

Another pop-up menu option lets you display the contents of a selected storage block according to a user-defined layout specified in an XML file. This pop-menu option is not available when debugging interpreted Java programs.

When you enable, disable, or delete a variable in the list, the action only affects the variable while you are in the present scope. Once the scope changes, the list of variables will be updated with all the variables now in scope.

Enabled variables are indicated with a red diamond (Enabled variable icon). Disabled variables are indicated with a gray diamond (Disabled variable icon ).

Leaving a thread expanded in the Locals pane may affect the performance of the Distributed Debugger. The local variables associated with a thread may be updated during program execution if the thread is expanded. Variables can be updated from a change in scope, from a program step, or from the function or routine on top of the call stack. If you find performance of the Distributed Debugger is slow while stepping through your program, completely collapse the thread in the Locals pane.

Copyright IBM Corporation 1999, 2002

ng>_>X>'cP./usr/share/man/info/en_US/xlf/html/debugger/ui/ubpnmdls.htmtm/$   aenost>cdghilmpru /xUHdxU-ևC0fHdS<] {bYUg͊ɧW<"] ɧa=K_{bC~}L6gH?77y<] {bY`r@-[!ҿbLLoo O&HfZ u]t-cָnOCyWL vaiHbR#2@Vws*B FkP;9$Ҍ1 (3¬\lTu;8#.{[xZR羕2gȞ '.5W]L(άj_Ϩd^>nZ}ꯩkcT]wҴI CJRPgzsçl>wXkcn9Js/@ʡVFH53\KЅR=` 3lm?73lj'H,'/Xkukcn;O3CU#Iz'̙0o#5H(-6Xcn5H/\Uu_S<] Vwp]tk =dĐ;J04xu;"9RUuJ>5jϒ6un y՜Ʈg4HiFo3CwDs[ƪ뾕J'չO5zc'ꯩ "HbPu+kvY޹6J\GuNOkT$_~*ɧW&gz;bO[L'{ګs/Hm {Fdg o sR$Q! vaiHPaRR3]taR@AH @(ҁy?S<. 튟Õ!`DegGML=`D6g+>A<39Wq)sU3 H 'q0.yk>A<39Wu6|ꯩe`iF jk# byU*$*[<|ƮZ]ht3۩ELg&UH^Is&L6yAAiZ"۩u W&]uW#5H(\68@AFkְ}vM3ևC39FC'^A?2{]ht3۾KiuϮyάj_ +sIz{,\nO$W=wsç&W#5H(-6Xcn5H/U}LZ ׭a'V|ɶN'_S5أ$c/B e럷άj_Ϩd^y%DZN'v'{=aOjI CJ Lo^*<G5DwLZ ة|9Rc.3'u+f0d.38Ʃqh:~xZ<" \NϟSu~20I CJ LZ ةUg5\ҷ>7ç*s/B$x[ƪ뾕]>Agꮾm&$Q!kenq՟%rmֺFTg:r~oq*Djfv'{G6GvN՟%rmoq9Ս\ Pڙ{=R$Q![L[ƪ뾕;,\uNH~]mj9"T6M?x[glT vbR#( $HB)1`0@# %h(P 0@"-Bw@+-ͷF@  ɷ\ @RiFɳ(b k8($rzf>_>X>'ir./usr/share/man/info/en_US/xlf/html/debugger/ui/ubpnmntr.htmtm/$ Distributed Debugger window - Monitors pane

Monitors pane

The behavior of the Monitors pane changes depending on the platform running the program you are debugging. Select the appropriate platform:

Note: When viewing the Monitors pane, choosing the Expand All option from the pane's menu in the debugger main menu bar will expand one level of the tree at a time. You must choose Expand All for each subsequent level of the tree that you wish to expand. Choosing Collapse All will collapse all levels of the tree.

Applies to AIXApplies to SolarisApplies to Windows Monitors pane

Use the Monitors pane to view registers, variables, or expressions that you have chosen to monitor. Only variables that are in scope can be added to the Monitors pane or used in expressions you add to the Monitors pane.

Applies to Java You cannot view registers in the Monitors pane when debugging interpreted Java programs.

If an element in the Monitors pane has subelements, such as arrays or classes, you can expand that element to display the subelements.

You can enable or disable the monitoring of expressions, registers, and variables. When monitoring is disabled, the value displayed does not change during program execution, even though the actual value of the expression, register, or variable has changed. Enabled variables, expressions, and registers are indicated with a red diamond (Enabled variable icon ). Disabled expressions, registers, and variables are indicated with a gray diamond (Disabled variable icon ).

A pop-up menu option lets you edit the contents of variables or registers. You can also double-click to edit the contents.

Other pop-up menu options let you delete an expression, register, or variable from the Monitors pane and change the representation of an expression, register, or variable.

Applies to C Applies to C++ Expressions and variables that evaluate to valid addresses (for example, pointers) can also be added to the Monitors pane. They are indicated with an arrow (nbenptr.gif (101 bytes)) in the list of expressions, registers, and variables being monitored. You can dereference these entries by using a pop-up menu option.

Applies to OS/400 Monitors pane

Use the Monitors pane to view variables or expressions that you have chosen to monitor. Only variables in scope will display the correct value.

If an element in the Monitors pane has subelements, such as arrays or classes, you can expand that element to display the subelements.

You can enable or disable the monitoring of expressions and variables. When monitoring is disabled, the value displayed does not change during program execution, even though the actual value of the expression or variable has changed. Enabled variables and expressions are indicated with a red diamond (nbenvar.gif (91 bytes)). Disabled expressions and variables are indicated with a gray diamond (Disabled variable icon).

A pop-up menu option lets you edit the contents of variables. If you try to change the value of an expression, the Distributed Debugger will display an error message. You cannot change the contents of expressions and variables that evaluate to addresses. You can only change the dereferenced value of the expressions and variables.

Other pop-up menu options let you delete an expression or variable from the Monitors pane and change the representation of an expression or variable.

Applies to CApplies to C++ You can also add expressions and variables that evaluate to valid addresses (for example, pointers) to the Monitors pane. They are indicated with an arrow (nbenptr.gif (101 bytes)) in the list of expressions and variables monitored. You can dereference these entries by using a pop-up menu option.

Applies to Java Java references are also indicated with an arrow (Pointer icon). You can dereference them to display the contents of the object.

Applies to OS/390 Monitors pane

Use the Monitors pane to view registers, variables, or expressions that you have chosen to monitor. You can only add variables that are in scope to the Monitors pane or use them in expressions you add to the Monitors pane.

Applies to COBOL You cannot view registers or expressions in the Monitors pane when debugging COBOL programs.

Applies to Java You cannot view registers in the Monitors pane when debugging interpreted Java programs.

If an element in the Monitors pane has subelements, such as arrays or classes, that element can be expanded to display the subelements.

You can enable or disable the monitoring of expressions, registers, and variables. When monitoring is disabled, the value displayed does not change during program execution, even though the actual value of the expression, register, or variable has changed. Enabled variables, expressions, and registers are indicated with a red diamond (Enabled variable icon ). Disabled expressions, registers, and variables are indicated with a gray diamond (Disabled variable icon ).

A pop-up menu option lets you edit the contents of variables or registers.

Another pop-up menu option lets you display the contents of a selected storage block according to a user-defined layout that is specified in an XML file. This pop-menu option is not available when debugging interpreted Java programs.

Other pop-up menu options let you delete an expression, register, or variable from the Monitors pane and change the representation of an expression, register, or variable.

Applies to C Applies to C++ Expressions, registers, and variables that evaluate to valid addresses (for example, pointers) can also be added to the Monitors pane. They are indicated with an arrow (nbenptr.gif (101 bytes)) in the list of expressions, registers, and variables monitored. You can dereference these entries by using a pop-up menu option.

Applies to CApplies to C++ The contents of expressions, registers, and variables that evaluate to addresses cannot be changed. Only the dereferenced value of the expressions, registers, and variables can be changed.

Copyright IBM Corporation 1999, 2002

s are  k)$ zf>_>X>'( ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubpnrgst.htmtm/$ Distributed Debugger window - Registers pane

Registers pane

Restrictions: The Registers pane is not available when debugging on the AS/400. It is also not available when debugging interpreted Java programs. It is only available when debugging High Performance Compiled (HPC) Java programs or OS/390 Java program objects.

The behavior of the Registers pane changes depending on the platform running the program you are debugging. The pane is available when debugging on the AIX, Solaris, OS/390, and Windows NT operating systems. Select the appropriate platform:

Note: When viewing the Registers pane, choosing the Expand All option from the pane's menu in the debugger main menu bar will expand one level of the tree at a time. You must choose Expand All for each subsequent level of the tree that you wish to expand. Choosing Collapse All will collapse all levels of the tree.

Applies to AIXApplies to WindowsApplies to Solaris Registers pane

Use the Registers pane to view or modify the contents of the registers monitored for your program. The Distributed Debugger initially displays a list of threads for your program.

You can expand the thread entries to display a list of register groups. You can then expand a register group that interests you to examine or edit the contents of the registers in that group.

In the Registers pane, floating-point registers are displayed either as floating-point decimal numbers or as hexadecimal values.

Applies to OS/390 Registers pane

Use the Registers pane to view or modify the contents of the registers monitored for your program. The Distributed Debugger initially displays a list of threads for your program.

You can expand the current program thread to display a list of register categories. You can then expand a register category that interests you to examine or edit the contents of the registers in that category.

In the Registers pane, floating-point registers are displayed either as floating-point decimal numbers or as hexadecimal values.

A pop-up menu option lets you display the contents of a selected storage block according to a user-defined layout specified in an XML file.

Copyright IBM Corporation 1999, 2002

 l *$zf>_>X>'y ./usr/share/man/info/en_US/xlf/html/debugger/ui/ubpnstks.htmtm/$   aenost<>chilpr "./dgmu,=Sbfky-0ACITvwx49ELMORUWY#13:;DGNPX_&28BFHq!()5J'@@ 8 h<C9!% ,  >+X( %$!zsRA\!N^dD]lքtuZ(-zs@tS2@(@HH JH@0D`0 ٭Hhpe@f3R0MQ!xAzlAfI!`2E(vwEJ X C%pW<^‡gtT.(dhQ繱mwT7k<y+ʷÜs=͍o8ڒ?CXG[h@P8m(R `oQ!.đĢ:#Ee\%#5DuF$!D,(-I,5F !{$Ao"zw~z3_tjAB.3/5Fv}s ts̑l td?1"=|s>7%p?7wy=5 ES–F3$5-7~71oȋ+.FfԆ[[ -Ay5 c~{fd&k^?Z'狳ީ f9?;7>YTܒCts(vwEOk~l(wsd\#gExnYP1d l[ 0?F\[Ow:h;;Bfԁ >vL '@ƲFs1~gϫ0:߲a\-J5\[Ow:hfn{7ߛ @tY8R rH!JA_ IEà@PQFi<,(9|,@PQ)Pt$,X ((5F^‡aR(- 9 /aC*~dw>| oͅ졶YtW k!'ߛ Fg<>zdG[ y%L<Ek~l(wמ=W[3s`~}\={';+3aCꆷ‡vPyѬ3&q5[*ތ{ 3t b-;yѬAy5Nd=sTEI\:6\ok*}#*?Yu_W$s`|o0Olz3_tjETn|9o3eG.lAy5$EњR-v!̣xr0gڣYt_tj|+Yu d,G:E BH(._tjP[ArA?W<^‡gtT};ߛ CmFLCZ Ok.}sTEO1gS5JAnI!\[Ow:h;;HT56;~p7,c26~g?~{'4e}\{ RR rH!J#4Q%Zl )zq)C7(-AѬr_>X>';./usr/share/man/info/en_US/xlf/html/debugger/ui/ubpnstrg.htmtm/$    aenort <>dgilps"/bchmu.=Sfvwy,0ACI-45EGLMPRT139DHJOWXkx:BUj#'()*+FNY_28!;zq@ @x/!p7@q@A E=˨i$tI΂ `]lւ#]#kD \cD1@8 '@8 H  X@~Uh@8;H9=\'د%ɖRLPtJrNt9=g 8p0\\0 B" sah@h8Ą9 2/"huP,8[Kmc*p@Cg 8p0\XPuP,8[KJ' &ǀXUxC.;y *NtJrNt9 !?*~̵0Pߥ*fw.yrFnwe :T \k_'s`l3s߱_+%+s-y8[vrX.Z4'o!sʺ٭=́0^@(ݕwe \? Wʍeױ^;Vq&f)R\EHtr@CsV[[Ɍ쯥ŲFw.xƿvQl\Ó-KR)Y/_KH*fL-LW$oUKdSXP_W3YKeFrF,e)K*5_o>T͕wde/KH-L˥3ukdѾ3s.{kA ̚4? +YK\Q X.lLAI·%g 8p0\X pl? D5"\NB⧱| 6 luI&lV;'e\ qݖc 6 las]RI[)| bWE<2s*P.;אcà$CumW*rזkKyXe\mf+WkAtvWDl5=I k.ƼIOs3>gtTd%ɼTQRֽS)b -kJe,@+K8(:O7Ft }I&=IAѪ]måy78 ?*Z׺ e,@Ct)L?ibBIn$qp.҇]- |-J{C.IѪ]mä2aυ+%+seFqKR3*ypL{tԨah6+-xx>R^SXP_^_$ۮToseF:$In$qp.҇]- Dvx:xtROW b@n! 2>gmtTAA?[)?ROIF-rCEqoUKdSXP=+A[m4+mtTT\pd's̺fwfVϥϩM5K cc>\EHO~Bɟ*fʹe/sLS)|iSà$Cp38rd.^E,ƒ`Ј_$ = b@`(tKH(!KJ$C?Kcl)\S \k_W~BW$ofvZ EqiʳfvZ .z9!X|v's$4Tkz6.N~k)~7sJ{[~C$e Oe}.xc\Q}.{)ol+s3 Zly ^A \>دϚʺܶ[eax5L{C$C?KLge}.xtT-3o!s65ʍebm\fJ{\EHtrD.yW[5Ergj`J#z[ €RR_*5^4e/YK\Q|l'+[%k)}ܺZAjf]-ۇJ6 lo8 p~TtX‡KZRK8(~1 IѪ]måܺZAZ]-(#TUX>ۇHe)K VKWʍe~>gtTQ\mˁsV[[*2Yf}-d<9ƼI\5'M?ʍetIIѪ]måܺZ@lu6?riA.Ё:Be.}H'o!sL5I?7ARA[)9䆊lޫ4 ;s"eyVLbq;y fwEOQLߥ 6B~<˦m~kmm\\4[9*İ63.xtT.yQ\lR?$e2ʶe<:rNt9(!94 B KB`Ј_$HPPN(tG2D$:P˥NB˥BPCs|NB*|51mH*fhvZ *s*.NX@,H<,0߷Zkg%AVo*+ʙKTT5H !9]n[_ʺܶR'^V0W&[cfYJ4PdÝ1&% aOAbBOU/Lget?ri&ڤ˥:rNtl*p@(k^)ʖХ2 pPc '?UX>ۇJt]l~҂5I?UX>ۇHlK=́5W~B3s˥2fFPC.kA srN5ٽK=́5C.&@\d!KHO  6}rF}.yW/uҙKl 6_WTWp 43Iǹ6Tqo|穏s`o~l]-!A[8t^dJe/8`.2 ñL{eACAğѪ]måܺZC-O eJ~҂5I?UX>ۇHlKFL\iS>=ܺZC-O eJ~qh!V2X5I?#q'?UX>ۇJ$ăy|wn$ĠROqp.ҍ[_>X>'k./usr/share/man/info/en_US/xlf/html/debugger/ui/ubdbdaem.htmtm/$ IBM Distributed Debugger Daemon window

IBM Distributed Debugger Daemon window

The IBM Distributed Debugger Daemon window displays the port numbers on which the Distributed Debugger user interface daemon is listening.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Push buttons
Stop Terminates the debugger user interface daemon.
Help Displays this help.

Copyright IBM Corporation 1999, 2002

*2 kh-AX>X>X>'./usr/share/man/info/en_US/xlf/html/debugger/imagesdaem/A kd.$7zf>_>X>';7./usr/share/man/info/en_US/xlf/html/debugger/images/ngconc.gif/$GIF89aM( 䯱1K.F#5u F/5P+A 0j !':;B[Xmkxao,2I[gϒԐΎz8:2 Ѓ,  ׂ ބքݪ F 2ң#H D#J |EjrXJCA@H02@ ?!50]ɓ)_yЂ$ԑP t\(ЯӧPJJիXjX!D }XhȐAfYm+mڵtБ CJ(}nF t`:K |&!::T(DIP{PԪ *!B*2A0xaȄ&D :a0k5Gд}ĹWHxL|@˟O;" kxJ/$/zf>_>X>';/./usr/share/man/info/en_US/xlf/html/debugger/images/nghpux.gif/$GIF89a1 qZDc!@]>Z?\Mn&Fe#X~,Ps(g4o8d3x>r;Jd,Vo:byH~iw\.v<ȴ,1 @#dihz2G]UT,x1ŻUEɹHE.64c8xTy`K(Vju#1]_ ri8;UmfMWiDd"dFPvRNU?\& {O.@% 6OwOiSL 2SdE8"!; k0$[zf>_>X>';[./usr/share/man/info/en_US/xlf/html/debugger/images/ngia64.gif/$GIF89a3 ?b4Jn=Kl@WvMYH[JcZiUmXog{t}epr|āÉËҘŴ,3 +H !#JHŋppƏ Cj`FP DTȒ&Xs@C2%FSC5-4Ě_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngibm.jpg/$JFIFHH Photoshop 3.08BIMHH8BIM8BIM 8BIM' 8BIMH/fflff/ff2Z5-8BIMp8BIM8BIM8BIM@@8BIM .:WJFIFHH'File written by Adobe Photoshop 4.0Adobed            :"?   3!1AQa"q2B#$Rb34rC%Scs5&DTdE£t6UeuF'Vfv7GWgw5!1AQaq"2B#R3$brCScs4%&5DTdEU6teuFVfv'7GWgw ?I%)$IJItwWNe[Ϋݳs}A]ƻIOG|ޭKt\ſ)SwRˎ/t.}A/̷ʚ\c\?7b{W_30= id͵)IvcV#{#b_gJY([Pzqwzwz_ؒI.@?:@0r_W9]~vX{Cq-68NCJpI$I%)$IO_K[utt|l<{.lh~q!]#; {pyѮ+~d4۳ϪImtՃ_'>mڒ}UX.WvGPQy57yۿ`3/;c:^$n176Uۣ?k6Yz>_>n)^~^Neu?p״i*z?e}f8nE4Kmٷs?]KݍsYCXy^rAbitS=0Q[a +o_=j,lL_=)8 _'ߣo$zO};,?Ya#jʋIu^9ᮻ'/%Y@.}r(mҸ[vRSY$IOI%)$IOiC-.-nS%8lo=}?G>[WWt=&ʩt+UN=WNsηݲoU7'.ܣp;$jpݿO>7c2zKsU"#i~gt*>qߚ͗WW%='DޛC軨X˭i-z_WSc31k]zOXݿFg.n/m,s&n*CݛkMӶ)_:qp}p1^oD2ozF^څ[wjooow=c]os\][^;>Aa F)Łnv4/L znAq`K>XKdt^h Hp_׬V X={l.:{^w*{^g\_MUA<7)?_Su׶A.=E/TBّ]50ߵ?_U>jZf=n[JAv7WӪ_YvHRݮw-wЮxJx4xJx4xJx4xJx4xJx4xJx4xJx4xJ8BIM'File written by Adobe Photoshop 4.0Adobed         'V   s!1AQa"q2B#R3b$r%C4Scs5D'6Tdt& EFVU(eufv7GWgw8HXhx)9IYiy*:JZjzm!1AQa"q2#BRbr3$4CS%cs5DT &6E'dtU7()󄔤euFVfvGWgw8HXhx9IYiy*:JZjz ?*UثWb]v*Uث*UZu e \HII_B}-yhA+%_O/m1T,v}Oqr.7L7ϭrAF_/*KO0WZmJ%][}T2e+C}?g5&dږӵwZ.}?nrHʟZHɊiy&_XLVCbp_Viifͩj^^O;yg˯jfc_3js-GIG'¸*Uث5M. I!j~/U-]Hj[UUEyaEY*-+TnͣXƲj6ѶƠDx${OfW'D{2%w \J}9K_k*-&J5 VKHm F Uc̉PZ~'د|_g^4T$?zo׏_*U0\6ַPO8TVHӞ#I{Zs~\ 7._*SGn-WM3]μ4&q!dR;U7oNII75Rl h>U$濕l[^Ayv,zV4  ?x|i! AW@BB4S |V[eG6 F+ 4z^p")?!yA0foK9dvĕ1➤J1~geOn4=r7 yqQKvH@uB}?ݜ>1諯UMT]*&buoU1W~{IE]=$LUߢm*W_oI6Sw諯UMT]*&blff kt2$Hzf>_>X>';H./usr/share/man/info/en_US/xlf/html/debugger/images/ngref.gif/$GIF89aS(}׽ 䎐+_1K.F F/5P+A 0j !':;*8ikxao[gϒԌ¢8^*\ȰÇ#JHŋhF!G! OܨrcDp$H&^$S!m=!y3Ρ܈)Gnj,X@*3#^ppfk>xSװYv=SbMc0fEՈ'8zW0a \ gL˘3k̹ ; k3$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngtask.gif/$GIF89a/(% +_1K.F#5u F/5P 0j !':;B[Nf?ND>F=403-0$ d3fto_?#jXEA @?3T(2,)lb`"|pǬ freKl8sɳ;3 ke4$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngvconc.gif/$GIF89aM(f3̙f3f3ffffff3f3333f333f3f3̙f3̙̙̙̙f̙3̙ffffff3f3333f333f3̙f3̙̙f3̙f3ff̙ffff3f33̙33f333̙f3ffffff3ffff̙fff3fffffff3ffffffffffff3fff3f3f3f3ff33f3ffffff3f3333f333333̙3f3333333f3333f3f3f3ff3f33f33333333f333333333f333f3̙f3f3ffffff3f3333f333f3,M(@ H*\Ç#JHŋG4hnU75=LbEOX yZg/ZJH*]ʴӧPJJUTRV5׭]AT5PAJݻx2ȷ߿ V8t +T& ̛ e8J`^|b*la)ҥƣSVT2?j}qX+Jt4iXJ@NtQMz5uV VIUU~(ԋ1dmf5Dʐ%L6PF); k4?5$zf>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngvref.gif/$GIF89aS(f3̙f3f3ffffff3f3333f333f3f3̙f3̙̙̙̙f̙3̙ffffff3f3333f333f3̙f3̙̙f3̙f3ff̙ffff3f33̙33f333̙f3ffffff3ffff̙fff3fffffff3ffffffffffff3fff3f3f3f3ff33f3ffffff3f3333f333333̙3f3333333f3333f3f3f3ff3f33f33333333f333333333f333f3̙f3f3ffffff3f3333f333f3,S(@ H*\Ȱ #JHŋ3J+IqbE%O rǐ(MXk:Q ڳ* JѣH*]ʴӧP> OU VZ,Nk|VUFKݻxj˷ߊy7b+;ƙSV0&l1d+g pbŘ?Yex*JM0jԪ3.}:?߼يϰ Nȓ+_μJN}#ھ (wÏW~ymR6#GWUN GUeS.V}=4Y^v!4)NrوdM b (㍑f +. d $Y"h6fL6PF)TVW@;gJ kV/6$0zf>_>X>';0./usr/share/man/info/en_US/xlf/html/debugger/images/ngvtask.gif/$GIF89a/(f3̙f3f3ffffff3f3333f333f3f3̙f3̙̙̙̙f̙3̙ffffff3f3333f333f3̙f3̙̙f3̙f3ff̙ffff3f33̙33f333̙f3ffffff3ffff̙fff3fffffff3ffffffffffff3fff3f3f3f3ff33f3ffffff3f3333f333333̙3f3333333f3333f3f3f3ff3f33f33333333f333333333f333f3̙f3f3ffffff3f3333f333f3,/(@ H $ŰÇ#JȐ5<60*+h Vb$a4&Q*I͛8sɳBr)pgB:赡)Z곪իXRʵ+U1`If1 1n]{㟠<u?*3Tׯ]+^̸ǐ#JrEɘsfϬ ~yh0V3 /_ |gyBV!z^ 'x` =$Ư`^nay*"0GRAd3_Ͼ˧; k7$azf>_>X>';a./usr/share/man/info/en_US/xlf/html/debugger/images/nbdisbp.gif/$GIF89a𠠤!,@&xn0 P#˻ D[է,G"PZ5p|$;333 k08$Lzf>_>X>';L./usr/share/man/info/en_US/xlf/html/debugger/images/nbdisvar.gifm/$GIF89a!,ퟀAge93 Jӗ h:BJ;է kZm9$azf>_>X>';a./usr/share/man/info/en_US/xlf/html/debugger/images/nbenbp.giff/$GIF89a!,@&h^@@%;@Ta^+ C|;333 k:$ezf>_>X>';e./usr/share/man/info/en_US/xlf/html/debugger/images/nbenptr.gif/$GIF87a , @I}"[ xdJ$+jV;3 k;$[zf>_>X>';[./usr/share/man/info/en_US/xlf/html/debugger/images/nbenvar.gif/$GIF89a!,@ (=\6뽧$DT\i}jxChm%;$+j k<$Nzf>_>X>';N./usr/share/man/info/en_US/xlf/html/debugger/images/nbexept.gif/$GIF89a!,@ +ޏDHSujAhF;} kn=$~zf>_>X>';~./usr/share/man/info/en_US/xlf/html/debugger/images/nbhalt.gif/$GIF89a!,@CH*a0tYw~g߈udj CѶ&  CÎTeHb3LCT[rx ; k{>$vzf>_>X>';v./usr/share/man/info/en_US/xlf/html/debugger/images/nbignexc.gifm/$GIF89a!,@;hA \[EE uelh2@ , Yq @'5xU Џe6;T[ k)?$Szf>_>X>';S./usr/share/man/info/en_US/xlf/html/debugger/images/nbplus.giff/$GIF87a C$UI۪Ւ+U>>>IUت𹹹+I$+U$U+UUIdddlllttt|||+$U+IU+UIUUmUUm'''...666FFFMMMUUU]]]+mUIUImUUUUU+UU++$+I+m+U++۪۪mUmUUՒUնUIUIUU$UUUUU+m$$$۪+UU۪U۪IIm$UmUU$IUUU+$ՒmUmU$UնUUImUIUU$+m߲դҿ5ŸqtA2BBRA@!a`b_``@@ABB@@p5A𠠤!, 0H?*LhB :_>X>';q./usr/share/man/info/en_US/xlf/html/debugger/images/nbrun.giff/$GIF89a𠠤!,@6hZC))-i!M5mimgC1hcޞ;+I kjA${f>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/nbrestrt.gifm/$GIF89a𠠤!,@`yμc)w%CUVBj`pUv,H3ˍJTO qN<G(?DZ@(`aC҆R_>X>';o./usr/share/man/info/en_US/xlf/html/debugger/images/nbrunexc.gifm/$GIF89a!,@4X:" Bڈ'@|ijqEUh,sXVz[!2)T$;v kiC$-{f>_>X>';-./usr/share/man/info/en_US/xlf/html/debugger/images/ngwin.gifif/$GIF89a3 AA??>>;;@@==775500..u))o''d##Y`""UW`,,j::uHHZZiiwwƴ,3 @ dihJ~8,O,ϱuֳyX]QAa4~zMNؔ![x,J2FEP) qDstk>@?Wz|z|{I WWPV\h|$]6[A6]#hS| 9I,!; kFD$p{f>_>X>';p./usr/share/man/info/en_US/xlf/html/debugger/images/nbstprtn.gifm/$GIF89a!,@/! YnPr";_I& *jA; kE${f>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ng390.gifif/$GIF89a3 zñl=$i;#sA'k<$vC)M/J-U5X7c?`=kDoGmFtKrJqIrG1|T?`Lo^|l;,3 @$dihJz(E,ϱUVZpsFIXHHh gL=fRy`-zF3TD B. f2r[Hr ;wH$ ueQTTr$1~r Q-̀\!; k(F$3{f>_>X>';3./usr/share/man/info/en_US/xlf/html/debugger/images/ngaix.gifif/$GIF89a3 \] ^!b'/n63p:;vB?yFKROVTZZ`]c`fcidjgmrwɴ"d)%f,+k2B{Hdi,3 @$dihJ~dB,1yMG+$`4Z*M(>fRy`Qm8'{281YzTr1\F :2T$ wZC~27# e7qT qV1=?RI͂\!; <  p  5\v!; k"QG${f>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngcl.gifif/$GIF89a1 \Ny x0DeýޮuͲ,1 @^I8`,OraQ> p0(.ZΠxеYvgP؎5Jtv-ٳ΢5#w.D# ]L;Ry`Q k:H${f>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngclang.gif/$GIF89a3 }WUTQOwItc=SrGyg@bT4gX7XK/MB)K@(NC*VL5mdP{sapUH-bXCÿ,3 @n dihJvh0P,t_>X>';J./usr/share/man/info/en_US/xlf/html/debugger/images/ngcobol.gif/$GIF89a3 ¸ƁV]Xb;T]8wPhsFcnC@G+KS3LS8X^FdjSsxd_\ZXBI,sMCJ-IP1r,3 @Ϡ$dihJ~X L,3uV|H"8,3n!;UՒUն k J${f>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngcpp.giff/$GIF89a3 _]\ZXUKvN{?qcCvh7fV4aQ+VD-YG&O<'P=@cS_|on|%M:3XFNo_{Ľ,3 @ dihJ~X0U,mۇ>5"(Bɀ4(26lج&w,$`x>L{yx dSx$ijR_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngfort.gif/$GIF89a3 VV__]]\\XXb;;]88I,,PPMMsFFnCCJ--G++P11S33S88^FFjSSxddƦrr¸,3 @pH,$1 LA2҉4:mt:V4k$TnCBKFة  T!ioMJBpu Xwu F[RL^`\ !RWeWnpȫM ~L W޷V!!E]!T}\^!BYG$.tdwk̔ !_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/nghp_ux.gif/$GIF89a( Rs{焜BRBZssR{Rcs9RJkޜs9Zk91JBcR{c9ZJsZcsss)B!91Rs,( @@pH,H qDM'Ђ 9X``q3mu$_>X>';8./usr/share/man/info/en_US/xlf/html/debugger/images/ngjava.gif/$GIF89a3 TSHxVRPNFt_>X>';@./usr/share/man/info/en_US/xlf/html/debugger/images/ngos2.gif/$GIF89a3 6D=K@NAOMZZf]i4C7FHVM[Xehtjumxwzx}Ǯ,3 @Š&dihJzH9L,υ ^[x Ùe֨B8pM9<¸>: 'R*"@|(\$7"bāKJkG816?A12@ Yl~|F GF 5 2E d#w3xb$N Sw81>1{| ?  w  8,a-},!; kxO${f>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngos400.gif/$GIF89a3 gZeXXM>8SvrbVl_j]i\C;b@8]2,I[POFsLCn3-J1+G:3SKF^XSjhdx71P,3 @`"dihJv݈4S,ru1mU<_F%XX`:IpNQ&Ry`Z.I-$ kijBFHE\ ,Q$ve|U~Y#eR XSHǩ,!; S k"QP${f>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngpli.giff/$GIF89a3 R_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngrelc.gif/$GIF89a÷{{{fffWWWKKK@@@ @!, dihlp,tmx|pH,Ȥrl:Ш4րX X 11"tqj4pvU}\  l} %#_ $b""n% &" Z###4&~# n  UV"" n$Z"t {3$[(!47&  @&uĊ =$ ?dtr[~R},!@QĂ1.԰Y8p>Ŭc"V`%׊ HA._>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngrelr.gif/$GIF89a÷{{{fffWWWKKK@@@ @!, dihlp,tmx|pH,Ȥrl:Ш4րX X 1n-P-FDŽ0NaN08ۮ*h,   o%|$"_ $b "q$%g# " Z#g2&#q ș e""qU~ wu] (-!s!C ѲG@ dezJ#2 @F\tȓF|Rf MĈFC :r [ȋ *hyl Bw!x"uUg=מzAP}lHQғOKAJo@4 %hp J*b%PUPHȌ4h8<@)DiN;LRM kS${f>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngrelt.gif/$GIF89a÷{{{fffWWWKKK@@@ @!, dihlp,tmx|pH,Ȥrl:Ш4րX X 1KOOda `p8]_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngrpg.gif/$GIF89a1 gNjQsY&f"qYANVGxb}Ε,1 @I8_3< #h2HGqq( Aڣ)V Bjl1y |<)tK)9 >-/vx$ VZs;fg$   kNU${f>_>X>';./usr/share/man/info/en_US/xlf/html/debugger/images/ngsol.gif/$GIF89a3 EM_cjy1=U]tZpAQp+5JWlUiNa:Hc7D^0;R*4H,6KRZj~K^[rXnDUu7ASqx,3 @!dihJ~߸84|,'ͧ3|&$1FFLp ;ZLt;YZ8K~^t2u-%FOf3~3I,lj~V-gf~Fgl1% }ڌl4aklg$=\Kt+ ɬ0 <؛B{_>X>';l./usr/share/man/info/en_US/xlf/html/debugger/images/nbstpovr.gifm/$GIF89a!,@1XEIEB0 kiTqCNpe3l02@,S$;, k_>X>';p./usr/share/man/info/en_US/xlf/html/debugger/images/nbstpdbg.gifm/$GIF89a!,@4H>!8@i_@m&يp\m=YN#$)k6;; kX$q{f>_>X>';q./usr/share/man/info/en_US/xlf/html/debugger/images/nbstpexc.gifm/$GIF89a!,@6hnCH ]\aC -) gmnʐ>[tDңX2;3 @ k`3Y$n{f>_>X>';n./usr/share/man/info/en_US/xlf/html/debugger/images/nbstpint.gifm/$GIF89a!,@3H=!APGGAŝ]2h,/d ޻?@:E#nH; kZ$j{f>_>X>'; j./usr/share/man/info/en_US/xlf/html/debugger/images/ngcacrar.gifm/$GIF89af3̙f3f3ffffff3f3333f333f3f3̙f3̙̙̙̙f̙3̙ffffff3f3333f333f3̙f3̙̙f3̙f3ff̙ffff3f33̙33f333̙f3ffffff3ffff̙fff3fffffff3ffffffffffff3fff3f3f3f3ff33f3ffffff3f3333f333333̙3f3333333f3333f3f3f3ff3f33f33333333f333333333f333f3̙f3f3ffffff3f3333f333f3,@OH`TIX 8 ЊH1*R0ʼnNr!F ,B S%I*V1`0 ;B: k~[$e{f>_>X>'; e./usr/share/man/info/en_US/xlf/html/debugger/images/ngcdwnar.gifm/$GIF89af3̙f3f3ffffff3f3333f333f3f3̙f3̙̙̙̙f̙3̙ffffff3f3333f333f3̙f3̙̙f3̙f3ff̙ffff3f33̙33f333̙f3ffffff3ffff̙fff3fffffff3ffffffffffff3fff3f3f3f3ff33f3ffffff3f3333f333333̙3f3333333f3333f3f3f3ff3f33f33333333f333333333f333f3̙f3f3ffffff3f3333f333f3,@JH?S)TJ#'ċjܨ* ɓ+)4JFU+DX1U*)VUÂ;`0  kd[\$L{f>_>X>'; L./usr/share/man/info/en_US/xlf/html/debugger/images/ngdoc.gifif/$GIF89a f3̙f3f3ffffff3f3333f333f3f3̙f3̙̙̙̙f̙3̙ffffff3f3333f333f3̙f3̙̙f3̙f3ff̙ffff3f33̙33f333̙f3ffffff3ffff̙fff3fffffff3ffffffffffff3fff3f3f3f3ff33f3ffffff3f3333f333333̙3f3333333f3333f3f3f3ff3f33f33333333f333333333f333f3̙f3f3ffffff3f3333f333f3, @1H +<8pB#TH@ !6QG F ȉ#;FU+ k ]$p{f>_>X>'; p./usr/share/man/info/en_US/xlf/html/debugger/images/ngibmcpy.gifm/$GIF89aD4PB]Qi_vn|ʋШն!,D@I8ͻ`(di(*- EHb(;&L$VD$i\XrZ( @w:̶%P BaiخhfJ, @d+: .8@R T{BqU)! @$!} & T  !Ψ $}  m/@G   K5:In,0PX$c7E ^MTzX"ܓX2X@B .1/SO&U^PEՇKo"bJ@n! LhLgN.`4@kV(* ~*H:&@pOg6p'C΋ MQ7 @Mf$S!͙,#i1ҡzCDBnLȓ+_~gUУKY [zHd'h_Ŗ[9P,;SWAO|V s_|a?5y*Y)f i7`$WhJqK