From: Ben C. <Be...@cl...> - 2004-07-05 10:15:26
|
Tim, Very glad to hear this. I has this once my self a while back. Took me ages to work it out :) Glad it's all working. Ben Tim Wuyts wrote: > Ben, > > Thx for the tip. The mysql version on the machine running perfparse was > indeed different (older: 3.23!) from the server (4.0.17). I upgraded the > client to 4.0.20, and at the same time (mysql wouldn't compile otherwise) > upgraded to the latest g++. > > This solved the problem. > > Thanks! > > Tim. > > >>-----Original Message----- >>From: per...@li... >>[mailto:per...@li...] On >>Behalf Of Ben Clewett >>Sent: maandag 5 juli 2004 9:46 >>To: Tim Wuyts >>Cc: per...@li... >>Subject: Re: [Perfparse-users] Segmentation fault running perfparse >> >>Tim, >> >>Oh dear, I've not seen this. >> >>You are probably not the only person, just the only one who has come >>reported this problem. >> >>Can I ask what system you are using, version of MySQL, OS version etc. >> >>My suspicion is that your version of the MySQL client libs is >>different >>from the MySQL server. Possibly you have two versions of the client >>libs in different directories. Can you check this first of all? >> >>You are a lot closer to the problem than us. Since it works >>perfectly >>with us. If there is anything else you can do to find the exact line >>which causes the failure, it would be of great interest. >> >>Regards, >> >>Ben Clewett. >> >> >>Tim Wuyts wrote: >> >>>Greetings Programs! >>> >>>I encountered a problem running perfparse (v0.10 and >> >>v0.0.11): whenever I >> >>>run it to parse the log file, it gives me a segmentation >> >>fault. As long as >> >>>you don't request to parse the logfile, e.g. by using --help or >>>--show-config, it runs fine. >>> >>>So I dug into the code and found that the call to the mysql >> >>library to >> >>>connect to the db (in common.c) causes the segmentation >> >>fault. I have no >> >>>clue as to why. I compiled a small program that connects to >> >>the database >> >>>using the same call with the same parameters, and that >> >>works perfectly. >> >>>I circumvented the problem by using mysql_connect and >> >>mysql_select_db >> >>>instead of mysql_real_connect. This works fine! The only >> >>problem with this >> >>>construct is that according to the mysql manual, the >> >>mysql_connect function >> >>>is deprecated. >>> >>>A few questions about this: >>>- Am I the only one experiencing this problem? >>>- What more info do you (the developers) need to look into >> >>this? (providing >> >>>you'd want to :) ) >>> >>>Regards, >>>Tim. >>> >>> >>> >>>------------------------------------------------------- >>>This SF.Net email sponsored by Black Hat Briefings & Training. >>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>>digital self defense, top technical experts, no vendor pitches, >>>unmatched networking opportunities. Visit www.blackhat.com >>>_______________________________________________ >>>Perfparse-users mailing list >>>Per...@li... >>>https://lists.sourceforge.net/lists/listinfo/perfparse-users >>> >> >> >> >>------------------------------------------------------- >>This SF.Net email sponsored by Black Hat Briefings & Training. >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>digital self defense, top technical experts, no vendor pitches, >>unmatched networking opportunities. Visit www.blackhat.com >>_______________________________________________ >>Perfparse-users mailing list >>Per...@li... >>https://lists.sourceforge.net/lists/listinfo/perfparse-users >> >> > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users > |