debugger: get/set property not displayed #7139

Open
3y3 opened this Issue Feb 17, 2014 · 2 comments

Projects

None yet

4 participants

@3y3
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}
}
@trevnorris trevnorris added the debugger label Feb 18, 2014
@jasnell
Member
jasnell commented May 28, 2015

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

@bajtos
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 richardlau pushed a commit to ibmruntimes/node that referenced this issue Jun 17, 2016
@evanlucas evanlucas 2016-06-16, Version 6.2.2 (Current)
Notable changes:

* **http**:
  - req.read(0) could cause incoming connections to stall and time out
    under certain conditions. (Fedor Indutny) [#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) [#7149](nodejs/node#7149)
* **npm**: upgrade npm to 3.9.5 (Kat Marchán) [#7139](nodejs/node#7139)

nodejs/node#7323
8c43437
@richardlau richardlau pushed a commit to ibmruntimes/node that referenced this issue Jun 17, 2016
@evanlucas evanlucas 2016-06-17, Version 6.2.2 (Current) Release
Notable changes:

* **http**:
  - req.read(0) could cause incoming connections to stall and time out
    under certain conditions. (Fedor Indutny) [#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) [#7149](nodejs/node#7149)
* **npm**: upgrade npm to 3.9.5 (Kat Marchán) [#7139](nodejs/node#7139)

nodejs/node#7323
091abb3
@gibfahn gibfahn pushed a commit to ibmruntimes/node that referenced this issue Jun 20, 2016
@evanlucas evanlucas 2016-06-17, Version 6.2.2 (Current) Release
Notable changes:

* **http**:
  - req.read(0) could cause incoming connections to stall and time out
    under certain conditions. (Fedor Indutny) [#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) [#7149](nodejs/node#7149)
* **npm**: upgrade npm to 3.9.5 (Kat Marchán) [#7139](nodejs/node#7139)

PR-URL: nodejs/node#7323
e427150
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment