Just a couple of notes as a I retrace my understanding of this behavior. Here's some relevant text from perlref, section "Making References":
*foo{THING} returns undef if that particular THING hasn’t been used yet, except in the case of scalars. *foo{SCALAR} returns a reference to an anonymous scalar if $foo hasn’t been used yet. This might change in a future release.
One consequence of this is that at the symbol-table level, the following two packages are indistinguishable: 
{
    package Foo;
    our $x = undef;
    our @x = qw( alpha beta gamma );
}

{
    package Bar;
    our @x = qw( alpha beta gamma );
}

[download]
... which I may demonstrate with some code of my own, once I come up with something convincing that navigates the sea of casting and dereferencing that is the Perl symbol table. So while I think I appreciate what broquaint is trying to get across, I don't think the above post addresses the "spirit" of the OP. I would agree with the as-yet unmade statement that Devel::Symdump is doing its best, but the underlying data is ambiguous, and so are the values returned from the module.

Indeed, such is the nature of globs. Thanks, bpphillips, for starting this conversation.

Update: Here's a more concrete example, following the package definitions above: 

use strict;
use warnings;
use Data::Dumper;

warn "Perl version is '$]'\n";

{
    package Foo;
    our $x = undef;
    our @x = qw( alpha beta gamma );
}

{
    package Bar;
    our @x = qw( alpha beta gamma );
}

symdump('Foo','x');
symdump('Bar','x');

sub symdump {
    my ($pkg, $symbol) = @_;
    local(*SYM) = do {
        no strict 'refs';
        ${*{"$pkg\::"}}{$symbol};
    };
    foreach my $slot (qw( SCALAR ARRAY HASH )) {
        warn Data::Dumper->Dump( [*SYM{$slot}], [ "\${ \*{\$$pkg\::{$s
+ymbol}}{$slot} }" ] );
    }
}

__END__

Perl version is '5.008005'
${ *{$Foo::{x}}{SCALAR} } = \undef;
${ *{$Foo::{x}}{ARRAY} } = [
                             'alpha',
                             'beta',
                             'gamma'
                           ];
${ *{$Foo::{x}}{HASH} } = undef;
${ *{$Bar::{x}}{SCALAR} } = \undef;
${ *{$Bar::{x}}{ARRAY} } = [
                             'alpha',
                             'beta',
                             'gamma'
                           ];
${ *{$Bar::{x}}{HASH} } = undef;

[download]

In reply to Re^2: Devel::Symdump and symbol table woes by trammell
in thread Devel::Symdump and symbol table woes by bpphillips

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.