StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6705876
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-15T10:46:57.817
FavoriteCount
0
LastActivityDate
2011-07-15T10:46:57.817
LastEditDate
LastEditorUserId
0
OwnerUserId
846252
ParentId
6702571
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I don't fully understand your question but all of the options for 'b' in the perl debugger can be viewed with 'h b': <pre><code>DB<3> h b b Sets breakpoint on current line) b [line] [condition] Set breakpoint; line defaults to the current execution line; condition breaks if it evaluates to true, defaults to '1'. b subname [condition] Set breakpoint at first line of subroutine. b $var Set breakpoint at first line of subroutine referenced by $var. b load filename Set breakpoint on 'require'ing the given file. b postpone subname [condition] Set breakpoint at first line of subroutine after it is compiled. b compile subname Stop after the subroutine is compiled. </code></pre> There doesn't appear to be a 'one usage for all cases' pattern. In my experience you can: <ul> <li>step through the debugger a few statements until the module(s) you are interested in are loaded</li> <li>'use' the module you want to set the break point in</li> </ul> Once your module of interest is loaded you can use the 'b [subname]' pattern. Don't forget that you might need to fully qualify the sub name with the package name: <pre><code> DB<5> use JSON; DB<6> b JSON::import DB<7> JSON->import JSON::import(/opt/xt/xt-perl/lib/site_perl/5.12.4/JSON.pm:78): 78: my $pkg = shift; auto(-1) DB<<8>> v 75 76 77 sub import { 78==>b my $pkg = shift; 79: my @what_to_export; 80: my $no_export; 81 82: for my $tag (@_) { 83: if ($tag eq '-support_by_pp') { 84: if (!$_ALLOW_UNSUPPORTED++) { </code></pre> You could also <ul> <li>add "$DB::single=1;" in your source code (don't forget to remove it when your done though!)</li> </ul> and just 'c' to continue through the debugger until you hot that line in your code. Having to add and remove special markers in your source goes against the general principle of debugging but is sometimes a useful way of stopping easily at somewhere difficult, or slow, to reach stepping through the debugger.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat's the all fit way to break on file:line in the Perl debugger?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USChisel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.