Re: BUG #7955: argv=0x0 on program start

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: dweber(at)htw-saarland(dot)de
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7955: argv=0x0 on program start
Date: 2013-03-17 10:04:26
Message-ID: 20130317100426.GA11180@feivel.credativ.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Mar 16, 2013 at 12:12:49PM +0000, dweber(at)htw-saarland(dot)de wrote:
> My program compiled with system compiler gcc-4.2.1 and ecpg from PostgreSQL
> version 9.2.3 terminates by receiving SIGSEGV. The gdb debugger shows
> argv=0x0 (see below). On PostgreSQL version 8.4.16 it runs without trouble.
>
> Debugger output:
> b$ gdb bin/prog prog.core
> GNU gdb 6.1.1 [FreeBSD]
> ...
> Program terminated with signal 11, Segmentation fault.
> ...
> #0 0x08048eec in main (argc=-1077949560, argv=0x0) at prog.pgc:87
> 87 {

Hmm, this looks like the program didn't even start. Honestly I fail to see how
this could be a bug in PostgreSQL. Are the libraries and the program compiled
with threading enabled? What happens if you use a very small test case instead
of your program?

Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Damian Weber 2013-03-17 19:55:29 Re: BUG #7955: argv=0x0 on program start
Previous Message dweber 2013-03-16 12:12:49 BUG #7955: argv=0x0 on program start