Bug 91780 - BASIC Debugger Stops at Incorrect Line
Summary: BASIC Debugger Stops at Incorrect Line
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
4.1.2.3 release
Hardware: x86-64 (AMD64) Linux (All)
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-31 16:24 UTC by stellarpower
Modified: 2023-12-04 03:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stellarpower 2015-05-31 16:24:47 UTC
In order to reproduce, open a new document, create a new module and add the following:

Sub foo(a as variant)
	Dim b as variant
	b = a
	msgbox("Hello, " + a)
	a.bar()
End Sub

Sub Main
	foo("World!")
End Sub


Then step into Main and into foo. On 4.1.2.3, the debugger stops at the line with the declaration of foo's arguments stating 'Object Variable Not Set'. However this error is in fact caused by attempting to call a member function on a variant containing a string and not an object.

I believe that the correct behaviour would be for the debugger to produce the error message on the line containing the call to bar as otherwise this can mislead the author from the real cause of the error - stopping on the subroutine argument list implies that there was a problem with passing the variant into the sub.
Comment 1 Buovjaga 2015-06-09 11:27:19 UTC
Reproduced "BASIC runtime error.
Object variable not set."

Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+
Build ID: d28102b1ed0c31500bbc68453a7b7613bd2bfa06
TinderBox: Win-x86@39, Branch:master, Time: 2015-06-09_01:06:39
Locale: fi-FI (fi_FI)
Comment 2 QA Administrators 2016-09-20 10:01:08 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-12-03 14:39:31 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2021-12-03 04:37:59 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2023-12-04 03:17:03 UTC
Dear stellarpower,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug