Anyone know the recent progress of YASM ?

I went to the site - www.tortall.net/projects/yasm/ - to check but,
perhaps due to me being enlightenment-disabled, I need to know if YASM
is usable as it is, or not.

Thanks in advance !

spamtrap@crayne.org wrote:
> Anyone know the recent progress of YASM ?
> 
> I went to the site - www.tortall.net/projects/yasm/ - to check but,
> perhaps due to me being enlightenment-disabled, I need to know if YASM
> is usable as it is, or not.

I have found YASM very reliable as an Intel syntax x86 assembler when
used in association with Microsoft Visual C++.

It is also sound as a 64-bit assembler under Windows x64. The few issues
I have had here are caused more by lack of MS documentation of 64-bit
object, linker and relocation characteristics than they are down to YASM
itself. Moreover I have found that the YASM team leader is first class
at sorting out these problems just as soon as they turn up.

Right now YASM uses Intel syntax but it is in process of being extended
to handle AT&T syntax.

  Brian Gladman

BRG <spamtrap@crayne.org> wrote:
> spamtrap@crayne.org wrote:
>> Anyone know the recent progress of YASM ?
>>
>> I went to the site - www.tortall.net/projects/yasm/ - to check but,
>> perhaps due to me being enlightenment-disabled, I need to know if YASM
>> is usable as it is, or not.
>
> I have found YASM very reliable as an Intel syntax x86 assembler
> when used in association with Microsoft Visual C++.

What happens with debug information? Can you single-step through
the YASM code in Visual Sudio source windows, like with MASM?

Ole Nielsby

news.cybercity.dk wrote:
> BRG <spamtrap@crayne.org> wrote:
> 
>>spamtrap@crayne.org wrote:
>>
>>>Anyone know the recent progress of YASM ?
>>>
>>>I went to the site - www.tortall.net/projects/yasm/ - to check but,
>>>perhaps due to me being enlightenment-disabled, I need to know if YASM
>>>is usable as it is, or not.
>>
>>I have found YASM very reliable as an Intel syntax x86 assembler
>>when used in association with Microsoft Visual C++.
> 
> What happens with debug information? Can you single-step through
> the YASM code in Visual Sudio source windows, like with MASM?
> 
> Ole Nielsby

I am afraid not.

Maybe this would not be too hard to add if there is good documentation
of how the relevant data is passed to the Microsoft debugger.

   Brian Gladman

news.cybercity.dk wrote:
> BRG <spamtrap@crayne.org> wrote:
> 
>>spamtrap@crayne.org wrote:
>>
>>>Anyone know the recent progress of YASM ?
>>>
>>>I went to the site - www.tortall.net/projects/yasm/ - to check but,
>>>perhaps due to me being enlightenment-disabled, I need to know if YASM
>>>is usable as it is, or not.
>>
>>I have found YASM very reliable as an Intel syntax x86 assembler
>>when used in association with Microsoft Visual C++.
> 
> 
> What happens with debug information? Can you single-step through
> the YASM code in Visual Sudio source windows, like with MASM?

I am afraid not, YASM doesn't handle debugging information for Visual
Studio.  If the formats are documented it might be possible to add this.

   Brian Gladman

Just an ignorant question:


        Does anyone here know of where to obtain the
        documentation regarding the format and/or relevant
        data that visual debugger uses ?


BRG wrote:
> news.cybercity.dk wrote:
> > BRG <spamtrap@crayne.org> wrote:
> >
> >>spamtrap@crayne.org wrote:
> >>
> >>>Anyone know the recent progress of YASM ?
> >>>
> >>>I went to the site - www.tortall.net/projects/yasm/ - to check but,
> >>>perhaps due to me being enlightenment-disabled, I need to know if YASM
> >>>is usable as it is, or not.
> >>
> >>I have found YASM very reliable as an Intel syntax x86 assembler
> >>when used in association with Microsoft Visual C++.
> >
> > What happens with debug information? Can you single-step through
> > the YASM code in Visual Sudio source windows, like with MASM?
> >
> > Ole Nielsby
>
> I am afraid not.
>
> Maybe this would not be too hard to add if there is good documentation
> of how the relevant data is passed to the Microsoft debugger.
> 
>    Brian Gladman

On Thu, 20 Oct 2005 07:40:20 +0000 (UTC), spamtrap@crayne.org wrote:

>Just an ignorant question:
>
>
>        Does anyone here know of where to obtain the
>        documentation regarding the format and/or relevant
>        data that visual debugger uses ?

Yes, It's in the MSDN library in the 'Specifications' section. 

The title is:
"Visual C++ 5.0 Symbolic Debug Information Specification"

It is a description of the 32-bit version of CodeView used for VC 5 &
6, and MASM 6.15.





Now all you have to do is find a copy of the MSDN library CD. :-)

<snip>
-- 
ArarghMail510 at [drop the 'http://www.' from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html

To reply by email, remove the garbage from the reply address.

spamtrap@crayne.org wrote:
> Just an ignorant question:
>
>
>         Does anyone here know of where to obtain the
>         documentation regarding the format and/or relevant
>         data that visual debugger uses ?

IIRC, it's found on MSDN. Frank Kotler turned me on to it at one time.
I don't have the documentation name with me (it's at home), but I can
assure you that the document does exist. Maybe Frank can recall the
name before I get home and find the stuff.
Cheers,
Randy Hyde

spamtrap@crayne.org wrote:
> Just an ignorant question:
> 
> 
>         Does anyone here know of where to obtain the
>         documentation regarding the format and/or relevant
>         data that visual debugger uses ?

Supposed to be in "Specs.chm" - available on a CD (but not online?)... I 
think you have to join their club. A friend sent me a copy... I'd be 
glad to pass it on... I've "decompiled" it into a bunch of cryptically 
named .html (etc.) files. I guess it was "debug" I grepped for, and 
there did seem to be the information we'd want. I haven't done anything 
about extracting the relevant parts - there's a *lot* besides the debug 
info specs!!!

I found a "Specs.chm" online, here:

<http://tampa.mikeyv.net/diskcopy/Microsoft/Visual%20Studio%2060/DN60AENU2/MSDN/>

It may be too old to be useful(???) - 1998. I think what I've got is 
newer... I understand they keep changing the spec from version to 
version. This may be a problem! Maybe someone who uses and is familiar 
with VS knows what we need. I'm clueless.

Would sure be nice to have Nasm and/or Yasm and/or Fasm have this ability!

Best,
Frank

Thanks, Frank and Randy !

I'm taking a look at
http://tampa.mikeyv.net/diskcopy/Microsoft/Visual%20Studio%2060/DN60AENU2/MSDN/
right now, and no, I don't belong to the "club" - can't afford it,
y'know, a student, working, living a third world country, and all that
:(

If there's any new site that you can find online, mind if you drop me a
line or two, please ?

Thanks again !!



Frank Kotler wrote:
> spamtrap@crayne.org wrote:
> > Just an ignorant question:
> >
> >
> >         Does anyone here know of where to obtain the
> >         documentation regarding the format and/or relevant
> >         data that visual debugger uses ?
>
> Supposed to be in "Specs.chm" - available on a CD (but not online?)... I
> think you have to join their club. A friend sent me a copy... I'd be
> glad to pass it on... I've "decompiled" it into a bunch of cryptically
> named .html (etc.) files. I guess it was "debug" I grepped for, and
> there did seem to be the information we'd want. I haven't done anything
> about extracting the relevant parts - there's a *lot* besides the debug
> info specs!!!
>
> I found a "Specs.chm" online, here:
>
> <http://tampa.mikeyv.net/diskcopy/Microsoft/Visual%20Studio%2060/DN60AENU2/MSDN/>
>
> It may be too old to be useful(???) - 1998. I think what I've got is
> newer... I understand they keep changing the spec from version to
> version. This may be a problem! Maybe someone who uses and is familiar
> with VS knows what we need. I'm clueless.
>
> Would sure be nice to have Nasm and/or Yasm and/or Fasm have this ability!
> 
> Best,
> Frank

Searching the net I found a site carrying kinda similar listing - can
you check them out for me if the specs.chm is the file I'm looking for,
and/or if it is a newer version ?

http://secundus.stunet.tu-freiberg.de/mirror/lehre/cd_data/msdn1001/MSDN/


Many thanks !!


randyhyde@earthlink.net wrote:
> spamtrap@crayne.org wrote:
> > Just an ignorant question:
> >
> >
> >         Does anyone here know of where to obtain the
> >         documentation regarding the format and/or relevant
> >         data that visual debugger uses ?
>
> IIRC, it's found on MSDN. Frank Kotler turned me on to it at one time.
> I don't have the documentation name with me (it's at home), but I can
> assure you that the document does exist. Maybe Frank can recall the
> name before I get home and find the stuff.
> Cheers,
> Randy Hyde

On Thu, 20 Oct 2005 19:04:40 +0000 (UTC), Frank Kotler
<spamtrap@crayne.org> wrote:

>spamtrap@crayne.org wrote:
>> Just an ignorant question:
>> 
>> 
>>         Does anyone here know of where to obtain the
>>         documentation regarding the format and/or relevant
>>         data that visual debugger uses ?
>
>Supposed to be in "Specs.chm" - available on a CD (but not online?)... I 
>think you have to join their club. A friend sent me a copy... I'd be 
>glad to pass it on... I've "decompiled" it into a bunch of cryptically 
>named .html (etc.) files. I guess it was "debug" I grepped for, and 
>there did seem to be the information we'd want. I haven't done anything 
>about extracting the relevant parts - there's a *lot* besides the debug 
>info specs!!!
>
>I found a "Specs.chm" online, here:
>
><http://tampa.mikeyv.net/diskcopy/Microsoft/Visual%20Studio%2060/DN60AENU2/MSDN/>

I just checked.  The VC++ 5.0 specs are in there.  Apparantly in the
'D2' directory, after you decompile it.  Also, the PE COFF format
info, if I read the headings correctly.  And a whole bunch of other
interesting things.

I found the .CHI file, but can't download it:
http://tampa.mikeyv.net/diskcopy/Microsoft/Visual%20Studio%2060/DN60AENU1/MSDN/
which makes using the .CHM file difficult.

>It may be too old to be useful(???) - 1998. I think what I've got is 
>newer... 
Probably not - it's still Revision 5, which matches the latest that I
have seen, which is 04/2001.

>I understand they keep changing the spec from version to 
>version. This may be a problem! Maybe someone who uses and is familiar 
>with VS knows what we need. I'm clueless.
>
>Would sure be nice to have Nasm and/or Yasm and/or Fasm have this ability!
Yes.

-- 
ArarghMail510 at [drop the 'http://www.' from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html

To reply by email, remove the garbage from the reply address.

On Fri, 21 Oct 2005 01:11:54 +0000 (UTC), spamtrap@crayne.org wrote:

>Searching the net I found a site carrying kinda similar listing - can
>you check them out for me if the specs.chm is the file I'm looking for,
>and/or if it is a newer version ?
>
>http://secundus.stunet.tu-freiberg.de/mirror/lehre/cd_data/msdn1001/MSDN/
Yes, same revison - 5 - , later date on the files.  I also just found
it, and checked.

Get both 'specs.chm' & 'specs.chi'.  

Then on any version of windows,  double click on the chm file.  

It's the last entry in the left hand pane.


-- 
ArarghMail510 at [drop the 'http://www.' from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html

To reply by email, remove the garbage from the reply address.

spamtrap@crayne.org wrote:

[snip]

> I just checked.  The VC++ 5.0 specs are in there.  Apparantly in the> 'D2' directory, after you decompile it.  Also, the PE COFF format
> info, if I read the headings correctly.  And a whole bunch of other
> interesting things.
> 
> I found the .CHI file, but can't download it:
> http://tampa.mikeyv.net/diskcopy/Microsoft/Visual%20Studio%2060/DN60AENU1/MSDN/
> which makes using the .CHM file difficult.
> 
>>It may be too old to be useful(???) - 1998. I think what I've got is 
>>newer... 
> 
> Probably not - it's still Revision 5, which matches the latest that I
> have seen, which is 04/2001.

Nevertheless, it seems likely that we need a later version since we
would now need to cope with 64-bit systems as well as 32-bit ones (the
spec referenced above seems to be for 32-bit systems).

It would hence be useful to understand what is on offer on the MSDN
documentation that sits alongside the soon to be released Visual Studio
..Net 2005.

    Brian Gladman