Baanboard.com

Go Back   Baanboard.com > Forum > Baan Quick Support: Functional & Technical > Tools Development

User login

Frontpage Sponsor

Main

Poll
For ERP LN feature pack upgrade, what method of install are you using?
Installation Wizard into existing VRC
37%
Installation Wizard into new VRC
39%
Manual into existing VRC
3%
Manual into new VRC
21%
Total votes: 38

Baanboard at LinkedIn


Reference Content

Reply
 
Thread Tools Display Modes
  #1  
Old 15th June 2008, 10:03
smusba smusba is offline
Senior Member
 
Join Date: Apr 2008
Posts: 173
smusba is on a distinguished road
Baan: Baan 1V - DB: Oracle 9i - OS: Windows xp
Smile debugging code
Baan: Baan IVc4
C/S: Client

Dear Gurus,


Please guide me how to debug the scripts in steps.



Last edited by smusba : 15th June 2008 at 10:55.
Reply With Quote
Sponsored Links
  #2  
Old 15th June 2008, 16:03
bdittmar's Avatar
bdittmar bdittmar is offline
Guru
 
Join Date: Apr 2002
Location: Germany, 50.584097,8.544078
Posts: 1,653
bdittmar will become famous soon enough
Baan: 2.2/3.1/4c4/LN6.1 FP6/FP9/HiDox - DB: tbase, ms-sql7, oracle10gV1, 11g - OS: HP-UX, W2K3, SLES
compile in debug mode and trace

Quote:
Originally Posted by smusba View Post
Dear Gurus,


Please guide me how to debug the scripts in steps.


Hello,

compile your source in debugmode and trace the variables you want or
set breakpoints.
Also you can use stop if <variable> = value.

Regards
__________________
//Bernd
Reply With Quote
  #3  
Old 16th June 2008, 08:58
smusba smusba is offline
Senior Member
 
Join Date: Apr 2008
Posts: 173
smusba is on a distinguished road
Baan: Baan 1V - DB: Oracle 9i - OS: Windows xp
Thank for your reply.I had compiled in debug mode what is the next step? Pls help me step by step.
Reply With Quote
  #4  
Old 16th June 2008, 09:17
bdittmar's Avatar
bdittmar bdittmar is offline
Guru
 
Join Date: Apr 2002
Location: Germany, 50.584097,8.544078
Posts: 1,653
bdittmar will become famous soon enough
Baan: 2.2/3.1/4c4/LN6.1 FP6/FP9/HiDox - DB: tbase, ms-sql7, oracle10gV1, 11g - OS: HP-UX, W2K3, SLES
debugger help !

Quote:
Originally Posted by smusba View Post
Thank for your reply.I had compiled in debug mode what is the next step? Pls help me step by step.
Debugger commands

--------------------------------------------------------------------------------

Debugger commands consist of from one to three words; the words can be separated from each other by one or more spaces. The assignment command is an exception. Here the variable and the value to be assigned are separated by a ':=' sign. Most commands require a line number and/or a source name. If no source name is specified, the default is the current source.

When you start the debugger for an object, the source used by the debugger is first searched for by using the directions in the file fdx.x.<pack.comb.> (where x.x is the bshell version), then it is searched for in the $BSE/tmp directory, and finally in the current directory.

Command Action
b [[source] line_number] Set a break point on the current or specified line of the current or specified source. The line is highlighted.

Note that you cannot set break points in included parts in a source. Instead the break point must be set in the included file.

B [source] Display all set break points in the current or specified source.

c [number] Continue (execute the source) up to the next break point. If you specify a number, the debugger skips that number of break points. The executed source lines are not displayed.

C [number] Same as 'c', except that the executed source lines are displayed.

cc Change the size of the command window. This is valid only when application and debugger are in the same window.

cs Change the size of the source window. This is valid only when the application and debugger are in the same window.

d [source line_number] Delete the break point on the specified line number in the source. If you do not specify a line number, the debugger provides the opportunity to interactively delete any break point in the current source file.

D [source] Delete all set break points in the specified or current source.

delete all Delete all traces and stop instructions.

delete number Delete a specified trace or stop instruction.

ds Delete the source window.

dd Generate a dump of the data dictionary.

<expression> Execute the specified expression.

f [noarg|noname][number] Display stack trace (present nesting of functions), with the arguments of the functions. If you specify a number, only that number of nestings is displayed.

noarg only the names of functions are displayed
noname arguments are displayed but not their names

fdebug Show the open tables on the command window.

Fdebug Print the open tables to the spooler.

g [source] line_number Continue program execution at the specified line number (goto).

help (or ?) Start the Help Viewer for debugger options.

instr Generate a symbolic dump of the object.

l Display the full list of program variables.

L Display the list of program variables that have a value, and display their current values. To stop displaying the contents of an array, enter 'n' at the question 'More ?'.

lp Print the output of the 'l' command.

Lp Print the output of the 'L' command.

mem Generate a dump including information about the memory allocated.

p Go to the source line currently being processed (this is useful after the view or seek command). The line is indicated by a greater than (>) sign before the line number.

q Exit the debugger (quit).

return Continue execution until the end of the current function.

s [number] Execute the program step by step, the specified number of instructions at a time (default is 1). During execution, the intermediate source lines are not displayed.

S [number] Similar to 's', except that a function call is executed as a single statement.

slow [number] Reduce the rate of running source code. The maximum number is 100; the minimum (and default) number is 0.

split number Split the command and source window. The specified number is the last line of the command window. This is often used after resizing the Debugger window.

status [trace|stop|number] Display traced variables and/or stop instructions. If you specify a number, only that traced variable or stop instruction is displayed.

stop if <expression> Stop execution when expression is True.

stop in <function> Stop execution when function is entered.

sym Generate a dump of the symbol table.

trap off Disables ‘trap on’. This command is available only when the bshell was started with the -dbgcpu flag.

trap on The debugger stops after execution of every function call. This command is available only when the bshell was started with the -dbgcpu flag.

t variable Trace the specified variable during program execution. The execution of the program stops every time the value of the variable is changed. You cannot trace array variables or common variables.

T variable [value] Same as 't', except that program execution is not stopped when the variable changes. If you specify a value, execution stops when the variable gets that value.

u [variable] Stop tracing the specified variable. If no variable is specified, you can stop tracing each variable interactively.

U Stop tracing all variables currently being traced.

v [source] line_number Display a specified source line in the source window (view). If line_number is greater than the total number of lines, the last line is displayed.

v {+-} number Shift the display to the source line that is number lines before or after the current source line.

/pattern Seek a matching text pattern in the current source and display that line.

[function.]variable [/option] Display the value of a specified variable. If you specify a function, the value of the local variable of that function is displayed. Otherwise, the value of the variable of the current function or the global variable is displayed. If a variable has no value (empty string or zero number), the value is not displayed.

/option can have the following values:

/ Use to display the value of a variable that has the same name as a Debugger command. For example, ‘b/’ displays the value of variable b.

/d Print the flags of the variable and the dimension for arrays.

/D Display the number of bytes allocated in a long or double variable. Display the number of bytes for one element in a string array.

The following options are useful for record buffers and binary data. They display the value of a string variable with its full declared length, regardless of NUL characters.

/x NUL characters are displayed as ‘^@’.

/X Characters with values 0 to 31 are displayed as ‘\x<value in hex>’.

/b All characters are displayed as ‘\x<value in hex>’.


variable := value Assign a value to a variable. The value can be:

a string constant or expression
a numeric constant or expression
a variable name

vi Activate the vi editor for the current source at the current source line. Changing the source has no influence on the source displayed by the debugger in the source window.

width value Change the width of command and source window. You can specify any value in the range 80 to 132.

<Ctrl>D/<Ctrl>U Page down or up in source.

<Esc> Toggle between normal and history mode.

<Arrow up>/ <Arrow down> In history mode, these display previously executed commands on the command line. In normal mode, these move the cursor through the source.
__________________
//Bernd
Reply With Quote
  #5  
Old 16th June 2008, 16:10
smusba smusba is offline
Senior Member
 
Join Date: Apr 2008
Posts: 173
smusba is on a distinguished road
Baan: Baan 1V - DB: Oracle 9i - OS: Windows xp
Thank you for you steps.
but, U have explained me the with the command. You see while debugging u have your window with tabs continue,next, step, return quit etc. I want help from this tab in steps
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Debugging the code after missing the breakpoint george7a Tools Development 4 24th January 2007 11:42
NEW: vbcode CODE extensions patvdv About Baanboard.com 3 13th March 2003 12:19
Debugging DAL code MariaC Tools Development 2 1st August 2002 15:40


All times are GMT +2. The time now is 21:56.


©2001-2017 - Baanboard.com - Baanforums.com