New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault with "thread" version of perl 5.8.3 #7218
Comments
From nog@MPA-Garching.MPG.DECreated by nog@mpa-garching.mpg.deMy name is Norbert Gruener. I am owner and maintainer of the Perl XS Recently I got two reports that my module is crashing under "Debian "perl, v5.8.3 built for i686-linux-thread-multi" then my module crashes. Whereas if I am using the version without "perl, v5.8.3 built for i686-linux" everything is working and no segmentation fault shows up. I don't know if this is of any interest for you or if you are saying If you are interested in this case I can supply you with details of Cheers, Norbert Perl Info
|
From @lizmatAt 11:18 +0000 4/8/04, Norbert Gruener (via RT) wrote:
Either that or build in some code so that the module refuses to This is definitely _not_ enough to go on. Does this only happen on Debian. Are other distributions unaffected Liz |
The RT System itself - Status changed from 'new' to 'open' |
From @iabynOn Thu, Apr 08, 2004 at 11:18:49AM -0000, Norbert Gruener wrote:
Questions: Is the fault reproducable? Dave. -- |
From nog@MPA-Garching.MPG.DEHi Liz, On Sun, Apr 11 2004, Elizabeth Mattijsen via RT wrote:
Yes, I am aware of that :-)
In the meantime I could reproduce that problem at my office. We are There are more details in the answer to Dave. Norbert |
From nog@MPA-Garching.MPG.DEHi Dave, On Sun, Apr 11 2004, Dave Mitchell via RT wrote:
Yes, it is.
I am not sure. At least I was not able to come up with a tiny test
To be honestly, I have no experience with "threading" that I could So, let me give you some more details where the AFS API crashes. The And these are the test outputs As you can see, the call for "longjmp" is crashing in "threaded". And Cheers, Norbert |
From nog@MPA-Garching.MPG.DEstatic jmp_buf jmp_tmp; afs_int32 savecontext(ep, savearea, sp) printf("LWP2-SaveContext-DEBUG-1 \n"); printf("LWP2-SaveContext-DEBUG-2 \n"); printf("LWP2-SaveContext-DEBUG-4 \n"); |
From @lizmatAt 07:56 +0200 4/13/04, Norbert Gruener wrote:
Have you tried running this under valgrind? ( http://valgrind.kde.org ) Maybe that will provide some clues. Liz |
From @lizmatAt 15:42 +0200 4/13/04, Norbert Gruener wrote:
Well, maybe: ==32696== I understand from your problem description that you only used a Liz |
From nick@ing-simmons.netNorbert Gruener <nog@MPA-Garching.MPG.DE> writes:
It may well be that those libraries are "thread aware" and if linked
Perl uses longjmp too so that should not itself be a problem. Enabling threads in perl does two things (mainly) as far as XS code 1. Changes #define-s so that perl variables are accessed via 2. Links with special "threading" versions of system libraries.
|
From nog@MPA-Garching.MPG.DEOn Tue, Apr 13 2004, Elizabeth Mattijsen wrote:
Not yet.
OK, here it comes ... I have attached the output. After the line "LWP2-SaveContext-DEBUG-5-5" normally the test crashes. Norbert |
From nog@MPA-Garching.MPG.DE~/AFS.short/src>/tmp/local/bin/valgrind /tmp/local/bin/perl ../examples/constructor ==32696== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. |
From nick@ing-simmons.netNorbert Gruener <nog@MPA-Garching.MPG.DE> writes:
That is the issue - is OpenAFS doing threading?
Prove it works okay with non-threaded perl?
|
From nog@MPA-Garching.MPG.DEOn Wed, Apr 14 2004, Nick Ing-Simmons wrote:
Ooops ^^^^^^^^^^^ :-)
I checked the sparse documentation. Yes, OpenAFS is doing threading
I haven't found any pointer how to do that.
I don't think so in this case. The XS code makes an OpenAFS
Do you think it is possible that the coincidence of "pthread" in Perl
Well, I am a little bit reluctant to call it "proven" but the AFS XS Norbert |
From nog@MPA-Garching.MPG.DEHi Nick, On Tue, Apr 13 2004, Nick Ing-Simmons wrote:
this makes complete sense to me. But what is the conclusion then? Is At the moment I don't have any idea which direction I should go. Norbert |
From nog@MPA-Garching.MPG.DEHi Liz, On Tue, Apr 13 2004, Elizabeth Mattijsen wrote:
That is correct.
I really don't know. The only thing which makes me a little bit sceptical is the output of I have attached the output of the equivalent OpenAFS command. The So, at the moment I am absolutely clueless :-(( Norbert |
From nog@MPA-Garching.MPG.DE~/AFS.short>/tmp/local/bin/valgrind /tmp/openafs/sbin/vos exa home nog |
From nog@MPA-Garching.MPG.DEHi Nick, hi Dave, hi Liz, On Wed, Apr 14 2004, Norbert Gruener wrote:
this statement brought me on the right track. Thank you Nick !!! :-) The problem is the "pthread" version of longjmp in connection with So, whoever is allowed to modify the status of that request, please close request # 28369 This is not a Perl problem. I want to thank all of you for your patience and your assistance. You Thank you, Norbert |
@Tux - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#28369 (status was 'resolved')
Searchable as RT28369$
The text was updated successfully, but these errors were encountered: