freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "Steven J. Backus" <backus AT math.utah.edu>
- To: freetds AT franklin.oit.unc.edu
- Subject: stored procedure causes core dump
- Date: Fri, 16 Mar 2001 15:10:34 -0700 (MST)
I'm calling a stored procedure (using dblib) as in:
dbfcmd(db, "exec lab_get_tmp %d, %c", *kind, study);
And afterwards, all my dbbinds dump core:
Program received signal SIGSEGV, Segmentation fault.
0x804d78a in dbbind (dbproc=0x8061620, column=1, vartype=1, varlen=0,
varaddr=0x8047688 "Üv\004\b\216ð°ß\001") at dblib.c:893
893 okay = okay && ((column >= 1) && (column <= resinfo->num_cols));
(gdb) bt
#0 0x804d78a in dbbind (dbproc=0x8061620, column=1, vartype=1, varlen=0,
varaddr=0x8047688 "Üv\004\b\216ð°ß\001") at dblib.c:893
#1 0x8049ea5 in main (argc=2, argv=0x804772c) at newestLabout.c:427
The stored procedure populates a temporary table. I tried
putting in a dbcancel after the call, but then the table never got
populated.
Anyone have any ideas?
Thanks,
Steve
-
stored procedure causes core dump,
Steven J. Backus, 03/16/2001
- <Possible follow-up(s)>
- Re: stored procedure causes core dump, Brian Bruns, 03/17/2001
- Re: stored procedure causes core dump, Steven J. Backus, 03/17/2001
Archive powered by MHonArc 2.6.24.