| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Reviewed-By: Trevor Norris <trevnorris@gmail.com>
PR-URL: https://github.com/joyent/node/pull/8476
|
| |
|
|
| |
Reviewed-by: Trevor Norris <trev.norris@gmail.com>
|
| |
|
|
|
|
|
| |
It wasn't doing anything, and actually due to
3ae0b17c76f693dd2e68a46f78c7dc7f595b33c6, it was causing
the readline `prompt()` function to be overwritten
which throws an error in the REPL shortly after.
|
| |\
| |
| |
| |
| | |
Conflicts:
src/node_zlib.cc
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The reason this wasn't working was because after restart, when restoring
breakpoints the scripts wasn't loaded, so the breakpoint.script was
undefined. As a fix I added another check to use breakpoint.scriptReq
instead of breakpoint.script, which is the same except when the
breakpoint is a function.
fixes #7027
|
| | |
| |
| |
| | |
Client's property `currentSource` has no use throughout the project.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We now wait to connect to the debuggee until we know that
its error stream has data, to ensure that the output message
"connecting..... ok" appears after "Debugger listening on port xyz"
I also increased the test timeout to let the more complex
tests finish in time on Windows
This change fixes the following unit tests on Windows:
test-debugger-repl.js
test-debugger-repl-term.js
test-debugger-repl-utf8.js
test-debugger-repl-restart.js
|
| |\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
deps/uv/ChangeLog
deps/uv/include/uv-darwin.h
deps/uv/src/unix/fsevents.c
deps/uv/src/unix/process.c
deps/uv/src/version.c
doc/api/addons.markdown
doc/api/cluster.markdown
doc/api/http.markdown
lib/http.js
lib/tls.js
src/node_crypto.cc
src/node_http_parser.cc
src/node_version.h
src/pipe_wrap.cc
src/v8abbr.h
src/v8ustack.d
test/simple/test-http-pipeline-flood.js
|
| | |
| |
| |
| | |
setBreakpoint() cause error when unnamed script is loaded
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When developer calls setBreakpoint with an unknown script name,
we convert the script name into regular expression matching all
paths ending with given name (name can be a relative path too).
To create such breakpoint in V8, we use type `scriptRegEx`
instead of `scriptId` for `setbreakpoint` request.
To restore such breakpoint, we save the original script name
send by the user. We use this original name to set (restore)
breakpoint in the new child process.
This is a back-port of commit 5db936d from the master branch.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixed a bug in debugger repl where `restart` command did not work
when a custom debug port was specified via command-line option
--port={number}.
File test/simple/helper-debugger-repl.js was extracted
from test/simple/test-debugger-repl.js
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Regression introduced by commit 9ef9a9d.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
explictly => explicitly
accesss => access
througput => throughput
epxression => expression
communiction => communication
becuase => because
repersent => represent
condonitions => conditions
decompresion => decompression
intentially => intentionally
eventes => events
listning => listening
resicved => received
becuase => because
fundimental => fundamental
colapse => collapse
privlages => privileges
sufficently => sufficiently
hapepns => happens
expliclitly => explicitly
thier => their
shold => should
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Increases the grep factor. Makes it easier to harmonize type checks
across the code base.
|
| | |
| |
| |
| |
| | |
Fix a bug in setBreakpoint() where not all regex characters are escaped
when constructing scriptRegEx for V8.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When developer calls setBreakpoint with an unknown script name,
we convert the script name into regular expression matching all
paths ending with given name (name can be a relative path too).
To create such breakpoint in V8, we use type `scriptRegEx`
instead of `scriptId` for `setbreakpoint` request.
To restore such breakpoint, we save the original script name
send by the user. We use this original name to set (restore)
breakpoint in the new child process.
|
| | |
| |
| |
| |
| | |
To improve troubleshooting of debugger problems in the future,
the debugger repl now prints the port it is connecting to.
|
| |/
|
|
|
|
|
|
|
| |
Fixed a bug in debugger repl where `restart` command did not work
when a custom debug port was specified via command-line option
--port={number}.
File test/simple/helper-debugger-repl.js was extracted
from test/simple/test-debugger-repl.js
|
| |
|
|
|
|
| |
Otherwise (especially with stdin) you sometimes end up in cases
where the high water mark is zero, and the current buffer is at 0,
and it doesn't need a readable event, so it never calls _read().
|
| | |
|
| |
|
|
|
| |
* debugger: Add NODE_FORCE_READLINE environment variable, handle
`SIGINT`'s sent to process while in this mode.
|
| | |
|
| |
|
|
| |
Both are errors in strict mode.
|
| |
|
|
| |
* fixes #3203
|
| |
|
|
|
|
| |
This should only be minimally used, since the `terminal` value will usually be
what you are expecting. This option is specifically for the case where `terminal`
is false, but you still want colors to be output (or vice-versa).
|
| |
|
|
| |
Fixes test/simple/test-force-repl.js
|
| |
|
|
|
|
|
|
| |
The overall goal here is to make readline more interoperable with other node
Streams like say a net.Socket instance, in "terminal" mode.
See #2922 for all the details.
Closes #2922.
|
| |
|
|
| |
Do not break automatically on exception, fixes #2926
|
| |
|
|
| |
* It was displaying useless warning
|
| |
|
|
|
| |
* When entering repl - clone 'SIGINT' listeners array (instead of using
existing), as it will be spliced in .removeAllListeners() call later.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`process.debug_port` is useful for changing debugger port in runtime,
before starting it (via SIGUSR1).
Using `--port=` argument for debugger repl, tests will run debugger
server on a `common.PORT` (as it usually does for any other servers).
`process._debugEnd()` stops debugger and its server.
* debugger: implemented process._debugEnd(), `node debug --port=5858 app.js`
* test: start debugger repl on common.PORT
* fixes #2613
* fixes #2614
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It was decided that the performance benefits that isolates offer (faster spin-up
times for worker processes, faster inter-worker communication, possibly a lower
memory footprint) are not actual bottlenecks for most people and do not outweigh
the potential stability issues and intrusive changes to the code base that
first-class support for isolates requires.
Hence, this commit backs out all isolates-related changes.
Good bye, isolates. We hardly knew ye.
|
| | |
|
| |
|
|
| |
Fixes #2304
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
* configurable via .prompt()'s preserveCursor argument (false by default)
|
| | |
|
| | |
|
| |
|
|
|
| |
* Updated test
* Use `node debug file`, not `node debug -e "..."` in test
|
| | |
|