From: groepaz (groepaz_at_gmx.net)
Date: 2001-08-02 22:26:23
Hello Ullrich, >> Then, how do you determine whether the emulator should load the >> 'C' file or the 'S' file (as 'C' compiles to 'S' assembles to 'O') >> to highlight the code being executed? This would have to be >> specified in the assembler file's header, e.g. similar to >> '.debuginfo<tab>off' use '.sourcefile<tab>filename.c' UvB> This is one of the reasons, the linker does not emit line info for assembler UvB> code: It does not know which is more important and should be used. i think it should emit line-information for ALL sourcefiles, even for assembler files created by the compiler itself... that should make it easy to display mixed C/asm in a debugger and step through it - also the debugger doesnt really need to know which info is "more important" since it would simply always prefer C over asm and have an option to switch to plain assembly. on a other totally different train..... is there some hook or sth in cc65 that would make it possible to link against a library for profiling? i am thinking of running the program on a c64 and send profiling information to the host (pc,amiga whatever) via parallel-cable (i am using pc64-cable but could ofcoz be whatever you like if you implement a few basic transfer routines for it)... same kinda setup i am using atm to send debug-info (as in printf ;D) to the pc and it would really rock to do serious profiling this way (you could easily create profile-info in some common format and analyze it with some really decent tools). -- Best regards, groepaz mailto:groepaz_at_gmx.net ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo_at_musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2001-12-14 22:05:40 CET