Sign in Join

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

Mailing lists / lazarus / 2014-04

Funny bug

7 messages · 6 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,

Just encountered this rather nice bug:

Debugging a project in Lazarus, linux.

I have in "Run Parameters"
Command-line parameters: "https://www.google.be/ out"

I copy all sources to windows, open the project start debugging. And get an error. Wondering what it is, I see that the command-line parameters setting was changed to

Command-line parameters: "https:\\www.google.be\ out"

Which is of course wrong...

I understand where it comes from, but do suggest to leave the entry in this box alone...

Michael.

Reply by email

zeljko
to Michael Van Canneyt
Michael Van Canneyt wrote 21 lines
Hi, Just encountered this rather nice bug: Debugging a project in Lazarus, linux. I have in "Run Parameters" Command-line parameters: "https://www.google.be/ out" I copy all sources to windows, open the project start debugging. And get an error. Wondering what it is, I see that the command-line parameters setting was changed to Command-line parameters: "https:\\www.google.be\ out" Which is of course wrong... I understand where it comes from, but do suggest to leave the entry in this box alone...

Or at least recognize "https:" and don't touch.

z.

Reply by email

Mattias Gaertner
to Michael Van Canneyt: Just encountered this rather nice bug: Debugging a project in Lazarus, linux. I have in…
Show quoted text 17 lines
Hi, Just encountered this rather nice bug: Debugging a project in Lazarus, linux. I have in "Run Parameters" Command-line parameters: "https://www.google.be/ out" I copy all sources to windows, open the project start debugging. And get an error. Wondering what it is, I see that the command-line parameters setting was changed to Command-line parameters: "https:\\www.google.be\ out" Which is of course wrong... I understand where it comes from, but do suggest to leave the entry in this box alone...

Under Linux '\' are converted when running with the gdb debugger.
It does not happen when running with the 'none' debugger.

Maybe this gives Martin an idea.

Mattias

Reply by email

Mark Morgan Lloyd
to zeljko: Or at least recognize "https:" and don't touch. z.
zeljko wrote 8 lines
> Command-line parameters: "https:\\www.google.be\ out" > > Which is of course wrong... > > I understand where it comes from, but do suggest to leave the entry in > this box alone... Or at least recognize "https:" and don't touch.

I think that might be a plausible rule for all places where slashes are munged, since most UIs now understand this type of "protocol" prefix.

Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues]

Reply by email

Michael Van Canneyt
to zeljko: Or at least recognize "https:" and don't touch. z.
zeljko wrote 24 lines
On 04/11/2014 10:45 AM, Michael Van Canneyt wrote: > > Hi, > > Just encountered this rather nice bug: > > Debugging a project in Lazarus, linux. > > I have in "Run Parameters" > Command-line parameters: "https://www.google.be/ out" > > I copy all sources to windows, open the project start debugging. And get > an error. > Wondering what it is, I see that the command-line parameters setting was > changed to > > Command-line parameters: "https:\\www.google.be\ out" > > Which is of course wrong... > > I understand where it comes from, but do suggest to leave the entry in > this box alone... Or at least recognize "https:" and don't touch.

Indeed, some kind of protocol/URI recognition would be nice.

Michael.

Reply by email

Martin Frb
to Mattias Gaertner: On Fri, 11 Apr 2014 10:45:12 +0200 (CEST) Under Linux '\' are converted when running with…
Mattias Gaertner wrote 6 lines
Under Linux '\' are converted when running with the gdb debugger. It does not happen when running with the 'none' debugger. Maybe this gives Martin an idea.

Confirmed, or rather, they are in most cases dropped.

That is a different issue though. And they do not get changed from \ to /

The problem is that gdb sees them as escape char.

<-exec-arguments -a /b \c \/d>
^done
(gdb)

and the app will see
-a /b c /b

I will ave to test this across different versions of gdb, to make sure, that a fix will not break some versions.

Reply by email