Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2015-04

GDB problem ?

6 messages · 4 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Michael Van Canneyt

Hi,

All of a sudden (no idea why), gdb stopped working on a particular program I was working on. I found the following error in the debug output:

(gdb)
=thread-exited,id="1",group-id="i1"
=thread-group-exited,id="i1"
^error,msg="During startup program exited with code 1." (gdb)

Impossible to debug after this:

(gdb)
<-exec-continue>
^error,msg="The program is not being run."
(gdb)

Running the same program in the gdb debugger manually does not produce this error. Any idea what anomaly can explain this ?

Restarting IDE, debugger: none of that helped.

Michael.

Reply by email

Graeme Geldenhuys
to Michael Van Canneyt
Michael Van Canneyt wrote
Restarting IDE, debugger: none of that helped.

Call it coincidence, but I've yesterday had some GDB issues via the IDE too. I switched to the fpdebugger and could continue again without problems.

You could possibly try that as a work-around.

I haven't actually switched back to GDB today yet, so I don't know if yesterday's issue magically fixed itself over night. You know that self-healing software feature is awesome. ;-)

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/

Reply by email

Martin Frb
to Michael Van Canneyt: All of a sudden (no idea why), gdb stopped working on a particular program I was working…
Michael Van Canneyt wrote 11 lines
Hi, All of a sudden (no idea why), gdb stopped working on a particular program I was working on. I found the following error in the debug output: (gdb) =thread-exited,id="1",group-id="i1" =thread-group-exited,id="i1" ^error,msg="During startup program exited with code 1." (gdb)

Dont know, never seen, but try the following:

http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#gdb.exe_has_stopped_working go to the debugger options and set the field
"DisableLoadSymbolsForLibraries" to "True"

And/Or change the the "InternalStartBreak" Try MainAddr, or Entry.

Reply by email

Den
to Michael Van Canneyt: All of a sudden (no idea why), gdb stopped working on a particular program I was working…

I've been having this problem on my Game Project for the longest time! .. Same error.. Just started happening one day. I had wrote a message one time about it on this list, remember Martin?

- Dennis

Michael Van Canneyt wrote 31 lines
Hi, All of a sudden (no idea why), gdb stopped working on a particular program I was working on. I found the following error in the debug output: (gdb) =thread-exited,id="1",group-id="i1" =thread-group-exited,id="i1" ^error,msg="During startup program exited with code 1." (gdb) Impossible to debug after this: (gdb) <-exec-continue> ^error,msg="The program is not being run." (gdb) Running the same program in the gdb debugger manually does not produce this error. Any idea what anomaly can explain this ? Restarting IDE, debugger: none of that helped. Michael. -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Martin Frb
to Den

Well I dont get the issue myself, so I canonly give generic advice.

To try and trace the problem, since it seems only when called by the IDE:

Open the "Debug Output" window, and see all the commands the IDE sent.

Start gdb
gdb -i mi

And repeat the commands. That should get you the error. Now try to find which one causes it.

Also of course make sure it is not the Antivirus (that may make a difference between gdb in started by hand, or started by the IDE.

Den wrote 45 lines
I've been having this problem on my Game Project for the longest time! .. Same error.. Just started happening one day. I had wrote a message one time about it on this list, remember Martin? - Dennis On 2015-04-28 04:23 AM, Michael Van Canneyt wrote: > > Hi, > > All of a sudden (no idea why), gdb stopped working on a particular > program I was working on. I found the following error in the debug > output: > > (gdb) =thread-exited,id="1",group-id="i1" > =thread-group-exited,id="i1" > ^error,msg="During startup program exited with code 1." > (gdb) > > Impossible to debug after this: > > (gdb) <-exec-continue> > ^error,msg="The program is not being run." > (gdb) > > Running the same program in the gdb debugger manually does not > produce this error. > Any idea what anomaly can explain this ? > > Restarting IDE, debugger: none of that helped. > > Michael. > > -- > _______________________________________________ > Lazarus mailing list > > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Michael Van Canneyt
to Martin Frb: Dont know, never seen, but try the following:…
Martin Frb wrote 19 lines
On 28/04/2015 10:23, Michael Van Canneyt wrote: > > Hi, > > All of a sudden (no idea why), gdb stopped working on a particular program > I was working on. I found the following error in the debug output: > > (gdb) =thread-exited,id="1",group-id="i1" > =thread-group-exited,id="i1" > ^error,msg="During startup program exited with code 1." > (gdb) Dont know, never seen, but try the following: http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#gdb.exe_has_stopped_working go to the debugger options and set the field "DisableLoadSymbolsForLibraries" to "True" And/Or change the the "InternalStartBreak" Try MainAddr, or Entry.

None of that was it.

The problem was in setting the command-line options. one of the special characters ? @ % & = caused an error. Quoting the command-line option containing them, helped.

Very strange indeed.

Michael.

Reply by email