Hi everyone!

I'm trying to debug strange bug in my Perl Ingres driver, I really don't
know what is causing it.

The problem is that, after fetching row, ^C stops working.

I have created minimal test case using ESQL/C:

( code is at http://pastebin.com/QFrDdYQa )

Example assumes that you have standard Ingres demonstration database
(demodb).

There is infinite loop, so ^C should be only way to cause program
termination, but it does not work in my example - if I press ^C nothing
happens.

If I comment out "EXEC SQL FETCH ..." line, everything works as expected.

I'm using latest Ingres Community Edition. Problem is present only under
Windows (I have tried Win 2003 R2 32-bit and Win7 64-bit), under Linux
everything works as expected.

What am I doing wrong?

Regards,
Tomasz

maybe the fetch instruction resets the signal handler;it sets the setctrlhandler win api function to null so it does not get interrupted and then forgets to turn it on again.but thats a speculation and a look on the underlying c code should be taken...

On Jul 31, 2012, at 8:48 AM, Tomasz Konojacki wrote:

I don't really do Windows, but a couple thoughts:

Is this specific to the data type fetched? i.e. does it really only happen when
fetching NCHAR data? or does it happen regardless of what you fetch?
If it's data type specific, I would suspect some kind of memory corruption.

Ingres library is setting and not restoring upon disconnect. You could try
poking around in $ING_SRC/cl/clf/ex_win to see if you can figure out
what is happening.

Karl

Well, I'm stupid, I don't know why I thought that NCHAR is the problem.
Problem is present only when I'm fetching DECIMAL columns, I have made
really trivial tests with only one (DECIMAL) column and results are
excactly the same as in posted test case.

Thanks,
Tomasz

W dniu 2012-08-03 16:00, Karl Schendel pisze: