MagGDBp: Unable to add a breakpoint in large PHP files.

[Andreas]

Hi Robert Sesek

Thank you very much for your excellent work and the 2.0 update!

Today I faced a regression in version 2.0.

I'm unable to add breakpoints in large PHP files. For example, I tried to add a breakpoint at line 843 in a file of the Drupal Core.

Reproduce:

• Clone/Install Drupal 8 Core (https://git.drupalcode.org/project/drupal, 8.8.X);
• Go to breakpoint Tab;
• Click the `+` symbol to add a "Line Number" (breakpoint);
• Select the file in the file browser;
• Click ok;
• Nothing will happen; the file doesn't appear in the list of breakpoints.

Do I do something wrong, or is this really an issue?

Thank you very much for your response.

Best Regards,

Andreas

[Robert Sesek]

Hi Andreas,

Thanks for the report! This is indeed a regression from 1.5, so I filed https://www.bluestatic.org/bugs/showreport.php?bugid=261 to track it. I was able to reproduce the issue, identify the bug, and code up a fix: https://src.bluestatic.org/?p=macgdbp.git;a=commitdiff;h=90f34b6d84f38b6fa4bc52784a47a4a970ee3156;hp=8eef7c99bed2f60c4daf9b9afc370b0ef413bdc2.

This will included in a 2.0.1 update in the near future.

Best,

Robert

--
You received this message because you are subscribed to the Google Groups "Blue Static Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bluestatic+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bluestatic/84a11ca5-eea3-4d6d-bfdc-c52068b1cf42%40googlegroups.com.

[Andreas]

Hi Robert,

Thank you very much for your prompt reply.

I hope you can ship 2.0.1 in the next days. The new version 2.X gives me the possibility to switch back to my loved SublimeText/Vim workflow because of a stable Debug Client. I used pugdebug for a while. But because of missing maintenance, I switched to an IDE based workflow. However, I'm not the "IDE Developer." I like to do my stuff in an editor and the terminal (I know dbgpCient, but it is much more comfortable to use it with the "MacGDBp UI").

Best,

Andreas

[Robert Sesek]

Hi Andreas,

Yes, I expect to publish 2.0.1 this week.

- Robert

On Mon, Apr 6, 2020 at 7:31 AM <an.r...@gmail.com> wrote:

Hi Robert,

Thank you very much for your prompt reply.

I hope you can ship 2.0.1 in the next days. The new version 2.X gives me the possibility to switch back to my loved SublimeText/Vim because of a stable Debug Client. I used pugdebug for a while. But because of missing maintenance, I switched to an IDE based workflow. However, I'm not the "IDE Developer." I like to do my stuff in an editor and the terminal (I know dbgpCient, but it is much more comfortable to use it with the "MacGDBp UI").

Best,

Andreas

Am Montag, 6. April 2020 05:34:39 UTC+2 schrieb Robert Sesek:

Hi Andreas,

Thanks for the report! This is indeed a regression from 1.5, so I filed https://www.bluestatic.org/bugs/showreport.php?bugid=261 to track it. I was able to reproduce the issue, identify the bug, and code up a fix: https://src.bluestatic.org/?p=macgdbp.git;a=commitdiff;h=90f34b6d84f38b6fa4bc52784a47a4a970ee3156;hp=8eef7c99bed2f60c4daf9b9afc370b0ef413bdc2.

This will included in a 2.0.1 update in the near future.

Best,

Robert

On Sun, Apr 5, 2020 at 6:29 PM Andreas <an....@gmail.com> wrote:

Hi Robert Sesek

Thank you very much for your excellent work and the 2.0 update!

Today I faced a regression in version 2.0.

I'm unable to add breakpoints in large PHP files. For example, I tried to add a breakpoint at line 843 in a file of the Drupal Core.

Reproduce:

• Clone/Install Drupal 8 Core (https://git.drupalcode.org/project/drupal, 8.8.X);
• Go to breakpoint Tab;
• Click the `+` symbol to add a "Line Number" (breakpoint);
• Select the file in the file browser;
• Click ok;
• Nothing will happen; the file doesn't appear in the list of breakpoints.

Do I do something wrong, or is this really an issue?

Thank you very much for your response.

Best Regards,

Andreas

--
You received this message because you are subscribed to the Google Groups "Blue Static Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blues...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bluestatic/84a11ca5-eea3-4d6d-bfdc-c52068b1cf42%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Blue Static Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bluestatic+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bluestatic/8479caef-38ba-40ab-9167-7369267100ce%40googlegroups.com.

[Robert Sesek]

2.0.1 is now live. Thanks again for the report!

[Andreas]

Hi Robert

Thank you very much for deploying version 2.0.1.

I just want to let you know, the update procedure from 2.0 to 2.0.1 was stuck in an endless "Installing update..." step in my case.

Mac Console Output

default 09:15:58.425138+0200 symptomsd defusing ticker tickerFatal having seen progress by flow for org.bluestatic.macgdbp, rxbytes 953702 duration 9.051 seconds started at time: Tue Apr 14 09:15:49 2020

default 09:16:14.247611+0200 runningboardd Acquiring assertion targeting executable<MacGDBp(502)> from originator [daemon<com.apple.coreservices.launchservicesd>:215] with description <RBSAssertionDescriptor; frontmost:75277; ID: 386-215-43738; target: 75277> attributes = {

    <RBSDomainAttribute: 0x7ffd2453a580; domain: com.apple.launchservicesd; name: RoleUserInteractiveFocal; sourceEnvironment: 0x0>;

}

default 09:16:14.247770+0200 runningboardd Assertion 386-215-43738 (target:executable<MacGDBp(502)>) will be created as active

default 09:16:15.613090+0200 MacGDBp MacOS error: -67062

default 09:16:15.617187+0200 MacGDBp MacOS error: -67062

default 09:16:15.624048+0200 MacGDBp OK: EdDSA signature is correct

default 09:16:15.624070+0200 MacGDBp This app has a DSA public key, so a DSA signature is required too

default 09:16:15.625799+0200 MacGDBp CSSM Exception: -2147415792 CSSMERR_CSP_INVALID_KEY

default 09:16:15.631076+0200 MacGDBp UNIX error exception: 17

default 09:16:15.667920+0200 lsd Non-fatal error enumerating at <private>, continuing: Error Domain=NSCocoaErrorDomain Code=260 "The file “PlugIns” couldn’t be opened because there is no such file." UserInfo={NSURL=PlugIns/ -- file:///Users/xxx/Library/Caches/org.bluestatic.macgdbp/org.sparkle-project.Sparkle/MacGDBp%20(Autoupdate).app/, NSFilePath=/Users/xxx/Library/Caches/org.bluestatic.macgdbp/org.sparkle-project.Sparkle/MacGDBp (Autoupdate).app/PlugIns, NSUnderlyingError=0x7faffe7054e0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

default 09:16:15.669644+0200 MacGDBp bundle 0x636c mod date changed from Tue Mar 10 01:44:12 2020 to Tue Apr 14 09:16:15 2020

default 09:16:15.669744+0200 MacGDBp bundle 0x636c node has changed

default 09:16:15.680761+0200 lsd Non-fatal error enumerating at <private>, continuing: Error Domain=NSCocoaErrorDomain Code=260 "The file “PlugIns” couldn’t be opened because there is no such file." UserInfo={NSURL=PlugIns/ -- file:///Users/xxx/Library/Caches/org.bluestatic.macgdbp/org.sparkle-project.Sparkle/MacGDBp%20(Autoupdate).app/Contents/, NSFilePath=/Users/xxx/Library/Caches/org.bluestatic.macgdbp/org.sparkle-project.Sparkle/MacGDBp (Autoupdate).app/Contents/PlugIns, NSUnderlyingError=0x7fb0000c72b0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

default 09:16:16.228790+0200 runningboardd Invalidating assertion 386-215-43738 (target:executable<MacGDBp(502)>) from originator 215

default 09:16:16.339653+0200 runningboardd [executable<MacGDBp(502)>:75277] Ignoring jetsam update because this process is not memory-managed

default 09:16:16.339701+0200 runningboardd [executable<MacGDBp(502)>:75277] Set darwin role to: UserInteractiveNonFocal

default 09:16:16.339744+0200 runningboardd [executable<MacGDBp(502)>:75277] Ignoring GPU update because this process is not GPU managed

However, downloading the .zip and coping the MacGDBp.app to /Applications works as expected.

Best,

Andreas

[Robert Sesek]

Hi Andreas,

Thanks for this report as well. I do test auto-update as part of my release process, but the dev build I used for the test did not reproduce this issue. Downloading the 2.0 update directly from the website and trying to update to 2.0.1 allow me to reproduce this. This problem was the result of the auto-updater binary somehow losing its executable bit during development. I've pushed 2.0.2 to correct the problem with the binaries. You can find recovery instructions here as well: https://www.bluestatic.org/blog/2020/04/18/macgdbp-2.0.2-released/.

Best,

Robert

--

You received this message because you are subscribed to the Google Groups "Blue Static Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bluestatic+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bluestatic/f28fa9cb-605a-4048-9c22-852d66a3462a%40googlegroups.com.

[Andreas]

Hi Robert

Thank you very much for your reply and for releasing version 2.0.2.

I downloaded version 2.0.2, and now I use it quite often. During my work, I noticed, the content of the "file window" (Screenshot, red rectangle) frequently disappears when the debugger comes to its breakpoints.

I don't know whether that's wanted. I can work without but would very much appreciate it when the contents remain visible.

Best,

Andreas

[Robert Sesek]

Hi Andreas,

That is not expected. Is it only ever for specific files, or seemingly all files? If you click on a different stack frame and then re-select the stack frame for the file with the breakpoint, does the source then load?

I have not observed this issue, so if you could help narrow down the steps that cause the problem that would be helpful in debugging this.

- Robert

--
You received this message because you are subscribed to the Google Groups "Blue Static Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bluestatic+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bluestatic/f5ef5dde-8090-42ff-b58b-5d7cd6a67cc0%40googlegroups.com.

[Andreas Ruoff]

Hi Robert

Thank you very much for your reply and your patience. Unfortunately, I can't show you the effect at the moment since my MacGDBp is crashing each time I start a debug connection. However, I hadn't the time yet to investigate, but I have attached you the Crash report.

 

Would it be a good idea to move our conversation to your issue tracker (https://www.bluestatic.org/bugs/)? Should I register an account?

Best,

Andreas 

[Robert Sesek]

Hi Andreas,

Thanks for the crash report. It's fine to just use the list for this, though filing a bug also works.

I have an idea as to what's causing the crash, but I don't understand the conditions that could cause it to occur. Does this happen every time you try and debug? Did anything change about your version of Xdebug or PHP recently? The relevant-looking code in MacGDBp has not changed recently. Would you be willing to try a beta build to see if a potential fix solves the issue?

Thanks!

- Robert

--

You received this message because you are subscribed to the Google Groups "Blue Static Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bluestatic+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bluestatic/CAO5-gSr%3DKw7HX1tTGBWJwu_Q_1Db6F%3Do6Tj2mv2tsWg1Cjw8Zg%40mail.gmail.com.

[Robert Sesek]

I just released 2.0.3, which includes a speculative fix for the crash you reported. Let me know if that fixed the issue.