FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Matthew Bartholomew [mailto:Matt AT Mastrapasqua.com]
> Sent: December 3, 2002 6:20 PM
>
> (gdb) r -v SQL
> Starting program: /usr/bin/isql -v SQL
> [New Thread 8192 (LWP 14857)]
>       
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 8192 (LWP 14857)]
> 0x4007b8df in uodbc_get_stats() from /usr/lib/libodbc.so.1
> (gdb) quit
> 
> I have no idea what the above message means, so if anyone can 
> shed some light...I would appreciate it.  

The message means:  In the shared library libodbc, there's a function
uodbc_get_stats() that attempted to access memory outside of its process
space.  When it did that, the operating system issued a SIGSEGV signal,
indicating a segment violation.  The application probably did not have a
handler installed to deal with that kind of signal, so the default handler
was called, immediately terminating the program.  

We're planning a new release soon; I recommend trying our nightly snapshot.


BTW, did you perchance configure FreeTDS --enable-threadsafe? 

Otherwise, if instead of "quit" you type "bt" (for "backtrace"), you'll see
the "call stack", the whole chain of function calls leading to
uodbc_get_stats().  That would be interesting information to the lists
you're cc'ing (and us) because it would give some context.  Like any train
wreck, the interesting thing -- if you're the NTSB and not CBS -- isn't the
crash, but what led up to it.  

Regards, 

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.