64 bit : GCC/GDB

[killerbot]

Dear all,

I have recently acquired new hardware. I am running now Windows Xp 64bit and Suse 10.1 on it.
Preparing in providing also 64bit CB version (don't ask me how for the moment ... ;-)  ), I ran into some troubles.
I installed manually MinGW 3.4.5 and GDB 6.2. I can compile nicely a console app in CB, but when debugging GDB crashes on me. This crash also happens when I run GDB from the command line. Anyone outhere who has some info for me on what to do for GDB and WinXP 64bit ??

Many thanks,
Lieven

[MortenMacFly]

...this may be a stupid question: But is your version of GDB compiled against a 64bit OS? I really could imagine that this plays a role for a debugger...?!
With regards, Morten.

[killerbot]

well the GDB is the standard one from MinGW, so i assume it is a 32 bit application, as is GCC 3.4.4, 3.4.5 and 4.x ?
I don't even know if it allows to create real 64bit applications ?

Now winXp 64bit should run 32bit app's, only 32-bit services are not allowed (and all 16bit apps are also out).

On the command line I get the following error :
  Error : dll starting at 0x78d41000 not found

[MortenMacFly]

On the command line I get the following error :
  Error : dll starting at 0x78d41000 not found

...strange. Do you have an idea what DLL this is? You could try "Dependency Walker" (http://www.dependencywalker.com) which migth help to figure that out. Maybe filemon from SysInternals will help you, too (if GDB tries to access a file that does not exist or similar).
Wih regards, Morten.

[killerbot]

Good idea Morton,

I checked with both the 64-bit and 32-bit version of Dependency walker. It seems I should use the 32-bit one, because GDB.exe is a 32 bit app.

Well it claimed it was missing to dependent dll-s :
1) msjava.dll     ---> this is not needed, blablabla
2) devmgr.dll

When doing the same thing on my 32 bit winXP (on a 32 bit machine), only the msjava.dll issue remained. The devmgr.dll does exist on winXP64, but it's the 64-bit variant, so it does not work with that. All other dependent dll's for GDB.exe are placed in a "wow" directory, but that devmgr.dll is not there. I tried to copy my 32bit version next to GDB.exe, but that did not help.
Stupid me, I forgot to copy it in that "wow" dir, so that's still something to test.

And the search goes on ....

[cmaxb]

I see this error, too. Did you ever resolve it?

[killerbot]

nope, once looked at mailing lists on MinGW, they don't support 64-bit, and it seems it's not in their short term plans.

Very sad, very sad. :-(  :evil:

[cmaxb]

Dependency Walker states that devmgr.dll is an AMD64 build. Yet it resides in System32 folder. Me thinks this a Microsoft issue.

[stahta01]

I getting ready to install WinXP x64 this weekend, I hope to get C::B to work, but it does NOT sound likely from this that I will be able to get the debugger to work.  If there is any process on this please post. I will post my process to this thread if I can make any headway on getting the debugger to work.

Tim S

[stahta01]

I getting ready to install WinXP x64 this weekend, I hope to get C::B to work, but it does NOT sound likely from this that I will be able to get the debugger to work.  If there is any process on this please post. I will post my process to this thread if I can make any headway on getting the debugger to work.

Tim S

Status update deleted the wrong hard drive partition; took to long to setup WinXP 32 for me to work on AMD64 (To tired of Security updates, 60 + security updates over dial-up is not something to look forward to again.)

Note: I found that x86_64-pc-mingw64 is the name of the target for GCC to target AMD64. The thread I read said GCC 4.3 is the earliest version likely to support x86_64-pc-mingw64. So, it is possible GCC 4.4 will be when minGW starts on AMD64 using GCC 4.x.

Tim S