Message-ID:	<00a901c30bff$5ad2db40$0600000a@broadpark.no>
From:	"Gisle Vanem" <giva AT bgnett DOT no>
To:	"Eli Zaretskii" <eliz AT elta DOT co DOT il>
Cc:	<djgpp-workers AT delorie DOT com>
References:	<001e01c30be4$c8fbcca0$0600000a AT broadpark DOT no> <3405-Sat26Apr2003151120+0300-eliz AT elta DOT co DOT il>
Subject:	Re: Debuglines for asm-code
Date:	Sat, 26 Apr 2003 16:23:06 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1165
Reply-To:	djgpp-workers AT delorie DOT com

"Eli Zaretskii" <eliz AT elta DOT co DOT il> said:

> > RHGDB is asking for c:\temp\ccVECL3d.s. How do I solve this
> > w/o the need for a temp .s file for RHGDB to debug?
> 
> One way is to have two rules: one to preprocess the .S file into .s,
> the other to assemble it.  I didn't try that, so it's just an idea to
> try.

Thanks, I tried this:

$(OBJDIR)/%.o: %.S
        $(CC) -E $< > $(OBJDIR)/$*.iS
        as --gdwarf2 $(OBJDIR)/$*.iS -o $@

which works with RHIDE/RHGDB. It steps through the .iS fine.
(as doesn't have --gcoff).

> Anyway, what exactly do you need the debug info for in the asm source?
> What debugger commands don't work on machine code with no debug info?

If I compile w/o debug-info, RHGDB doesn't enter that module at all.
At least not here with v1.5. It's not that big deal anyway since my bug
is elsewhere. Just had to trace the .S file to be sure.

Gisle V.

Entropy isn't what it used to be.

- Raw text -