How to reduce code?

[Lorenzo Villari]

I premise I'm not a C expert...
I'm trying to modify some sources and I can't figure out what's the cause
of a crash...

If I could reduce the code I think I would isolate the problem...
but unfortunately I can not do it because it uses a parser created
automatically by yacc and a lexer created automatically by lex...
what do you think I can do to reduce the code?

As I was saying I'm not an expert and creating from scratch a parser and
lexer that could behave like that is beyond my possibilities...

[scriptOmatic]

Lorenzo Villari wrote:

>
> I premise I'm not a C expert...
> I'm trying to modify some sources and I can't figure out what's the cause
> of a crash...
>
> If I could reduce the code I think I would isolate the problem...
> but unfortunately I can not do it because it uses a parser created
> automatically by yacc and a lexer created automatically by lex...
> what do you think I can do to reduce the code?
>
> As I was saying I'm not an expert and creating from scratch a parser and
> lexer that could behave like that is beyond my possibilities...

You mention lex and yacc. When you compile you can add switches to the
lex and yacc lines that will automatically help you debug the code.
For lex I think it is -d.

man lex
man yacc

FYI: are you sure you are using lex (not flex) and yacc (not bison)?

flex and bison are the GNU replacements for lex/yacc.

--
[url]http://ftp.opensysmon.com[/url] is a shell script archive site with an
open source system monitoring and network monitoring software package.
Many platforms are supplied already compiled.

[Lorenzo Villari]

> FYI: are you sure you are using lex (not flex) and yacc (not bison)?
>

In fact I'm using Flex and Bison...

[David Schwartz]

"Lorenzo Villari" <vlllnz@tiscali.it> wrote in message
news:9owUa.205681$lK4.5899873@twister1.libero.it.. .

> I premise I'm not a C expert...
> I'm trying to modify some sources and I can't figure out what's the cause
> of a crash...

You could compile with '-g' and then do a post-mortem debug with 'gdb'
on the core file. The exact options and program might be different on your
platform, but most UNIX machines provide a way to get detailed core dumps
and do a post-mortem analysis on them. This assumes the crash you are
referring to is a fatal crash that causes the program to stop executing.

DS