News:

MASM32 SDK Description, downloads and other helpful links
MASM32.com New Forum Link
masmforum WebSite

RadASM 3.0 bugtest

Started by KetilO, May 31, 2010, 12:28:11 PM

Previous topic - Next topic

dancho

hey donkey,
assembler is fasm,
this is not problem with assembler syntax,structure is init properly,
just small bug with ide ( not referencing structure elements )...
anyway thx for your effort...

Dancho

donkey

"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable

donkey

#197
Hi Ketil,

I have been adding new build types to GoAsm.ini and find that the drop down combo box that they are selected from is a bit limiting. Is it possible to have it expanded to ensure that the longest entry name will be visible ? The same applies to the drop down on the toolbar.

These are the build types I am proposing:

[Make]
Debug=0
Run=0,'Cmd /k',''
Make=GoRC,GoAsm,GoLink,lib
Help=
0=Win32 ANSI Release,'/r "$R"',"$R.res",'/c /x86 "$C"',"$C.obj",'$C $M $R',"$C.exe",'',
1=Win32 Unicode Release,'/r "$R"',"$R.res",'/c /x86 /d UNICODE "$C"',"$C.obj",'$C $M $R',"$C.exe",'',
2=Win32 MSLU Release,'/r "$R"',"$R.res",'/c /d UNICODE "$C"',"$C.obj",'$C $M $R /mslu',"$C.exe",'',
3=DLL32 ANSI Release,'/r "$R"',"$R.res",'/c /x86 "$C"',"$C.obj",'$C $M $R /dll /entry DllEntryPoint',"$C.exe",'',
4=DLL32 Unicode Release,'/r "$R"',"$R.res",'/c /x86 /d UNICODE "$C"',"$C.obj",'$C $M $R /dll /entry DllEntryPoint',"$C.exe",'',
5=Console release,'/r "$R"',"$R.res",'/c /x86 "$C"',"$C.obj",'$C $M $R /console',"$C.exe",'',
6=Win32 ANSI Debug,'/r "$R"',"$R.res",'/c /x86 "$C"',"$C.obj",'$C $M $R /Debug coff',"$C.exe",'',
7=Win32 Unicode Debug,'/r "$R"',"$R.res",'/c /x86 /d UNICODE "$C"',"$C.obj",'$C $M $R /Debug coff',"$C.exe",'',
8=Win32 MSLU Debug,'/r "$R"',"$R.res",'/c /d UNICODE "$C"',"$C.obj",'$C $M $R /Debug coff /mslu',"$C.exe",'',
9=DLL32 ANSI Debug,'/r "$R"',"$R.res",'/c /x86 "$C"',"$C.obj",'$C $M $R /dll /entry DllEntryPoint /Debug dbg',"$C.exe",'',
10=DLL32 Unicode Debug,'/r "$R"',"$R.res",'/c /x86 /d UNICODE "$C"',"$C.obj",'$C $M $R /dll /entry DllEntryPoint /Debug dbg',"$C.exe",'',
11=Win32 Driver Release,'/r "$R"',"$R.res",'/c /x86 "$C"',"$C.obj",'$C $M $R /Driver /Entry DriverEntry',"$C.exe",'',
12=Win64 ANSI Release,'/r "$R"',"$R.res",'/c /x64 "$C"',"$C.obj",'$C $M $R',"$C.exe",'',
13=Win64 Unicode Release,'/r "$R"',"$R.res",'/c /x64 /d UNICODE "$C"',"$C.obj",'$C $M $R',"$C.exe",'',
14=DLL64 ANSI Release,'/r "$R"',"$R.res",'/c /x64 "$C"',"$C.obj",'$C $M $R /dll /entry DllEntryPoint',"$C.exe",'',
15=DLL64 Unicode Release,'/r "$R"',"$R.res",'/c /x64 /d UNICODE "$C"',"$C.obj",'$C $M $R /dll /entry DllEntryPoint',"$C.exe",'',
16=Win64 ANSI Debug,'/r "$R"',"$R.res",'/c /x64 "$C"',"$C.obj",'$C $M $R /Debug coff',"$C.exe",'',
17=Win64 Unicode Debug,'/r "$R"',"$R.res",'/c /x64 /d UNICODE "$C"',"$C.obj",'$C $M $R /Debug coff',"$C.exe",'',
18=DLL64 ANSI Debug,'/r "$R"',"$R.res",'/c /x64 "$C"',"$C.obj",'$C $M $R /dll /entry DllEntryPoint /Debug dbg',"$C.exe",'',
19=DLL64 Unicode Debug,'/r "$R"',"$R.res",'/c /x64 /d UNICODE "$C"',"$C.obj",'$C $M $R /dll /entry DllEntryPoint /Debug dbg',"$C.exe",'',
20=Library ANSI,'/r "$R"',"$R.res",'/c /x86 "$C"',"$C.obj",'',,'$C',"$C.lib"
21=Library Unicode,'/r "$R"',"$R.res",'/c /x86 /d UNICODE "$C"',"$C.obj",'',,'$C',"$C.lib"


Edgar
"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable

KetilO

Thanks Edgar

New upload.

Version 3.0.0.7h 2010-12-09
---------------------------
o Adjusted the size of some dialogs.
o Added Donkey's goasm build options and templates.

KetilO

Shooter

KetilO,
In the last entry of my post dealing with image sizes, http://www.masm32.com/board/index.php?topic=15552.0, I think that it's something you might need to help me on.

Thanks,
-Shooter
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

donkey

#200
Hi Ketil,

I've been trying to get a feel for how the internal debugger works and can't seem to get it to recognize symbol data. I keep getting the following error:

QuoteNo debug info found. Use the /Zd, /Zi and /DEBUG command line options.
C:\Programming\RadASM3\Masm\Projects\TestStrLen\TestStrLen.exe

My build is as follows:


rc /v "TestDialog.rc"
Microsoft (R) Windows (R) Resource Compiler Version 5.2.3690.0

Copyright (C) Microsoft Corporation.  All rights reserved.


Creating TestDialog.RES

Using codepage 1252 as default
RC: RCPP -CP 1252 -f C:\Programming\RadASM3\Masm\Projects\TestDialog\RCa02876 -g C:\Programming\RadASM3\Masm\Projects\TestDialog\RDa02876 -DRC_INVOKED -D_WIN32 -pc\:/ -E -I. -I . -I C:\Programming\RadASM3\masm\include -I C:\Programming\Headers

TestDialog.rc.
Writing DIALOG:1000, lang:0x409, size 110.
Writing MENU:10000, lang:0x409, size 128

ml /c /coff /Cp /Zi /Zd "TestDialog.asm"
Assembling: TestDialog.asm
Microsoft (R) Macro Assembler Version 10.00.30319.01
Copyright (C) Microsoft Corporation.  All rights reserved.


link /SUBSYSTEM:WINDOWS /DEBUG /VERSION:4.0 /OUT:"TestDialog.exe" "TestDialog.obj"  "TestDialog.res"
Microsoft (R) Incremental Linker Version 10.00.30319.01
Copyright (C) Microsoft Corporation.  All rights reserved.

LINK : TestDialog.exe not found or not built by the last incremental link; performing full link

Make done.


I also tried Embedded COFF symbols however it will not recognize those either. Since you're using DbgHelp.dll it should be able to easily handle both COFF and PDB symbols. I just can't seem to get it to work.

Edgar
"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable

Shooter

I tried to make a new project using RadASM 3.0.0.7g, "Project | New Project" with the following settings:

Programming Language: GoASM
Project Name: Shooter's Tab Demo
Project Description: Tab Strip Demo
Folder Creation:
   Project Subfolder: Checked
   Bak: Checked
   Res: Checked
   Mod: Checked
   Inc: Checked

Files (Tab):
   Code File: Checked
   Header File: Checked
   Resource File: Checked
   Text File: Not Checked

Build (Tab):
"Window Release" (Only option available, btw, how do I add to this?)

Template (Tab):
   "Win32_TemplateA.tpl"


I created a blank dialog in the .RC file. Without making changes to the code or the .RC, I attempted to compile and received this error (see attached screen shot):

"Label of this name already declared:-
?"


Is this a bug?

-Shooter
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

donkey

The template files for RadAsm were created by me.

Win32_TemplateA is creates a window application with an RC file for resources. There are no resources in the RC file when it is created since the window creation does not require them so an empty RC is created. It expects you to add resources i.e. an icon before you build it. If you wish to have a window application without any RC file use Win32_NoResA instead. For the Dialog, please post the project so I can look at why there was no ID assigned to the dialog.

Edgar
"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable

Shooter

#203
Edgar,
As requested, please see the attached .zip. I have made zero changes to the created file set from the template, except the .RC... it is as it was originally created by RadASM.

Note: I added the IDD_DLG1 to the raw, defaulted .RC before compiling.

-Shooter
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

donkey

Hi Shooter,

One of the cardinal rules in Windows is that if you insist on using spaces in file names you should enclose them in quotes. I rarely ever use spaces in project names (or files in general) so the templates don't inlcude them. Change this:

#include Shooter's Tab Demo.h

to

#include "Shooter's Tab Demo.h"

And it should work fine.

Edgar
"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable

KetilO

Hi Edgar

DbgHelp.dll
---------------------------------------------------------------------------------------------------
NOTE:
The debugger needs a recent version of dbghelp.dll to work.

o Windows Vista:
  - My Vista came with version 6.0.6001.18000. It works OK.
o Windows XP:
  - Download and install:
    http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi
    The only thing you need is DbgHelp.dll in:
    C:\Program Files\Debugging Tools for Windows (x86)\srcsrv
    Copy it to RadASM root (C:\RadASM).
o Windows 2000:
  - Not tested.
o Windows 9x and Me:
  - Not tested.
o Windows 7
   - Not tested

KetilO

donkey

Hi Ketil,

Yes, I am using the same version of DbgHelp but it wasn't in the RadAsm root folder, you probably mentioned it somewhere but I missed it as usual. However putting it in the RadAsm root folder did not change the error:

DbgHelp.dll version 6.0.6001.18000 (longhorn_rtm.080118-1840)
No debug info found. Use the /Zd, /Zi and /DEBUG command line options.
C:\Programming\RadASM3\Masm\Projects\TestDialog\TestDialog.exe
CREATE_PROCESS_DEBUG_EVENT ProcessID: 264 ThreadID: 2668


Using the latest version from the debugging tools I get the following:

DbgHelp.dll version 6.11.0001.404 (debuggers(dbg).090225-1745)
No debug info found. Use the /Zd, /Zi and /DEBUG command line options.
C:\Programming\RadASM3\Masm\Projects\TestDialog\TestDialog.exe
CREATE_PROCESS_DEBUG_EVENT ProcessID: 4492 ThreadID: 5208


I have attached a simple MASM project that gave the errors above.

Note that I ran this on Vista 32 bit.

I ran the project through a symbol viewer example I wrote and everything seems fine with the PDB:


"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable

Ya

Hi, KetilO
The the "find dialog" is invalid when open a file as hex.
                                                              (My english is very poor. :'()

Shooter

Quote from: donkey on December 09, 2010, 08:23:37 PM
One of the cardinal rules in Windows is that if you insist on using spaces in file names you should enclose them in quotes. I rarely ever use spaces in project names (or files in general) so the templates don't inlcude them. Change this:

#include Shooter's Tab Demo.h

to

#include "Shooter's Tab Demo.h"

Edgar,
As I mentioned before, I hadn't changed a thing... it was all 'default', but I'll catch it next time. :green2

-Shooter
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

KetilO

Hi Edgar

I have no idea why it does not work for you.

On XP:

DbgHelp.dll version 6.11.0001.404 (debuggers(dbg).090225-1745)
DbgHelp found 1 source files containing 55 lines and 9 symbols. 0 symbols was not found.

** Debugging started: C:\RadASM30\Masm\Projects\TestDialog\TestDialog.exe
CREATE_PROCESS_DEBUG_EVENT ProcessID: 1348 ThreadID: 2604
LOAD_DLL_DEBUG_EVENT C:\WINDOWS\system32\ntdll.dll


On Vista:

DbgHelp.dll version 6.0.6001.18000 (longhorn_rtm.080118-1840)
DbgHelp found 1 source files containing 55 lines and 9 symbols. 0 symbols was not found.

** Debugging started: C:\Downloads\TestDialog\TestDialog\TestDialog.exe
CREATE_PROCESS_DEBUG_EVENT ProcessID: 2496 ThreadID: 2704
LOAD_DLL_DEBUG_EVENT C:\Windows\system32\ntdll.dll


KetilO