Sure! Lemme just figure out how to make MinGW do that
Sure! Lemme just figure out how to make MinGW do that
You need gdb for this.Originally Posted by OnionRingOfDoom
C:\...\gdb app.exe
(gdb) run
<program crashes>
(gdb) bt
<backtrace>
(gdb) quit
Ok, lemme install this doohicky
Last edited by OnionRingOfDoom; 26th January 2006 at 20:38.
#0 0x10047934 in _size_of_stack_reserve__ ()
Cannot access memory at address 0x200000
that's what it gave me.
Only this? Maybe there was something more?Originally Posted by OnionRingOfDoom
If there is no main() in the backtrace, it might mean that there is some problem with libraries. Make sure you have "QT += network" in your .pro file.
Yep, QT += network" is in the .pro file.Originally Posted by jacek
If you want, I can upload the entire source somewhere, and you can see what it does on your end?
According to Murphy's law it will work on my systemOriginally Posted by OnionRingOfDoom
Does your program crash before it starts?
Nope, I have to start up the program in server mode, then start another instance of the program in client mode. As soon as I click OK on the connect dialog box after typing in the propper port and IP, the server indicates that the client has sucessfully connected, and then the client crashes.Originally Posted by jacek
Last edited by OnionRingOfDoom; 26th January 2006 at 21:35.
And there was only one entry in the backtrace? Did you compile your application in debug mode?Originally Posted by OnionRingOfDoom
Anyway, you try to read data from the socket before they arrive --- you must wait for readyRead() signal.
...How do I compile it in debug mode?
Add "CONFIG += debug" to your .pro file (and remove "release" if it's there).Originally Posted by OnionRingOfDoom
Ok so I changed the connection to do the readSpeed() function whenever readyRead() was emitted. However, now nothing happens when the client connects.
I also added a new connection at the end of the acceptConnection() function, which is as follows: connect(slider, SIGNAL(valueChanged(int)), this, SLOT(sendSpeed()));
so now, whenever I move the slider (and it outputs valueChanged signal), it crashes.
Last edited by OnionRingOfDoom; 26th January 2006 at 22:08.
After further fiddling, it seems that it's not the server's writing to the IO device that's the problem, it's the client's reading from the IO device that's causing the crash. Moving the slider thus causes the server to write data, and the client tries to read it or something, but crashes.
Does it crash if you change MainWindow::readSpeed() to:?Qt Code:
void MainWindow::readSpeed() { label->setNum(0); }To copy to clipboard, switch view to plain text mode
Did you try to generate that backtrace again?
Bookmarks