Access violation when XDR decoding a custom object

NEW
Unassigned

Status

()

Core
JavaScript Engine
8 years ago
4 years ago

People

(Reporter: Franck, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

1.94 KB, text/plain
Details
1.03 KB, text/plain
Details
(Reporter)

Description

8 years ago
In js_XDRObject(), you try to call js_GetClassPrototype with a NULL JSClass argument (in  xdr->mode != JSXDR_ENCODE  case).
This leads to an "Access violation reading location 0x00000000" in js_FindClassObject() on the following line (jsobj.cpp:3848):
  JSAtom *atom = js_Atomize(cx, clasp->name, strlen(clasp->name), 0);
(Reporter)

Comment 1

8 years ago
Created attachment 448756 [details]
testcase
(Reporter)

Comment 2

8 years ago
Created attachment 448757 [details]
stacktrace
(Reporter)

Comment 3

8 years ago
The bug is not present prior tracemonkey-e643badaabc2 (2010.02.05)
(I made a terrible mistake when exposing XDR API such that it could be called in such ways. Apologies to all involved.)
(Assignee)

Updated

4 years ago
Assignee: general → nobody
You need to log in before you can comment on or make changes to this bug.