ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In any event, when you get a segv the first thing to do is get figure out what line it happens on, either with printfs or (preferably) by gdb on the core file.
Originally posted by aluser Well, there seems to be a missing end brace to the while((subrow = ... loop. Did you miss pasting one before the mysql_close() calls?
yes sorry, forgot to paste that, the brace is not causing the segfault.
gdb doesn't ouput the line, it just tell's me that the error is in the main structure.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1210264160 (LWP 22394)]
0xb7faa592 in mysql_fetch_row () from /usr/lib/libmysqlclient.so.14
(gdb)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.