mirror of
https://gitlab.rtems.org/rtems/rtos/rtems.git
synced 2026-09-20 18:35:22 +08:00
2008-02-27 Joel Sherrill <joel.sherrill@oarcorp.com>
* shell/file.t, shell/general.t, shell/memory.t, shell/network.t, shell/rtems.t, shell/shell.texi: Many commands now have real descriptions with examples.
This commit is contained in:
Joel Sherrill
@@ -1,3 +1,9 @@
|
||||
2008-02-27 Joel Sherrill <joel.sherrill@oarcorp.com>
|
||||
|
||||
* shell/file.t, shell/general.t, shell/memory.t, shell/network.t,
|
||||
shell/rtems.t, shell/shell.texi: Many commands now have real
|
||||
descriptions with examples.
|
||||
|
||||
2008-02-27 Joel Sherrill <joel.sherrill@oarcorp.com>
|
||||
|
||||
* shell/file.t, shell/general.t: More commands documented.
|
||||
|
||||
@@ -36,6 +36,11 @@ The RTEMS shell has the following file and directory commands:
|
||||
|
||||
@section Commands
|
||||
|
||||
This section details the File and Directory Commands available. A
|
||||
subsection is dedicated to each of the commands and
|
||||
describes the behavior and configuration of that
|
||||
command as well as providing an example usage.
|
||||
|
||||
@c
|
||||
@c
|
||||
@c
|
||||
|
||||
+65
-53
@@ -15,10 +15,10 @@ The RTEMS shell has the following general commands:
|
||||
@itemize @bullet
|
||||
|
||||
@item @code{alias} - Add alias for an existing command
|
||||
@item @code{date} - Print current date and time
|
||||
@item @code{date} - Print or set current date and time
|
||||
@item @code{id} - show uid gid euid and egid
|
||||
@item @code{tty} - show ttyname
|
||||
@item @code{whoami} - show current user
|
||||
@item @code{whoami} - print effective user id
|
||||
@item @code{logoff} - logoff from the system
|
||||
@item @code{exit} - alias for logoff command
|
||||
|
||||
@@ -26,6 +26,10 @@ The RTEMS shell has the following general commands:
|
||||
|
||||
@section Commands
|
||||
|
||||
This section details the General Commands available. A
|
||||
subsection is dedicated to each of the commands and
|
||||
describes the behavior and configuration of that
|
||||
command as well as providing an example usage.
|
||||
@c
|
||||
@c
|
||||
@c
|
||||
@@ -106,7 +110,7 @@ extern rtems_shell_cmd_t rtems_shell_ALIAS_Command;
|
||||
@c
|
||||
@c
|
||||
@page
|
||||
@subsection date - print current date and time
|
||||
@subsection date - print or set current date and time
|
||||
|
||||
@pgindex date
|
||||
|
||||
@@ -114,11 +118,18 @@ extern rtems_shell_cmd_t rtems_shell_ALIAS_Command;
|
||||
|
||||
@example
|
||||
date
|
||||
date DATE TIME
|
||||
@end example
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command prints the current date.
|
||||
This command operates one of two modes. When invoked with no
|
||||
arguments, it prints the current date and time. When invoked
|
||||
with both @code{date} and @code{time} arguments, it sets the
|
||||
current time.
|
||||
|
||||
The @code{date} is specified in @code{YYYY-MM-DD} format.
|
||||
The @code{time} is specified in @code{HH:MM:SS} format.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
@@ -134,7 +145,10 @@ The following is an example of how to use @code{date}:
|
||||
|
||||
@example
|
||||
SHLL [/] $ date
|
||||
Fri Jan 1 00:00:06 1988
|
||||
Fri Jan 1 00:00:09 1988
|
||||
SHLL [/] $ date 2008-02-29 06:45:32
|
||||
SHLL [/] $ date
|
||||
Fri Feb 29 06:45:35 2008
|
||||
@end example
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
@@ -188,7 +202,9 @@ id
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command prints the user identity. This includes the user id
|
||||
(uid), group id (gid), effective user id (euid), and effective
|
||||
group id (egid).
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
@@ -196,14 +212,26 @@ This command returns 0 on success and non-zero if an error is encountered.
|
||||
|
||||
@subheading NOTES:
|
||||
|
||||
NONE
|
||||
Remember there is only one POSIX process in a single processor RTEMS
|
||||
application. Each thread may have its own user identity and that
|
||||
identity is used by the filesystem to enforce permissions.
|
||||
|
||||
@subheading EXAMPLES:
|
||||
|
||||
The following is an example of how to use @code{id}:
|
||||
The first example of the @code{id} command is from a session logged
|
||||
in as the normal user @code{rtems}:
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
SHLL [/] # id
|
||||
uid=1(rtems),gid=1(rtems),euid=1(rtems),egid=1(rtems)
|
||||
@end example
|
||||
|
||||
The second example of the @code{id} command is from a session logged
|
||||
in as the @code{root} user:
|
||||
|
||||
@example
|
||||
SHLL [/] # id
|
||||
uid=0(root),gid=0(root),euid=0(root),egid=0(root)
|
||||
@end example
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
@@ -257,7 +285,8 @@ tty
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command prints the file name of the device connected
|
||||
to standard input.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
@@ -272,7 +301,8 @@ NONE
|
||||
The following is an example of how to use @code{tty}:
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
SHLL [/] $ tty
|
||||
/dev/console
|
||||
@end example
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
@@ -314,7 +344,7 @@ extern rtems_shell_cmd_t rtems_shell_TTY_Command;
|
||||
@c
|
||||
@c
|
||||
@page
|
||||
@subsection whoami - show current user
|
||||
@subsection whoami - print effective user id
|
||||
|
||||
@pgindex whoami
|
||||
|
||||
@@ -326,11 +356,12 @@ whoami
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command displays the user name associated with the current
|
||||
effective user id.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
This command returns 0 on success and non-zero if an error is encountered.
|
||||
This command always succeeds.
|
||||
|
||||
@subheading NOTES:
|
||||
|
||||
@@ -341,7 +372,8 @@ NONE
|
||||
The following is an example of how to use @code{whoami}:
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
SHLL [/] $ whoami
|
||||
rtems
|
||||
@end example
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
@@ -395,22 +427,26 @@ logoff
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command logs the user out of the shell.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
This command returns 0 on success and non-zero if an error is encountered.
|
||||
This command does not return.
|
||||
|
||||
@subheading NOTES:
|
||||
|
||||
NONE
|
||||
The system behavior when the shell is exited depends upon how the
|
||||
shell was initiated. The typical behavior is that a login prompt
|
||||
will be displayed for the next login attempt or that the connection
|
||||
will be dropped by the RTEMS system.
|
||||
|
||||
@subheading EXAMPLES:
|
||||
|
||||
The following is an example of how to use @code{logoff}:
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
SHLL [/] $ logoff
|
||||
logoff from the system...
|
||||
@end example
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
@@ -452,7 +488,7 @@ extern rtems_shell_cmd_t rtems_shell_LOGOFF_Command;
|
||||
@c
|
||||
@c
|
||||
@page
|
||||
@subsection exit - alias for logoff command
|
||||
@subsection exit - exit the shell
|
||||
|
||||
@pgindex exit
|
||||
|
||||
@@ -464,56 +500,32 @@ exit
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command causes the shell interpreter to @code{exit}.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
This command returns 0 on success and non-zero if an error is encountered.
|
||||
This command does not return.
|
||||
|
||||
@subheading NOTES:
|
||||
|
||||
NONE
|
||||
In contrast to @ref{General Commands logoff - logoff from the system, logoff},
|
||||
this command is built into the shell interpreter loop.
|
||||
|
||||
@subheading EXAMPLES:
|
||||
|
||||
The following is an example of how to use @code{exit}:
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
SHLL [/] $ exit
|
||||
Shell exiting
|
||||
@end example
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
|
||||
@findex CONFIGURE_SHELL_NO_COMMAND_EXIT
|
||||
@findex CONFIGURE_SHELL_COMMAND_EXIT
|
||||
|
||||
This command is included in the default shell command set.
|
||||
When building a custom command set, define
|
||||
@code{CONFIGURE_SHELL_COMMAND_EXIT} to have this
|
||||
command included.
|
||||
|
||||
This command can be excluded from the shell command set by
|
||||
defining @code{CONFIGURE_SHELL_NO_COMMAND_EXIT} when all
|
||||
shell commands have been configured.
|
||||
This command is always present and cannot be disabled.
|
||||
|
||||
@subheading PROGRAMMING INFORMATION:
|
||||
|
||||
@findex rtems_shell_rtems_main_exit
|
||||
|
||||
The @code{exit} is implemented by a C language function
|
||||
which has the following prototype:
|
||||
|
||||
@example
|
||||
int rtems_shell_rtems_main_exit(
|
||||
int argc,
|
||||
char **argv
|
||||
);
|
||||
@end example
|
||||
|
||||
The configuration structure for the @code{exit} has the
|
||||
following prototype:
|
||||
|
||||
@example
|
||||
extern rtems_shell_cmd_t rtems_shell_EXIT_Command;
|
||||
@end example
|
||||
The @code{exit} is implemented directly in the shell interpreter.
|
||||
There is no C routine associated with it.
|
||||
|
||||
|
||||
+164
-36
@@ -25,6 +25,11 @@ The RTEMS shell has the following memory commands:
|
||||
|
||||
@section Commands
|
||||
|
||||
This section details the Memory Commands available. A
|
||||
subsection is dedicated to each of the commands and
|
||||
describes the behavior and configuration of that
|
||||
command as well as providing an example usage.
|
||||
|
||||
@c
|
||||
@c
|
||||
@c
|
||||
@@ -36,28 +41,43 @@ The RTEMS shell has the following memory commands:
|
||||
@subheading SYNOPSYS:
|
||||
|
||||
@example
|
||||
mdump [addr [size]]
|
||||
mdump [address [length]]
|
||||
@end example
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command displays the contents of memory at the @code{address}
|
||||
and @code{length} in bytes specified on the command line.
|
||||
|
||||
When @code{length} is not provided, it defaults to @code{320} which
|
||||
is twenty lines of output with sixteen bytes of output per line.
|
||||
|
||||
When @code{address} is not provided, it defaults to @code{0x00000000}.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
This command returns 0 on success and non-zero if an error is encountered.
|
||||
This command always returns 0 to indicate success.
|
||||
|
||||
@subheading NOTES:
|
||||
|
||||
NONE
|
||||
Dumping memory from a non-existent address may result in an unrecoverable
|
||||
program fault.
|
||||
|
||||
@subheading EXAMPLES:
|
||||
|
||||
The following is an example of how to use @code{mdump}:
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
@end example
|
||||
@smallexample
|
||||
SHLL [/] $ mdump 0x10000 32
|
||||
0x0001000000 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
|
||||
0x0001001000 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
|
||||
SHLL [/] $ mdump 0x02000000 32
|
||||
0x02000000A1 48 00 00 29 00 80 33-81 C5 22 BC A6 10 21 00 .H..)..3.."...!.
|
||||
0x02000010A1 48 00 00 29 00 80 33-81 C5 22 BC A6 10 21 01 .H..)..3.."...!.
|
||||
SHLL [/] $ mdump 0x02001000 32
|
||||
0x0200100003 00 80 00 82 10 60 00-81 98 40 00 83 48 00 00 ......`...@..H..
|
||||
0x0200101084 00 60 01 84 08 A0 07-86 10 20 01 87 28 C0 02 ..`....... ..(..
|
||||
@end smallexample
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
|
||||
@@ -105,28 +125,37 @@ extern rtems_shell_cmd_t rtems_shell_MDUMP_Command;
|
||||
@subheading SYNOPSYS:
|
||||
|
||||
@example
|
||||
wdump [addr [size]]
|
||||
wdump [address [length]]
|
||||
@end example
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command displays the contents of memory at the @code{address}
|
||||
and @code{length} in bytes specified on the command line.
|
||||
|
||||
When @code{length} is not provided, it defaults to @code{320} which
|
||||
is twenty lines of output with sixteen bytes of output per line.
|
||||
|
||||
When @code{address} is not provided, it defaults to @code{0x00000000}.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
This command returns 0 on success and non-zero if an error is encountered.
|
||||
This command always returns 0 to indicate success.
|
||||
|
||||
@subheading NOTES:
|
||||
|
||||
NONE
|
||||
Dumping memory from a non-existent address may result in an unrecoverable
|
||||
program fault.
|
||||
|
||||
@subheading EXAMPLES:
|
||||
|
||||
The following is an example of how to use @code{wdump}:
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
@end example
|
||||
@smallexample
|
||||
SHLL [/] $ wdump 0x02010000 32
|
||||
0x02010000 0201 08D8 0201 08C0-0201 08AC 0201 0874 ...............t
|
||||
0x02010010 0201 0894 0201 0718-0201 0640 0201 0798 ...........@....
|
||||
@end smallexample
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
|
||||
@@ -174,12 +203,14 @@ extern rtems_shell_cmd_t rtems_shell_WDUMP_Command;
|
||||
@subheading SYNOPSYS:
|
||||
|
||||
@example
|
||||
medit addr value [value ...]
|
||||
medit address value1 [value2 ... valueN]
|
||||
@end example
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command is used to modify the contents of the memory starting
|
||||
at @code{address} using the octets specified by the parameters
|
||||
@code{value1} through @code{valueN}.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
@@ -187,15 +218,22 @@ This command returns 0 on success and non-zero if an error is encountered.
|
||||
|
||||
@subheading NOTES:
|
||||
|
||||
NONE
|
||||
Dumping memory from a non-existent address may result in an unrecoverable
|
||||
program fault.
|
||||
|
||||
@subheading EXAMPLES:
|
||||
|
||||
The following is an example of how to use @code{medit}:
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
@end example
|
||||
@smallexample
|
||||
SHLL [/] $ mdump 0x02000000 32
|
||||
0x02000000 A1 48 00 00 29 00 80 33-81 C5 22 BC A6 10 21 00 .H..)..3.."...!.
|
||||
0x02000010 A1 48 00 00 29 00 80 33-81 C5 22 BC A6 10 21 01 .H..)..3.."...!.
|
||||
SHLL [/] $ medit 0x02000000 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09
|
||||
SHLL [/] $ mdump 0x02000000 32
|
||||
0x02000000 01 02 03 04 05 06 07 08-09 00 22 BC A6 10 21 00 .........."...!.
|
||||
0x02000010 A1 48 00 00 29 00 80 33-81 C5 22 BC A6 10 21 01 .H..)..3.."...!.
|
||||
@end smallexample
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
|
||||
@@ -243,12 +281,14 @@ extern rtems_shell_cmd_t rtems_shell_MEDIT_Command;
|
||||
@subheading SYNOPSYS:
|
||||
|
||||
@example
|
||||
mfill addr size value
|
||||
mfill address length value
|
||||
@end example
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command is used to fill the memory starting at @code{address}
|
||||
for the specified @code{length} in octets when the specified at
|
||||
@code{value}.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
@@ -256,15 +296,31 @@ This command returns 0 on success and non-zero if an error is encountered.
|
||||
|
||||
@subheading NOTES:
|
||||
|
||||
NONE
|
||||
Filling a non-existent address range may result in an unrecoverable
|
||||
program fault. Similarly overwriting interrupt vector tables, code
|
||||
space or critical data areas can be fatal as shown in the example.
|
||||
|
||||
@subheading EXAMPLES:
|
||||
|
||||
The following is an example of how to use @code{mfill}:
|
||||
In this example, the address used (@code{0x23d89a0}) as the base
|
||||
address of the filled area is the end of the stack for the
|
||||
Idle thread. This address was determined manually using gdb and
|
||||
is very specific to this application and BSP. The first command
|
||||
in this example is an @code{mdump} to display the initial contents
|
||||
of this memory. We see that the first 8 bytes are 0xA5 which is
|
||||
the pattern used as a guard by the Stack Checker. On
|
||||
the first context switch after the pattern is overwritten
|
||||
by the @code{mfill} command, the Stack Checker detect the pattern
|
||||
has been corrupted and generates a fatal error.
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
@end example
|
||||
@smallexample
|
||||
SHLL [/] $ mdump 0x23d89a0 16
|
||||
0x023D89A0 A5 A5 A5 A5 A5 A5 A5 A5-FE ED F0 0D 0B AD 0D 06 ................
|
||||
SHLL [/] $ mfill 0x23d89a0 13 0x5a
|
||||
SHLL [/] $ BLOWN STACK!!! Offending task(0x23D4418): id=0x09010001; name=0x0203D908
|
||||
stack covers range 0x23D89A0 - 0x23D99AF (4112 bytes)
|
||||
Damaged pattern begins at 0x023D89A8 and is 16 bytes long
|
||||
@end smallexample
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
|
||||
@@ -312,12 +368,14 @@ extern rtems_shell_cmd_t rtems_shell_MFILL_Command;
|
||||
@subheading SYNOPSYS:
|
||||
|
||||
@example
|
||||
mmove dst src size
|
||||
mmove dst src length
|
||||
@end example
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command is used to copy the contents of the memory
|
||||
starting at @code{src} to the memory located at @code{dst}
|
||||
for the specified @code{length} in octets.
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
@@ -331,9 +389,15 @@ NONE
|
||||
|
||||
The following is an example of how to use @code{mmove}:
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
@end example
|
||||
@smallexample
|
||||
SHLL [/] $ mdump 0x023d99a0 16
|
||||
0x023D99A0 A5 A5 A5 A5 A5 A5 A5 A5-A5 A5 A5 A5 A5 A5 A5 A5 ................
|
||||
SHLL [/] $ mdump 0x02000000 16
|
||||
0x02000000 A1 48 00 00 29 00 80 33-81 C5 22 BC A6 10 21 00 .H..)..3.."...!.
|
||||
SHLL [/] $ mmove 0x023d99a0 0x02000000 13
|
||||
SHLL [/] $ mdump 0x023d99a0 16
|
||||
0x023D99A0 A1 48 00 00 29 00 80 33-81 C5 22 BC A6 A5 A5 A5 .H..)..3..".....
|
||||
@end smallexample
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
|
||||
@@ -386,7 +450,40 @@ malloc [info|stats]
|
||||
|
||||
@subheading DESCRIPTION:
|
||||
|
||||
This command XXX
|
||||
This command prints either information or statistics about the
|
||||
C Program Heap used by the @code{malloc} family of calls based upon
|
||||
the value of the first argument passed to the command.
|
||||
|
||||
When the subcommand @code{info} is specified, information on the
|
||||
current state of the C Program Heap is reported. This includes the following
|
||||
information:
|
||||
|
||||
@itemize @bullet
|
||||
@item Number of free blocks
|
||||
@item Largest free block
|
||||
@item Total bytes free
|
||||
@item Number of used blocks
|
||||
@item Largest used block
|
||||
@item Total bytes used
|
||||
@end itemize
|
||||
|
||||
When the subcommand @code{stats} is specified, statistics on the
|
||||
the C Program Heap are reported. Malloc Family Statistics must
|
||||
be enabled for all of the values to be updated. The statistics
|
||||
available includes the following information:
|
||||
|
||||
@itemize @bullet
|
||||
@item
|
||||
@item Currently available memory (in kilobytes)
|
||||
@item Currently allocated memory (in kilobytes)
|
||||
@item Maximum amount of memory ever allocated (in kilobytes)
|
||||
@item Lifetime tally of allocated memory (in kilobytes)
|
||||
@item Lifetime tally of freed memory (in kilobytes)
|
||||
@item Number of calls to @code{malloc}
|
||||
@item Number of calls to @code{free}
|
||||
@item Number of calls to @code{realloc}
|
||||
@item Number of calls to @code{calloc}
|
||||
@end itemize
|
||||
|
||||
@subheading EXIT STATUS:
|
||||
|
||||
@@ -394,16 +491,47 @@ This command returns 0 on success and non-zero if an error is encountered.
|
||||
|
||||
@subheading NOTES:
|
||||
|
||||
NONE
|
||||
@findex CONFIGURE_MALLOC_STATISTICS
|
||||
|
||||
The @code{CONFIGURE_MALLOC_STATISTICS} @code{confdefs.h} constant
|
||||
must be defined when the application is configured for the full
|
||||
set of statistics information to be available.
|
||||
|
||||
@subheading EXAMPLES:
|
||||
|
||||
The following is an example of how to use @code{malloc}:
|
||||
The following is an example of how to use the @code{malloc} command.
|
||||
|
||||
@example
|
||||
EXAMPLE_TBD
|
||||
SHLL [/] $ malloc info
|
||||
Number of free blocks: 3
|
||||
Largest free block: 3626672
|
||||
Total bytes free: 3627768
|
||||
Number of used blocks: 130
|
||||
Largest used block: 1048
|
||||
Total bytes used: 10136
|
||||
SHLL [/] $ malloc stats
|
||||
Malloc statistics
|
||||
avail:3552k allocated:9k (0%) max:10k (0%) lifetime:21k freed:12k
|
||||
Call counts: malloc:203 free:93 realloc:0 calloc:20
|
||||
SHLL [/] $ malloc info
|
||||
Number of free blocks: 3
|
||||
Largest free block: 3626672
|
||||
Total bytes free: 3627768
|
||||
Number of used blocks: 130
|
||||
Largest used block: 1048
|
||||
Total bytes used: 10136
|
||||
SHLL [/] $ malloc stats
|
||||
Malloc statistics
|
||||
avail:3552k allocated:9k (0%) max:10k (0%) lifetime:23k freed:14k
|
||||
Call counts: malloc:205 free:95 realloc:0 calloc:20
|
||||
@end example
|
||||
|
||||
Note that in the above example, the lifetime allocated and free
|
||||
values have increased between the two calls to @code{malloc stats}
|
||||
even though the amount of memory available in the C Program Heap
|
||||
is the same in both the @code{malloc info} invocations. This indicates
|
||||
that memory was allocated and freed as a side-effect of the commands.
|
||||
|
||||
@subheading CONFIGURATION:
|
||||
|
||||
@findex CONFIGURE_SHELL_NO_COMMAND_MALLOC
|
||||
|
||||
@@ -22,6 +22,10 @@ The RTEMS shell has the following network commands:
|
||||
|
||||
@section Commands
|
||||
|
||||
This section details the Network Commands available. A
|
||||
subsection is dedicated to each of the commands and
|
||||
describes the behavior and configuration of that
|
||||
command as well as providing an example usage.
|
||||
@c
|
||||
@c
|
||||
@c
|
||||
|
||||
+248
-67
File diff suppressed because it is too large
Load Diff
@@ -82,7 +82,7 @@ This is the online version of the RTEMS Shell User's Guide.
|
||||
* General Commands::
|
||||
* File and Directory Commands::
|
||||
* Memory Commands::
|
||||
* RTEMS Commands::
|
||||
* RTEMS Specific Commands::
|
||||
* Network Commands::
|
||||
* Function and Variable Index::
|
||||
* Concept Index::
|
||||
|
||||
Reference in New Issue
Block a user