Skip to content
This repository was archived by the owner on Nov 11, 2024. It is now read-only.

Commit 25a7c43

Browse files
committed
Update README.md.
1 parent 61e0e3b commit 25a7c43

File tree

1 file changed

+6
-20
lines changed

1 file changed

+6
-20
lines changed

README.md

+6-20
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@ serialization of the `Mono.Debugger.Client.Configuration` class. This file is
206206
read on startup if it exists.
207207

208208
At startup, SDB will scan the `~/.sdb` directory for plugin assemblies. It will
209-
attempt to load all command and type formatter definitions.
209+
attempt to load all command definitions.
210210

211211
Finally, SDB will read `~/.sdb.rc` and execute any commands (one per line) from
212212
it. This is useful if you prefer to change your settings with commands that you
@@ -233,10 +233,11 @@ while debugging. This may be useful to debug SDB itself.
233233

234234
## Plugins
235235

236-
At the moment, SDB has one extension point which is the `Command` class and the
237-
associated `CommandAttribute` class. A class implementing `Command` that is
238-
tagged with `CommandAttribute` will be instantiated at startup time and put
239-
into the root command list.
236+
At the moment, SDB has one extension point which is the
237+
`Mono.Debugger.Client.Command` class and the related
238+
`Mono.Debugger.Client.CommandAttribute` class. A class implementing `Command`
239+
that is tagged with `CommandAttribute` will be instantiated at startup time and
240+
put into the root command list.
240241

241242
For SDB to find custom commands, they should be compiled into `.dll` assemblies
242243
and put in `~/.sdb` (or some other directory specified in `SDB_PATH`).
@@ -287,18 +288,3 @@ Here's an example of compiling and using a test plugin:
287288

288289
(sdb) mycmd foo bar baz
289290
Hello! I received: foo bar baz
290-
291-
## Issues
292-
293-
* There is no completion for commands - the default completion instead tries to
294-
complete file names which is not very useful most of the time.
295-
* Decompilation is not implemented. The `ICSharpCode.Decompiler` library needs
296-
to be separated from ILSpy for this to be practical.
297-
* The exit code of inferior processes is not shown. There is apparently no way
298-
to get it from `Mono.Debugging`.
299-
* Attach support is not implemented. This requires special support in the
300-
debugging libraries.
301-
* Some Mono versions throw a `NullReferenceException` when SDB shuts down. This
302-
is because of a bug in the finalizer of `System.Timers.Timer` in Mono. This
303-
bug has been fixed and should be available in whatever Mono version comes
304-
after 3.2.5.

0 commit comments

Comments
 (0)