unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Sunjoong Lee <sunjoong@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org
Subject: Re: crash in guile-sqlite3
Date: Mon, 30 Apr 2012 19:32:43 +0900	[thread overview]
Message-ID: <CAK93xhoMm+A0he-g589C5dtqoK-FeFWDYX2byXErfBvu2pXMuA@mail.gmail.com> (raw)
In-Reply-To: <87zk9tppb7.fsf@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

2012/4/30 Andy Wingo <wingo@pobox.com>
>
> Would you mind sending a pull request on gitorious?  Preferably we could
> add a test case too.
>

 I apologize for my poor english; I'm willing to "send a pull request on
gitorious" but don't know what means that sentence.

Joonas had reported that Segmentation fault crash will be occur
in guile-sqlite3 when you use sqlite-bind with a string; I think he would
suspect it  as sqlite-finalize's problem.

I realized sqlite-bind treats sqlite-transient as a pointer and it would
occur same Segmentation fault when you with bytevector; only numerical
value will work well. That's because sqlite3_bind_blob
and sqlite3_bind_text of libsqlite3 expect it's last argument as a function
pointer or just uint64_t type of 0x00000000 or 0xffffffff; you can use C
function if sqlite-transient be it but you should use 0x00000000 or
0xffffffff if not so, and the meaning of SQLITE_TRANSIENT is it's a
0xffffffff.

Joonas, would you mind sending a pull request on gitorious?

[-- Attachment #2: Type: text/html, Size: 1410 bytes --]

  reply	other threads:[~2012-04-30 10:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27  5:40 crash in guile-sqlite3 Sunjoong Lee
2012-04-27 19:00 ` David Pirotte
2012-04-27 20:08   ` Sunjoong Lee
2012-04-27 22:58     ` David Pirotte
2012-04-27 23:59     ` David Pirotte
2012-04-29  1:58 ` Sunjoong Lee
2012-04-30  9:00   ` Andy Wingo
2012-04-30 10:32     ` Sunjoong Lee [this message]
2012-04-30 10:46       ` Andy Wingo
2012-04-30 12:44         ` Sunjoong Lee
2012-05-01 11:45   ` Joonas Sarajärvi
2012-05-01 15:01     ` Joonas Sarajärvi
2012-05-01 15:05       ` Daniel Krueger
2012-05-01 15:10         ` Daniel Krueger
  -- strict thread matches above, loose matches on Subject: below --
2012-05-01 19:37 Sunjoong Lee
2012-05-02  4:41 ` Joonas Sarajärvi
2012-04-26 18:51 Joonas Sarajärvi
2012-04-26 20:24 ` rixed
2012-04-26 21:04   ` Noah Lavine
2012-04-27  6:31     ` rixed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAK93xhoMm+A0he-g589C5dtqoK-FeFWDYX2byXErfBvu2pXMuA@mail.gmail.com \
    --to=sunjoong@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=wingo@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).