2011/3/20 Nicolas Barbier :
> 2011/3/20 hom :
>
>> I trace into scan.c because I want to known how the paser tree is
>> built and I debug the source step by step.
>
> I suggest you learn how flex/bison work first. The contents of the *.c
> files generated by flex/bison
2011/3/20 Martijn van Oosterhout :
> On Sun, Mar 20, 2011 at 11:50:01AM +0800, hom wrote:
>> I trace into scan.c because I want to known how the paser tree is
>> built and I debug the source step by step.
>> Then the eclipse pick up the scan.I and the excute order does
2011/3/19 Vaibhav Kaushal :
> Hello hom,
>
> Frankly I am a learner as well. The experts here are almost always ready
> to help and would be a better source of information.
>
> Moreover I am also using eclipse but I do not use it for building the
> source. I use it only as
o-parse-analyze-in-Eclipse-td3408033.html
--
Best Wishes!
hom
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
2011/3/18 Brendan Jurd :
> On 18 March 2011 01:57, hom wrote:
>> I try to known how a database is implemented
>
> This objective is so vast and so vague that it's difficult to give
> meaningful help.
>
> I'd emphasise Kevin Grittner's very worthwhile adv
2011/3/18 Markus Wanner :
> Hom,
>
> On 03/17/2011 04:49 PM, Kevin Grittner wrote:
>> That's ambitious.
>
> Absolutely, yes. Exercise patience with yourself.
>
> A method that hasn't been mentioned, yet, is digging out your debugger
> and attach it to a c
2011/3/17 Kevin Grittner :
> hom wrote:
>
>> I try to known how a database is implemented and I have been
>> reading PG source codes for a month.
>
> That's ambitious.
>
> find -name '*.h' -or -name '*.c' \
> | egrep -v '
2011/3/17 Bruce Momjian :
> hom wrote:
>> Hi,
>>
>> I try to known how a database is implemented and I have been reading
>> PG source codes for a month.
>>
>> Now, I only know a little about how PG work. :(
>>
>> I just know PG wo
e. it may be
that I could't split the large module into small piece which may help
to understand.
Is there any article or some way could help understand the source code ?
Thanks for help ~
--
Best Wishes!
hom
--
Sent via pgsql-hackers mailing list (pgs
but if Eclipse steps in scan.I, the excute order does not match the source code.
what should I do if I want to debug functions defined in scan.I ?
2011/3/5 Robert Haas :
> On Fri, Mar 4, 2011 at 11:40 AM, hom wrote:
>> I think Eclipse just find incorrect file.
>> when Eclipse co
I think Eclipse just find incorrect file.
when Eclipse compiles the code, it should use scan.c to build.
But when debugging, Eclipse open scan.l to step in.
I don't known how to trace into scan.c :(
2011/3/4 Heikki Linnakangas :
> On 04.03.2011 14:55, hom wrote:
>>
>> when
order is still unmatched.
May it be scan.c actually ?
PS: I have turn "Search for duplicate source files" option on.
2011/3/4 Heikki Linnakangas :
> On 03.03.2011 16:46, hom wrote:
>>
>> Hi,
>>
>> I'm debug Postgresql with Eclipse under Redha
order didn't match the source code.
How can I make the Eclipse open the right file?
Thank you for answering
PS: I have set compile optimization level to 0 with CFLAGS='-O0' and
it worked well in other source code.
--
Best Wishes!
hom
--
Se
It works!
Thanks Kevin and Lbrar!
:)
2011/3/1 Ibrar Ahmed :
> - export CFLAGS='-O0' may work for you.
>
>
> On Tue, Mar 1, 2011 at 8:21 PM, Kevin Grittner
> wrote:
>> hom wrote:
>>
>>> How can I do to make sure the right excute order when I
the cause maybe the share library and the source code do not match.
I have add MY_PG_INS_DIR/lib to LD_LIBRARY_PATH, but it does't work at all.
How can I do to make sure the right excute order when I debug step by step ?
Thank you for answering.
--
Best Wishes!
15 matches
Mail list logo
