Sign in Join

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

Mailing lists / lazarus / 2011-06

Debugging problem

10 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

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

Roland Turcan

Hello all,

I have FPC r17690 and Lazarus r31132 on Mac OS X 10.5.8 with all updates and I cannot debug any thread, it crashes on debugger error:

The GDB command: "-thread-info" returned the error: ",msg="Undefined mi command: thread-info (missing implementation)""

What can I do?

Thanks in advance.

Best regards, TRoland http://www.rotursoft.sk http://exekutor.rotursoft.sk -------------- next part -------------- A non-text attachment was scrubbed... Name: gdb_error.png Type: image/png Size: 27785 bytes Desc: not available URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110608/883abd76/attachment-0001.png>

Reply by email

Martin
to Roland Turcan
Roland Turcan wrote 10 lines
Hello all, I have FPC r17690 and Lazarus r31132 on Mac OS X 10.5.8 with all updates and I cannot debug any thread, it crashes on debugger error: The GDB command: "-thread-info" returned the error: ",msg="Undefined mi command: thread-info (missing implementation)"" What can I do?

First of all: You do get that msg, if you open the threads window? Or always?
Only for apps using threads, or for other apps too?

If always and for none threaded apps too, then open the history window, and disable it's power button.

Reason I ask: I can get that error in gdb, and it does prevent threads from being shown. But I do not get an "oops error state" due to it.

The current state of the implementation of the thread window is, that it uses the newer --thread-info command. But that does not exist in older gdb (and yes, I know on Mac you don't have a newer gdb). So with older gdb (including Mac) the thread window will currently stay empty.

I do not know, why in your case it causes the "error sate", that is not supposed to happen (and as I said, I can not reproduce that here, using an older gdb).
Could you please create a "Log File" (--debug-log), using a Lazarus compiled with "-dDBG_VERBOSE -dDBGMI_QUEUE_DEBUG " as described on http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Log_info_for_debug_session

Do you have a 32 or 64bit cpu?

----
As for the implementation of threads for Mac. I do not yet have a timeplan on it.
See gdbmidebugger.pp line 1835
function TGDBMIDebuggerCommandThreads.DoExecute: Boolean;

There is a comment.
Need to implement fallback to the older command, and a parser for the result....

Reply by email

Roland Turcan
to Roland Turcan: I have FPC r17690 and Lazarus r31132 on Mac OS X 10.5.8 with all updates and I cannot…

Hello all,

This error occurs in non-threaded code as well.

TRoland;

<<< 08.06.2011 13:54 - Roland Turcan "" >>>
RT> Hello all,

RT> I have FPC r17690 and Lazarus r31132 on Mac OS X 10.5.8 with all RT> updates and I cannot debug any thread, it crashes on debugger error:

RT> The GDB command: "-thread-info" returned the error: RT> ",msg="Undefined mi command: thread-info (missing implementation)""

RT> What can I do?

RT> Thanks in advance.

Reply by email

Martin
to Roland Turcan
Roland Turcan wrote
Hello all, This error occurs in non-threaded code as well.

What happens , if you power off the "history" window?

Yes I know, it isn't convenient, as their is no persistent setting...

but the issue needs to be fixed in the threads code, anyway... For that I will need the log file, please

Show quoted text 19 lines
TRoland; <<< 08.06.2011 13:54 - Roland Turcan "">>> RT> Hello all, RT> I have FPC r17690 and Lazarus r31132 on Mac OS X 10.5.8 with all RT> updates and I cannot debug any thread, it crashes on debugger error: RT> The GDB command: "-thread-info" returned the error: RT> ",msg="Undefined mi command: thread-info (missing implementation)"" RT> What can I do? RT> Thanks in advance.

Reply by email

Martin
to Martin

Ok, I can reproduce.

Mac GdB outputs an extra line ^error"

which is the problem....

Martin wrote 39 lines
On 08/06/2011 13:45, Roland Turcan wrote: > Hello all, > > This error occurs in non-threaded code as well. What happens , if you power off the "history" window? Yes I know, it isn't convenient, as their is no persistent setting... but the issue needs to be fixed in the threads code, anyway... For that I will need the log file, please > TRoland; > > <<< 08.06.2011 13:54 - Roland Turcan "">>> > RT> Hello all, > > RT> I have FPC r17690 and Lazarus r31132 on Mac OS X 10.5.8 with all > RT> updates and I cannot debug any thread, it crashes on debugger > error: > > RT> The GDB command: "-thread-info" returned the error: > RT> ",msg="Undefined mi command: thread-info (missing implementation)"" > > RT> What can I do? > > RT> Thanks in advance. > > > > > -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Roland Turcan
to Martin

Hello Martin,

Thanks you were faster than me, I was just going to reproduce.

Can you fix and commit it into svn?

TRoland;

<<< 08.06.2011 15:08 - Martin "" >>>
M> Ok, I can reproduce.

M> Mac GdB outputs an extra line ^error"

M> which is the problem....

Martin wrote 39 lines
> On 08/06/2011 13:45, Roland Turcan wrote: >> Hello all, >> >> This error occurs in non-threaded code as well. > > What happens , if you power off the "history" window? > > Yes I know, it isn't convenient, as their is no persistent setting... > > but the issue needs to be fixed in the threads code, anyway... > For that I will need the log file, please > >> TRoland; >> >> <<< 08.06.2011 13:54 - Roland Turcan "">>> >> RT> Hello all, >> >> RT> I have FPC r17690 and Lazarus r31132 on Mac OS X 10.5.8 with all >> RT> updates and I cannot debug any thread, it crashes on debugger >> error: >> >> RT> The GDB command: "-thread-info" returned the error: >> RT> ",msg="Undefined mi command: thread-info (missing implementation)"" >> >> RT> What can I do? >> >> RT> Thanks in advance. >> >> >> >> >> > > > -- > _______________________________________________ > Lazarus mailing list > > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

M> --
M> _______________________________________________ M> Lazarus mailing list
M>
M> http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Erwin van den Bosch
to Martin: Ok, I can reproduce. Mac GdB outputs an extra line ^error" which is the problem....

Hello group,

I'm trying to convert some Delphi component to Lazarus. But without much success.
It's an Edit control with buttons in it and a dropdown panel. Just like a combobox. I use this component for creating date selection controls and custom lookup comboboxes.

It uses some windows specific calls. I need some help to convert/rewrite it under Lazarus. I would be very happy if I can get it to work under Windows and Linux but for now Windows only is good enough. I'm porting a one million lines project from Delphi to Lazarus and these custom components are very important for that project.

I have written a small Delphi app/unit with the main functionality. (Delphi 2007)

http://download.fpc-lazarus.nl/DropdownCtrl.rar

There is a compiled exe included. Please take a look at the code. Can it be done with Lazarus?

Thanks!

Regards,
Erwin van den Bosch

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110608/1330ba28/attachment-0001.html>

Reply by email

Graeme Geldenhuys
to Erwin van den Bosch

2011/6/8 Erwin van den Bosch :

It uses some windows specific calls. I need some help to convert/rewrite it under Lazarus. I would be very happy if I can get it to work under Windows and Linux but for now Windows only is good enough.

Unfortunately I can't commend on LCL, but I can say it would be rather easy to implement in fpGUI. I think it should be quipe doable in LCL too.

Issues with your component:
Running the sample application you gave, your component has some rather odd behaviour. Click the 'v' to get the dropdown panel to appear. Now drag the main form away. Your dropdown panel stays in limbo, and don't close on loosing mouse focus.

Regards, ? - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://fpgui.sourceforge.net

Reply by email

Erwin van den Bosch
to Graeme Geldenhuys
Graeme Geldenhuys wrote
Unfortunately I can't commend on LCL, but I can say it would be rather easy to implement in fpGUI. I think it should be quipe doable in LCL too.

Graeme, I don't know much about fpGui. I will look at fpGui.

Show quoted text 6 lines
Issues with your component: Running the sample application you gave, your component has some rather odd behaviour. Click the 'v' to get the dropdown panel to appear. Now drag the main form away. Your dropdown panel stays in limbo, and don't close on loosing mouse focus.

You are right. But I stripped down the component. Removed a lot of code to make it easier to focus on the essential parts of this component. What I need is a way to:
- View the dropdown panel but the focus must stay in the edit control
- The panel must be on top of the window and stay on top
- The window must keep the focus (stay active window)
- The panel may display itself over the border of the window
- Shadow is nice but not needed
- Buttons in the edit control is nice but they can also be on the right site near the edit.

Regards, Erwin

Reply by email

Graeme Geldenhuys
to Erwin van den Bosch
Erwin van den Bosch wrote
You are right. But I stripped down the component. Removed a lot of code to make it easier to focus on the essential parts of this component.

Ah, that would explain it. :-)

What I need is a way to:

...snip...

That is exactly how I implemented the fpGUI's ComboBox, CalendarCombo, CalculatorCombo etc. I'm pretty sure LCL's custom drawing API should be able to accomplish the same.

Regards,
- Graeme -

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

Reply by email