Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 258
  • Last Modified:

Possible __NASMDEFSEG problems

Hi,

I looked in my .map file after it has been compiled by NASM.  And  this is what i see:

Detailed map of segments

 0000:0000 0271 C=CODE   S=_TEXT          G=(none)  M=ex1.ASM ACBP=68
 0000:0271 0128 C=CODE   S=_TEXT          G=(none)  M=ex2.ASM ACBP=28
 003A:0000 0008 C=BSS    S=_BSS           G=(none)  M=ex1.ASM ACBP=68
 003A:0008 000E C=BSS    S=_BSS           G=(none)  M=ex2.ASM ACBP=28
 003B:0006 0010 C=       S=__NASMDEFSEG   G=(none)  M=ex2.ASM ACBP=28

I looked in the nasm manual and it says the nasmdefseg appears IF you have code before an explicit segment definition.  HOWEVER, I do NOT have any code before one -- I'm very confused and I'm wondering about the possible implicatins of this issue.

Like what if nasm has a bug and puts ALL my code before that?  Is there a max, etc?

Thanks
0
sceptre04
Asked:
sceptre04
1 Solution
 
DancieCommented:
Lets see the source
0
 
sceptre04Author Commented:
Ok the problem is solved -- was instead of doing a #include inside the code, I was compiling the .h file in from the command line.  As a result, nasm put that .h file in the nasmdefseg.

Thanks for the offer though Dancie!
0
 
NetminderCommented:
User resolved; closed, 50 points refunded.

Netminder
Site Admin
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now