🚀 go-pugleaf

In article <6icd56$b46$1@winter.news.erols.com>#1/1,
  "Eric Fowler" <v-ericfo@microsoft.com> wrote:
>
> I have some GNU assembler code running on FreeBSD. I am assembling using
> the gcc compiler/'as'-driver and would like to debug with gdb. To further
> establish my credentials as a masochist, I am doing this in text mode using
> vi.
> I can easily get gcc-compiled C code to generate symbols, but if I pass the
> -ggdb or the -g flag to gcc for assembler code, I get a binary that has no
> symbols(at least, that's what gdb says). How can I debug my assembler
> source in gdb?
>
>

I tried using GDB in linux, but AS can't include debugging stuff in the
.o files. What's even worse, you can only set breakpoints on labels in GDB,
not where you want the breakpoint to be set.
It's hard to debug an ASM only program with GNU tools.

One way could be to put all your ASM code in a C/C++ file and then
"compile" it and then run it with GDB. You can also check the .s file
(the .s file gcc produced from your "C" file) to see how they add debugging
symbols. There's also a command line switch you can pass to gcc and it will
print all files it executes including the command line it passes to them
(so you know what options to pass to AS).
See in the man page for all options.

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/   Now offering spam-free web-based newsreading