Michael Meskes wrote:
> It appears to work for other tests though, but your
> regression.diffs suggests it doesn't here. Could you please check this by
> checking out the changes, re-running "make checktcp" and checking whether the
> regression.diffs file changes?
I re-ran the test and got 'sou
On Wed, Dec 17, 2008 at 12:09:01PM +0900, ITAGAKI Takahiro wrote:
> Hi, I found the cause.
Thanks a lot. Patch just checked in, please try again with CVS HEAD.
> The attached patch fixes the segfault. Regression tests can finish
> successfully but there is still a difference. The diff seems to be
On Wed, Dec 17, 2008 at 07:40:20AM -0500, Andrew Dunstan wrote:
> This test is not run by the buildfarm. It's not part of ecpg's
> "installcheck" suite.
I was under the impression that at least some members do run it. What else is
the test good for? Back when it was implemented it was taken out
Tom Lane wrote:
ITAGAKI Takahiro writes:
Hi, I found the cause.
...
Actual error occurs in vfprintf() because act->name can be NULL.
sprintf(..., "%s", NULL) could work on some platform (the result is '(null)'),
but it crashes on Windows (msvcrt). We need to avoid passing NULLs as
argument
Tom Lane writes:
> ITAGAKI Takahiro writes:
>> Hi, I found the cause.
>> ...
>> Actual error occurs in vfprintf() because act->name can be NULL.
>> sprintf(..., "%s", NULL) could work on some platform (the result is
>> '(null)'),
>> but it crashes on Windows (msvcrt). We need to avoid passing N
ITAGAKI Takahiro writes:
> Hi, I found the cause.
> ...
> Actual error occurs in vfprintf() because act->name can be NULL.
> sprintf(..., "%s", NULL) could work on some platform (the result is '(null)'),
> but it crashes on Windows (msvcrt). We need to avoid passing NULLs as
> arguments to "%s" fo
Andrew Dunstan wrote:
> > Thanks. The backtrace is kind of strange, but I might have found it.
> > Could you please update from CVS and re-run?
>
> same result ;-(
Hi, I found the cause.
Segfault comes from the following lines.
[ecpg/test/connect/test1.pgc]
exec sql connect to tcp:pos
Michael Meskes wrote:
On Sun, Dec 14, 2008 at 11:36:21AM -0500, Andrew Dunstan wrote:
See below
...
Thanks. The backtrace is kind of strange, but I might have found it. Could you
please update from CVS and re-run?
same result ;-(
cheers
andrew
--
Sent via pgsql-hackers mail
On Sun, Dec 14, 2008 at 11:36:21AM -0500, Andrew Dunstan wrote:
> See below
> ...
Thanks. The backtrace is kind of strange, but I might have found it. Could you
please update from CVS and re-run?
Thanks again.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com
Michael Meskes wrote:
Hello,
Could anyone with a MinGW system please run the ecpg regression suite including
tcp checks for the current CVS HEAD for me?
I ran the test but got a segfault.
I hope it can help you.
Not really I'm afraid.
Is there any way you could send me a
Hello,
> > Could anyone with a MinGW system please run the ecpg regression suite
> > including
> > tcp checks for the current CVS HEAD for me?
>
> I ran the test but got a segfault.
> I hope it can help you.
Not really I'm afraid.
Is there any way you could send me a backtrace? I guess this h
Hello,
Michael Meskes wrote:
> Could anyone with a MinGW system please run the ecpg regression suite
> including
> tcp checks for the current CVS HEAD for me?
I ran the test but got a segfault.
I hope it can help you.
$ make checktcp NO_LOCALE=on
== running regression test queries
Could anyone with a MinGW system please run the ecpg regression suite including
tcp checks for the current CVS HEAD for me?
Just run "make checktcp" in src/interfaces/ecpg and afterwards send me the file
.../ecpg/test/results/connect-test1.stderr. There is a special expected file
for MinGW which i
13 matches
Mail list logo
