From 49a0946e8f119a809f39a39810f8cf82b3f5f2a9 Mon Sep 17 00:00:00 2001 From: Sami Vaarala Date: Wed, 4 Sep 2013 00:34:19 +0300 Subject: [PATCH] ditz issue update --- ...94fda22e5d7974ec381378e799cfdefd7b680.yaml | 21 ++++++++ ...4e283b06d50a65c5f7db22a6393e9e47f4438.yaml | 28 +++++++++++ ...281b62690fe31b0f46be685d7ffe47efb05da.yaml | 18 +++++++ ...a7af8c503a9b25f3e0fec0ae887ef11b7f80f.yaml | 22 ++++++++ ...53e2cd14fdb7052499f4e98746441735ed192.yaml | 6 ++- ...e2709818e510a45e64eacf68326be3e7542a2.yaml | 50 +++++++++++++++++++ ...c6688d5b86d9d2403b286d0dc00f44fad5f7b.yaml | 6 ++- ...68f7b545aa072dc250ade23d1d6dcdb42fba7.yaml | 8 ++- ...bab8af11e60088d2310751c8ac63a46a4c819.yaml | 6 ++- ...cb991207e793c61faa230041bc88e2277fd95.yaml | 18 +++++++ ...e0eae173ddc2e9e4030384418f63b690039df.yaml | 18 +++++++ ...86694c1b7d053ed406c60110eef0a22a2b487.yaml | 8 ++- ...923b08f28b40cd3e7c2bc6b3e59cf2ad8656a.yaml | 22 ++++++++ ...d709f9971594e3bdf4800f3d1faee46016d9a.yaml | 6 ++- 14 files changed, 229 insertions(+), 8 deletions(-) create mode 100644 bugs/issue-1a994fda22e5d7974ec381378e799cfdefd7b680.yaml create mode 100644 bugs/issue-1f04e283b06d50a65c5f7db22a6393e9e47f4438.yaml create mode 100644 bugs/issue-306281b62690fe31b0f46be685d7ffe47efb05da.yaml create mode 100644 bugs/issue-3dea7af8c503a9b25f3e0fec0ae887ef11b7f80f.yaml create mode 100644 bugs/issue-729e2709818e510a45e64eacf68326be3e7542a2.yaml create mode 100644 bugs/issue-c5ecb991207e793c61faa230041bc88e2277fd95.yaml create mode 100644 bugs/issue-d5ce0eae173ddc2e9e4030384418f63b690039df.yaml create mode 100644 bugs/issue-ec8923b08f28b40cd3e7c2bc6b3e59cf2ad8656a.yaml diff --git a/bugs/issue-1a994fda22e5d7974ec381378e799cfdefd7b680.yaml b/bugs/issue-1a994fda22e5d7974ec381378e799cfdefd7b680.yaml new file mode 100644 index 00000000..0a27f33a --- /dev/null +++ b/bugs/issue-1a994fda22e5d7974ec381378e799cfdefd7b680.yaml @@ -0,0 +1,21 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: uclibc math library may be missing fmin(), fmax(), round() +desc: |- + Perhaps related? + + http://comments.gmane.org/gmane.comp.lib.uclibc.general/14630 +type: :task +component: duk +release: v0.7 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-08-31 22:53:04.631136 Z +references: [] + +id: 1a994fda22e5d7974ec381378e799cfdefd7b680 +log_events: +- - 2013-08-31 22:53:04.804116 Z + - sva + - created + - "" diff --git a/bugs/issue-1f04e283b06d50a65c5f7db22a6393e9e47f4438.yaml b/bugs/issue-1f04e283b06d50a65c5f7db22a6393e9e47f4438.yaml new file mode 100644 index 00000000..2e8526a2 --- /dev/null +++ b/bugs/issue-1f04e283b06d50a65c5f7db22a6393e9e47f4438.yaml @@ -0,0 +1,28 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: clean up value stack reserve + extra handling +desc: |- + Currently there are only internal constants for value stack reservation. + The duktape.h header should expose at least the reserve that a user can + expect to have upon function entry. + + Also, currently on entry to a Duktape/C function only DUK_VALSTACK_INTERNAL_EXTRA + value stack reserve is automatically allocated. If this constant is really + for internal use only, there is actually no user reservation by default. + This should be fixed by adding the user reserve to the value stack check + at least when entering a Duktape/C function (this isn't necessary for + Ecmascript functions). +type: :task +component: duk +release: v0.7 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-08-23 23:17:56.338437 Z +references: [] + +id: 1f04e283b06d50a65c5f7db22a6393e9e47f4438 +log_events: +- - 2013-08-23 23:17:56.511375 Z + - sva + - created + - "" diff --git a/bugs/issue-306281b62690fe31b0f46be685d7ffe47efb05da.yaml b/bugs/issue-306281b62690fe31b0f46be685d7ffe47efb05da.yaml new file mode 100644 index 00000000..f2030314 --- /dev/null +++ b/bugs/issue-306281b62690fe31b0f46be685d7ffe47efb05da.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: add an API primitive to get a heap ptr for debugging? +desc: Something like duk_get_voidptr(). +type: :task +component: duk +release: v0.7 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-08-27 21:16:46.442040 Z +references: [] + +id: 306281b62690fe31b0f46be685d7ffe47efb05da +log_events: +- - 2013-08-27 21:16:46.622933 Z + - sva + - created + - "" diff --git a/bugs/issue-3dea7af8c503a9b25f3e0fec0ae887ef11b7f80f.yaml b/bugs/issue-3dea7af8c503a9b25f3e0fec0ae887ef11b7f80f.yaml new file mode 100644 index 00000000..1010db3e --- /dev/null +++ b/bugs/issue-3dea7af8c503a9b25f3e0fec0ae887ef11b7f80f.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: DUK_PROFILE autodetection should choose 64-bit profile if packed tval not possible +desc: "" +type: :task +component: duk +release: v0.6 +reporter: sva +status: :closed +disposition: :fixed +creation_time: 2013-08-28 20:19:18.786432 Z +references: [] + +id: 3dea7af8c503a9b25f3e0fec0ae887ef11b7f80f +log_events: +- - 2013-08-28 20:19:18.974048 Z + - sva + - created + - "" +- - 2013-08-28 20:28:49.871763 Z + - sva + - closed with disposition fixed + - "" diff --git a/bugs/issue-52e53e2cd14fdb7052499f4e98746441735ed192.yaml b/bugs/issue-52e53e2cd14fdb7052499f4e98746441735ed192.yaml index 837a3728..99f86774 100644 --- a/bugs/issue-52e53e2cd14fdb7052499f4e98746441735ed192.yaml +++ b/bugs/issue-52e53e2cd14fdb7052499f4e98746441735ed192.yaml @@ -3,7 +3,7 @@ title: fix behavior of duk_push_string() and duk_push_lstring() for NULL arg desc: "" type: :task component: duk -release: v0.6 +release: v0.7 reporter: sva status: :unstarted disposition: @@ -16,3 +16,7 @@ log_events: - sva - created - "" +- - 2013-08-27 20:39:43.458282 Z + - sva + - assigned to release v0.7 from v0.6 + - "" diff --git a/bugs/issue-729e2709818e510a45e64eacf68326be3e7542a2.yaml b/bugs/issue-729e2709818e510a45e64eacf68326be3e7542a2.yaml new file mode 100644 index 00000000..09aa0d61 --- /dev/null +++ b/bugs/issue-729e2709818e510a45e64eacf68326be3e7542a2.yaml @@ -0,0 +1,50 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: clean up execution error (e.g. duk_pcall) return codes +desc: |- + Separate between "error from call" and "error setting up call"? + + If this is distinguished in the return code of the call, all call sites + will have to deal with it. + + One approach is to push an error on the stack even in "error setting + up call" case, but allow the caller to detect the case by inspecting + the error object. For instance, make the error object an instance of + a special error like APIError and add an API call to detect error type, + like:: + + if (duk_get_error_code(ctx, -1) == DUK_ERR_API_ERROR) { + ... + } + + What to do if the input arguments and stack are incompatible, and + return stack semantics cannot be met? For instance, if there are + not enough arguments on the value stack to match a "nargs" parameter, + we can't pop off enough arguments. + + Options include: + + 1. Disregard these as programmer errors and call the fatal handler. + + 2. Throw an ordinary error. If the duk_pcall/duk_safe_call was called + from a context without error catching, the error becomes fatal + anyway. But this way, there is a chance that an outer error handler + will catch the error. + + 3. Return a special error code indicating that the stack is in an + inconsistent (unexpected) state. All call sites would then need + to take this into account. +type: :task +component: duk +release: v0.7 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-08-27 21:15:20.899635 Z +references: [] + +id: 729e2709818e510a45e64eacf68326be3e7542a2 +log_events: +- - 2013-08-27 21:15:21.072680 Z + - sva + - created + - "" diff --git a/bugs/issue-7a8c6688d5b86d9d2403b286d0dc00f44fad5f7b.yaml b/bugs/issue-7a8c6688d5b86d9d2403b286d0dc00f44fad5f7b.yaml index 65865cb9..88af80d0 100644 --- a/bugs/issue-7a8c6688d5b86d9d2403b286d0dc00f44fad5f7b.yaml +++ b/bugs/issue-7a8c6688d5b86d9d2403b286d0dc00f44fad5f7b.yaml @@ -9,7 +9,7 @@ desc: |- This applies to both buffers and strings. type: :bugfix component: duk -release: v0.6 +release: v0.7 reporter: sva status: :unstarted disposition: @@ -34,3 +34,7 @@ log_events: which is less than the duk_u32 range (we don't support strings longer than 2**32 anyway). Another alternative is to change the internal string helpers to use a size_t. +- - 2013-08-27 20:40:01.277065 Z + - sva + - assigned to release v0.7 from v0.6 + - "" diff --git a/bugs/issue-80c68f7b545aa072dc250ade23d1d6dcdb42fba7.yaml b/bugs/issue-80c68f7b545aa072dc250ade23d1d6dcdb42fba7.yaml index 548ea44c..87ca9341 100644 --- a/bugs/issue-80c68f7b545aa072dc250ade23d1d6dcdb42fba7.yaml +++ b/bugs/issue-80c68f7b545aa072dc250ade23d1d6dcdb42fba7.yaml @@ -5,8 +5,8 @@ type: :task component: duk release: v0.6 reporter: sva -status: :unstarted -disposition: +status: :closed +disposition: :fixed creation_time: 2013-06-20 22:30:21.925600 Z references: [] @@ -16,3 +16,7 @@ log_events: - sva - created - "" +- - 2013-08-28 21:02:51.705994 Z + - sva + - closed with disposition fixed + - "" diff --git a/bugs/issue-8d3bab8af11e60088d2310751c8ac63a46a4c819.yaml b/bugs/issue-8d3bab8af11e60088d2310751c8ac63a46a4c819.yaml index 0bd99764..e9154075 100644 --- a/bugs/issue-8d3bab8af11e60088d2310751c8ac63a46a4c819.yaml +++ b/bugs/issue-8d3bab8af11e60088d2310751c8ac63a46a4c819.yaml @@ -15,7 +15,7 @@ desc: |- certain limit. type: :task component: duk -release: v0.6 +release: v0.7 reporter: sva status: :unstarted disposition: @@ -28,3 +28,7 @@ log_events: - sva - created - "" +- - 2013-08-27 20:39:36.194908 Z + - sva + - assigned to release v0.7 from v0.6 + - "" diff --git a/bugs/issue-c5ecb991207e793c61faa230041bc88e2277fd95.yaml b/bugs/issue-c5ecb991207e793c61faa230041bc88e2277fd95.yaml new file mode 100644 index 00000000..e86e0169 --- /dev/null +++ b/bugs/issue-c5ecb991207e793c61faa230041bc88e2277fd95.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: initial duktape.org website +desc: "" +type: :task +component: duk +release: v0.6 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-08-27 20:44:33.391376 Z +references: [] + +id: c5ecb991207e793c61faa230041bc88e2277fd95 +log_events: +- - 2013-08-27 20:44:33.548481 Z + - sva + - created + - "" diff --git a/bugs/issue-d5ce0eae173ddc2e9e4030384418f63b690039df.yaml b/bugs/issue-d5ce0eae173ddc2e9e4030384418f63b690039df.yaml new file mode 100644 index 00000000..8e39e573 --- /dev/null +++ b/bugs/issue-d5ce0eae173ddc2e9e4030384418f63b690039df.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: provide an API primitive for garbage collection +desc: "" +type: :task +component: duk +release: v0.7 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-08-27 22:18:20.410420 Z +references: [] + +id: d5ce0eae173ddc2e9e4030384418f63b690039df +log_events: +- - 2013-08-27 22:18:20.687276 Z + - sva + - created + - "" diff --git a/bugs/issue-eb386694c1b7d053ed406c60110eef0a22a2b487.yaml b/bugs/issue-eb386694c1b7d053ed406c60110eef0a22a2b487.yaml index 3860c007..b60b2170 100644 --- a/bugs/issue-eb386694c1b7d053ed406c60110eef0a22a2b487.yaml +++ b/bugs/issue-eb386694c1b7d053ed406c60110eef0a22a2b487.yaml @@ -5,8 +5,8 @@ type: :task component: duk release: v0.6 reporter: sva -status: :unstarted -disposition: +status: :closed +disposition: :fixed creation_time: 2013-08-18 21:41:53.171295 Z references: [] @@ -16,3 +16,7 @@ log_events: - sva - created - "" +- - 2013-08-27 20:39:16.800705 Z + - sva + - closed with disposition fixed + - "" diff --git a/bugs/issue-ec8923b08f28b40cd3e7c2bc6b3e59cf2ad8656a.yaml b/bugs/issue-ec8923b08f28b40cd3e7c2bc6b3e59cf2ad8656a.yaml new file mode 100644 index 00000000..a191655d --- /dev/null +++ b/bugs/issue-ec8923b08f28b40cd3e7c2bc6b3e59cf2ad8656a.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: where should platform specific headers like time.h be included? +desc: |- + Currently duk_builtin_date.c includes these, based on platform defines. + + However, the headers depend on e.g. _XOPEN_SOURCE being defined, and + that should be defined before any system headers are included. +type: :task +component: duk +release: v0.7 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-08-28 20:45:31.606103 Z +references: [] + +id: ec8923b08f28b40cd3e7c2bc6b3e59cf2ad8656a +log_events: +- - 2013-08-28 20:45:31.795481 Z + - sva + - created + - "" diff --git a/bugs/issue-ed9d709f9971594e3bdf4800f3d1faee46016d9a.yaml b/bugs/issue-ed9d709f9971594e3bdf4800f3d1faee46016d9a.yaml index 73d3ea21..316425b7 100644 --- a/bugs/issue-ed9d709f9971594e3bdf4800f3d1faee46016d9a.yaml +++ b/bugs/issue-ed9d709f9971594e3bdf4800f3d1faee46016d9a.yaml @@ -3,7 +3,7 @@ title: memory not zeroed correctly by duk_hbuffer_resize desc: Causes API testcase test-resize-buffer.c to valgrind gripe. type: :bugfix component: duk -release: v0.6 +release: v0.7 reporter: sva status: :unstarted disposition: @@ -16,3 +16,7 @@ log_events: - sva - created - "" +- - 2013-08-27 20:39:48.803941 Z + - sva + - assigned to release v0.7 from v0.6 + - ""