Debugging - step into command

Hello,
I'm using Oracle9i JDeveloper and I feel so inconvenient with step into debugging command.
If I don't have a break point in a method, the step into command doesn't step into the method. Also, why there is no step command?
If I misuse the command, please let me know.
Thanks,
Julie.

Usually the step into command works well. I guess your problem might be the following:
The source code you are stepping into is not included in the sources directory of your project file. In this case you are not able to step into a method from your project, as Jdeveloper does no find the source code. But if you have the source code open in an other project (or even workspace) you can set a breakpoint there and the Debugger will break and show the source code.
So the solution is: Add the source directory of the method you want to step into to the sources directory of your project (or add it to the sources directory of the library if the method comes in in a library).

Similar Messages

Can't step into code in another file

Hi,
When debugging my application in CVI 2013, if I set a breakpoint before a call to a function in another C file, the Step Into command just steps over the function call, even though the source for both is my own and both files are included in the project. If I set a breakpoint in the function in the second file, the application doesn't stop at all, preventing me from seeing what is happening.
I have been able to do this in the past and now it is no longer functioning, what could I have possibly changed?
Thanks
Francois Campbell

I also very recently encountered such a situation.
I don't know why I couldn't remember it before.
CVI was not respecting my breakpoints at all.
It did not even do "break at first step".
Then it turned out that, it was becasue the files were on a network drive, not stored locally in my hard disk.
This also surprised me, because I had all the access rights on that network folder.
The only solution was to copy the project to a local folder, then it started to break appropriately.
I do not think this is expected behavior.
Maybe I should create e new thread for this issue of mine.
All the best,
S. Eren BALCI
www.aselsan.com.tr

Step into and other debugging items are grayed out in ISE debug menu in PS4.0

hi friends
i don't know why things go wrong for me
it's about 3 hours that i am googling & studying documents on how to use Debugger in PS 4.0 ISE
the problem is i open my script in ISE, but when i open debug menu, step over,
step into, step out, stop debugger and many other items on debug menu in ISE are
gray out.
( my script contains about 20 commands)
i need to run my script in line by line method (step into)
but its gray out :-(
i studies many pages regarding powershell debugger but none of the mentioned first enabling debugger ( i think maybe it's off by default)
am i on the right way ? is debugger feature by default off in PS 4.0 ISE? is this what debugging items are gray out?
i looked for a cmdet to enumerate the current state of ISE debugger (on or off) but unfortunately didn't find anything.
another confusion: is it necessary to run the entire script at least one time so that step into feature be available to use?
is yes, that's too bad. i want first examine my script line by line
any help please
thanks in advanced

Unless you have break points inserted and the script actually running, then those options will be greyed out. You need to first insert your break point, and then run the script. Once the code where the break point is going to be executed, the script
will stop there allowing you to step into or out of
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
Don't Retire Technet
Hi clayman
thanks for your answer. useful
after examining many different states finally i discovered the Hidden rule which i didn't find this on the net.
the rule is:
when we want to examine our entire script line by line ( step into our script), we must create a line breakpoint on the
first line of the script &
then press F5, now the items on the debug menu are available such as step into
i wrote this for people who encounter such problem but after lots of search on the internet, they find no document describing this
please mark as answer if this helps you

Sent step by step apdu command to load cap file into javacard

Dear All,
I have log file about process loading cap file into card:
Loading "E:\Sample.cap" ...
T - 80F28000024F00
C - 08A000000003000000019E9000
ISD AID : A000000003000000
T - 80E602001407A000000132000108A00000000300000000000000
C - 009000
T - 80E80000C8C48209B6010011DECAFFED010202010107A000000132000102001F0011001F00000015009A005D0772000A00C8001B03E400020000000002000004001502000107A0000000620001000107A000000062010106005D80810000C20000810200800000FF000100000000810500FF0003000000028000130008010D000002CA02DE02E202E702EE02F602FB0308032B036204AA04C804E8000009040308020705060C0D00010D040308020705060C0D090A0B010707720003201D046D06048D00141C7500120001000300
C - 009000
T - 80E80001C800098F00163D1D8C001A77068D001401770110188C001B7A0220181D8C001C7A03101C026B07017F001D7A7B001D670D8F001F3D1C8C00207F001D7B001D1C8B00127B001D93038903290803290903290A03290B03290D03290E707F1506160E251100FF53290C160C606D1B1604160E41251100FF53290D160D605C191E160E41251100FF531505160E251100FF53435B290F160F6308160F0245290F160F10096D075909017005590801160F10146D27160D160C432910161063081610024529101610100C6D0700
C - 009000
T - 80E80002C8590B01700B161010106F05590A01590E01160E1607A4FF7F1100961609411608430547290F160F630703290F700E160F1100FF6F071100FF290FAD0005160F5B38104B160B41160A43290F160F630703290F700E160F1100FF6F071100FF290FAD0007160F5B387A045603290503290603290704290803290916066008160610096F0F1B1607590701251100FF53290616056008160510096F0E191E590201251100FF532905160610096F2E160510096F281605160643290A160A6308160A0245290A160A10086D00
C - 009000
T - 80E80003C80C16091008160A434129095908017042160610096F0E590801160565355905FF7030160510096F0E590801160665235906FF701E160616056F0E16061605432906032905700C1605160643290503290616071604A4FF5D1609106445290916096307117FFF29091609160847290916091100FF6F071100FF2909AD000316095B387A0430191E0441251100FF5375002D00020081000D0082001B18068901191E0541251100FF537818078901191E054125191E0641258D001778191E0441251100FF53107F6E101800
C - 009000
T - 80E80004C8058901191E0441251100FF537803780320188C001B18110100900B870218110118900B870318110118900B870418110080900B87051808900C8706181D880718AE0788081804048D00138709181006048D00158700181006048D0015870A7A02201D046D06048D0014181D880718AE0788087A011006780110AE0B780210AD090325780310AD090303387A0110AE08780330191E1103008D00183B057805501D1604411100806F040378AE0B6106078D0014AD051D1A1F16048D00193B1604780540AD090303381800
C - 009000
T - 80E80005C803880B1803890C1803890D1803890E1803880F1F60081FAD05926F06058D0014191EAD05031F8D00193B1804880F7A0543032905AE0B046B06088D001419031E41257501300002FFC600110000000D058D00141819031E418C001E290618AF011E41890119AF0125066A06058D00141806881008AF01412904A800E2181916048C001E2905191604257300C800010004000F0031008600A71605AD02926F06058D0014191604AF0141AD020316058D00193B181605890CA8009AAD0603191604AF0141251100FF5300
C - 009000
T - 80E80006C839AD0604191604AF01410441251100FF5339AD0605191604AF01410541251100FF5339AD0606191604AF01410641251100FF5339AD0607191604AF01410741251100FF533970441605AD03926F06058D0014191604AF0141AD030316058D00193B181605890D70231605AD04926F06058D0014191604AF0141AD040316058D00193B181605890E700216041605AF014141290416041606A7FF1DAF0CAF0D41AF0E41610C058D00147006058D00147A0210AE0B046A0BAE0F6007AE10066A06088D00141804880B1800
C - 009000
T - 80E80007C8AE0788087A0440AD09030338AE0B6106078D0014180488111F650A18191E1F8B00217802780846032905032906032907032908AE116106088D0014AE0861040378AE107501DF00010003000918191E8C001E29091FAF011609416C6B04AF01412904705D181916041E418C001E29051916041E41257300400000000400110013004000220031702F1605652B1E160441AF0141290870201605651C1E160441AF0141290670111605650D1E160441AF01412907700216041605AF0141412904160416096FA1AD060700
C - 009000
T - 80E80008C8261100FF53290916091609452909AD0A0316098D00183B16069800B916079800B418191606191607AD03AD04AF0E8C0022AD0007251100FF53AD0606264510084F29091609AD0607266C14AD0903043818AE078808180388111140007816091609452909AD000716098D00183BAD0005251100FF53AD0605264510084F29091609AD0607266C14AD0903043818AE078808180388111140007816091609452909AD000516098D00183BAD0005AD0007AD0A058D0023AD0A05AD0A038D00246214AD0903043818AE0700
C - 009000
T - 80E80009C8880818038811114000781608604918191608AD02AF0C8C0025AD0003251100FF53AD0604264510084F29091609AD0607266C14AD0903043818AE078808180388111140007816091609452909AD000316098D00183BAD0003AD0A05AD0A078D0023AD0A07AD0A038D00246214AD0903043818AE0788081803881111400078AD09030338AE086511183D840804435B88087006058D0014037803430329047031181D160441251100FF5329051A1F160441251100FF532906160516066F040478160516066D0402781600
C - 009000
T - 80E8000AC80404415B29041604056CCE03780462032906042907703D181D160741251100FF531A1F160741251100FF534116064129061504160516074116065B3816061100FF6F070429067005032906160704435B2907160763C37A08000A000200010000000000000A001B0500000000000100000004000000130002002B003300090001000105009A002602001D0602001D0B02001D0002001D0102001D0202001D0302001D0402001D0D02001D0E02001D0502001D0702001D0F02001D0802001D0902001D0A02001D110200
C - 009000
T - 80E8000BC8001D0C02001D10038105020681080C060000330681080D01001D000681100506811006068110020600027A06800000068105000500000006000225010013000600002B03001D0D0600005906000728060006EB060001430900C8008BFF1726E2220E1F1A080808060403020809090F0302090507081D08100704040404060B0A082A04030C03260C030C050609060B060B060B060F0C030C060C030C080D02031205040B030205050A1D08061408330F0F0B0C111A020205080C060602040D09080C060602040D0900
C - 009000
T - 80E8800C5A03030603080602040E0205080C060602040D090303060308060204060506050039090D050508080B04050503030403FFFF06243509090D31180A2C091416081414200E690E130E270615190E19171B711B3B3C0D09233B0D092C00
C - 009000
Completed !
However, I want to run step by step a command to load this cap file into card.
When I sent "80F28000024F00", it is ok. It response: 08A000000003000000019E9000
After that, I sent next command: 80E602001407A000000132000108A00000000300000000000000, it response as 6985.
I don't understand why. Please help me this problem. I must do how to load this cap
Thanks & Best Regards
Kelvin Nguyen

Hi,
You need to delete the old CAP file before loading it again. The problem is that when you call INSTALL FOR LOAD it sees there is already a CAP file with that AID present.
You can try sending a GET STATUS command listing load files to see what is on the card already. You need to delete what is present to be able to load/install again.
Shane

Unable to automatically step into the server. the remote procedure cannot be debugged.

Hi,
I am trying to deploy report using ssis script c# code.I am using the proxy for ReportingService2010 and following code is giving the error.
code:
ReportingService2010 rs = new ReportingService2010();
rs.Credentials = System.Net.CredentialCache.DefaultCredentials;
rs.CreateFolder("MSI Report Demo", "/", null);
Error:
unable to automatically step into the server. the remote procedure cannot be debugged. This usually indicates that debugging has not been enabled on the server.
Please share the idea on it.
Thanks in advance.
-Gautam

just make a trust between to domain and it works .

How to make Form builder 10g step into libraries *.pll while remote debug

How to make Form builder 10g step into libraries *.pll while remote debug. It attaches fine and goes through code located in form but skips pll's. In this case I am interested in debuging CUSTOM.pll. How to step into pll's and is it possible at all?

Is the library in the same directory or within your FORMS_PATH? Note that the runtime setting in the default.env doesn't work for the builder.
cheers

Can't step into subroutines and functions

While debuging in Sun Studio 10 I have problems steping into functions and subroutines. On the step command it just moves down to the next line instead of entering the function or subroutine.
After som testing I found that this only seems to happen when to source files are in different directories. If a place a subrotines source in the same directory as the main program source I am able to step into it.
How do I solve this problem without having to place all source files in the same directory?

You should make sure that the code containing the
subroutines you're trying to step into was compiled with -g.
You should also not move the source code or the object files around
after you compile them. (There are ways to accomodate that, but
let's leave that for later).
A good diagnostic that might help you is the "module" command.
In the dbx command line issue:
(dbx) module file_containing_mysubroutine.f
or
(dbx) module file_containing_mysubroutine.o

Shortcut for step into

Hi,
Does it exist a shortcut(for keyboard!) in form6i to do the "step into" action icon in debug mode?
I'm tired to click on it.
Thanks!
Roxane

You can create a batch file in windows.(prod.bat) each file to connect to each database.
open editor and give sqlplus command with TNS service, and save it as prod.bat , Icon will be saved as "EXECUTABLE" so then by clicking directly you can reach to sqlplus.

Is it possible to step into a CVI dll when called by TestStand?

As the question says: "Is it possible to step into a CVI dll when called by TestStand?"
I am sure Ray F. may have a few tricks up his sleeves... Hope you see this post, Ray!
I compiled a dll using CVI. The dll is called as a test by TestStand.
I do have an "exe" version of the code that I use for debug with a testbed, but the behaviour is not the same as testing the actual target while running TestStand. My goal is to get as close as possible to the real events.
Thanks,
JLV

Sorry about that,
There are two ways as I was saying:
1. You can configure the CVI adapter to Execute Steps in a External Instance of CVI (requires CVI 6.0 or greater).
Only go to Configure->Adapters and select the LabWindows CVI adapter and click on configure and select the corresponding option.
After that set a break point in the step that you want to debug.
An external instance of CVI will be launched where you can set break points and step into the code.
2. From CVI Specifying an external process:
In CVI go to Run Specify External Process and enter the seqEdit.exe as the program name (you have to browse to the location <TestStand>\Bin\SeqEdit.exe).
As the argument you enter the name of the sequence file you want to debug.
Now just select Run->Debug SeqEdit.Exe
The Sequence Edtior will be launched and you can set break point in your CVI code and step into it when the step is executed.
Check the Using LabWindows/CVI with TestStand reference manual for more information.
I hope it helps you to get started.
Regards.

Problem in using Step into and Step Over button in Test Stand user interface development.

hi,
I am developing operator interface in VC++
currently I am facing a problem, I have created Teststand UI button controls dynamically on the dialog, I have assigned the buttons for break, Resume, Break all, Resume all, Step into and step over.
Break, Besume, Break all , Resume all buttons are working fine, the Step into and step over buttons are enabling if I break the execution, but after breaking the execution when I click the Step into button I expect that the current step will be executed and, breaks at the next statement, but when I click the Step Into button It is behaving like resume button, I mean the executioin is going on till the end of the sequence file, it is not breaking at the next statement,
Is my Step into button working the way it is supposed to be?, it is the same case with my step over button alsoI am connecting the TSUI button control to the execution view mgr in the CTestExecDlg:nDisplayExecutionApplicationMgr(LPDISPATCH exec, ExecutionDisplayReasons reason)
message funciton , and nothing I am doing nothing else, this is my code statement how I am connecting the button to the execution view manager.
mExecutionTab.m_pControlPtrArray[0].mExecutionViewMgr->ConnectCommand(mExecutionTab.MiscControls.m_StepInto,CommandKind_StepInto,0,CommandConnection_NoOptions);
mExecutionTab.m_pControlPtrArray[0].mExecutionViewMgr->ConnectCommand(mExecutionTab.MiscControls.m_StepOver,CommandKind_StepOver,0,CommandConnection_NoOptions);
Am I missing anything wrong? Can anyone please help me out.

Al B,
I'm not the original author of this post, but I have encountered a similar problem. My C# application has implemented the following "debug" buttons that work just fine: Run All, Pause, Continue, Stop. But my Step Over button causes the Sequence to run to completion. When the user clicks on the StepOver button, only one line is executed:
this.axExecutionViewMgr.Execution.StepOver();
but it behaves like its calling
this.axExecutionViewMgr.ResumeExecution();
Can you offer any insight into this issue?

Stepping into Java Beans from JSP

I am trying to figure out how to step into the Java Source code for my beans that are used in my JSP pages. I need to be able to debug them by stepping into them, using break points, etc.
I have Nitro installed and a sample JSP page with the import to my test Java Bean class. What I did was create two projects in my work space. One as a Web project application and one as a Java project. I referenced and opened both projects. Everything compiles fine and the syntax is correct.
The problem is I can not make the link for importing the class.
I get this error: Class com.BrianTest.MyBean not found in import com.BrianTest.MyBean
Anyone got a clue or a good example? I did try and add the class path and I tried to put it in a Jar file and attach the source to the Jar, but same problem.
Thanks :?

Stepping into jsp:useBean is not possible, but you can step-into jsp getter & setter tag.
Since you are using java bean from a dependent project you need to configure your server with DevLoader.
And currently only Tomcat server can be configured with Sysdeo Devloader to handle this situation
Download Sysdeo DevLoader for Tomcat from http://www.sysdeo.com/eclipse/tomcatPlugin.html
NOTE: If the project is self sufficient and not dependent on other projects/locations for classess/libraries then NitroX picks up all the libraries & classes present within default WEB-INF/lib & WEB-INF/classes respectively. And in this case you need not modify server configuration.
Sysdeo DevLoader is to allow your web project to use libraries/classes from dependent projects. All you need to do is extract DevLoader.zip present within tomcatPluginV3.zip inside your Tomcat/server/classes folder.
For more information about DevLoader please refer to http://www.sysdeo.com/eclipse/readmeDevLoader.html
This will solve your problem and you should be able to run/debug your application. And most important make sure you have the correct NitroX build that supports Sysdeo DevLoader, refer http://www.m7.com/whatsnew.htm document against your build id (Help > About NitroX > NitroX Icon)

Why is timing different when subvi is called vs. stepped into?

I have a subvi that is called from within a larger vi. This subvi uses a sequence of wait(ms) vis and custom white-noise generator vis to create a sequence of sounds outputted to headphones. The timing of the sequence is very reliable when the subvi is either run directly or if I step-into it from the calling vi. However, when labview calls the subvi as part of the larger routine, the sequence is off.
It's confusing because I'd expect the same behavior regardless of step-into or running it from the calling vi. Any help will be much apprecitated.

What do you mean by step into? Is that during the debug phase?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Step into step over step out disabled while running

Hello all,
Step into, Step over and Step out are getting disabled whenever I run the sequence. Also Run Button is getting disabled after the execution breaks at break point.
Its very difficult to debug the code because of these isssues.
Is that anything to do with custom process model ? I use a third party process model. But in other PCs which are also using the same process model dont have these issues.

Hey sridar,
Does this happen with a simple sequence file? For example, if you create a new sequence file with only a Message Popup step, set a breakpoint, and then try to debug, does it work properly or do you have the debugging buttons grayed out in this case too?
This is most likely happening because your sequence has multiple threads and not all of the threads are being suspended when you hit the breakpoint. For example, if you have a LabVIEW VI executing in a different thread when the breakpoint is hit, you will not be able to debug unless the LabVIEW thread suspends. Here is a KnowledgeBase article describing this case: http://digital.ni.com/public.nsf/allkb/46D1E157756C37E686256CED0075E156?OpenDocument
It is possible that it is being caused by the process model, but I'd start by trying a very simple sequence file. If that works properly, we know it's something in your larger sequence file. If the simple file also does not allow debugging, we might look into the process model for the issue.
Let us know if you have any further questions!
Daniel E.
TestStand Product Support Engineer
National Instruments

Can't step into CVI step that calls LabVIEW DLL?

Windows 2000 SP1
TestStand 2.01f
LabWindows CVI 6.0
LabVIEW 6.1 Runtime
We have a framework based on TestStand and CVI. A customer has supplied us
with a DLL written in LabVIEW 6.1 and packaged with the Application Builder
that we need to call from a CVI test library DLL. They say they can't
supply us with a non-LabVIEW implementation. We installed the LabVIEW 6.1
run-time. We added code to the CVI test library to dynamically load and
unload the LabVIEW DLL using LoadLibrary and FreeLibrary. LoadLibrary is
called in a function in the MainSequence Startup step group, FreeLibrary is
called in a function in the MainSequence Cleanup step group.
Things run as expected when the CVI DLL is built as Release or Debug and the
CVI
adapter is configured to run in-process.
However, if we try to debug CVI DLL by building it as Debug and configuring
the CVI adapter to run in an external instance of CVI, things hang the first
time we try to step into, or run, a CVI test library step that calls one of
the functions in the LabVIEW DLL. On the Applications tab in Task Manager,
the item named LabVIEW is marked as 'Not Responding'. The only way to
recover is to kill the LabVIEW process, which takes down CVI and TestStand
with it. If none of the LabVIEW DLL functions are called, no problems are
seen (no hang).
I assume the problem has something to do with the library getting mapped to
the wrong process space (TestStand v. the external CVI instance). Is there
any way to solve this problem? Any ideas or suggestions would be
appreciated.
Joe

> Out of curiousity, what happens if you attempt to debug your DLL from
> CVI? For example, configure TestStand to run its steps 'inProcess'...
> but then close the TestStand application and in CVI, configure it so
> that the Specified External Process dialog points to TestStand's
> SeqEdit.exe (CVI launches TestStand when debugging the project). Once
> TestStand is running, run your test and set your break points as
> usual, you should be able to step into the CVI code if nothing else.
> If not, I would be interested in hearing what problems you encounter.
When 'debugging' SeqEdit from CVI, we experienced no lock up.
Thanks for this suggestion. Debugging from CVI is a workaround for now,
though not highly desirable as it is reverse from normal debug proc
edure
(user can't step into CVI from TestStand). Still would like to know if
'normal' debugging of this problem is possible.
> The nice thing about debugging directly from Labwindows/CVI while
> TestStand runs 'inprocess' is that you can avoid some library linking
> errors, which may be the source of the troubles you are seeing.
The problem appears to be general to LabVIEW DLLs called from an external
instance of CVI under TestStand. We were able to reproduce the problem with
a simple LabVIEW VI compiled to a DLL, then called from a simple CVI DLL
under TestStand. We will package up some sample code and submit it to NI
tonight or tomorrow.
Thanks for you help.
Joe

A breakpoint problem (step into and step over makes differences)

Hi All, I have a subvi to implement read data and return it to display on front panel. Right now it is not working well on display. But when I set the breakpoint to debug, I found the step into the sub vi can make everything work, but if step over this block, it will be the same as the normal operation. Could anyone advise why this differences happend? Thank you very much!
Attachments:
breakpoint.PNG ‏49 KB

It's hard to tell, but you might have a race condition. Where is the VISA Resouce coming out of inside of the Diagram Disable Structure? If it is connected to the property node, then you have a race condition. Please attach a snippet or the actual VI to make debugging a little easier.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Debugging - step into command

Similar Messages

Maybe you are looking for