The MASM Forum Archive 2004 to 2012
Welcome, Guest. Please login or register.
April 22, 2018, 10:04:05 PM

Login with username, password and session length
Search:     Advanced search
128553 Posts in 15254 Topics by 684 Members
Latest Member: mottt
* Home Help Search Login Register
+  The MASM Forum Archive 2004 to 2012
|-+  Specialised Projects
| |-+  Compiler Based Assembler
| | |-+  Pelle's C compiler and tools (Moderator: Vortex)
| | | |-+  Polink mapinfo:lines broken?
« previous next »
Pages: [1] Print
Author Topic: Polink mapinfo:lines broken?  (Read 3980 times)
jj2007
Member
*****
Gender: Male
Posts: 6011



Polink mapinfo:lines broken?
« on: May 16, 2012, 07:45:27 AM »

Following a suggestion from Alex, I tried to get the line numbers for a little app and stumbled over this:

Linker options: /map /mapinfo:lines

Microsoft Link.exe:
Code:
Line numbers for SkelTryCatch.obj(tmp_file.asm) segment .text
   108 0001:00000006   111 0001:00000034   112 0001:00000036   114 0001:00000038
   114 0001:0000004b   117 0001:0000005b   119 0001:00000060   119 0001:00000060
   120 0001:00000078   121 0001:0000007d   122 0001:0000007e   122 0001:00000088
   123 0001:00000092   124 0001:00000094   125 0001:000000ab   126 0001:000000ac
   127 0001:000000ae   128 0001:000000b0   128 0001:000000ba   129 0001:000000c4
   130 0001:000000c9   130 0001:000000c9   131 0001:000000d7   132 0001:000000dd
   134 0001:000000e1   133 0001:000000fe   133 0001:00000105   133 0001:00000110
   135 0001:0000012a   136 0001:0000012c   138 0001:0000015f   138 0001:00000161
   139 0001:0000016d   140 0001:00000172   141 0001:00000174   141 0001:0000017e
   142 0001:00000188   145 0001:0000018a   146 0001:0000018f   147 0001:000001a6
   147 0001:000001eb   148 0001:0000020e

Same with polink:
Code:
Line numbers for SkelTryCatch.obj(tmp_file.asm) segment .text

   108 0001:00000000     3 0001:00000034     4 0001:00000036     6 0001:00000038
   114 0001:00000000     3 0001:0000005b   119 0001:00000000     1 0001:00000078
     2 0001:0000007d     3 0001:0000007e   122 0001:00000000     1 0001:00000092
     2 0001:00000094     3 0001:000000ab     4 0001:000000ac     5 0001:000000ae
     6 0001:000000b0   128 0001:00000000     1 0001:000000c4   130 0001:00000000
     1 0001:000000d7     2 0001:000000dd     4 0001:000000e1   133 0001:00000000
   133 0001:00000000   133 0001:00000000     2 0001:0000012a     3 0001:0000012c
     5 0001:0000015f   138 0001:00000000     1 0001:0000016d     2 0001:00000172
     3 0001:00000174   141 0001:00000000     1 0001:00000188     4 0001:0000018a
     5 0001:0000018f     6 0001:000001a6   147 0001:00000000     1 0001:0000020e

Is that a known problem? Any workaround?
Thanks, jj

P.S.: See also replacement for /mapinofo:lines in Visual Studio 2005 - our friends in Redmond messed it up. Keep a copy of good ol' link.exe 5.12.8078 dated 19 March 1998  tgrin
« Last Edit: May 17, 2012, 04:35:10 PM by jj2007 » Logged

Antariy
Member
*****
Gender: Male
Posts: 1041


Re: Polink mapinfo:lines broken?
« Reply #1 on: May 18, 2012, 01:01:06 AM »

Maybe PoLink properly treat the OBJs that are produced by PoAsm?

Also, advices, following to the link, like: "use this tool to get line numbers... use other tool to get first tool working properly... you need to download and install petabyte of the some stuff to get the latest version of the some small dll..." - this is really better than having simple textual MAP file with all info required green2
Logged
jj2007
Member
*****
Gender: Male
Posts: 6011



Re: Polink mapinfo:lines broken?
« Reply #2 on: May 18, 2012, 11:26:48 AM »

Yeah, people in Redmond are really funny green

I implemented the "jump to the source line that triggered the exception" feature now, see http://www.masm32.com/board/index.php?topic=12460.msg159921#msg159921  BigGrin
Logged

Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP The MASM Forum Archive 2004 to 2012 | Powered by SMF 1.0.12.
© 2001-2005, Lewis Media. All Rights Reserved.
Valid XHTML 1.0! Valid CSS!