Recent

Author Topic: Debugger error on win32  (Read 10715 times)

Slow

  • Guest
Debugger error on win32
« on: April 24, 2005, 01:09:19 pm »
When I run the project (F9) I got the message "Ooops, the debugger entered the error state Save your work now !"
Someone can help me?
Thanks

glober

  • Full Member
  • ***
  • Posts: 130
Debugger error on win32
« Reply #1 on: April 24, 2005, 07:55:43 pm »
I don't think the message actually refers to anything important.
I got rid of the message on my system by getting a newer version of
the "gdb" debugger.  BTW, I am running Gentoo Linux, not sure which
 debuggers are used on windows. You can see what you are using under
Environment > Debugger Options > General.

Marc

  • Administrator
  • Hero Member
  • *
  • Posts: 2584
Debugger error on win32
« Reply #2 on: April 26, 2005, 06:47:35 pm »
it means that Lazarus got an output from gdb which was unexpected, so it cannot continue
//--
{$I stdsig.inc}
//-I still can't read someones mind
//-Bugs reported here will be forgotten. Use the bug tracker

Anonymous

  • Guest
Debugger error on win32
« Reply #3 on: June 20, 2006, 01:38:32 pm »
I'm also having this problem. I can't even run a simple, blank project inside lazarus (though building the project and running it outside of lazarus is fine).

I'm running windows 2003, 64bit (on an Athlon 64).

Marc

  • Administrator
  • Hero Member
  • *
  • Posts: 2584
Debugger error on win32
« Reply #4 on: June 20, 2006, 04:28:23 pm »
can you show us the last lines of the debugger output (view -> debugger -> debugger output)
//--
{$I stdsig.inc}
//-I still can't read someones mind
//-Bugs reported here will be forgotten. Use the bug tracker

mathx

  • Newbie
  • Posts: 5
Debugger error on win32
« Reply #5 on: June 21, 2006, 02:13:14 pm »
Here it is:
Quote

<info file>
&"info file\n"

~"Symbols from \"G:/000/000/project1.exe\".\n"

~"Local exec file:\n"

~"\t`G:/000/000/project1.exe', file type pei-i386.\n"

~"\tEntry point: $40100c\n"

~"\t$00401000 - $005057c0 is .text\n"

~"\t$00506000 - $0057c930 is .data\n"

~"\t$0057d000 - $00590e96 is .bss\n"

~"\t$00591000 - $00593b00 is .idata\n"

^done

(gdb)

<-exec-run>
^running

(gdb)

&"Error: dll starting at 0x78d41000 not found.\n"

&"\n"

Marc

  • Administrator
  • Hero Member
  • *
  • Posts: 2584
Debugger error on win32
« Reply #6 on: June 21, 2006, 03:07:06 pm »
Quote

&"Error: dll starting at 0x78d41000 not found.\n"


eehhhhh..... this means that some OS dll couldn't be loaded/found. I never saw this before.
I looked at my XP and I couldn't find a dll loaded at that space. (the closest was at 0x7800000)

What OS are you using and does runnint project1.exe work ?
//--
{$I stdsig.inc}
//-I still can't read someones mind
//-Bugs reported here will be forgotten. Use the bug tracker

mathx

  • Newbie
  • Posts: 5
Debugger error on win32
« Reply #7 on: June 21, 2006, 10:03:49 pm »
I'm running Windows Server 2003, standard edition (x64 edition). Running project1 from windows explorer is fine, the problem seems to be running it inside the lazarus IDE...

update: Aparently this has has already been reported here before.

Also, I found this page about this error on stand alone GDB...[/url]

CCRDude

  • Hero Member
  • *****
  • Posts: 600
Debugger error on win32
« Reply #8 on: June 22, 2006, 08:10:30 pm »
Oh, that error... I've got the same (also same address) on XP Pro 64 bit edition... I always assumed that it was related to the 64 bit OS and used the chance to spend more time on thinking and less on debugging :D (well, or I'm Delphi-spoiled, where the debugger was so buggy - jumping into lines of closed other projects while debugging - that I found no debugging at all more refreshing ;) ).

Marc

  • Administrator
  • Hero Member
  • *
  • Posts: 2584
Debugger error on win32
« Reply #9 on: June 23, 2006, 10:46:01 am »
Quote from: "mathx"
I'm running Windows Server 2003, standard edition (x64 edition). Running project1 from windows explorer is fine, the problem seems to be running it inside the lazarus IDE...

update: Aparently this has has already been reported here before.

Also, I found this page about this error on stand alone GDB...[/url]


Thanks for the site. I'll do some test on XP64 with a 32bit gdb.
If it fails, there is one more reason for an internal debugger.
//--
{$I stdsig.inc}
//-I still can't read someones mind
//-Bugs reported here will be forgotten. Use the bug tracker

 

TinyPortal © 2005-2018