Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-9079

mongo shell crashes - can't handle type: 14 a: "b"

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.4.0
    • Component/s: Shell
    • Labels:
    • Environment:
      linux, ubuntu 12.10
      server: mongodb-10gen 2.4.0,
      shell: 2.4.0

      erlang R15B01
      driver: mongodb-erlang
    • Linux
    • Hide

      erlang:
      > application:start(bson). application:start(mongodb).
      >

      {ok, C}

      = mongo_connection:start_link(

      {localhost, 27017}

      ).
      > mongo:do(safe, master, C, mydb, fun() -> mongo:insert(mycol,

      {a,b}

      ) end).

      mongo shell:
      > use mydb
      > db.mycol.find()

      Show
      erlang: > application:start(bson). application:start(mongodb). > {ok, C} = mongo_connection:start_link( {localhost, 27017} ). > mongo:do(safe, master, C, mydb, fun() -> mongo:insert(mycol, {a,b} ) end). mongo shell: > use mydb > db.mycol.find()

      I've inserted a document

      {a,b}

      (

      {atom(), atom()}

      via erlang.
      When trying to display that document the shell crashes with the following message.

      Fri Mar 22 11:19:57.677 Assertion: 16661:can't handle type: 14 a: "b"
      0x747301 0x7106bb 0x710bfc 0x6ee1dc 0x6f3c3b 0x990843 0x990223 0x9ed1e0 0xee3eb406362
      mongo(_ZN5mongo15printStackTraceERSo+0x21) [0x747301]
      mongo(_ZN5mongo11msgassertedEiPKc+0x9b) [0x7106bb]
      mongo() [0x710bfc]
      mongo(_ZN5mongo7V8Scope16mongoToV8ElementERKNS_11BSONElementEb+0x48c) [0x6ee1dc]
      mongo() [0x6f3c3b]
      mongo(_ZN2v88internal8JSObject35GetPropertyAttributeWithInterceptorEPS1_PNS0_6StringEb+0x453) [0x990843]
      mongo(_ZN2v88internal10JSReceiver32GetPropertyAttributeWithReceiverEPS1_PNS0_6StringE+0xb3) [0x990223]
      mongo(_ZN2v88internal19Runtime_HasPropertyENS0_9ArgumentsEPNS0_7IsolateE+0x70) [0x9ed1e0]
      [0xee3eb406362]
      Fri Mar 22 11:19:57.684 mongo got signal 11 (Segmentation fault), stack trace:

      Fri Mar 22 11:19:57.690 0x747301 0x5dc542 0x7f11cb80e4a0 0x9fe232 0x895046 0x7f371f 0x6f3c58 0x990843 0x990223 0x9ed1e0 0xee3eb406362
      mongo(_ZN5mongo15printStackTraceERSo+0x21) [0x747301]
      mongo(_Z12quitAbruptlyi+0x382) [0x5dc542]
      /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f11cb80e4a0]
      mongo(_ZN2v88internal7Runtime22ForceSetObjectPropertyEPNS0_7IsolateENS0_6HandleINS0_8JSObjectEEENS4_INS0_6ObjectEEES8_18PropertyAttributes+0x302) [0x9fe232]
      mongo(_ZN2v88internal16ForceSetPropertyENS0_6HandleINS0_8JSObjectEEENS1_INS0_6ObjectEEES5_18PropertyAttributes+0x66) [0x895046]
      mongo(_ZN2v86Object8ForceSetENS_6HandleINS_5ValueEEES3_NS_17PropertyAttributeE+0xef) [0x7f371f]
      mongo() [0x6f3c58]
      mongo(_ZN2v88internal8JSObject35GetPropertyAttributeWithInterceptorEPS1_PNS0_6StringEb+0x453) [0x990843]
      mongo(_ZN2v88internal10JSReceiver32GetPropertyAttributeWithReceiverEPS1_PNS0_6StringE+0xb3) [0x990223]
      mongo(_ZN2v88internal19Runtime_HasPropertyENS0_9ArgumentsEPNS0_7IsolateE+0x70) [0x9ed1e0]
      [0xee3eb406362]

      Note: Both drivers mongodb-erlang and php5-mongo can read the document properly.

            Assignee:
            Unassigned Unassigned
            Reporter:
            uuid0 Bjoern Kortuemm
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: