Yeah, I've seen this before, and it's very aggrivating. Probably has nothing to do with Inline, just C and perl. I'm guessing memory is just being initialized differently when you're running under the debugger. My only suggestion is to insert print statements and try again. =/
-Ken > -----Original Message----- > From: Ira Woodhead [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 27, 2006 9:39 AM > To: inline@perl.org > Subject: segfaults and the perl debugger > > Hi guys, > > I'm working with Inline C and I have a segmentation fault > that occurs in certain easily reproduced conditions. I can't > seem to get any more specific error messages (such as where > the damn thing is happening) because when I put it into the > debugger, it doesn't happen! Everything seems to work > correctly if I simply call with -d and hit 'c' for continue. > > Anyone seen this? Is this a clue to something? > > Cheers! > > > PS: Happens on both linux x86 and intel macosx. I'm not that > bothered yet so I won't paste the pages of version info I > know I should. I'm just idly wondering if someone's seen this > kind of thing before. > > -------------------------------------------------------- > > -------------------------------------------------------- > > > > ATTENTION: DO NOT read, copy or disseminate this > communication unless you are the intended addressee. This > message and any file(s) or attachment(s) transmitted with it > are confidential, intended only for the named recipient, and > may contain information that is a trade secret, proprietary, > protected by the attorney work product doctrine, subject to > the attorney-client privilege, or is otherwise protected > against unauthorized use or disclosure. This message and any > file(s) or attachment(s) transmitted with it are transmitted > based on a reasonable expectation of privacy consistent with > ABA Formal Opinion No. 99-413. If you have received this > communication in error, please e-mail the sender and notify > the sender immediately that you have received the > communication in error. Thank you. >
