[Patch] Wrong #line directives in rxvtperl.C
roland at verifysoft.de
Mon Aug 14 14:27:58 CEST 2006
it doesn't really matter who gets the wrong #line directives.
Tools relying on that will have serious problems, lets then say then "gdb".
In opposite to put in the correct source information, xsubpp
could also be invoked with -nolinenumbers. Then would have
all source line information implicit in rxvtperl.C, with my
revoked patch would see the source of the generated code, e.g.
to lines in rxvtperl.xs.
I know that this is not easy to debug, but having references to
non-existing source files does this make really hard.
Oh, I want to debug rxvtperl.C for learning purposes, and if lucky
On Tue, Aug 08, 2006 at 11:44:34AM +0200, Marc Lehmann wrote:
> On Tue, Aug 08, 2006 at 10:37:28AM +0200, Roland Baer <roland at verifysoft.de> wrote:
> > the generator for src/rxvtperl.C xsubpp needs the filename
> > extension to be passed with "-csuffix .C". Otherwise, we
> > have #line references to the rxvtperl.c (lowercase) in that
> > file, and subsequently tools using that information fail to
> > find that file.
> I am curious: which tools are those, and why is this a problem (I can only
> think of debugging tools, and who needs to debug generated code?).
> The choice of a
> -----==- _GNU_
> ----==-- _ generation Marc Lehmann
> ---==---(_)__ __ ____ __ pcg at goof.com
> --==---/ / _ \/ // /\ \/ / http://schmorp.de/
> -=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE
More information about the rxvt-unicode