Should I look elsewhere??
So...
If after recompiling postgres with -g in the CFLAGS and still getting 0x40050768 in ?? ()
in gdb, should I look elsewhere???
Thanks
-Mat
--
Mathieu Dube
Mondo-Live
www.flipr.com
post the rest of the traceback.
0x40* is the address inside some shared library, most likely libc.
full traceback will show what happened before it got to libc
-alex
On Mon, 5 Feb 2001, Mathieu Dube wrote:
Show quoted text
So...
If after recompiling postgres with -g in the CFLAGS and still getting 0x40050768 in ?? ()
in gdb, should I look elsewhere???Thanks
-Mat
On Mon, 05 Feb 2001, you wrote:
You're not backtracing the same core file as before, are you?
???
I dont see what you mean
I build postgresql with -g and then put libpq.a in my project's dir
all my files are compiled with -g too
the only other thing I use is posix threads
How do I know what function is supposed to be in the place of ?? that gdb
outputs
Thanks
-Mat
The core file produced by something compiled with debug symbols should be
much nicer to read..-Mitch
----- Original Message -----
From: "Mathieu Dube" <mathieu_dube@videotron.ca>
To: <pgsql-hackers@postgresql.org>
Sent: Monday, February 05, 2001 5:03 PM
Subject: Should I look elsewhere??So...
If after recompiling postgres with -g in the CFLAGS and still getting0x40050768 in ?? ()
in gdb, should I look elsewhere???
Thanks
-Mat
--
Mathieu Dube
Mondo-Live
www.flipr.com
--
Mathieu Dube
Mondo-Live
www.flipr.com
Import Notes
Reply to msg id not found: 041601c08fbf4aa88ee00200000a@windows