reply to jeff message
Hi All,
I am working in a company that use entirely DOS and assembly to develop a GUI platform and a variety of graphic related application. I have always been struggling to find an all-in-one solution for Linux assembly program, so that we can do the porting.
From my experience, I think the most salient problem that hinder people from using assembly as her development tool lies in the absent of a robust assembly debugger. Although people says gdb is good enough, I still don't know how to treak it to symbolically debug my intel-syntax asm program. I've also try ald before, but I think it's the problem of nasm, it cannot show the symbols too.
After I got the gift from Jeff, I've tried it out all night, and I finally figure out how to debug my asm program symboliclly under kdbg, with his suggestion of using another version of nasm. With Jeff's tool, I finally can tried to start doing the porting.
I believe, with an integrated assembly development package, more and more people using asm under DOS/MS Windows like me will give a try to Linux. Thanks Jeff for his endeavour, and of course other programmers who contributed to the linux assembly tools.
Thanks and Regards,
Lawrence
peter w krause ??:
Quoted 14 lines
Lawrence am Donnerstag, 18. September 2003 02:13:
Quoted 10 lines
Hi All,
From my experience, I think the most salient problem that hinder people from using assembly as her development tool lies in the absent of a robust assembly debugger. Although people says gdb is good enough, I still don't know how to treak it to symbolically debug my intel-syntax asm program. I've also try ald before, but I think it's the problem of nasm, it cannot show the symbols too.
Quoted 4 lines
latest version can. the older one can be patched:
re http://www.lxhp.in-berlin.de/lhplinks.html#ald
Hi hp, thanks for your advice. I've tried this version of ald before, but still can't get full symbolic capability. I believe the problem is not attributed to ald, but the inability of nasm to generate proper debugging information to the debugger. I've also tried the amended nasm version you've post on your site too, but I still encounter failure.
If I am wrong on this point, would you please instruct me how to setup the debugging environment? For instance, which version of nasm/ld/ald should use, and if there are any parameter needed to be set during compliatoin, etc. After all, ald is much more similiar with the environment that I am using now.
Quoted 11 lines
Quoted 6 lines
After I got the gift from Jeff, I've tried it out all night, and I finally figure out how to debug my asm program symboliclly under kdbg, with his suggestion of using another version of nasm. With Jeff's tool, I finally can tried to start doing the porting.
did I miss something?
What do you mean about this? I am not quite understand...
Quoted 5 lines
best,
hp
Thanks and Regards,
Lawrence
Lawrence am Donnerstag, 18. September 2003 02:13:
Quoted 8 lines
Hi All,
From my experience, I think the most salient problem that hinder people from using assembly as her development tool lies in the absent of a robust assembly debugger. Although people says gdb is good enough, I still don't know how to treak it to symbolically debug my intel-syntax asm program. I've also try ald before, but I think it's the problem of nasm, it cannot show the symbols too.
latest version can. the older one can be patched:
re http://www.lxhp.in-berlin.de/lhplinks.html#ald
Quoted 5 lines
After I got the gift from Jeff, I've tried it out all night, and I finally figure out how to debug my asm program symboliclly under kdbg, with his suggestion of using another version of nasm. With Jeff's tool, I finally can tried to start doing the porting.
did I miss something?
best,
hp
Signature · 1 line
Linux,Assembly,Forth: http://www.lxhp.in-berlin.de/index-lx.shtml
Quoted 1 line
Quoted 1 line
hp -at- lxhp -dot- in-berlin -dot- de <<