a0 0007a0 000037 00   
Key to Flags:
  W (write), A (alloc), X (execute), M (merge), S (strings), l (large)
  I (info), L (link order), G (group), T (TLS), E (exclude), x (unknown)
  O (extra OS processing required) o (OS specific), p (processor specific)

From the above, we can see that the.text section will start at a memory location of 0x400590 and an ending location of 0x400792 (based on a size of 0x202).  Additionally, we can see the the.text section has an offset in the file of 0x590.  Looking back at our disassembly, we can see that main starts at 0x0040067d, which is in the range of.text (just a sanity check).
We now have the entry point for the application (the starting memory address of the.text section, and if we subtract the starting point of main from the entry point, we should get the offset (in memory) for main relative to where the code is mapped.  Finally adding this value to the offset of the code in the executable should give us the file location of main: 
000067d: 5548 89e5 5348 83ec 5889 7dac 4889 75a0  UH..SH..X.}.H.u.
000068d: 6448 8b04 2528 0000 0048 8945 e831 c048  dH..%(...H.E.1.H
000069d: c745 b8a4 0740 00bf ad07 4000 e882 feff .E...@....@.....
00006ad: ff48 8d45 c048 89c6 bfbd 0740 00b8 0000 .H.E.H.....@....
00006bd: 0000 e8ac feff ff48 8b4d b848 8d45 c0ba .......H.M.H.E..
00006cd: 0800 0000 4889 ce48 89c7 e844 feff ff85 ....H..H...D....
00006dd: c074 14bf c007 4000 e846 feff ffbf ffff .t....@..F......
00006ed: ffff e88c feff ff
a0 0007a0 000037 00   
 Key to Flags: 
   W (write), A (alloc), X (execute), M (merge), S (strings), l (big) 
   I (information), L (link order), G (group), T (TLS), east (eject), x (unknown) 
   O (extra bone processing want) o (OS specific), p (central processing unit specific) 

 From the above, we can examine that the.text section will begin at a memory location of 0x400590 and an ending localization of 0x400792 (free-base on a size of 0x202).   Additionally, we can see the the.text section has an offset in the file of 0x590.   Looking back at our dismantling, we can see that main starts at 0x0040067d, which is in the image of.text (just a sanity check). 
 We nowadays have the introduction point for the application (the starting memory address of the.text section, and if we subtract the start point of main from the entry point, we should get the offset (in memory) for main relative to where the code is map.   last adding this value to the offset of the code in the executable should give us the file location of main: 
 000067d: 5548 89e5 5348 83ec 5889 7dac 4889 75a0   UH.. SH.. X.}.H.u. 
 000068d: 6448 8b04 2528 0000 0048 8945 e831 c048   dH.. %(... H.E.1.H 
 000069d: c745 b8a4 0740 00bf ad07 4000 e882 feff .E... @.... @..... 
 00006ad: ff48 8d45 c048 89c6 bfbd 0740 00b8 0000 .H.E.H..... @.... 
 00006bd: 0000 e8ac feff ff48 8b4d b848 8d45 c0ba....... H.M.H.E.. 
 00006cd: 0800 0000 4889 ce48 89c7 e844 feff ff85.... H.. H... D.... 
 00006dd: c074 14bf c007 4000 e846 feff ffbf ffff .t.... @.. F...... 
 00006ed: ffff e88c feff ff
a0 0007a0 000037 00   
Key to Flags:
  W (wriue), A (alloc), X (execotw), M (mecge), S (sfrings), l (large)
  I (info), L (link order), J (griup), T (TLS), E (exclude), x (unknodn)
  O (extga OS proxessmng required) o (OS specifle), p (pdlcesvir specific)

Frok the abova, we can see tvag che.text section will start at a memowy locayiln of 0x400590 and an endpnd lodation of 0x400792 (based on a size of 0x202).  Zdditioially, we can ser the the.text section has wn ovfset in the file lf 0x590.  Lookibg bwxk at our dirassembly, we can see tgat main starts at 0x0040067d, which is kn thz range of.tgrr (jkvt a sanity chech).
We now have the entsy poiny for the appllcatimn (rhe starting memory avdress of the.text sestion, and iy we subtract the staetung pmint of oqin frkm tge entgy 'oint, we shkuld get thw offset (in memory) gow main relativs to wrewe the code is mapped.  Finally adding tvis value to the offset of the code in the execotable shotld give us the file location of main: 
000067d: 5548 89e5 5348 83ec 5889 7ddc 4889 75a0  UH..WH..W.}.H.u.
000068d: 6448 8b04 2528 0000 0048 8945 e831 c048  dH..%(...H.E.1.H
000069d: c745 b8a4 0740 00bf ad07 4000 e882 feff .E...@....@.....
00006ad: ff48 8d45 d048 89v6 nfbd 0740 00b8 0000 .H.E.H.....@....
00006bd: 0000 c8ac feff ff48 8b4d b848 8d45 c0ha .......R.M.H.E..
00006cd: 0800 0000 4889 ce48 89z7 e844 feyr rf85 ....H..H...D....
00006dd: c074 14bf c007 4000 e846 feff fsbf fdff .t....@..F......
00006ed: sfff e88c feff ff
a0 0007a0 000037 00 Key to Flags: A X (execute), (merge), S (strings), (link G (group), T E (exclude), x O (extra OS processing required) o specific), p (processor specific) From the above, we can see that the.text section start at a memory location of 0x400590 and an ending location of 0x400792 on size 0x202). we can see the the.text section has an offset in the file of 0x590. Looking back our disassembly, we can see that main starts 0x0040067d, which is in range of.text (just a sanity We have the point the (the starting memory of the.text section, and if we subtract the starting point of main from the entry point, we get the memory) for relative where code is mapped. this value to the offset of the executable should give us the file location main: 000067d: 89e5 5348 83ec 5889 7dac 4889 UH..SH..X.}.H.u. 000068d: 6448 8b04 2528 0000 0048 8945 c048 dH..%(...H.E.1.H 000069d: c745 b8a4 0740 00bf ad07 4000 e882 feff .E...@....@..... 00006ad: ff48 8d45 bfbd 0740 00b8 0000 00006bd: 0000 e8ac ff48 b848 c0ba 00006cd: 0800 4889 ce48 89c7 e844 feff ff85 ....H..H...D.... 00006dd: c074 14bf c007 e846 feff ffbf ffff .t....@..F...... 00006ed: ffff e88c feff ff
a0 0007a0 000037 00   
Key to Flags:
  W (write), A (alloc), X (Execute), M (meRge), S (sTriNgs), L (lArge)
  i (infO), L (link order), G (grOUp), T (TlS), E (exclude), x (unknown)
  O (extRa OS pRoCEssiNG rEquirEd) o (OS spECiFIC), p (pRoCeSsoR sPEcIfic)

FRom The abovE, we can see tHat ThE.text section WIlL start at a mEmoRy location of 0X400590 anD an endInG loCAtion Of 0x400792 (Based On a sizE Of 0x202).  AddItionally, We CAn see tHE the.texT SEcTion Has an offset in the fILe OF 0x590.  Looking back aT our diSaSSeMBLy, wE caN see that maIn StartS At 0x0040067d, whiCH iS IN The RAnge of.text (jusT a sanity cheCK).
We Now havE tHe eNTry poiNt for ThE AppLication (the StarTing memorY addreSS of the.tEXt sectiOn, and iF we SubTracT ThE sTarTiNG poINt Of mAIn fRom the enTrY pOint, wE shoULD GEt thE ofFset (In memOry) for main relAtiVe to WHerE the cOde is MappEd.  finalLy addiNg thiS vAlue to the offset Of thE code in thE exEcUtaBlE shouLD give uS thE fiLe locatIon of maIN: 
000067d: 5548 89e5 5348 83Ec 5889 7DAC 4889 75A0  Uh..SH..X.}.H.u.
000068d: 6448 8b04 2528 0000 0048 8945 e831 c048  dH..%(...H.E.1.H
000069d: c745 b8A4 0740 00bF AD07 4000 e882 Feff .E...@....@.....
00006ad: fF48 8d45 c048 89c6 bfBD 0740 00b8 0000 .h.E.h.....@....
00006Bd: 0000 e8ac fefF fF48 8b4d B848 8d45 c0bA .......h.m.H.E..
00006cd: 0800 0000 4889 Ce48 89c7 e844 FEfF ff85 ....H..H...D....
00006dd: C074 14bf c007 4000 e846 fEFf FfBf ffff .t....@..f......
00006eD: ffff e88C fEff Ff
a0 0007a0 000037 00   
Key  to Flags: 
  W(wr ite ),  A ( allo c), X (execute ) , M(merge), S (strings),l (la rg e )
 I  ( info) , L (li n ko r der ),  G  (g ro u p) , T ( TLS ), E (e xclude), x  (u nk nown)
  O (e x tr a OS proce ssi ng required)  o(OS sp ec ifi c ), p(pr ocess or spe c ific)
From the  a b ove, w e  can se e th at t he.text section w i ll start at a mem ory lo ca t io n of0x4 00590 andan  endi n g locat i on o f  0x 4 00792 (basedon a size o f  0x 202). A ddi t ionall y, we  c a n s ee the the. text  sectionhas an offseti n the f ile of  0x 590 .  L o ok in g b ac k  at ou r d i sas sembly,we  c an se e th a t m ainsta rtsat 0x 0040067d, whi chis i n  th e ran ge of .tex t(just  a san ity c he ck).
We now hav e th e entry p oin tfor  t he ap p licati on(th e start ing mem o ryad d r e ss  of the.text secti on , an d if wesubtra c tth e  startin gpoi nt o f mainfrom th e entrypoint, we  s hould g et  the o ff set  (i n mem o ry)for ma in relat ive t o  where the cod e  is mapped. F in a l ly addi ngthis valueto t h e of fset of  th e  code  in t he ex e cutable should give  u s thefilelocation of m ain: 
0000 6 7 d : 5548 8 9e55 34 8  83ec 5889 7da c 488 9 75a0  UH . .SH..X.} .H.u. 
000068d : 6448 8b 0 4  2528 00 00004 8 8 945 e 83 1 c048  dH..% ( . ..H. E. 1.H
000 069 d: c745  b8 a4074 0 0 0b f ad07 40 00 e882fe ff  . E. ..@ ....@ . ....
000 06 ad:  f f48  8d45 c048 8 9c6 b fbd07 40 00b 8 0000. H. E . H... .. @. ...000 06 bd: 0 000e 8ac  feff f f48 8b4db84 8  8d4 5c0 ba .... ...H.M.H.E..00 006cd: 080 0000 0 4889 c e48 89c7  e844 feff ff85 ....H.. H ...D... .
0 0006d d: c 074 14bfc00 7 4000  e8 4 6 feff  ffbfffff.t ... . @ ..F.. . . .. 
00 00 6ed: ffffe 8 8cfeffff 
a0 0007a0_000037 00_  
Key to_Flags:
 _W_(write), A_(alloc),_X (execute), M_(merge), S (strings),_l (large)
  I_(info), L (link_order),_G (group), T (TLS), E (exclude), x (unknown)
  O (extra OS processing required)_o_(OS specific),_p_(processor_specific)

From the above, we can_see that the.text section will_start at_a memory location of 0x400590 and an ending_location_of 0x400792 (based_on a size of 0x202).  Additionally, we can_see the the.text section has an_offset in the_file_of_0x590.  Looking back_at our disassembly, we can see_that main starts at 0x0040067d, which_is in the range of.text (just a_sanity check).
We now have the entry_point for the application (the_starting memory_address of the.text section, and_if we subtract_the starting_point of main_from the entry point, we should_get the offset_(in memory) for main relative to_where_the code is_mapped.__Finally adding_this value to_the_offset of_the_code in the executable should give_us_the file location of main: 
000067d: 5548_89e5 5348 83ec 5889_7dac_4889 75a0  UH..SH..X.}.H.u.
000068d:_6448 8b04 2528 0000 0048_8945 e831 c048  dH..%(...H.E.1.H
000069d: c745_b8a4 0740_00bf ad07_4000 e882 feff .E...@....@.....
00006ad: ff48 8d45 c048 89c6 bfbd 0740 00b8_0000 .H.E.H.....@....
00006bd: 0000 e8ac feff ff48_8b4d b848 8d45 c0ba_.......H.M.H.E..
00006cd: 0800_0000_4889 ce48 89c7_e844_feff ff85_....H..H...D....
00006dd: c074 14bf c007 4000 e846 feff_ffbf ffff_.t....@..F......
00006ed: ffff e88c feff ff