Home
| Search
| C & C++
| D
| DMDScript
| News Groups
| index
| prev
| next
|
Archives
D Programming
DD.gnu digitalmars.D digitalmars.D.bugs digitalmars.D.dtl digitalmars.D.dwt digitalmars.D.announce digitalmars.D.learn digitalmars.D.debugger C/C++ Programming
c++c++.announce c++.atl c++.beta c++.chat c++.command-line c++.dos c++.dos.16-bits c++.dos.32-bits c++.idde c++.mfc c++.rtl c++.stl c++.stl.hp c++.stl.port c++.stl.sgi c++.stlsoft c++.windows c++.windows.16-bits c++.windows.32-bits c++.wxwindows digitalmars.empire digitalmars.DMDScript |
c++ - microEmacs
I'm not sure if I should post this here, but anyway... Walter, microEmacs doesn't work well. Only medos.exe and melinux work properly, and this one without colors. But neither men.exe or mex.exe work: both fail to load. Tested with DMC 8.41 on Windows XP Pro SP2, and gcc3.3 on Fedora Core 2. ------------------- Carlos Santander B. Oct 25 2004
"Carlos Santander B." <Carlos_member pathlink.com> wrote in message news:clj9as$2j4t$1 digitaldaemon.com...I'm not sure if I should post this here, but anyway... Walter, microEmacs doesn't work well. Only medos.exe and melinux work Oct 25 2004
In article <cljfkn$2qvv$1 digitaldaemon.com>, Walter says..."Carlos Santander B." <Carlos_member pathlink.com> wrote in message news:clj9as$2j4t$1 digitaldaemon.com...I'm not sure if I should post this here, but anyway... Walter, microEmacs doesn't work well. Only medos.exe and melinux work Oct 25 2004
"Carlos Santander B." <Carlos_member pathlink.com> wrote in message news:cljr6r$90j$1 digitaldaemon.com...In article <cljfkn$2qvv$1 digitaldaemon.com>, Walter says..."Carlos Santander B." <Carlos_member pathlink.com> wrote in message news:clj9as$2j4t$1 digitaldaemon.com...I'm not sure if I should post this here, but anyway... Walter, microEmacs doesn't work well. Only medos.exe and melinux work Oct 25 2004
In article <clk1cl$gdq$1 digitaldaemon.com>, Walter says..."Carlos Santander B." <Carlos_member pathlink.com> wrote in message news:cljr6r$90j$1 digitaldaemon.com...In article <cljfkn$2qvv$1 digitaldaemon.com>, Walter says..."Carlos Santander B." <Carlos_member pathlink.com> wrote in message news:clj9as$2j4t$1 digitaldaemon.com...I'm not sure if I should post this here, but anyway... Walter, microEmacs doesn't work well. Only medos.exe and melinux work Oct 25 2004
"Walter" <newshound digitalmars.com> escribió en el mensaje news:clk1cl$gdq$1 digitaldaemon.com... | | "Carlos Santander B." <Carlos_member pathlink.com> wrote in message | news:cljr6r$90j$1 digitaldaemon.com... | > In article <cljfkn$2qvv$1 digitaldaemon.com>, Walter says... | > >"Carlos Santander B." <Carlos_member pathlink.com> wrote in message | > >news:clj9as$2j4t$1 digitaldaemon.com... | > >> I'm not sure if I should post this here, but anyway... | > >> Walter, microEmacs doesn't work well. Only medos.exe and melinux work | > >properly, | > >> and this one without colors. But neither men.exe or mex.exe work: both | > >fail to | > >> load. | > >> Tested with DMC 8.41 on Windows XP Pro SP2, and gcc3.3 on Fedora Core | 2. | > > | > >I use men.exe every day. What exactly happens when it "fails to load"? | > For mex.exe, there is no file cx.obj, so the linker doesn't produce a | valid | > application. | | You need to download the dos extender from www.dosextender.com to link with. | The linker complains with this: ibmpc.obj Offset 0000CH Record Type 0088 Warning 169: Memory Model Conflict mouse.obj Offset 0000CH Record Type 0088 Warning 169: Memory Model Conflict Over 20 similar to this: c:\devtools\dm\bin\..\lib\SDX.lib(NMALLOC) Offset 02200H Record Type 0090 Error 1: Previous Definition Different : __allocinit And finally this: c:\devtools\dm\bin\..\lib\user32.lib Error 43: Not a Valid Library File | > For men.exe, men.def requires a file ntstub.exe, which doesn't exist | either. If | > I remove that line from men.def, when I run men.exe I get "The instruction | in | > 0x00403915... Memory can't be writen...". | | You can use any DOS program as the stub. ntstub.exe is part of the Digital | Mars CD. I've attached it. It's 97 bytes <g>. | | | That didn't work either. Same problem as before (without ntstub.exe). ----------------------- Carlos Santander Bernal Oct 25 2004
user32.lib should not be linked in with a DOS extender application. user32.lib is only for Win32 apps. It seems to me that somehow, your build process is mixing up commands to build the mex and men. Either that or you didn't 'clean' the directory when switching building from one to the other. "Carlos Santander B." <carlos8294 msn.com> wrote in message news:clk4e5$jru$1 digitaldaemon.com..."Walter" <newshound digitalmars.com> escribió en el mensaje news:clk1cl$gdq$1 digitaldaemon.com... | | "Carlos Santander B." <Carlos_member pathlink.com> wrote in message | news:cljr6r$90j$1 digitaldaemon.com... | > In article <cljfkn$2qvv$1 digitaldaemon.com>, Walter says... | > >"Carlos Santander B." <Carlos_member pathlink.com> wrote in message | > >news:clj9as$2j4t$1 digitaldaemon.com... | > >> I'm not sure if I should post this here, but anyway... | > >> Walter, microEmacs doesn't work well. Only medos.exe and melinux Oct 26 2004
"Walter" <newshound digitalmars.com> escribió en el mensaje
news:clm1kj$2rvp$1 digitaldaemon.com...
| user32.lib should not be linked in with a DOS extender application.
| user32.lib is only for Win32 apps. It seems to me that somehow, your build
| process is mixing up commands to build the mex and men. Either that or you
| didn't 'clean' the directory when switching building from one to the other.
|
Now I made sure to "make clean" before "make mex" and before "make men". Both
compiled and linked well.
Running mex:
INTERRUPT 0DH, GENERAL PROTECTION FAULT possible illegal address
error code = 0000
eax = 00013E00 esi = 000100C7 flags = 3246 ds = 017F
ebx = FABB0005 edi = 000000C0 eip = 00003FB8 es = 01C7
ecx = 00000000 ebp = 00C09FFF cs = 019F fs = 01AF
edx = 00000000 esp = 00000112 ss = 017F gs = 0000
Running men: same as before ("The instruction in 0x00403915... Memory can't be
writen..."). If you read closely, you'll notice it's the same address as before.
-----------------------
Carlos Santander Bernal
Oct 26 2004
"Carlos Santander B." <carlos8294 msn.com> wrote in message news:clmish$g6h$1 digitaldaemon.com..."Walter" <newshound digitalmars.com> escribió en el mensaje news:clm1kj$2rvp$1 digitaldaemon.com... | user32.lib should not be linked in with a DOS extender application. | user32.lib is only for Win32 apps. It seems to me that somehow, your Oct 27 2004
"Walter" <newshound digitalmars.com> escribió en el mensaje
news:clpb9f$i1b$1 digitaldaemon.com...
|
| "Carlos Santander B." <carlos8294 msn.com> wrote in message
| news:clmish$g6h$1 digitaldaemon.com...
| > Running men: same as before ("The instruction in 0x00403915... Memory
| can't be
| > writen..."). If you read closely, you'll notice it's the same address as
| before.
|
| What happens when you run men.exe under the debugger?
|
|
Oddly, um, it runs. But outside the debugger, I keep getting the same error.
-----------------------
Carlos Santander Bernal
Nov 06 2004
"Carlos Santander B." <carlos8294 msn.com> wrote in message news:cmjfsd$2s00$1 digitaldaemon.com... Nov 06 2004
"Walter" <newshound digitalmars.com> escribió en el mensaje news:cmjt3p$au8$2 digitaldaemon.com... | | "Carlos Santander B." <carlos8294 msn.com> wrote in message | news:cmjfsd$2s00$1 digitaldaemon.com... | > Oddly, um, it runs. But outside the debugger, I keep getting the same | error. | | Hmm. Sounds like it might be an uninitialized data problem. | | So, is it a programming error, a compiler error...? ----------------------- Carlos Santander Bernal Nov 09 2004
"Carlos Santander B." <carlos8294 msn.com> wrote in message news:cmrjtm$2eck$1 digitaldaemon.com..."Walter" <newshound digitalmars.com> escribió en el mensaje news:cmjt3p$au8$2 digitaldaemon.com... | | "Carlos Santander B." <carlos8294 msn.com> wrote in message | news:cmjfsd$2s00$1 digitaldaemon.com... | > Oddly, um, it runs. But outside the debugger, I keep getting the same | error. | | Hmm. Sounds like it might be an uninitialized data problem. | | So, is it a programming error, a compiler error...? Nov 09 2004
|