Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

debugger: get/set property not displayed #7139

Closed
3y3 opened this issue Feb 17, 2014 · 2 comments
Closed

debugger: get/set property not displayed #7139

3y3 opened this issue Feb 17, 2014 · 2 comments
Labels

Comments

@3y3
Copy link

3y3 commented Feb 17, 2014

Test for issue

function test(){
  var prop,
      object = {};
  Object.defineProperty(object, 'prop', {
    get: function(){return prop},
    set: function(value){prop = value;}
  });
  debugger;
//REPL > object
//{prop: undefined}
}
@jasnell
Copy link
Member

jasnell commented May 28, 2015

@3y3 ... is this still an issue for you?

@bajtos
Copy link

bajtos commented Jun 22, 2015

@jasnell I can confirm the issue is still present in iojs@2.3.0.

  1. Create file "test.js"
function test(){
  var prop = 'value',
      object = {};
  Object.defineProperty(object, 'prop', {
    get: function(){return prop},
    set: function(value){prop = value;},
    enumerable: true
  });
  debugger;
}
test();
  1. Run node debug test.js
debug> cont
< object { prop: [Getter/Setter] }
< object.prop value
break in test.js:11
  9   console.log('object', object);
 10   console.log('object.prop', object.prop);
>11   debugger;
 12 }
 13
debug> repl
Press Ctrl + C to leave debug repl
> object
{ prop: undefined }
> object.prop
'value'
>

Notice that object.prop is set, but the debugger output for object does not include prop's value.

richardlau pushed a commit to ibmruntimes/node that referenced this issue Jun 17, 2016
Notable changes:

* **http**:
  - req.read(0) could cause incoming connections to stall and time out
    under certain conditions. (Fedor Indutny) [nodejs#7211](nodejs/node#7211)
  - When freeing the socket to be reused in keep-alive Agent wait for
    both prefinish and end events. Otherwise the next request may be
    written before the previous one has finished sending the body, leading
    to a parser errors. (Fedor Indutny) [nodejs#7149](nodejs/node#7149)
* **npm**: upgrade npm to 3.9.5 (Kat Marchán) [nodejs#7139](nodejs/node#7139)

nodejs/node#7323
richardlau pushed a commit to ibmruntimes/node that referenced this issue Jun 17, 2016
Notable changes:

* **http**:
  - req.read(0) could cause incoming connections to stall and time out
    under certain conditions. (Fedor Indutny) [nodejs#7211](nodejs/node#7211)
  - When freeing the socket to be reused in keep-alive Agent wait for
    both prefinish and end events. Otherwise the next request may be
    written before the previous one has finished sending the body, leading
    to a parser errors. (Fedor Indutny) [nodejs#7149](nodejs/node#7149)
* **npm**: upgrade npm to 3.9.5 (Kat Marchán) [nodejs#7139](nodejs/node#7139)

nodejs/node#7323
gibfahn pushed a commit to ibmruntimes/node that referenced this issue Jun 20, 2016
Notable changes:

* **http**:
  - req.read(0) could cause incoming connections to stall and time out
    under certain conditions. (Fedor Indutny) [nodejs#7211](nodejs/node#7211)
  - When freeing the socket to be reused in keep-alive Agent wait for
    both prefinish and end events. Otherwise the next request may be
    written before the previous one has finished sending the body, leading
    to a parser errors. (Fedor Indutny) [nodejs#7149](nodejs/node#7149)
* **npm**: upgrade npm to 3.9.5 (Kat Marchán) [nodejs#7139](nodejs/node#7139)

PR-URL: nodejs/node#7323
@Trott Trott closed this as completed Apr 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants