ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just installed Cigwin on Windows 7, S.P. 1. How do I get gdb to Access the symbol table? I assemble and link with[code]
as -o t01.o -L t01.S
ld -o t01 t01
This gets a Windows PE ejecutable, which gdb seems to have no trouble in executing. When I issue the list command, it says "No symbol table is loaded", though.
All of this runs under Cygwin, which unluckily puts messages not in English. ld message is something like this: relocation truncated to ajust 16 against '.data'. Should I use some sort of an org?
I now have messages i English! Thanks. No. offset msg should be handled by the assembler as a 16-bit displacement, which shure Works in 8086 and following architectures.
In the Intel 80386 and later, ... address offsets are 32-bit (instead of 16-bit), and the segment base in each segment descriptor is also 32-bit (instead of 24-bit).
Actually, Windows is neither linux nor DOS. Windows' system-calls aren't meant to use from user-programs; the standard way is calling Windows API functions from DLL's like KERNEL32.DLL, USER32.DLL, WS2_32.DLL
You've a made a 32bit exe, therefore the address space is 32 bit.
nEVER mind. One: x86 is downwards compatible, so code written for 8086 will run on 80586 and upwords. Two: you have three ways to run a modern x86: flat, segmented and real (which is also segmented). I think this puts an end to our discussion.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.