Opened 6 years ago

Last modified 15 months ago

#1826 new feature request

unable to list source for <exception thrown> should never occur

Reported by: guest Owned by:
Priority: normal Milestone:
Component: GHCi Version: 6.8.1
Keywords: Cc: iampure@…
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Difficulty: Easy (less than 1 hour)
Test Case: Blocked By:
Blocking: Related Tickets:

Description

I get the very unhelpful "unable to list source for <exception thrown>". I would like to get one of the following two responses, the last one is best.

Do this and that to list source
We currently cannot list source, because you did and that Do you still want to list source                although it requires to do that and that(for example automatically recompiling and reexecuting it until the same program point) [Y/n]?

Change History (16)

comment:1 Changed 6 years ago by guest

  • Cc iampure@… added

comment:2 Changed 6 years ago by simonmar

  • Milestone set to 6.8 branch

Ok, would this help?

Source location of exception is unknown, try `:back` and then `:list`.

or if you're not using :trace it would suggest doing that first.

comment:3 Changed 6 years ago by simonmar

  • Architecture changed from Unknown to Multiple
  • Component changed from Compiler to GHCi
  • Milestone changed from 6.8 branch to 6.8.3
  • Operating System changed from Unknown to Multiple

comment:4 Changed 6 years ago by simonmar

  • Difficulty changed from Unknown to Easy (1 hr)

comment:5 Changed 6 years ago by igloo

I've improved the error, but I'm not sure how to tell if we are running with :trace; is there an easy way?

comment:6 Changed 6 years ago by simonmar

Perhaps by checking whether the history is empty?

comment:7 Changed 6 years ago by igloo

  • Resolution set to fixed
  • Status changed from new to closed

Thanks; now fixed in 6.8 branch and HEAD, modulo #2054.

comment:8 Changed 6 years ago by igloo

  • Priority changed from normal to low
  • Resolution fixed deleted
  • Status changed from closed to reopened

Ah, so actually the :trace detection doesn't work if you :trace an already evaluated CAF, so sometimes the error will tell you to use :trace when you already are doing.

comment:9 Changed 6 years ago by igloo

  • Milestone changed from 6.8.3 to 6.10 branch

comment:10 Changed 6 years ago by simonmar

  • Architecture changed from Multiple to Unknown/Multiple

comment:11 Changed 6 years ago by simonmar

  • Operating System changed from Multiple to Unknown/Multiple

comment:12 Changed 5 years ago by igloo

  • Milestone changed from 6.10 branch to 6.12 branch

comment:13 Changed 4 years ago by simonmar

  • Difficulty changed from Easy (1 hr) to Easy (less than 1 hour)

comment:14 Changed 4 years ago by igloo

  • Milestone changed from 6.12 branch to 6.12.3

comment:15 Changed 4 years ago by igloo

  • Milestone changed from 6.12.3 to _|_
  • Priority changed from low to normal
  • Type of failure set to None/Unknown

comment:16 Changed 15 months ago by morabbin

Bump; what's the state of :trace detection now?

Note: See TracTickets for help on using tickets.