In the process of converting the .xs file to .c, lots of #line directives are introduced to allow the debugger to know the original source of the lines of code directly copied from the XS. It is possible that gdb is getting confused by these, or xsubpp may have got confused and emitted the wrong lines - you could try stripping out all the lines in the .c file starting #line and recompiling, which might allow gdb to do a better job.

First though it is worth confirming that your program is actually sitting in the infinite loop; you might consider printing a dot and then sleeping a second within the loop, or alternatively you could try to force an error for gdb to catch, for example by dereferencing a null pointer:

  char c = *(char*)0;
[download]

Hugo

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.