Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re: Bug 3732 #3765

Closed
vicuna opened this issue Aug 18, 2005 · 1 comment
Closed

Re: Bug 3732 #3765

vicuna opened this issue Aug 18, 2005 · 1 comment
Labels

Comments

@vicuna
Copy link

vicuna commented Aug 18, 2005

Original bug ID: 3765
Reporter: administrator
Status: closed (set by @damiendoligez on 2005-12-15T13:47:35Z)
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Child of: #3732

Bug description

Actually, in doing more work to get around this problem I've found that
the issue is more complicated. If I set a breakpoint at offset 678 or at
offset 702, both report that a breakpoint was added on line 20 (wrong in
both cases). However, if I set a breakpoint at offset 678, the debugger
WILL stop at 678. Unfortunately, it will also stop at 702. It's strange...
the debugger stops at to clearly distinct spots in the code, but reports
the exact same breakpoint... which it claims is on another line entirely.

I had been trying to work around this problem in the IDE I am developing,
but in light of this discover I don't think that will work. For now I will
most likely leave out breakpoints from my program entirely, leaving them
for the user to manage in the debug console.

I hope my reports help you track this down,

-- Nate

On Tue, 16 Aug 2005, Nathaniel J. Gaylinn wrote:

Just to help out a bit with a bug I reported:

It seems that when setting a breakpoint at a given character offset, the
breakpoint IS set correctly. What appears to be going wrong is the reporting
of WHERE the breakpoint was set.

So, for example, if I request a breakpoint at offset 64, OCaml will respond
that the breakpoint was created at offset 31. However, the program WILL break
at offset 64, despite the fact that it always reports the wrong line number
when queried.

Hopefully this will help you narrow down the problem!

-- Nate

@vicuna
Copy link
Author

vicuna commented Aug 26, 2005

Comment author: administrator

see also #3732, #3759, #3766

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant