Re: yacc & dbx

michi@ptcburp.ptcbu.oz.au (Michael Henning)
31 Jan 91 02:45:11 GMT

          From comp.compilers
Related articles
yacc & dbx htf@castle.edinburgh.ac.uk (H T Fallside) (1991-01-29)
Re: yacc & dbx michi@ptcburp.ptcbu.oz.au (1991-01-31)
Re: yacc & dbx megatest!djones@decwrl.dec.com (1991-02-01)
Re: yacc & dbx lupine!rfg@uunet.UU.NET (1991-02-02)
| List of all articles for this month |
Newsgroups: comp.compilers
From: michi@ptcburp.ptcbu.oz.au (Michael Henning)
Keywords: yacc, debug
Organization: Pyramid Technology Corporation
References: <9101291603.aa15778@castle.ed.ac.uk>
Date: 31 Jan 91 02:45:11 GMT

htf@castle.edinburgh.ac.uk (H T Fallside) writes:


>Anyone have any suggestions about ways of getting dbx to behave sensibly
>with a yacc generated parser as part of the program - ie indexing into the
>source during debug ?


There is not necessarily any sensible way to deal with #line directives in
the generated .c file. The easiest thing is usually to pre-process the
generated code with sed or some other tool to remove the #line directives
before compilation.


Michi.
--
Michael Henning +61 75 950255
Pyramid Technology +61 75 522475 FAX
Research Park, Bond University michi@ptcburp.ptcbu.oz.au
Gold Coast, Q 4229, AUSTRALIA uunet!munnari!ptcburp.oz!michi
[My experience is quite different; I've found it quite useful to put in
breakpoints and single step by line in the .y file. If you don't like the
#line directives, the -l flag to yacc prevents them. -John]
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.