Qt program crash why?
-
@ChrisW67 thanks;
"sudo devmem2 0x80000000" gives value in terminal is 0x0 but in qt code its value is 2147483648 which I stated above in previous post.
thankswrote on 4 Jan 2022, 11:34 last edited by KroMignon 1 Apr 2022, 11:35@Wasee said in Qt program crash why?:
"sudo devmem2 0x80000000" gives value in terminal is 0x0 but in qt code its value is 2147483648 which I stated above in previous post.
I would try to do thing step by step.
First ensure theQProcess
call is working, and then try to parse result.
I am not sure that the way you are usingQProcess
withsudo
is the best way.
I would do it this way:QProcess proc; QStringList args; proc.setProcessChannelMode(QProcess::MergedChannels); args << "devmem2" << "0x80000000"; proc.start("sudo", args); if(proc.waitForFinished()) { QString result = QString(proc.readAll()); qDebug() << "devmem2 done and returning" << result; } else qDebug() << "failled to start devmem2";
NOTE: to add code in your post, please use
</>
button, this made it easier to read -
wrote on 5 Jan 2022, 05:55 last edited by
@KroMignon thanks for your help:
I coded as you suggested my output is:
devmem2 done and returning: "/dev/mem opened. Memory mapped at address 0xb6f90000. Value at address 0x80000000 (0xb6f90000): 0x0 "
This is very long string I just needed value 0x0 not whole string.Thanks your help!
-
@KroMignon thanks for your help:
I coded as you suggested my output is:
devmem2 done and returning: "/dev/mem opened. Memory mapped at address 0xb6f90000. Value at address 0x80000000 (0xb6f90000): 0x0 "
This is very long string I just needed value 0x0 not whole string.Thanks your help!
@Wasee said in Qt program crash why?:
This is very long string I just needed value 0x0 not whole string
Then simply split the string using ':' character and take the second part, see https://doc.qt.io/qt-5/qstring.html#split-5.
This of course assumes that there is only one ':' in the result string. If not, you will need to use split() with regular expression. -
@KroMignon thanks for your help:
I coded as you suggested my output is:
devmem2 done and returning: "/dev/mem opened. Memory mapped at address 0xb6f90000. Value at address 0x80000000 (0xb6f90000): 0x0 "
This is very long string I just needed value 0x0 not whole string.Thanks your help!
wrote on 5 Jan 2022, 07:01 last edited by KroMignon 1 May 2022, 07:18@Wasee said in Qt program crash why?:
I coded as you suggested my output is:
devmem2 done and returning: "/dev/mem opened. Memory mapped at address 0xb6f90000. Value at address 0x80000000 (0xb6f90000): 0x0 "
This is very long string I just needed value 0x0 not whole string.
Thanks your help!That is only a simple string manipulation.
The easiest way is to search for the first occurence of0x
by starting from the end and then parse this string part.
Take a look a QString documentation, you should be able to find this yourself. -
wrote on 5 Jan 2022, 09:22 last edited by
@KroMignon Hi;
I added following lines in code:QProcess proc; QStringList args; proc.setProcessChannelMode(QProcess::MergedChannels); args << "devmem2" << "0x80000000"; proc.start("sudo", args); if(proc.waitForFinished()) { QString result = QString(proc.readAll()); qDebug() << "devmem2 done and returning" << result; args = result.split(QRegExp("\\:")); args.removeFirst(); qDebug()<<"Truncated:"<<args; } else qDebug() << "failled to start devmem2";
Its giving value ("0x0") I need it without bracket 0x0.
Thanks -
@KroMignon Hi;
I added following lines in code:QProcess proc; QStringList args; proc.setProcessChannelMode(QProcess::MergedChannels); args << "devmem2" << "0x80000000"; proc.start("sudo", args); if(proc.waitForFinished()) { QString result = QString(proc.readAll()); qDebug() << "devmem2 done and returning" << result; args = result.split(QRegExp("\\:")); args.removeFirst(); qDebug()<<"Truncated:"<<args; } else qDebug() << "failled to start devmem2";
Its giving value ("0x0") I need it without bracket 0x0.
Thankswrote on 5 Jan 2022, 09:31 last edited by@Wasee said in Qt program crash why?:
Its giving value ("0x0") I need it without bracket 0x0.
ThanksWhy doing so complicated?
Have your readQString
documentation?
You should foundQString::lastIndexOf()
QString result = QString(proc.readAll()); QString value = result.mid(result.lastIndexOf("0x")); qDebug()<<"Truncated:"<<value;
-
wrote on 7 Jan 2022, 06:50 last edited by
@KroMignon Hi;
Truncated: "0x1
"
Why its not "0x0"? Last quotation mark is on next line. -
@KroMignon Hi;
Truncated: "0x1
"
Why its not "0x0"? Last quotation mark is on next line.wrote on 7 Jan 2022, 07:09 last edited by KroMignon 1 Jul 2022, 07:10@Wasee said in Qt program crash why?:
Why its not "0x0"? Last quotation mark is on next line.
perhaps because the return value has changed?
Did you display QProcess output to compare with result?QString result = QString(proc.readAll()); QString value = result.mid(result.lastIndexOf("0x")); qDebug()<<"Returned value:"<<result ; qDebug()<<"Truncated:"<<value;
Note: it seems that returned string contains also a carriage return byte, you could remove this by using
QString::simplified()
(cf. https://doc.qt.io/qt-5/qstring.html#simplified) -
wrote on 7 Jan 2022, 07:20 last edited by
@KroMignon Hi;
qDebug()<<"Returned value:"<<result ;
Returned value:"/dev/mem opened.
Memory mapped at address 0xb6f90000.
Value at address 0x80000000 (0xb6f90000): 0x1
"thanks
-
wrote on 7 Jan 2022, 10:41 last edited by
Hi everyone;
I code following and getting ASSERT: "count > 0" error. The program has unexpectedly finished. Why?QProcess proc; QStringList args; proc.setProcessChannelMode(QProcess::MergedChannels); args << "devmem2" << "0x80000000"; proc.start("sudo", args); if(proc.waitForFinished()) { QString result = QString(proc.readAll()); qDebug() << "devmem2 done and returning" << result; QString dds_en = result.mid(result.lastIndexOf("0x")); QString test=dds_en.simplified(); qDebug()<<"Detected:"<<dds_en; if(test="0x0"){ QProcess p1 ; p1.startDetached("/bin/bash", QStringList() << "-c" << "/home/ijaz/bashScripts/script1.sh"); QProcess Rx_CF; Rx_CF.start("cat /sys/bus/iio/devices/iio:device1/out_altvoltage0_RX_LO_frequency"); Rx_CF.waitForFinished(-1); // will wait forever until finished Rx_CF_read =Rx_CF.readAllStandardOutput(); qDebug() << "RX LO"<<Rx_CF_read; } if(test="0x1"){ ac=Rx_CF_read; QFile f("/sys/bus/iio/devices/iio:device1/out_altvoltage1_TX_LO_frequency"); if (f.open(QIODevice::WriteOnly)) { qint64 count = f.write(ac.toUtf8()); Q_ASSERT(count > 0); f.close(); qDebug()<<"QFile Run"<<count; } } } else qDebug() << "failled to start devmem2";
Thanks
-
Hi everyone;
I code following and getting ASSERT: "count > 0" error. The program has unexpectedly finished. Why?QProcess proc; QStringList args; proc.setProcessChannelMode(QProcess::MergedChannels); args << "devmem2" << "0x80000000"; proc.start("sudo", args); if(proc.waitForFinished()) { QString result = QString(proc.readAll()); qDebug() << "devmem2 done and returning" << result; QString dds_en = result.mid(result.lastIndexOf("0x")); QString test=dds_en.simplified(); qDebug()<<"Detected:"<<dds_en; if(test="0x0"){ QProcess p1 ; p1.startDetached("/bin/bash", QStringList() << "-c" << "/home/ijaz/bashScripts/script1.sh"); QProcess Rx_CF; Rx_CF.start("cat /sys/bus/iio/devices/iio:device1/out_altvoltage0_RX_LO_frequency"); Rx_CF.waitForFinished(-1); // will wait forever until finished Rx_CF_read =Rx_CF.readAllStandardOutput(); qDebug() << "RX LO"<<Rx_CF_read; } if(test="0x1"){ ac=Rx_CF_read; QFile f("/sys/bus/iio/devices/iio:device1/out_altvoltage1_TX_LO_frequency"); if (f.open(QIODevice::WriteOnly)) { qint64 count = f.write(ac.toUtf8()); Q_ASSERT(count > 0); f.close(); qDebug()<<"QFile Run"<<count; } } } else qDebug() << "failled to start devmem2";
Thanks
wrote on 7 Jan 2022, 10:52 last edited byThis post is deleted! -
wrote on 7 Jan 2022, 10:56 last edited by
@KroMignon Hi;
Rx_CF_read and ac are define in header file as QString. Rx_CF_read is RX LO value which is reading from device continuously.
Thanks -
Hi everyone;
I code following and getting ASSERT: "count > 0" error. The program has unexpectedly finished. Why?QProcess proc; QStringList args; proc.setProcessChannelMode(QProcess::MergedChannels); args << "devmem2" << "0x80000000"; proc.start("sudo", args); if(proc.waitForFinished()) { QString result = QString(proc.readAll()); qDebug() << "devmem2 done and returning" << result; QString dds_en = result.mid(result.lastIndexOf("0x")); QString test=dds_en.simplified(); qDebug()<<"Detected:"<<dds_en; if(test="0x0"){ QProcess p1 ; p1.startDetached("/bin/bash", QStringList() << "-c" << "/home/ijaz/bashScripts/script1.sh"); QProcess Rx_CF; Rx_CF.start("cat /sys/bus/iio/devices/iio:device1/out_altvoltage0_RX_LO_frequency"); Rx_CF.waitForFinished(-1); // will wait forever until finished Rx_CF_read =Rx_CF.readAllStandardOutput(); qDebug() << "RX LO"<<Rx_CF_read; } if(test="0x1"){ ac=Rx_CF_read; QFile f("/sys/bus/iio/devices/iio:device1/out_altvoltage1_TX_LO_frequency"); if (f.open(QIODevice::WriteOnly)) { qint64 count = f.write(ac.toUtf8()); Q_ASSERT(count > 0); f.close(); qDebug()<<"QFile Run"<<count; } } } else qDebug() << "failled to start devmem2";
Thanks
-
@KroMignon Hi;
Rx_CF_read and ac are define in header file as QString. Rx_CF_read is RX LO value which is reading from device continuously.
Thankswrote on 7 Jan 2022, 10:59 last edited by KroMignon 1 Jul 2022, 11:02@Wasee said in Qt program crash why?:
Rx_CF_read and ac are define in header file as QString. Rx_CF_read is RX LO value which is reading from device continuously.
ThanksAre you sure
Rx_CF_read
contains a valid value?
Why are you using an extra copy toac
?
Are you are writing into a linux virtual file, I don't think it supports UTF-8, but should be latin1.I would change to code as follow, to understand what's happening:
if(test=="0x1"){ QFile f("/sys/bus/iio/devices/iio:device1/out_altvoltage1_TX_LO_frequency"); qDebug() << "Try to set out_altvoltage1_TX_LO_frequency to" << Rx_CF_read; if (f.open(QIODevice::WriteOnly)) { qint64 count = f.write(Rx_CF_read.toLatin1()); Q_ASSERT(count > 0); f.close(); qDebug()<<"QFile Run"<<count; } }
EDIT ==>
=
is to set a value, to compare use==
!!!!
if(test="0x0")
==>if(test=="0x0")
if(test="0x1")
==>if(test=="0x1")
-
wrote on 7 Jan 2022, 11:12 last edited by
@KroMignon Hi;
I change the code but getting ASSERT: "count > 0" error. The program has unexpectedly finished.Try to set out_altvoltage1_TX_LO_frequency to ""
Thanks -
@KroMignon Hi;
I change the code but getting ASSERT: "count > 0" error. The program has unexpectedly finished.Try to set out_altvoltage1_TX_LO_frequency to ""
Thankswrote on 7 Jan 2022, 11:40 last edited by@Wasee said in Qt program crash why?:
Try to set out_altvoltage1_TX_LO_frequency to ""
According to the debug message, you are writing an empty string.
So why shouldcount
be greater than 0?Have you also change the
if
statements?
if(test="0x1")
will changetest
to "0x1" and not comparetest
with string "0x1"In C/C++ the comparison operator is
==
-
wrote on 7 Jan 2022, 12:07 last edited by
@KroMignon Hi;
If statement is working for if(test=="0x0") but not for if(test=="0x1"). Even test value in terminal is "0x1". at this point not entertaining to this if condition.
thanks -
@KroMignon Hi;
If statement is working for if(test=="0x0") but not for if(test=="0x1"). Even test value in terminal is "0x1". at this point not entertaining to this if condition.
thankswrote on 7 Jan 2022, 13:14 last edited by JonB 1 Jul 2022, 13:15@Wasee
You really need to use a debugger, or even just debug statements, to find out for yourself things like what is in a variable, how should asking here help, other people don't know whether you get0x0
versus0x1
or whatever back, you are best placed to discover that.... -
@KroMignon Hi;
If statement is working for if(test=="0x0") but not for if(test=="0x1"). Even test value in terminal is "0x1". at this point not entertaining to this if condition.
thankswrote on 7 Jan 2022, 14:06 last edited by KroMignon 1 Jul 2022, 14:07@Wasee said in Qt program crash why?:
If statement is working for if(test=="0x0") but not for if(test=="0x1"). Even test value in terminal is "0x1". at this point not entertaining to this if condition.
thanksI don't want to hurt you, but it looks like you are not really understanding what you are doing.
Why you don't use the debugger to set break points and running this part of code step by step to see what is really happening, as @JonB suggest to you?
29/38