Bug 5822 - Report invalid vs unavailable differently in core files
Summary: Report invalid vs unavailable differently in core files
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Phil Muldoon
URL:
Keywords:
Depends on:
Blocks: 5819
  Show dependency treegraph
 
Reported: 2008-03-03 19:55 UTC by Andrew Cagney
Modified: 2008-03-03 19:55 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2008-03-03 19:55:11 UTC
Consider a process with the address map:

0x1000 - 0x2000 /bin/ls
0xa000 - 0xb000 /usr/lib/libc.so
0xf000 - 0xffff [stack]

(ok its a little simple :-) and the core command:

  $ fcore -segments=stack

then, when examining the program there are two possible errors:

- the address is invalid because it doesn't fall within any of the above valid
addresses; e.g., print *(void*)0

- the address's value is unavailable because it wasn't written to the core file;
e.g., print environ (which would be in the heap)

the two cases should be differentiated with differing error messages.