| From: | hom <obsidianhom(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Open unmatch source file when step into parse_analyze() in Eclipse? |
| Date: | 2011-03-04 16:51:30 |
| Message-ID: | AANLkTimNiOFVb+Mk3cgsz621RTtiVJ9kKjthAHUNe=LJ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 <robertmhaas(at)gmail(dot)com>:
> On Fri, Mar 4, 2011 at 11:40 AM, hom <obsidianhom(at)gmail(dot)com> wrote:
>> 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.
>
> That's a feature, not a bug.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
--
Best Wishes!
hom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Colson | 2011-03-04 16:55:33 | Re: Perl 5.12 complains about ecpg parser-hacking scripts |
| Previous Message | David E. Wheeler | 2011-03-04 16:50:06 | Re: Quick Extensions Question |