bug-cflow
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-cflow] cflow-1.1 doesn't find main


From: Sergey Poznyakoff
Subject: Re: [Bug-cflow] cflow-1.1 doesn't find main
Date: Mon, 11 Sep 2006 21:58:53 +0300

Robert E. Michael <address@hidden> wrote:

>     I did notice that the printed error message now has the long
> (i.e., full path) invocation name, rather than the short name
> one usually expects.  But perhaps that is what is expected of
> gnu tools.

Yes, the general principle is: the tool identifies itself with the name
under which it was invoked.  Compare (on GNU system):

  $ mv foobar x
  mv: cannot stat `foobar': No such file or directory
  $ /usr/bin/mv foobar x
  /usr/bin/mv: cannot stat `foobar': No such file or directory

> it would be of great help if I had a convenient way to suppress the
> common library routines such as "strchr" (and its relatives), and
> maybe even some common IO routines line "fprintf".  That way
> I can concentrate on the unique structure of that system, instead
> of being bogged down by having to scan past lots of function
> names which do not help me understand the new system.

Aha, yes, I see.  Currently there is no easy way to achieve this, but it
should not be hard to implement. Right from the top of my head I'd
propose an option telling cflow to display only those symbols
that are defined anywhere in the sources it is given in the command
line. Will such an option help?

Regards,
Sergey




reply via email to

[Prev in Thread] Current Thread [Next in Thread]