Re: From NASM to Visusal Studio source debugging
- From: ",a\\/b" <spamtrap@xxxxxxxxxx>
- Date: Fri, 30 Sep 2005 08:10:52 +0000 (UTC)
On Thu, 29 Sep 2005 22:59:16 +0000 (UTC), "news.cybercity.dk"
<spamtrap@xxxxxxxxxx> wrote:
>I know NASM (and YASM) can produce the required obj
>format (-f win32) but as far as I can tell neither assembler
>will deliver debug info with this format.
>
>(Or am I wrong? Is the debug information required for
>source level debugging present in the format per se? I
>don't think so...)
i know only this and it is enough for me
if n_file.asm is a nasm file
nasmw -f obj n_file.asm
will make n_file.obj
if you have a file main.c
that call functions in n_file.obj
bcc32 -v main.c n_file.obj
(bcc32 is a Borland c compiler)
make the file main.exe
and that file has the debug information
of the name of *each function* and data position
of files main.obj and n_file.obj
(so in the debug program of Borland i can see each function
and data of file n_file.asm )
Do you have need of other debug information? Of what kind?
.
- References:
- From NASM to Visusal Studio source debugging
- From: news.cybercity.dk
- From NASM to Visusal Studio source debugging
- Prev by Date: Re: Fiddling with the Instruction Pointer
- Next by Date: Re: Linux asm code
- Previous by thread: From NASM to Visusal Studio source debugging
- Next by thread: Shadow RAM control
- Index(es):
Relevant Pages
|
