[GENERAL] Breakpoints are not triggered in analyze.c (debugging Postgresql in Visual studio)

2014-01-16 Thread Felix . 徐
Hi all,

I've set up a developing environment on my windows using Visual Studio
2012, everything works fine, except that the breakpoints set in analyze.c
are not triggered in debug mode (breakpoints in main.c and some
initialization code worked well), and I'm sure that line has been executed
since my own messages have been printed on the console. Does anyone have
any experience debugging postgresql in Visual Studio?

Thanks!


Re: [GENERAL] Breakpoints are not triggered in analyze.c (debugging Postgresql in Visual studio)

2014-01-16 Thread Tom Lane
=?GB2312?B?RmVsaXgu0Ow=?= ygnhz...@gmail.com writes:
 I've set up a developing environment on my windows using Visual Studio
 2012, everything works fine, except that the breakpoints set in analyze.c
 are not triggered in debug mode (breakpoints in main.c and some
 initialization code worked well), and I'm sure that line has been executed
 since my own messages have been printed on the console. Does anyone have
 any experience debugging postgresql in Visual Studio?

There are two different source files named analyze.c; I wonder which one
the debugger thinks you are talking about ...

In gdb, the solution for this is to always start by setting a breakpoint
by function name.  Once you're stopped in a particular source file, gdb
will assume that that file is meant by b linenumber references.  Perhaps
the same kind of trick will work with VS.

regards, tom lane


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


Re: [GENERAL] Breakpoints are not triggered in analyze.c (debugging Postgresql in Visual studio)

2014-01-16 Thread ygnhzeus
Hi Tom,
I'm debugging the /backend/commends/analyze.c.
I've set up a Function breakpoint in visual studio,but seems no luck, T_T

2014-01-17



ygnhzeus



发件人:Tom Lane t...@sss.pgh.pa.us
发送时间:2014-01-16 23:31
主题:Re: [GENERAL] Breakpoints are not triggered in analyze.c (debugging 
Postgresql in Visual studio)
收件人:Felix.徐ygnhz...@gmail.com
抄送:pgsql-generalpgsql-general@postgresql.org

=?GB2312?B?RmVsaXgu0Ow=?= ygnhz...@gmail.com writes: 
 I've set up a developing environment on my windows using Visual Studio 
 2012, everything works fine, except that the breakpoints set in analyze.c 
 are not triggered in debug mode (breakpoints in main.c and some 
 initialization code worked well), and I'm sure that line has been executed 
 since my own messages have been printed on the console. Does anyone have 
 any experience debugging postgresql in Visual Studio? 

There are two different source files named analyze.c; I wonder which one 
the debugger thinks you are talking about ... 

In gdb, the solution for this is to always start by setting a breakpoint 
by function name.  Once you're stopped in a particular source file, gdb 
will assume that that file is meant by b linenumber references.  Perhaps 
the same kind of trick will work with VS. 

regards, tom lane