Opened 9 years ago

Last modified 21 months ago

#3000 new feature request

:break command should recognize also nonexported top level symbols in qualified IDs

Reported by: phercek Owned by:
Priority: lowest Milestone:
Component: GHCi Version: 6.10.1
Keywords: debugger Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:

Description

When a breakpoint is defined for a qualified function name ( ( conid . )+ varid ). Then the name should be found even when it is not exported (i.e. when varid is not in the export list).
The qualification ensures no ambiguity can happen so it should be allowed since it is line number independent which means breakpoint definitions sourced with ":." would be more robust against code modifications.

Change History (14)

comment:1 Changed 9 years ago by phercek

Actually it would be cool if function names of the form ( conid . )* ( varid . )* varid could be recognized too.
The identifer can have a sequence of varids at the end. The idea is to identify a function which is defined in a where clause (or even a let clause (the first let function with given name)).
E.g. for this source file:

fn s = 'a' : add s
  where add = (++"z")

it could look like :break Main.fn.add and it would be tha same as :break 2 (breakpoint on 'add').

comment:2 Changed 9 years ago by igloo

difficulty: Unknown
Milestone: 6.12 branch

comment:3 Changed 7 years ago by igloo

Milestone: 6.12 branch6.12.3

comment:4 Changed 7 years ago by igloo

Milestone: 6.12.36.14.1
Priority: normallow

comment:5 Changed 7 years ago by igloo

Milestone: 7.0.17.0.2

comment:6 Changed 7 years ago by igloo

Milestone: 7.0.27.2.1

comment:7 Changed 6 years ago by igloo

Milestone: 7.2.17.4.1

comment:8 Changed 6 years ago by igloo

Milestone: 7.4.17.6.1
Priority: lowlowest

comment:9 Changed 5 years ago by igloo

Milestone: 7.6.17.6.2

comment:10 Changed 3 years ago by thoughtpolice

Milestone: 7.6.27.10.1

Moving to 7.10.1.

comment:11 Changed 3 years ago by thoughtpolice

Milestone: 7.10.17.12.1

Moving to 7.12.1 milestone; if you feel this is an error and should be addressed sooner, please move it back to the 7.10.1 milestone.

comment:12 Changed 3 years ago by thoughtpolice

Moving to 7.12.1 milestone; if you feel this is an error and should be addressed sooner, please move it back to the 7.10.1 milestone.

comment:13 Changed 2 years ago by thoughtpolice

Milestone: 7.12.18.0.1

Milestone renamed

comment:14 Changed 21 months ago by thomie

Milestone: 8.0.1
Note: See TracTickets for help on using tickets.